Hi there,

Today we will talk about how pre-mortems help leaders spot risks early, reduce surprises, and build stronger plans before failure happens.

Most projects do not fail because teams are lazy. They fail because risks stay invisible until it is too late. People rush into execution, assume the best-case outcome, and discover problems only when changing course becomes expensive. A pre-mortem solves this by making failure discussable before it happens.

The Leadership Lesson Explained

A pre-mortem is a short exercise where the team assumes the project has failed and then works backward to explain why. This removes optimism bias and makes hidden risks easier to name. Instead of asking, “What could go wrong?” you ask, “It failed. What happened?”

The real value of a pre-mortem comes from what happens next. Risks get turned into owners, guardrails, and early proof points that can be tracked. Over time, this practice reduces surprises and builds a culture where truth shows up early.

Case Study: Gary Klein’s Pre-Mortem Method

Psychologist Gary Klein introduced the pre-mortem as a practical way to improve decision quality before execution begins. Teams imagine a future where the plan failed and then list the most plausible reasons without blame. This approach helps groups surface risks that are often suppressed during normal planning conversations.

Organizations use the method because it is both fast and effective. It increases risk awareness without slowing momentum and improves alignment around threats and assumptions. Teams move forward with more confidence because they prepare for reality, not just hope for it.

Takeaway: Assume failure early, name the real risks, and turn them into guardrails and proof points before you commit fully.

Five Tactics to Run Pre-Mortems That Work

1) Run the pre-mortem before the plan is locked

Pre-mortems work best when change is still cheap. Running one after kickoff often turns the conversation into hindsight instead of preparation. The best time is when the team has a draft plan and can still adjust the scope, timeline, or resources.

Try this: Schedule a 30-minute pre-mortem right after the project brief is written. Ask each team member to arrive with two risks already in mind.

Why it works: Early timing protects flexibility. People speak more openly when they know changes are still possible.

2) Use the “it failed” prompt to unlock honesty

Standard risk discussions often stay polite, vague, and overly optimistic. The “it failed” prompt makes people think in concrete terms and lowers the pressure to sound positive. It gives the team permission to name what they actually fear.

Try this: Say, “It is 60 days from now and this project failed. Write down the top three reasons why.” Collect responses silently before opening the discussion.

Why it works: Silent writing reduces groupthink. Specific risks surface faster than general concerns.

3) Sort risks into themes and choose the top five

A long list of risks creates paralysis instead of progress. Teams need to focus on the few risks most likely to damage outcomes. Grouping them into themes like scope, dependencies, timing, people, and quality makes the conversation easier to manage.

Try this: Cluster risks on a board and ask the team to vote on the five most dangerous ones. Write those five in the project brief under a section called “Known Risks.”

Why it works: Focus prevents overwhelm. A short list creates action instead of anxiety.

4) Turn risks into mitigations, owners, and triggers

A risk without a mitigation plan is just organized stress. Every major risk needs one owner, one mitigation step, and one trigger that signals the risk is becoming real. This turns worry into action and makes escalation easier.

Try this: For each top risk, create three lines: “Mitigation,” “Owner,” and “Trigger.” Add a clear escalation rule, such as “Escalate if blocked for 48 hours.”

Why it works: Ownership drives follow-through. Triggers remove emotion from escalation and course correction.

5) Add early proof points and a review date

A pre-mortem loses value if the team never looks at it again. Early proof points help test the riskiest assumptions quickly, before they become expensive. A review date keeps the team learning instead of drifting.

Try this: Pick one proof point to test in week one and schedule a review in week two. Revisit the risk list and update it based on real evidence.

Why it works: Proof reduces uncertainty. Reviews keep the plan tied to reality.

Five Common Pre-Mortem Mistakes and How to Fix Them

1) Treating the exercise as negativity

Some leaders shut down risk discussions because they want to “stay positive.” That approach hides reality and increases the chance of surprises later. The team learns that silence is safer than honesty.

Fix: Frame the pre-mortem as a tool for protecting speed and quality. Praise people who surface risks early and clearly.

2) Making the list too long

A long risk list quickly becomes a graveyard of forgotten concerns. People stop reading it, and nothing changes in the actual plan. The exercise starts to feel like paperwork instead of leadership.

Fix: Limit the list to the top five risks and make each one actionable. Track only the risks you are truly willing to mitigate.

3) Naming risks without assigning owners

Risks drift when everyone assumes someone else will handle them. Mitigations never happen, and the same issues show up later under more pressure. Accountability becomes blurry.

Fix: Assign one owner to each risk and write that name in the project brief. Review ownership every week until the risk has been reduced.

4) Skipping triggers and escalation rules

Teams often notice problems but still delay action because nobody knows when to escalate. People waste time debating whether the issue is serious enough. That delay increases stress and makes recovery harder.

Fix: Define triggers such as timeline slips, metric drops, or missed dependencies. Escalate based on the trigger, not on mood or opinion.

5) Running the pre-mortem once and forgetting it

Projects change, but static risk lists do not. Teams move forward while the old assumptions stay untouched, and the same blind spots return. Learning stops when the document becomes decoration.

Fix: Revisit the risk list in week two and then once a month after that. Update mitigations and close risks that are no longer relevant.

Weekly Challenge

Run a 30-minute pre-mortem for one active project this week. Assume it failed, write down the top reasons why, and choose the five biggest risks. Assign an owner, mitigation, and trigger to each one, then add one proof point to test in week one. Schedule a review in two weeks and update the plan based on what you learn.