State a prediction before looking at the outcome
Commit to a prediction before the result is known to prevent the narrative from rewriting your memory of your forecast.
Why it works
Hindsight bias — the sense that you knew it all along — is driven partly by narrative construction: once an outcome is known, memory of the pre-outcome state is revised to match it. Writing down a prediction before the result is known creates an external record that resists this revision. It makes the gap between pre-outcome uncertainty and post-outcome apparent inevitability visible and measurable.
How to do it
- Before any event whose outcome matters to your learning, write your prediction with an explicit probability.
- Record the date.
- After the outcome is known, compare the prediction to what happened — without revising your memory of your thinking.
Evidence
Hindsight bias is among the most replicated findings in cognitive psychology. Fischhoff’s original research showed that people consistently believe they would have known the outcome before it happened. Written pre-outcome predictions provide the only reliable corrective. (observational)
Sources
- Fischhoff (1975), "Hindsight ≠ Foresight," Journal of Experimental Psychology
Common mistake
Recording the prediction ambiguously so it can be read as correct regardless of outcome — a prediction must specify a direction and a probability to be checkable.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for The Narrative Fallacy: Why We Can’t Stop Making Stories
- Identify what the narrative leaves out
After hearing or constructing a causal story, deliberately list the facts it doesn’t explain.
- Generate alternative histories for past outcomes
For any past success or failure, construct two or three plausible alternative paths that could have led to a different outcome.
- Conduct a randomness audit of outcomes you’re explaining
Before attributing an outcome to skill, strategy, or character, estimate how much of it could be chance.
- Run a pre-mortem to interrupt forward narrative construction
Before committing to a plan, imagine it failed completely — then generate the most plausible story of why.
- Separate the data from the narrative you’ve built around it
List the raw facts, then list the story you’ve layered on top — and check whether the story actually follows.
- Be skeptical of clean lessons extracted from messy outcomes
When a story produces a neat takeaway, ask whether the lesson is actually in the data or in the narrative shaping.
Related concepts
- Thinking, Fast and Slow, Made Usable
Two systems, the biases they create, and when to slow down
- Base-Rate Neglect: Why We Ignore the Odds
How to let prior probabilities do their real work in your decisions
- Hindsight Bias: Why Everything Seems Obvious in Retrospect
How "I knew it all along" corrupts judgment — and the practices that correct it