Pre-Mortem Retrospective: Prevent Failure Before It Happens

What if you could learn from your failures before they happen? That’s the power of a Pre-Mortem retrospective—a technique where teams imagine their project has failed and work backward to identify what could have caused it.

Unlike traditional risk planning, the Pre-Mortem unlocks deeper insights by making failure feel real. This guide shows you how to run one effectively.

What Is a Pre-Mortem Retrospective?

A Pre-Mortem (also called a premortem or prospective hindsight) flips the typical retrospective. Instead of looking back at what happened, you imagine looking back from a future where things went wrong.

The setup:

“It’s [future date]. The project has failed spectacularly. What went wrong?”

By framing failure as certain (not possible), you bypass optimism bias and surface risks that people might otherwise dismiss.

Origin

The Pre-Mortem technique was popularized by psychologist Gary Klein. His research showed that prospective hindsight—imagining a future event has already occurred—increases the ability to identify reasons for outcomes by 30%.

Pre-Mortem vs Post-Mortem

Aspect	Pre-Mortem	Post-Mortem
Timing	Before/during project	After project/incident
Focus	Potential failures	Actual failures
Purpose	Prevention	Learning
Failure status	Imagined	Real
Emotional state	Low stakes (hypothetical)	High stakes (real impact)

Why Pre-Mortems Work

Defeats Optimism Bias

Teams naturally focus on how things will succeed. Pre-Mortems force pessimistic thinking that wouldn’t otherwise emerge.

Makes Concerns Speakable

Framing failure as “already happened” gives permission to voice worries:

❌ “I think this deadline is unrealistic” (sounds negative)
✅ “The project failed because the deadline was unrealistic” (just describing failure)

Surfaces Hidden Risks

Different team members see different risks. The Pre-Mortem format draws out diverse perspectives.

Creates Psychological Safety

It’s safer to critique a hypothetical failure than to criticize current plans.

Drives Proactive Action

Identified risks lead to prevention strategies, not just acknowledgment.

When to Use a Pre-Mortem

Project Kickoffs

Before starting major work, identify what could derail you.

Mid-Project Check-ins

Halfway through, reassess risks with updated context.

Before Major Releases

Before launch, surface last-minute concerns.

Sprint Planning

Quick Pre-Mortem on sprint goals: “If we miss this sprint goal, why?”

High-Stakes Decisions

Before committing to important decisions, Pre-Mortem the negative outcomes.

Best For

Attribute	Recommendation
Team size	4-12 people
Experience level	Any
Duration	45-60 minutes
Best timing	Project start, before releases, critical decisions

How to Run a Pre-Mortem Retrospective

Before the Meeting

Define the scope - What project/feature/goal are you Pre-Morteming?
Set the future date - When would failure be apparent?
Prepare the prompt - Write out the failure scenario
Gather context - Current plans, timeline, goals

Step-by-Step Facilitation

Step 1: Set the Scene (5 minutes)

Create the mental shift:

“Close your eyes for a moment. It’s [specific future date]. Our [project/feature/goal] has failed. Not just underperformed—failed completely. I need you to accept this as fact: it failed.”

Let this sink in for 10-15 seconds.

“Now, open your eyes. Your job is to explain what happened. What went wrong? Why did we fail?”

Step 2: Individual Brainstorming (10 minutes)

Everyone writes failure reasons:

One reason per sticky note/card
Write in past tense (“The deadline was too aggressive”)
No discussion yet—capture individual perspectives
Encourage specific scenarios, not vague risks

Step 3: Share and Group (15 minutes)

Collect all failure reasons:

Go around the room, each person shares one reason
Place on board
Group similar reasons
Continue until all reasons are shared
Avoid debating—just collect

Step 4: Prioritize Failures (10 minutes)

Vote on most likely/impactful failures:

Each person gets 3-5 votes
Can vote on likelihood OR impact
Identify top 5-7 failure modes

Step 5: Develop Prevention Strategies (15-20 minutes)

For each top failure:

“How could we prevent this?”
“What early warning signs should we watch for?”
“What would we do differently?”

Create specific, actionable prevention plans.

Step 6: Assign Ownership (5 minutes)

Each prevention strategy needs:

An owner responsible for implementation
A timeline or trigger
How success will be measured

The Key Prompt

The framing matters. Use strong, definitive language:

Strong:

“It’s January 15th. The project has completely failed. We missed the deadline by 3 weeks, went 50% over budget, and the client is furious. What happened?”

Weak:

“What might go wrong with our project?”

The strong version makes failure feel real, unlocking deeper insights.

Pre-Mortem Template

