Hindsight Bias: Why "I Knew It" Keeps You Repeating Failures

Have you ever had a friend who left their umbrella behind, got caught in a downpour, and then shouted, “I knew it was going to rain today!"—even though an hour earlier, they had insisted, “These clouds don’t look like rain.”

This is hindsight bias. It is the illusion that once we know the outcome, our memory of the past is rewritten to make it seem inevitable. Because of this, we inadvertently erase the opportunity to learn from our failures.

An investor who says, “I knew it would burst eventually,” after a stock price drop,

A colleague on Monday morning criticizing a coach for a substitution made during yesterday’s game, saying, “I wouldn’t have pulled him out,”

A pundit who explains the results as inevitable only after the votes are counted.

I sometimes become that “Monday morning colleague” myself. Researchers have concluded that this bias isn’t a defect in a few people, but a default setting hardwired into everyone’s brain.

How Hindsight Bias Was First Identified

The starting point was a 1975 experiment by psychologist Baruch Fischhoff.

The design was simple. Participants were asked to read the background of an obscure historical event (such as the 1814 war between the British and the Gurkhas of Nepal) and assign probabilities to various possible outcomes.

• Foresight Group: Assigned probabilities without knowing the outcome.
• Hindsight Group: Read the same text but were told, “This is how it actually ended.” They were then asked to “assign probabilities as if you didn’t know the result.”

The hindsight group consistently assigned higher probabilities to the outcome they were told. Even when asked to ignore the answer, they couldn’t.

What’s more interesting is what followed: most participants didn’t even realize that knowing the outcome had influenced their judgment. They genuinely believed, “I would have seen it that way, too.”

Fischhoff named this phenomenon creeping determinism. It means that knowledge of an outcome spreads into our understanding of the past like ink dropped in water.

However, science doesn’t end with a single experiment.

In a replication study by a Brazilian research team (Seda et al.) that used a preregistered method, the effect size in some conditions was weaker than in the original paper. It is more accurate to say that the magnitude of the bias varies depending on the context, rather than questioning its existence altogether.

Why Does Hindsight Bias Occur? Outcomes Rewrite the Past

The key is the ease of the narrative.

Once you know the ending, a chain of causality—“A happened, leading to B, which caused C”—flows easily through your mind.

This is bolstered by the availability heuristic, where we perceive things that are easy to recall as more plausible. Conversely, alternative paths, such as “What if Z had happened instead of B?” become harder to imagine, and because they are difficult to recall, we assume they were unlikely. The uncertain past is thus reassembled into a single, straightforward path.

This leads to two major consequences.

First, we judge others unfairly. The question, “It’s obvious now, why didn’t they know?” biases evaluations in medical malpractice lawsuits, intelligence analysis, and disaster response investigations.

Second, we become overconfident in ourselves. This is the more dangerous part. It proceeds as follows:

1. Knowledge of the outcome seeps into memory, making the past look inevitable.
2. The surprise and uncertainty felt at the time are erased from memory.
3. We believe, “I knew more than I actually did.”
4. Because we mistake our prediction as accurate, we miss the negative feedback we should have received from our incorrect predictions.
5. The chance to correct our judgment vanishes, and the next decision becomes even more reckless.

And the next mistake is covered up by the same bias. Therefore, hindsight bias is not just a minor habit of misremembering the past; it is a mechanism that blocks learning itself.

Pearl Harbor and 9/11: What “Failing to Connect the Dots” Misses

Behind every major intelligence failure, there is almost always the assessment: “The signs were all there, but they failed to connect the dots.” This is the most typical sentence created by hindsight bias.

Roberta Wohlstetter of the RAND Corporation challenged this narrative.

In her 1962 book Pearl Harbor: Warning and Decision, she wrote that instead of “connecting the dots,” we must view it as a signal-to-noise problem. Before the event, definitive signals are buried in the noise of irrelevant data, misleading information, countless false alarms, and enemy deception.

That was the case with Pearl Harbor in 1941.

Decoded Japanese diplomatic cables, fleet movements, and embassy activities look like clear signals now. But at the time, American analysts knew an attack was imminent but expected the target to be Southeast Asia, like the Philippines or the Malay Peninsula. For a resource-strapped Japan facing oil embargoes, heading south toward oil fields made much more strategic sense. The signals pointing to Hawaii were few and ambiguous. The dots only became a picture the moment the bombs fell.

