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.
Why it works
The narrative fallacy makes outcomes feel inevitable in retrospect: once you know how things turned out, the path to that outcome seems the only possible one. Generating counterfactuals — "what plausible differences in conditions would have produced a different result?" — weakens the perceived inevitability by making visible that there were many possible paths, most of which did not depend only on the factors your narrative highlights.
How to do it
- Choose a past outcome (business success, project failure, personal win or loss).
- Construct two plausible alternative histories: "If X had been different, the outcome could have been Y."
- Ask which factors in the counterfactuals were within anyone’s control and which were chance.
Evidence
Counterfactual thinking is a well-studied cognitive phenomenon. Research by Kahneman and Miller (1986) on counterfactual reasoning and by Roese (1997) on its functions shows that generating alternatives improves causal reasoning by weakening the perceived uniqueness of the actual path. (observational)
Sources
- Roese (1997), "Counterfactual Thinking," Psychological Bulletin
Common mistake
Generating only counterfactuals that make the outcome seem even more certain ("it would have happened anyway") rather than counterfactuals that reveal genuine contingency.
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.
- 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