THE IDEA
The story that’s too clean to be true
Humans are storytelling animals. When we encounter a sequence of events, we instinctively construct a narrative: this happened, which caused that, which led to this outcome. The story is satisfying. It makes sense. It has cause and effect, a beginning and an end, and usually a lesson.
The problem is that the real world is far messier than any story. Events have multiple causes, many of them invisible. Outcomes are contingent on factors nobody noticed. The same situation could easily have produced a completely different result. But the narrative flattens all of this into a clean, linear, post-hoc explanation that makes the outcome seem inevitable.
Nassim Nicholas Taleb called this the narrative fallacy - our compulsion to fit complex, random, or multi-causal events into neat stories. The fallacy isn’t that stories are wrong. It’s that they’re too right - too clean, too certain, too complete. They give us the feeling of understanding while actually obscuring the complexity, contingency, and randomness that characterise real events.
IN PRACTICE
The story that writes itself backward
A company succeeds. Business books are written explaining why: visionary leadership, innovative culture, bold strategy. Each chapter is a clean narrative of cause and effect. But the same company, with the same leadership and culture, could easily have failed - a different market timing, a competitor’s lucky break, a regulatory change. The narrative was written backward from the outcome, selecting the details that support the story and ignoring the ones that complicate it.
A relationship ends. Both parties construct a narrative. “It was always going to fail because of X.” “I should have seen the signs.” But at the time, the “signs” were ambiguous. Other relationships with the same signs survived. The narrative that seems so clear in retrospect was invisible in real time - because it didn’t exist until the ending was known.
A sports commentator explains a team’s winning streak: “They found their identity, the new signing gelled with the squad, the manager’s tactical change was inspired.” The same team, with the same changes, could have lost those matches with slightly different bounces of the ball. The commentary would have been different: “The signing hasn’t gelled, the tactical change was naive.” The narrative follows the result, not the other way around.
WORKING WITH THIS
Holding stories lightly
You can’t stop constructing narratives. It’s how the human brain processes information. But you can hold your narratives with appropriate scepticism.
When you catch yourself telling a clean story about a complex event, ask: what am I leaving out? What other stories could explain the same events? What role did luck, timing, or invisible factors play? If the story sounds inevitable, it’s probably oversimplified. Real events are rarely inevitable.
Be particularly suspicious of narratives about success and failure. Success stories overweight the winner’s actions and underweight the role of circumstance. Failure stories overweight the loser’s mistakes and underweight the systemic factors. Both tell compelling stories. Neither captures the full picture.
Use multiple narratives rather than one. When analysing a complex event, construct three different explanations. Each one will feel complete on its own. The fact that multiple plausible stories can be told about the same events is itself the most important insight - it reveals the complexity that any single narrative hides.
THE INSIGHT
The line to remember
The cleaner the story, the more of the truth it’s hiding. Reality doesn’t have a plot - we impose one, and then forget we did.
RECOGNITION
When this is in play
You’re seeing the narrative fallacy when a complex event is explained with a single, clean story. When success is attributed entirely to good decisions and failure entirely to bad ones. When the explanation makes the outcome seem inevitable despite being constructed after the fact. When “the story of how we got here” has a beginning, middle, and end that’s too neat for real life. When someone says “it was obvious in retrospect” - retrospect is where the narrative fallacy lives.