Pre-Mortem Template
Imagine your project has already failed. Now figure out why.
A pre-mortem flips the usual post-mortem: instead of asking what went wrong after the fact, you ask what could go wrong before you start. Run this with your team before any significant project, decision, or launch.
1. The Setup
Imagine it's [timeframe] from now and this project has failed spectacularly. Not a minor setback — a genuine failure. What happened?
2. Individual Brainstorm (5 minutes, silent)
Each person writes down reasons the project failed. No discussion yet. Be specific and honest.
1.
2.
3.
4.
5.
6.
3. Round Robin
Go around the table. Each person shares one reason. No debate, no defending, just listening. Record all reasons here.
Failure Reason Category
Wrong Problem / Wrong Approach / Poor Execution / External / People
Wrong Problem / Wrong Approach / Poor Execution / External / People
Wrong Problem / Wrong Approach / Poor Execution / External / People
Wrong Problem / Wrong Approach / Poor Execution / External / People
Wrong Problem / Wrong Approach / Poor Execution / External / People
Wrong Problem / Wrong Approach / Poor Execution / External / People
Wrong Problem / Wrong Approach / Poor Execution / External / People
Wrong Problem / Wrong Approach / Poor Execution / External / People
Wrong Problem / Wrong Approach / Poor Execution / External / People
Wrong Problem / Wrong Approach / Poor Execution / External / People
4. Prioritise
As a group, identify the top 3 most likely or most damaging failure modes.
Risk 1
Risk 2
Risk 3
5. Mitigations
For each top risk, what can you do now to prevent it or reduce its impact?
Risk 1 mitigation:
Risk 2 mitigation:
Risk 3 mitigation:
6. Kill Criteria
What would make you stop this project entirely? Define the signals now, before optimism bias sets in.
Tip: The first response to someone raising a concern should be gratitude, not justification. Thank people for pulling the cord.
thepracticalthinker.com
From Well, That Didn't Work — Drew Bruce | The Practical Thinker