9/11 in 2001 had a similar structure.

The 9/11 Commission also concluded they “failed to connect the dots,” but at the time, intelligence agencies were accustomed to Cold War-style state-on-state threats, and information was trapped in silos between the CIA, FBI, and NSA. An FBI Phoenix field agent’s report about extremists enrolling in flight schools was dismissed by superiors, and the idea of using a passenger plane as a missile was beyond the imagination of most analysts.

Therefore, the assessment that they “failed to connect the dots” is dangerously simplistic rather than just wrong. All the countless threats that didn’t happen—the noise—are forgotten, leaving only the few signals that pointed to the actual event. This narrative led to reforms like the creation of the ODNI to “connect information better.” However, connecting the dots is a symptom revealed in hindsight; the ability to distinguish signals from noise in real-time or an organization’s lack of imagination can remain unchanged. An organization optimized to prevent the last attack is often still vulnerable to the next novel surprise.

Kodak and Nokia: Failures Look Different Through the Lens of Hindsight Bias

A company that invented the digital camera filed for bankruptcy protection in 2012, and a company that held nearly half the smartphone market in 2007 collapsed within a few years. It’s hard to understand now. “How could they have been so blind?”

In 1975, Kodak engineer Steve Sasson took the first digital photo with a device the size of a toaster. The management’s reaction, summarized by Sasson’s own recollection, was, “That’s cute. But don’t tell anyone.” In hindsight, it looks like an all-time blunder.

But if you open Kodak’s books from that time, the picture changes.

Kodak operated on a ‘razor and blade’ model, selling cameras cheaply and making money through film, photo paper, and chemicals. The digital camera was a razor that didn’t need blades. It wasn’t that Kodak didn’t know the future of digital; it was because they knew it too well that they were terrified of cannibalizing their golden-egg film business. It was rational in the short term, and fatal in the long term.

Nokia’s success was also the cause of its failure.

Having become an absolute powerhouse with durable bodies, long-lasting batteries, and a strong brand, the company underestimated the weight of the app ecosystem and touch interfaces after the iPhone. They clung to the cumbersome Symbian operating system for too long.

They believed they could catch up on brand strength alone, and within a culture of internal competition and rigid decision-making, new ideas from engineers were often buried.

Hindsight bias turns these complex dilemmas into moral stories of “incompetence.” In my view, the real lesson lies on the other side.

The success models of both companies created cultures and incentives optimized for protecting existing businesses, and that structure read new technology as a threat to the core business rather than an opportunity. Within the framework of the time, they were partially rational choices.

If you conclude, “They were idiots,” leaders of currently successful organizations miss the fact that their own success can blind them to the next disruptive innovation.

What you should avoid isn’t just ‘obvious mistakes,’ but the paradox of success.

The Financial Crisis and the Itaewon Tragedy: The Trap of the “Predictable Disaster” Frame

After a tragedy, the phrase media outlets use most often is “predictable disaster” (man-made disaster).

It implies that it wasn’t a random accident but could have been prevented with due diligence. Sometimes that’s true. The problem is that the judgment is almost always made after the event.

After the 2008 Lehman Brothers bankruptcy, the list of causes seemed all too clear.

Housing bubbles, predatory subprime lending, CDOs and CDSs that no one properly understood, and loose regulation. After the crisis, experts and politicians agreed it could have been foreseen. But as the movie The Big Short shows, those who actually bet on the collapse were a tiny minority treated as eccentrics. The noise at the time was the long period of economic stability called the ‘Great Moderation,’ global savings gluts, and the belief that “US housing prices do not fall nationwide.” The risks were hidden behind complex, opaque product structures.

Coverage after the Itaewon tragedy on October 29, 2022, also immediately converged on “predictable disaster.”

Narrow alleys, poor crowd control, international preventive cases, and crowd density simulations were discussed daily, and the focus shifted to assigning responsibility. However, when Newstapa analyzed news reports from the two weeks before the tragedy, not a single article had warned about a crowd crush accident. The space was filled with Halloween product promotions and police drug crackdown news. The risks that seem obvious now were absent from the media, the public, and authorities’ field of vision at the time. Analysis shows the same frame was repeated in coverage after the Sewol ferry disaster.

I hope there is no misunderstanding.

