Skip to content
Ever Works

Pre-Mortem Analysis

Project planning technique where teams imagine the project has already failed and work backward to identify risks. Research shows it increases accurate risk forecasting by 30%.

Last updated: 2026-03-15 06:45

Overview

Pre-mortem analysis is a project planning technique developed by psychologist Gary Klein where teams imagine a scenario where a project has already failed, then work backward to identify the factors that could lead to that failure. This proactive approach helps teams anticipate and mitigate risks before they occur.

Core Concept

Unlike a post-mortem (which analyzes failure after it happens), a pre-mortem assumes failure will happen and asks "Why?" This mental time travel helps overcome optimism bias and surfaces risks teams might otherwise overlook.

Research Backing

Forecasting Accuracy

Research suggests that mentally transporting to the future increased the ability to accurately forecast risks by 30%.

Psychological Benefits

How to Conduct a Pre-Mortem

Timing

Ideally conduct 1-3 months before project launch, allowing sufficient time to address identified issues.

Step-by-Step Process

1. Set the Scene (5 minutes)

Facilitator explains: "It's [date 6-12 months from now]. Our project has failed spectacularly. It's a complete disaster."

2. Individual Brainstorming (5-10 minutes)

Each team member independently writes down reasons for the failure:

3. Share Failures (15-20 minutes)

Round-robin sharing:

4. Categorize Risks (10 minutes)

Group similar failure reasons:

5. Prioritize (10 minutes)

Rank risks by:

6. Develop Mitigations (20-30 minutes)

For top risks, create action plans:

7. Document and Schedule Review (5 minutes)

Sample Pre-Mortem Questions

Project Failure Scenarios

Specific Risk Categories

Team & Resources:

Communication:

Technical:

External:

Benefits

Proactive Risk Management

Team Dynamics

Better Planning

Project Success Rates

Variations

Pre-Mortem for Personal Goals

Adapt for individual planning: "It's one year from now. I completely failed at [goal]. Why?"

Pre-Parade

Opposite approach - imagine wild success: "It's one year from now. We exceeded every goal. How?"

Pre-Mortem + Pre-Parade

Run both for balanced perspective:

Common Mistakes

Skipping It: "We don't have time" - but finding time now prevents disasters later

Superficial Analysis: Stopping at obvious risks, missing subtle ones

No Follow-Through: Identifying risks but not creating mitigation plans

Defensive Posture: Team members getting defensive about potential failures

Ignoring Outliers: Dismissing "unlikely" scenarios that could be catastrophic

One and Done: Not revisiting as project evolves

When to Conduct Pre-Mortems

Project Lifecycle

Types of Projects

Especially valuable for:

Integration with Other Methods

With Agile

With Risk Registers

With Project Planning

Comparison: Pre-Mortem vs Post-Mortem

Pre-Mortem:

Post-Mortem:

Tools and Templates

Digital:

In-Person:

Success Metrics

How to know if pre-mortem was effective:

Best Practices

  1. Create Psychological Safety: Encourage honesty without blame
  2. Diverse Perspectives: Include different roles and viewpoints
  3. Be Specific: Vague risks get vague solutions
  4. Assign Ownership: Each risk needs a mitigation owner
  5. Set Review Cadence: Revisit as project progresses
  6. Document Everything: Future you will forget details
  7. Follow Through: Identify risks is useless without action
  8. Balance with Optimism: Don't demoralize team

Related Items