The Premortem: A Smarter Way to Surface the Risks That Actually Matter

Where the Premortem Comes From

The premortem technique was developed by cognitive psychologist Gary Klein, known for his work on naturalistic decision-making. Klein observed that people think more clearly about risks when they imagine a failure that has already happened. This “prospective hindsight” bypasses groupthink, politeness, and the fear of challenging the plan.

Instead of asking, “What could go wrong?”, the premortem asks:

“It’s 12–24 months from now. The project failed. Why?”

That single shift changes the quality of the conversation immediately.

Why Premortems Work

Premortems outperform conventional risk workshops because they:

• Remove the fear of being “negative” or political.
• Surface tacit knowledge that people won’t volunteer in normal meetings.
• Prevent senior-leader anchoring.
• Produce concrete failure scenarios instead of vague categories.
• Reveal risks that structured templates routinely miss.

When people are told the project has already failed, they stop protecting feelings and start protecting outcomes.

How to Run a Proper Premortem

A premortem is only as good as the discipline with which it is run. Here is an expanded walk-through.

1. Set the scene

The facilitator — usually the PM or PMO lead — frames the exercise:

“It’s 18 months from now. The project went ahead. It failed badly. Assume the failure is real. What happened?”

This framing must be absolute. Certainty unlocks candour. If you soften it — “imagine it might have failed” — the exercise collapses back into a normal risk workshop.

2. Silent individual writing

Every participant writes a short explanation of why the project failed. No discussion. No collaboration. No influence. This step is essential. It prevents anchoring and gives quieter voices equal weight. People will write things they would never say out loud in a traditional meeting.

3. Round-robin collection

Go around the room. Each person shares one failure cause at a time. No debate. No rebuttals. No problem-solving yet. Just collection. Continue until every cause is captured. This creates a surprisingly rich set of failure modes — often far more insightful than anything produced by a standard risk workshop.

4. Cluster and clarify

Group similar failure modes. Convert narratives into clear risk statements. Remove duplicates. Identify patterns. This is where the raw material becomes structured insight. You’ll often see themes emerge: governance gaps, unrealistic timelines, brittle dependencies, stakeholder misalignment, or technology constraints.

5. Rank the risks

Most risk frameworks use Likelihood × Impact. But in a premortem, impact is already known. The premise of the exercise is that the project has failed — the highest possible impact score on any scale.

Because impact is fixed at the maximum, ranking focuses on two factors:

• Plausibility — how likely is this failure mode?
• Addressability — can the team meaningfully mitigate or monitor it?

This is a more useful lens for premortem outputs. It helps you identify the risks that are both realistic and actionable — the ones that deserve to be in the top 5–10.

6. Assign owners and early-warning tests

Each selected risk gets:

• A clear owner
• A mitigation or monitoring action
• A “test” — how the team will know early if the risk is materialising

A practical way to define both the risk and its early-warning test is through IF…THEN… statements:

• IF a critical dependency slips by more than two weeks, THEN the integration window collapses.
• IF stakeholder engagement drops below monthly touchpoints, THEN alignment will degrade and decisions will stall.
• IF the vendor cannot deliver the API changes by the agreed milestone, THEN downstream systems will miss their readiness dates.

These statements force clarity. They define the risk in operational terms and make the early-warning trigger explicit. They also give the risk owner a concrete signal to watch for — not a vague sense of “monitoring.”

Premortems that stop at the list create anxiety.

Premortems that assign owners and IF…THEN tests create control.

7. Populate the risk register

When you move premortem risks into the risk register, you’ll need to assign impact scores. This is where the premortem premise matters: because the exercise assumes failure, the impact score should be high by default. If a premortem-identified risk wouldn’t actually cause meaningful failure, it shouldn’t have survived the ranking process. This keeps the register honest and prevents dilution of the top risks.

Why This Technique Deserves Advocacy

The premortem isn’t just another facilitation trick. It’s one of the most effective ways to cut through noise, politics, and optimism bias — especially in organisations where people hesitate to challenge assumptions.

• It helps PMs and teams focus on the risks they can actually manage.
• It strengthens planning without slowing delivery.
• It creates a shared understanding of what failure really looks like — often the missing ingredient in early-stage project design.
• It gives leaders a clearer picture of where to invest attention.

Most importantly, it gives leaders a clearer picture of where to invest attention. If a project has ten risks worth tracking, the premortem will find them. If it has three, the premortem will find those too. And if it has twenty, the premortem will help you prioritise the ones that matter most.

In a world where complexity keeps rising and delivery expectations keep tightening, the premortem isn’t a “nice-to-have.” It’s a practical, repeatable technique that helps teams think first, act precisely, and protect value — not just delivery.

See more on delivering with discipline here: Fail Fast or Just Failing? The Difference That Matters.