Premortem Analysis

Overview

Unlike a “postmortem,” which analyzes why a project failed after the fact, a “Premortem” is a proactive strategy conducted at the start of a project. By imagining that the project has already failed and then working backward to determine the causes, this model allows teams to bypass optimism bias and identify hidden risks before they materialize.

Rating (1–5)

• Applicability: 5
• Immediacy: 4
• Difficulty to Understand: 3
• Misuse Risk: 2

Evaluation Comment

Extremely effective for making project risks visible and actionable. However, if the team over-indexes on pessimistic scenarios without developing countermeasures, it can lead to “analysis paralysis” or a loss of momentum.

The First Question

“Imagine we are one year into the future and this project has been a complete disaster. What went wrong?”

Objectives

• To surface latent risks that are often suppressed during the “honeymoon phase” of a project.
• To dismantle “Optimism Bias” and groupthink.
• To foster a culture where voicing concerns is seen as a contribution to success.

Poor Questions

• “Let’s just assume everything goes according to plan for now.” (Ignores the reality of uncertainty)
• “What are some things that might go wrong?” (Too weak; does not trigger the same creative “hindsight” as assuming failure has already occurred)

How to Use (Step-by-Step)

1. Define the Plan

   • Briefly review the current plan or hypothesis.

2. Imagine the Failure

   • State clearly: “The project has failed spectacularly.” Create a mental space where the disaster is a certainty.

3. Generate Reasons for Failure

   • Have participants brainstorm and list every possible reason why the project failed. Be specific (e.g., “The competitor launched a similar feature two months earlier”).

4. Develop Countermeasures

   • Review the list of reasons and design specific actions to prevent these scenarios or mitigate their impact.

Output Examples

1. Risk-Mitigation Log

• Imagined Failure A: The user interface was too confusing for our core demographic.
  • Countermeasure: Schedule usability testing sessions every two weeks during the development phase.
• Imagined Failure B: Key team members left the project mid-way.
  • Countermeasure: Cross-train team members and improve documentation to reduce dependency on individuals.

2. Visualization

• Risk Tree: A branching diagram showing the primary failure at the top and various contributing causes branching out below.
• Pre-emptive Action Map: A table mapping “Potential Failure Points” to “Current Defensive Measures.”

Use Cases

• Business: Before launching a major project, entering a new market, or implementing a significant organizational change.
• Daily Life: Before making life-altering decisions (e.g., moving to a new city, starting a business).
• Judgment / Thinking: When you feel a dangerous level of “overconfidence” in a plan.

Typical Misuses

• Pure Pessimism: Listing risks but failing to create actionable countermeasures, leading to fear instead of preparation.
• Treating Risks as Facts: Assuming every imagined risk is a certainty, which can lead to unnecessary over-engineering.
• Surface-level Brainstorming: Only listing obvious risks rather than digging for the “uncomfortable” structural blind spots.

Relationship with Other Models

• Related: Second-Order Thinking, Bayesian Thinking (updating based on new scenarios).
• Complementary: Risk-Reward Thinking, Cognitive Bias Awareness (counteracting optimism bias).