There's a 20-minute meeting most teams never run. It's called a pre-mortem. You do it before the work starts, not after it fails. Most teams skip it. That's expensive.

You've seen this pattern. The product launch that flopped. The quarter that missed. The team that fell apart. You sit in the post-mortem afterward and get really smart about the exact problem you should have seen coming six months ago.

The post-mortem is useful. But it's the most expensive way to learn.

The pre-mortem flips this. You imagine the project has already failed, completely and visibly, and you work backwards to figure out why. Then you fix those problems before they become real ones.

This technique was developed by psychologist Gary Klein and popularized through Daniel Kahneman's work on planning fallacy and cognitive bias. It's one of the better-evidenced planning interventions in behavioural science, and most leadership teams have never heard of it.

What follows is the full agenda, plus why this is different from standard risk analysis and how to run it with a room full of optimists who think everything is on track.

‍

Why Standard Risk Analysis Fails (And Pre-Mortem Doesn't)

Every project has a risk log. Almost nobody takes it seriously.

The reason is psychological: when a team is excited about a new initiative, the brain actively suppresses concerns. Pointing out risks feels like pessimism. Naming failure scenarios feels like you're not a team player. The result is a risk register full of generic bullet points that nobody actually believes will happen.

This is what Kahneman calls planning fallacy, the systematic tendency to underestimate time, cost, and obstacles while overestimating benefits. It's not incompetence. It's how human brains work when they're invested in an outcome.

The pre-mortem short-circuits this by assuming failure and then asking teams to explain it. When failure is already baked into the premise, the social pressure to be optimistic disappears. People suddenly get honest about the thing they've been quietly worried about but didn't want to be the one to say.

Our strategy offsite facilitation practice incorporates the pre-mortem specifically because of this pattern: the most important information in any planning session is usually the thing someone is not saying.

‍

When to Run a Pre-Mortem

A pre-mortem is most valuable when:

• The stakes are high. Launch, raise, hire, restructure, anything where a wrong call costs you months
• The decision is hard to reverse. Once it's done, it's done
• The team is genuinely excited. Excitement is the cognitive condition pre-mortems are designed to counterbalance
• A small number of assumptions carry the entire plan
• You sense the room is too aligned. The "we're all on the same page" feeling is often the warning sign, not the success metric

It works for a 12-person exec team planning an annual strategy. It works for a product team kicking off a new sprint cycle. It works in the room before a critical client pitch. The format scales.

What doesn't benefit from a pre-mortem: small, low-stakes, reversible decisions. Save the structured facilitation for what actually matters.

‍

The 20-Minute Pre-Mortem: Full Agenda

This is a working agenda you can run tomorrow. You need a facilitator (someone who can stay neutral), a way to capture ideas (sticky notes, digital whiteboard, or shared doc), and the right framing upfront.

‍

Setup (2 minutes)

The facilitator says exactly this:

"I want you to imagine it's one year from today. This project has failed, completely, visibly, and badly. The launch missed, the team is demoralized, key people have left, or whatever version of failure feels most relevant. I'm not asking you to predict failure. I'm asking you to explain it. Take the next few minutes and write down every reason you can think of for why this happened."

That's the key framing: you're not predicting, you're explaining. Past tense. It's already happened. This small shift dramatically increases the quality and honesty of responses.

‍

Individual writing (5 minutes)

Silent individual work. Everyone writes their list of failure reasons independently, before any discussion. This prevents groupthink and ensures quieter voices contribute equally. No talking. No peeking at each other's answers.

‍

Share and cluster (8 minutes)

Each person reads their list aloud. The facilitator clusters similar themes in real time. Don't debate or react yet, just capture. In a healthy pre-mortem, you'll see 3 to 5 dominant themes emerge: maybe scope creep, maybe unclear ownership, maybe a dependency nobody flagged, maybe a resource assumption that's wrong.

‍

Prioritize and assign (5 minutes)

As a group, pick the top 2 to 3 failure scenarios by vote or facilitator judgment. For each:

• What's the early warning signal we'd see if this was happening?
• What's one concrete action we can take to reduce the probability?
• Who owns that action?

Don't try to solve everything. Two honest interventions on real risks are worth more than eight items on a mitigation plan nobody will follow.

‍

Document (post-session)

The facilitator captures the key failure themes, the warning signals, and the committed actions. This document becomes a standing agenda item in your meeting accountability system, someone checks the warning signals at regular intervals.

‍

What Good Pre-Mortem Data Looks Like

The discomfort is the signal. A team that agrees on everything in a pre-mortem either has an unusually aligned project (rare) or is not being honest (common).

‍

Pre-Mortem vs. Post-Mortem: The Real Difference

Both are retrospective tools, but they work at opposite ends of the timeline and produce different types of value.

The best teams run both. Many quarterly business reviews fold a pre-mortem element into the "risks to next quarter's targets" conversation, applying the same logic to quarterly planning rather than just project launches.

‍

Pre-Mortem at the Strategy Level

The pre-mortem principle scales all the way up to annual strategy. When leadership teams sit down to build a strategy offsite agenda, one of the most valuable sessions is the "strategic pre-mortem."

The prompt: "It's 18 months from now. We pursued this strategy and it failed to move the company forward. Why?"

This question surfaces the strategic assumptions that are most fragile. It's common to discover that the entire strategy rests on one or two assumptions, a market condition, a competitor move, a hiring outcome, that nobody has explicitly named. The pre-mortem forces those assumptions into the open, where they can be stress-tested.

Paired with clear OKRs that track the right leading indicators, the strategic pre-mortem becomes a living risk management practice, not a one-time exercise.

‍

The Team Dynamics of a Good Pre-Mortem

One thing to know before you run this: the pre-mortem reveals your team's psychological safety level almost immediately.

In a low-safety team, the individual writing phase will produce surface-level, safe risks. Nobody will name the uncomfortable truth, the team member who always blocks progress, the budget assumption that's clearly wrong, the dependency on a relationship that's already strained. People will write what they're comfortable saying in front of their manager.

In a high-safety team, you get the real concerns. The ones that might sound disloyal or pessimistic in a normal meeting. This is where the learning lives.

If your pre-mortem produces generic risks, the problem isn't the exercise, it's the safety level in the room. And that's a different conversation, but an important one.

‍

Run Your First Pre-Mortem This Week

Pick an in-progress or upcoming project with real stakes.

Block 30 minutes with the project team. Send the framing ahead of time so nobody walks in cold. Run the four steps. Capture the outputs.

You will learn something you didn't know. Every time. That's not the goal, it's the guarantee.

Planning a strategy offsite or leadership retreat? Our facilitators run pre-mortems as a standard part of the agenda. See how we structure a full strategy offsite.

‍

Frequently Asked Questions