Some teams run a "pre-mortem" before a big project: they imagine it has already failed and work backward to figure out w

Yes, there is solid cognitive science behind the pre-mortem.

What the Research Shows

The foundation of the pre-mortem comes from a 1989 study by Deborah Mitchell, J. Edward Russo, and Jay Pennington on prospective hindsight—imagining that an event has already occurred and reasoning backward to understand why.

Their research found that asking people to explain a future outcome as a certainty (rather than just asking "what might go wrong?") increased their ability to correctly identify reasons for future outcomes by roughly 30%.

Later, cognitive psychologist Gary Klein adapted this into the formal "project pre-mortem." The technique works because it bypasses two major psychological traps:

1. Overcoming groupthink and social friction: In standard planning, people holding doubts often stay silent to avoid seeming unsupportive. A pre-mortem flips the social incentive: finding plausible failure modes becomes a demonstration of insight and loyalty rather than pessimism.
2. Bypassing optimism bias: When you ask, "Could this fail?", the brain naturally defends the plan. When you ask, "It has failed—why?", the brain shifts from defending the plan to solving a puzzle.

---

How to Run a 45-Minute Pre-Mortem for 5–6 People

To prevent the session from turning into a venting session or producing vague, useless anxieties, use a tight, structured sequence that moves quickly from generation to triage to action.

1. Set the Stage (3 minutes)

Give the premise clearly:

"Fast-forward six months. The launch was a total disaster. The product didn't work, customers are unhappy, and the project failed. Take five minutes to write the story of how that happened."

Rule: Ground it in specifics. Ban vague complaints (e.g., instead of "Communication was bad," require "The backend and frontend teams assumed the other was handling authentication, so it wasn't built in time").

2. Silent Brainwriting (5 minutes)

Have everyone write their failure modes individually on sticky notes or a shared digital board (Miro, FigJam, or a doc). Why silent? It prevents the loudest voice from anchoring the room and protects candid feedback.

3. Round-Robin Sharing (10 minutes)

Go around the circle. Each person shares one unique risk at a time until all distinct ideas are on the board.

• Facilitate neutral clustering: Group overlapping points without debating them yet.

4. The 2x2 Filter: High Impact vs. High Likelihood (10 minutes)

Small teams cannot fix 20 hypothetical problems. Give each person three votes to identify the failures that are both plausible and lethal.

• Discard vague complaints and low-probability edge cases.
• Pick only the top 3 to 5 risks to solve today.

5. Reverse the Script into Mitigations (15 minutes)

For each top risk, answer two questions:

1. Early Warning Trigger: "What will we see in week 3 or 4 that signals this failure is starting to happen?"
2. Preventative Action: "What change do we make to our plan or ownership today to reduce this risk?"

Assign every mitigation a single owner.

---

Three Guardrails to Keep It Constructive

• The "Within Our Influence" Rule: If someone brings up an unchangeable macro risk (e.g., "The economy collapses"), acknowledge it, park it, and redirect: "Assuming standard conditions, what internally causes us to trip up?"
• Separate the Problem from the Person: Frame every failure as a process, communication, or resource bottleneck rather than an individual's shortcoming.
• Never End on the Gloom: The exercise is only successful if the team walks away feeling more in control of the project, not less. Always end with the updated action plan.