The Builder's Psychology Lab · Tool
Executive Premortem Toolkit
A premortem surfaces the concerns that ordinary planning suppresses. Use this before any major commitment. Print it or save it as a PDF, then run it with your team.
- 1
State the decision
Name the plan clearly, so everyone reacts to the same thing.
- 2
Assume it failed
Move to a year from now: the initiative failed badly.
- 3
Explain why, independently
Each person writes the causes before any discussion.
- 4
Cluster preventable causes
Group the failures; separate bad luck from bad conditions.
- 5
Assign owners and warning signals
Give each preventable cause an owner and an early indicator.
The warning signals and owners feed straight back into the plan, so the premortem strengthens the decision rather than just critiquing it.
Page 1
Why conduct a premortem?
Ordinary planning asks what could go wrong and gets polite, guarded answers. A premortem asks something different. It assumes the decision has already failed and asks the team to explain why. This move, which researchers call prospective hindsight, has been shown to raise the number and specificity of concerns people surface, because it is safer to explain a failure that has notionally already happened than to predict one and look like a naysayer. Gary Klein popularized it for teams. Its value is that it converts private doubt into shared, actionable information before the commitment is made rather than after it fails.
Page 2
Facilitation instructions
- State the decision or plan clearly, so everyone is reacting to the same thing.
- Ask the group to assume it is a year from now and the initiative has failed badly.
- Give participants silent writing time to list why it failed, individually.
- Collect the explanations independently, before any discussion, so no one anchors on the first voice.
- Cluster the failure causes into themes.
- Identify which causes are preventable conditions rather than bad luck.
- Assign owners and decision rights for the preventable ones.
- Define the early warning indicators that would tell you a cause is materializing.
Page 3
Individual worksheet
It is twelve months from now. The initiative failed badly. What happened?
What did leaders fail to notice?
What assumption proved false?
What concern remained unspoken?
Which dependency was treated as certain?
Where did authority sit too far from the knowledge?
What signal appeared early but was ignored?
What prevented the organization from changing course?
Page 4
The Four A's risk scan
Attention
What is competing for the attention this needs to succeed?
Alignment
Where do participants hold different definitions of success?
Authority
Who can approve, stop, redirect, or escalate the work?
Adaptability
What evidence would cause us to revise the plan?
Page 5
Decision hygiene record
Decision
Date
Decision owner
Key assumptions
Reference class (how similar efforts have actually turned out)
Known uncertainties
Stop criteria
Escalation threshold
Review date
Page 6
Debrief connection
A premortem is only half of the loop. After the work is done, close it by comparing what you feared to what actually happened, and feed the difference into your next planning cycle.
What actually happened?
Which assumption proved correct?
Which assumption proved wrong?
What did we notice too late?
What should change before the next planning cycle?
Want to know which of the Four A's is most likely to sink your next initiative? The Executive Diagnostic reads all four conditions across your organization.
Take the Executive Diagnostic →