Every year, capable leadership teams make mistakes that someone else has already documented. An acquisition overpays for synergies that never arrive. A product launches into a market that isn't ready. A reorganization destroys the informal networks that made the old structure work. The case studies exist. The post-mortems were written. Often, someone in the room has read them.

This is one of the more puzzling patterns in organizational decision-making. Learning from others' mistakes should be the cheapest education available. Someone else paid the tuition, and all we have to do is pay attention. Yet the evidence, from boardrooms to battlefields, suggests we rarely absorb these lessons in ways that change our behavior.

The problem is not access to information. Our minds process other people's failures differently from our own. Two forces do most of the damage: a belief that our situation is special, and an emotional distance that keeps borrowed lessons abstract. Understanding both is the first step toward decision processes that actually learn.

When leaders review a failed decision made elsewhere, a predictable thought follows: that wouldn't happen here. Their company is different. Their team is stronger. Their timing is better. Daniel Kahneman and Dan Lovallo called this the inside view. It is the tendency to judge a decision by its specific details rather than by how similar decisions have usually turned out.

The inside view feels like rigor. You know your own situation intimately, with all its texture and nuance. Other cases look thin by comparison, reduced to a few headline facts. That gap in detail creates an illusion. The more you know about your own case, the more unique it appears, and the less relevant everyone else's experience seems. Deeper familiarity can actually make you more confident that the base rates don't apply to you.

Attribution makes the problem worse. When others fail, we tend to blame their flaws: poor judgment, weak execution, arrogance. When we picture ourselves in the same circumstances, we imagine making better calls. This is a form of the fundamental attribution error, and it quietly turns structural lessons into judgments about character. If the last CEO's merger failed because he was reckless, and you are not reckless, the lesson seems to have nothing to say to you.

NASA's Columbia Accident Investigation Board found this pattern in 2003. Its report identified organizational causes strikingly similar to those behind the Challenger disaster seventeen years earlier, including the gradual normalization of known anomalies. The agency had studied Challenger extensively. But a later generation could see its own situation as different, with new technology, new people and new risks. The lesson was available. The uniqueness illusion made it feel like it didn't apply.

Takeaway

The more detail you have about your own situation, the more unique it will feel. That is exactly when you should ask how situations like yours usually end.

Gary Klein studied experienced firefighters, nurses and military commanders, and his research shows that expertise is largely built from pattern recognition. Experts rarely deliberate through a list of options. They recognize a situation as familiar and know what tends to work. Those patterns are laid down through experience, and experience carries emotional weight. A failure you lived through leaves a mark that shapes how you see the next situation.

Other people's failures arrive without that weight. You read about the collapsed partnership or the botched restructuring as a story, not as a consequence you felt. There was no sleepless night, no tense board meeting, no colleague you had to let go. Construal level theory suggests that we process psychologically distant events in more abstract terms. Abstract lessons are easy to agree with and easy to forget, because nothing in them triggers recognition when a similar moment arrives.

This creates a peculiar gap. A leader can state the lesson perfectly: don't let sunk costs drive the decision. The same leader can fail to notice that they are in exactly that situation right now. The knowledge is stored as a principle, but the danger shows up as a specific moment with its own urgency and politics. Without an emotional cue linking the two, the principle stays filed away, unused.

There is also a protective element. Research on unrealistic optimism, beginning with Neil Weinstein's work in the 1980s, shows that people consistently rate themselves as less likely than their peers to experience negative events. Keeping others' failures at arm's length is partly a way to protect confidence. That confidence helps people act decisively, but it has a cost. The distance that keeps us comfortable also keeps the lesson from landing.

Takeaway

A lesson you understand but have never felt is stored as a principle, while danger arrives as a moment. Principles rarely recognize moments on their own.

If the barriers are uniqueness and distance, the remedies involve forcing comparison and closing the gap. The first technique is reference class forecasting. Before committing to a major decision, deliberately identify a set of similar past cases and ask how they turned out. The question is not what makes your situation special. It is what usually happens to decisions like this one. Start with the base rate, then adjust only for differences that are genuine.

The second technique targets attribution. When studying a failure, separate what the decision-maker could have known at the time from what only became visible in hindsight. Then ask what pressures they faced: deadlines, incentives, incomplete data, a confident sponsor. Most failures look less like stupidity and more like reasonable people responding to a difficult environment. Once you can see their environment, you can ask whether yours resembles it. A judgment about character becomes a pattern you can use.

The third technique supplies the missing emotion. Klein's premortem asks a team to imagine that the decision has already failed and to explain why. Borrowed failures make excellent material for this. Try a prompt like: assume we have repeated exactly what happened to Company X, and walk through how we got there. The exercise makes an abstract lesson concrete and personal. Simulations, war games and detailed storytelling do the same job, giving others' experiences enough texture to feel almost like your own.

Finally, build lessons into structure rather than memory. Aviation's incident reporting systems and the military's after-action reviews work because they turn individual failures into checklists, procedures and shared language. Leadership teams can adopt a simple version: a short tripwire list of specific warning signs drawn from others' failures, reviewed at key decision points. A lesson built into the process doesn't depend on anyone feeling humble at the right moment.

Takeaway

Treat every documented failure as a rehearsal rather than a story. The question is not what they got wrong, but what would have to be true for you to get it wrong the same way.

Failing to learn from others is rarely a failure of intelligence. It is the predictable result of how minds handle information that is distant, thin on detail and emotionally flat. Leaders who understand this can stop relying on good intentions and start designing around it.

A practical framework has four moves. Compare: find the reference class before trusting the inside view. Contextualize: reconstruct the pressures behind others' failures. Simulate: use premortems to make borrowed lessons feel personal. Systematize: build warning signs into the decision process itself.

Someone has almost certainly made your next big mistake already. The question is whether you treat their experience as a cautionary tale about them, or as a rehearsal for you.