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.
Why it works
Data and narrative feel inseparable because the narrative is formed automatically and immediately. By the time you consciously access information, the story is already attached. Separating them requires explicitly listing what happened (observable events, measurable facts) versus what you have inferred about it (causality, character, meaning). The gap between these two lists is where the narrative fallacy lives.
How to do it
- Choose a situation you have a strong view about.
- Write two columns: "What I observed" (behaviors, outcomes, words said) and "What I inferred" (motives, character, causes).
- Ask: "Does my inference actually follow from the observation, or am I adding it?"
Evidence
The observation/inference distinction is a classic tool in critical thinking and social cognition. Research on attribution error (Ross, 1977) shows that inferences about character and motive are frequently added to and mistaken for observations. (mechanistic)
Common mistake
Placing inferences in the "observation" column because you believe them firmly — the rule is not what you believe but what you could have recorded on video.
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.
- 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