┌─────────────────────────────────────────────────────────────────────┐
│                    PRE-MORTEM: [PROJECT NAME]                       │
│                                                                     │
│  "It's [DATE]. The [project] has failed completely.                 │
│   What went wrong?"                                                 │
├─────────────────────────────────────────────────────────────────────┤
│                                                                     │
│  FAILURE REASONS                           VOTES                    │
│  ────────────────                          ─────                    │
│  • Requirements kept changing               ●●●●●                   │
│  • Key team member left mid-project         ●●●●                    │
│  • Integration with System X failed         ●●●●                    │
│  • Underestimated testing time              ●●●                     │
│  • Stakeholder expectations misaligned      ●●●                     │
│  • Technical debt slowed everything         ●●                      │
│  • Team burnout from overtime               ●●                      │
│                                                                     │
├─────────────────────────────────────────────────────────────────────┤
│  PREVENTION STRATEGIES                                              │
│  ────────────────────                                               │
│                                                                     │
│  Failure: Requirements kept changing                                │
│  Prevention: Lock requirements after Day 5, change control process  │
│  Owner: Product Manager                                             │
│  Warning Sign: More than 2 changes per week                         │
│                                                                     │
│  Failure: Key team member left mid-project                          │
│  Prevention: Document knowledge, pair programming, retention check  │
│  Owner: Team Lead                                                   │
│  Warning Sign: Team member expressing dissatisfaction               │
│                                                                     │
└─────────────────────────────────────────────────────────────────────┘

Sample Pre-Mortem Questions

To Surface Failures

“What caused us to miss the deadline?”
“Why did the customer reject our work?”
“What made the team fall apart?”
“Why did the technology fail us?”
“What did we not see coming?”

To Develop Prevention

“How could we have prevented this?”
“What warning signs should we watch for?”
“What would we do differently from Day 1?”
“Who should be responsible for monitoring this risk?”
“What’s the earliest intervention point?”

To Test Robustness

“Even if we do X, could this still fail? How?”
“What’s our backup plan if this prevention doesn’t work?”
“Is this risk completely preventable, or just reducible?”

For discussion prompts that pair well with this format, see our retrospective questions guide.

Tips for Facilitating Pre-Mortems

1. Commit to the Failure Premise

Don’t say “imagine it might fail”—say “it has failed.” The certainty is what unlocks insight.

2. Encourage Wild Scenarios

Some of the best insights come from unlikely-sounding failures:

“What if our entire team got sick?” → Cross-training and documentation “What if our main tool went down?” → Backup processes

3. Separate Brainstorming from Evaluation

During collection, don’t debate whether failures are realistic. Capture everything first, evaluate later.

4. Include External Factors

Failures aren’t always within team control:

Market changes
Organizational shifts
Vendor problems
Economic factors

5. Make It Safe

Some failures involve calling out gaps in plans from leaders. Reinforce that all concerns are valuable.

6. Follow Through

A Pre-Mortem without action is just anxiety generation. Convert every key risk into a prevention strategy with an owner.

Common Pre-Mortem Failures to Consider

Technical

Technology doesn’t work as expected
Integration with other systems fails
Performance doesn’t meet requirements
Security vulnerabilities discovered
Technical debt slows development

People

Key team member leaves
Team burnout from overtime
Skills gap discovered too late
Stakeholder conflicts
Communication breakdown

Process

Requirements change constantly
Timeline was unrealistic
Dependencies not managed
Testing insufficient
Release process problems

External

Budget cut mid-project
Organizational priority shift
Vendor/partner failure
Market conditions change
Regulatory requirements change

Pre-Mortem Variations

Speed Pre-Mortem

Compressed version (20 minutes):

State the failure scenario (2 min)
Everyone writes 3 failures (3 min)
Quick share and vote (5 min)
Discuss top 3 (7 min)
One action per failure (3 min)

Category Pre-Mortem

Structure failures by type:

Technical failures
Process failures
People failures
External failures

Optimistic Pre-Mortem (“Pre-Parade”)

Flip it: “The project was a massive success. What happened?” Then compare pessimistic and optimistic scenarios.

Rolling Pre-Mortem

At each sprint planning:

“If this sprint fails, why?”

Quick ongoing risk check.

Pre-Mortem vs Other Formats

Pre-Mortem vs Futurespective

Aspect	Pre-Mortem	Futurespective
Assumption	Failure has occurred	Success has occurred
Focus	Risks and prevention	Enablers and planning
Tone	Pessimistic	Optimistic
Best for	Risk identification	Goal alignment

Use both: Pre-Mortem for risks, Futurespective for opportunities.

Pre-Mortem vs Traditional Risk Assessment

Aspect	Pre-Mortem	Risk Assessment
Frame	Failure is certain	Risks are possible
Engagement	High (story-based)	Lower (list-based)
Insights	Deeper, more diverse	Standard, expected
Format	Collaborative session	Often individual/small group

Pre-Mortem surfaces risks that standard risk assessment misses.

If you find Pre-Mortems valuable, try:

Futurespective - Optimistic future-looking
Timeline Retrospective - Chronological reflection
Six Thinking Hats - Black Hat = risks
Sailboat Retrospective - Rocks = upcoming risks

See our complete sprint retrospective formats guide for 30+ options.

Run Pre-Mortem with RetroFlow

Most retro tools charge per user or cap free boards at 3. RetroFlow doesn’t — every feature is free, no account needed. Share a link and your team starts contributing in seconds.

Start Free Retrospective →

Retrospective Formats Retrospectives Facilitation