How to run a pre-mortem that catches the failure your team is not talking about.

The pre-mortem is one of the highest-leverage sessions you can run before a major project launch. It takes under an hour and routinely surfaces the one risk that would have been fatal.

Setup. The pre-mortem should happen 1–2 weeks before launch or go-live — not the day before, when it's too late to act on findings. Invite the core project team plus one or two skeptical outsiders who know enough to be useful but aren't so invested they'll hold back.

Step 1 — Set the scenario (5 min). Facilitator reads a statement aloud: "Imagine it is 12 months from today. This project has failed. Not a small hiccup — a significant failure. We missed our key metrics, stakeholders are disappointed, and we're trying to understand what happened. Your job is to explain why it failed."

This is prospective hindsight — a technique Gary Klein found dramatically increases the identification of reasons for future outcomes. Framing failure as already happened frees people to name risks they'd normally suppress.

Step 2 — Silent writing (10 min). Everyone writes down every failure reason they can think of — one per sticky note. No screening. Silly reasons, political reasons, technical reasons, market reasons — all on the board. The goal is quantity. A good pre-mortem generates 15–40 failure scenarios from a team of 6.

Step 3 — Read out and cluster (15 min). Each person reads their stickies aloud without justification. The facilitator clusters similar ones on the whiteboard. Categories often emerge: execution risks, dependency risks, market risks, resource risks, assumption risks.

Step 4 — Rank by likelihood × impact (15 min). Dot-vote the top 5–7 failure scenarios. For each top scenario, ask: What's the likelihood (1–3) and what's the impact if it happens (1–3)? Multiply to get a risk score. Any scenario scoring 6–9 needs a mitigation plan.

Step 5 — Mitigation assignments (10 min). For the top 3–5 risks: who owns it, what's the mitigation action, and what's the trigger that tells you the risk is materializing? Write this directly on the whiteboard next to each risk cluster.

Output. A ranked risk register with mitigations and owners — not a vague "watch list" but a concrete action plan. This becomes a standing agenda item for weekly status checks.

Snap the whiteboard with BoardSnap after the session. The AI reads the cluster labels, risk scores, and mitigation notes and outputs a clean risk register ready for your project tracker.