This is not to say we shouldn’t hold people accountable. The fact that authorities’ preparation was inadequate and the claim that the danger was visible to everyone beforehand are two separate issues.

In the face of huge tragedies, people want to know ‘why,’ and hindsight bias turns complex causes into a straight line: “Someone didn’t do A, so B happened.” It brings the comfort that finding and punishing the perpetrator will prevent a recurrence.

In return, reflection on systemic issues like budget shortages, conventions, regulatory loopholes, and complacency within organizations is pushed to the background. It is like treating the symptoms while leaving the disease.

3 Tools to Reduce Hindsight Bias

You can’t turn off your brain’s default settings. The goal is not to predict the future, but to fix the process of judgment. There are three tools.

Pre-mortem: Imagine failure in advance

Proposed by cognitive psychologist Gary Klein, the pre-mortem is the opposite of a post-mortem, which dissects a project after it’s finished. Before starting, gather the team and ask: “It’s six months later. This project has failed miserably. Why did it fail?”

The reason for its effectiveness is that it gives a license for dissent.

In a meeting where everyone says it’s a “perfect plan,” it’s hard to be the one to say, “But I’m worried about this” (as anyone who has worked in an office knows).

The pre-mortem turns finding the reasons for failure into everyone’s mission, drawing out anxieties and knowledge that were hidden within the team.

Based on Klein’s method, here is the five-step process I’ve summarized:

1. Briefing: Share the final plan.
2. Declaration of Premise: “The project has ended in total failure. Let’s each quietly write down the reasons for 10 minutes.”
3. Round-robin Sharing: One by one, share one reason at a time until all reasons are on the board. No rebuttals allowed.
4. Prioritization: Vote to select the most fatal and likely risks.
5. Reinforcement: Return to the original plan and incorporate measures to prevent those risks.

Decision Journal: Lock in the ‘you’ from that moment

Hindsight bias rewrites the memory of what you believed before knowing the outcome.

A decision journal prevents bias from creeping in by leaving that memory as an immutable record. Don’t write about lunch menus; use it for decisions with lasting consequences like changing jobs, investing, or hiring. The template I use has five lines:

• Date
• Decision: What are you choosing? (e.g., Accepting a job offer from Company A)
• Context and Alternatives: Current situation, options considered then discarded (e.g., staying, applying to Company B)
• Expected Outcome and Probability: What do you expect and how confident are you? (e.g., 20% salary increase in 1 year, 70% probability)
• Psychological State: Are you excited, anxious, or impatient?

The value comes not when you write it, but when you read it again. If you open it every three months or every quarter, your judgment habits and blind spots—which memory would have cleanly erased—are laid bare. The moment you confirm, “I was only 70% sure back then,” is the most honest feedback.

Writing Down Two Counter-Reasons

This is the simplest tool. Before making a conclusion, pause and ask:

“What if this judgment is wrong? What would the path be if the exact opposite result happened?”

This strategy, ‘consider the opposite,’ has been proven effective in reducing confirmation bias, anchoring bias, and hindsight bias. It forces you to look away from the easy explanation that first came to mind, breaking tunnel vision.

There is one trap.

In a 2002 experiment by the Sanna and Schwarz research team, people who were asked to write two reasons why the result could have been different showed reduced hindsight bias, but those asked to write ten showed an increase. Because it became difficult to squeeze out reasons, the brain read that difficulty as evidence: “See, a different result really was unlikely.” So, it’s better to write just 2~3 counter-reasons—only as many as come to mind easily.

Here is a summary of the three tools in a table:

Comparison of 3 Tools to Reduce Hindsight Bias

Technique	Core Principle	Suitable Situations	First Step
Pre-mortem	Assume failure to find hidden risks	Team projects, strategic planning, new product launches	Schedule a 1-hour meeting and ask, “If we failed, why?”
Decision Journal	Record reasoning before knowing results to prevent memory distortion	Job changes, investments, hiring	Fill out the 5-line template before deciding and read it 3 months later
Counter-reasons	Intentionally imagine scenarios opposite to initial judgment	Daily judgments, opinion formation, evaluating proposals	Write down “2 reasons why I could be wrong”

There is no need to become cynical just because you know about this bias.

Instead, you stop judging past decision-makers by today’s correct answers and start looking at the process they followed amidst the incomplete information and noise they faced.

Next time someone says, “I knew it would happen,” I think I’d like to quietly ask: where did you write that down at the time?