Dr. Wallace’s Favorite Mental Models

Hindsight Bias

Learn it → Apply it → Save as Skill

Once you know how something turned out, it feels like you always knew it would. That feeling is reconstruction, not memory. After an outcome is known, people systematically overestimate how predictable it was beforehand, and often misremember their own prior estimate as having been closer to the truth than it actually was.

Why This Library Is Different

Learn it. Apply it. Save as Skill.

The Dr. Wallace’s Favorite Mental Models series is designed to turn useful ways of thinking into reusable tools. Each model gives you a fast visual overview, deeper interactive learning, practical application exercises and an AI-ready Markdown skill you can save for future use.

Instead of merely reading about mental models, you can gradually build your own AI skills library: a collection of portable reasoning skills that can help ChatGPT, Claude, Grok and other AI assistants apply the mental models you value.

30-Second Understanding
The past feels more predictable than it was.

Before an outcome is known, people express real uncertainty. Once it is known, that same uncertainty tends to disappear from memory, replaced by a confident sense that the result was obvious all along. The bias distorts judgments of other people's foresight and of our own past selves.

Core question: Am I judging this decision by what was knowable at the time it was made, or by what became obvious only after the outcome arrived?

Stated confidence, before versus after

Before outcome
~35%
Recalled after
~65%

Illustrative pattern: in Fischhoff and Beyth's original studies, people asked to recall the probability they had assigned before an event consistently "remembered" a higher number for outcomes that occurred. The exact shift varied by item; this bar shows the direction and rough scale of the effect, not a single quoted statistic.

Mental Model Compass

Use it whenever a decision is being judged after its outcome is already known.

The bias is most relevant anywhere a reviewer, judge, or the decision-maker themselves already knows how things turned out.

PostmortemsPrimary use case
BeginnerDifficulty
3 minUnderstand
10–30 minApply to a real review
PostmortemsPerformance reviewsMedical reviewLegal & negligence judgmentHistorical & strategic analysisForecasting
Model at a Glance

Outcome known → Memory reconstructs → Confidence rises → Uncertainty erased.

The bias is not a single error but a short chain of automatic steps that runs almost every time an outcome is reviewed.

01The outcome becomes known

A result arrives: a project fails, a patient's diagnosis is confirmed, a trade goes bad, an election is decided.

02Memory reconstructs itself

Recall of what was predicted or expected beforehand quietly shifts to align with what actually happened, without the person noticing the edit.

03Confidence in "having known" rises

The reconstructed memory feels like it was always there, producing a genuine, unearned sense of having foreseen the result.

04The original uncertainty is erased

The real ambiguity, competing signals, and limited information faced at decision time drop out of view entirely, making the past look obvious.

When Should I Use This?

Recognize the situation.

Open a use case to see what the bias changes in practice.

Incident review
Running a blameless postmortem after an outage

Once the root cause is known, it can feel obvious that "someone should have seen this coming." Reconstruct what the on-call engineer actually knew, monitored, and could plausibly have inferred at the time, not what is obvious now that the failure mode is understood.

Performance reviews
Judging a past decision a report made

A call that didn't pan out can look careless in hindsight even if it was reasonable given what was known then. Separate "the outcome was bad" from "the decision process was bad," and ask what information was actually available at decision time.

Medical review
Evaluating a missed or delayed diagnosis

A finding that is easy to spot on a scan once you know what to look for can seem like it should have been obvious the first time. Reviewers who already know the diagnosis rate the original images as more clearly abnormal than reviewers who do not, which is exactly the bias at work.

Legal & negligence
Assessing whether a risk was "foreseeable"

Negligence standards often turn on what a reasonable person could have foreseen beforehand, but jurors and reviewers who already know the harm occurred tend to rate it as having been more foreseeable than people who do not yet know the outcome. This gap can inflate liability judgments independent of the actual quality of the original decision.

Investing & trading
Reviewing a trade or investment post-mortem

A losing trade can look like an obvious mistake once the price move is known, even if the original thesis was reasonable given the information available. Separate process quality from outcome quality before drawing lessons, or you will overcorrect toward whatever the market happened to do.

Historical & strategic
Explaining why a war, election, or company failed

Historians and strategists writing after the fact tend to construct a tidy, seemingly inevitable chain of causes leading to the known result, a pattern Fischhoff called "creeping determinism." Real decision-makers at the time faced genuine branching possibilities that the tidy narrative erases.

Worked Example

Nixon's trip to China, a psychiatric ward, and a failed startup.

These are the model's own founding and applied research, and the pattern is directly from the published studies.

Nixon · original
Nixon · recalled
Malpractice · no harm
Malpractice · severe
Founders · predicted
Founders · recalled
STUDY 1Fischhoff & Beyth (1975) had people estimate the likelihood of various outcomes of Nixon's 1972 visits to China and the USSR before the trips. Afterward, participants recalled higher probabilities than they had actually given for outcomes that occurred, and lower probabilities for outcomes that did not.
METHODFischhoff's related "creeping determinism" procedure gave people a short case with several possible endings, told them which ending was true, then asked them to rate how likely each ending had seemed in advance. People consistently rated the true ending as having been more foreseeable, even reading the identical case facts as everyone else.
STUDY 2In malpractice-style vignette studies (LaBine & LaBine and related work), the same clinical decision was judged far more negligent, and the resulting harm far more foreseeable, when the vignette described a serious bad outcome than when it described no injury at all, even though the information available to the original decision-maker was identical.
STUDY 3Research on entrepreneurs found a large share of founders whose startups later failed had genuinely predicted success beforehand, but a noticeably smaller share recalled having held that optimistic belief once the failure was known.
WHO IT AFFECTEDThe pattern shows up in laypeople, clinicians, and legal decision-makers alike; expertise reduces it only modestly and does not eliminate it.
SOURCEFischhoff, B., & Beyth, R. (1975). "I knew it would happen": Remembered probabilities of once-future things. Organizational Behavior and Human Performance, 13(1), 1–16.
Do not conclude: "the outcome proves the original decision was wrong." The useful finding across all three settings is that knowing the outcome changes the judgment of foreseeability itself, independent of whatever the original decision quality actually was.
History & Accuracy

