Identify what the narrative leaves out
After hearing or constructing a causal story, deliberately list the facts it doesn’t explain.
Why it works
Narrative construction is selective: the brain assembles facts that fit a causal chain and discards facts that don’t, not maliciously but automatically. The result is that the story feels complete even when it isn’t. Deliberately generating the omissions — asking "what else happened that the story doesn’t account for?" — breaks the completeness illusion and makes the gaps visible rather than invisible.
How to do it
- After constructing or hearing a narrative explanation, ask: "What happened that this story doesn’t explain?"
- List at least three facts or events that the narrative omits or explains away.
- Ask: "Does the story still hold if these facts are weighted equally with the ones it features?"
Evidence
Consistent with hindsight bias research (Fischhoff, 1975) and with the sensemaking literature (Weick, 1995): narratives are constructed retrospectively and are systematically tidier than the actual evidence justifies. Taleb’s narrative fallacy formalizes this as a distinct bias. (mechanistic)
"Narrative fallacy" is Taleb’s term; the underlying mechanisms (hindsight bias, selective memory, causal attribution) are separately well-established.
Sources
- Fischhoff (1975), "Hindsight ≠ Foresight: The Effect of Outcome Knowledge on Judgment Under Uncertainty," Journal of Experimental Psychology: Human Perception and Performance
Common mistake
Listing only minor or irrelevant omissions — the check is most useful when you surface facts that genuinely challenge the causal structure of the story.
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
- 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.
- 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.
- 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