A 1975 paper that gave the "knew-it-all-along" feeling a name.

Expand for the distinction between the original research and the looser popular usage of the term.

What did Baruch Fischhoff actually show in 1975?

Fischhoff, working with Ruth Beyth, ran the first direct experiments demonstrating that people's memory of their own prior probability estimates shifts toward whatever outcome later occurred. He also introduced a separate "creeping determinism" method: give people a case with several possible endings, tell them which one was true, and they will rate that ending as having seemed more likely all along, even without needing to recall an actual prior estimate of their own.

Is hindsight bias the same thing as being "wise after the event"?

The everyday phrase describes the same experience, but Fischhoff's contribution was showing it is a systematic, measurable memory and judgment distortion rather than just a folk observation, and demonstrating specific conditions, such as outcome severity, that make it larger or smaller.

Does hindsight bias mean people are lying about what they knew?

Generally no. The core finding is that the distortion happens in genuine memory and judgment, not in deliberate self-serving deception. That is part of what makes it hard to correct: the person doing the judging usually believes their reconstructed certainty is accurate.

Common Mistakes

Knowing about the bias does not automatically cancel it out.

Judging a decision by its outcome alone

A good decision can still produce a bad outcome, and a bad decision can still get lucky. Evaluate the information and reasoning available at decision time, separately from how things turned out.

Trusting your own memory of "what you predicted"

People systematically misremember their own prior estimates once they know the outcome. Where possible, check a written prediction, ticket, or forecast made before the outcome, rather than relying on recall.

Assuming a bad outcome makes harm more foreseeable

Severity of the outcome measurably inflates judgments of foreseeability and negligence, independent of what information was actually available. A worse result is not itself evidence that the risk was clearer beforehand.

Building a tidy, inevitable-sounding narrative

Postmortems and historical accounts that read as a single obvious causal chain toward the known ending are usually smoothing over genuine uncertainty and competing possibilities that existed at the time.

Using "it was foreseeable" to blame instead of to improve

A blame-focused hindsight framing discourages honest reporting of near-misses and early warning signs, which are exactly what future prevention depends on.

Skipping the pre-outcome record entirely

Without a documented prediction, plan, or risk assessment made before the outcome, there is no reliable way to check whether the situation was actually as foreseeable as it now feels.

When Not to Use It

Some situations are not really about hindsight at all.

Use direct evidence when...

a written prediction, risk assessment, or warning genuinely exists from before the outcome. If the risk was actually flagged and ignored, that is a real accountability failure, not a hindsight-bias illusion, and should be named as one.

Use Base Rate Neglect instead when...

the core problem is that someone ignored how common an outcome is in general, rather than misjudging how predictable one specific past event was.

Use the Planning Fallacy instead when...

the issue is an overly optimistic forecast made before the fact, rather than a distorted memory of that forecast after the fact.

Counterpoint: "hindsight bias" can be misused to excuse genuine negligence. Distinguishing "this was truly unforeseeable at the time" from "this was flagged clearly and ignored" is the whole job of a fair review, and hindsight-bias language should never substitute for checking which one actually happened.
Combine It With

One model rarely does the whole job.

Try It Yourself

Build a Hindsight Bias review prompt.

This browser tool structures your thinking. It does not send your information anywhere or perform AI analysis.

Your AI-ready prompt

Complete the fields, then build your prompt.
Save as Skill

Turn this mental model into a reusable AI skill.

Save as Skill converts the model into portable Markdown instructions that teach an AI when and how to apply Hindsight Bias, what questions to ask, what evidence to seek, what mistakes to avoid, and how to structure its analysis.

Build your own Mental Models Skills Library

Save the skills you find useful and organize them into your own reusable library. The Markdown is intentionally model-neutral, so it can be used wherever an AI system accepts uploaded files, project knowledge, custom instructions, or reusable text context. Platform capabilities differ, so this is a portable skill file rather than a claim of one-click installation.

Go Deeper

For readers who want the nuance.

Is hindsight bias the same as outcome bias?

They are close relatives but not identical. Hindsight bias is about misremembering or misjudging how predictable an outcome was beforehand. Outcome bias is about judging the quality of a decision by how it turned out rather than by the information available when it was made. The two often occur together and reinforce each other in reviews.

Does expertise protect people from this bias?

Only partly. Studies of clinicians and legal decision-makers still find the effect, though its size can vary by domain and by how the review is structured. Expertise does not appear to eliminate it outright.

Can anything reliably reduce hindsight bias in a review?

The most consistent approach in the research is "consider the opposite": deliberately generating reasons the outcome might not have happened, or comparing against a documented prediction made before the outcome, rather than relying on recalled impressions of what was expected.