pre-mortem

pre-mortem - Pre-Launch Product Risk Assessment

Skill Overview

pre-mortem is a risk assessment skill designed by experienced product managers. By assuming that a product launch has failed, it works backward to identify real risks, categorizing issues into three types: Tiger (real problems), Paper Tiger (overblown concerns), and Elephant (unspoken concerns), and developing mitigation plans based on urgency.

Use Cases

1. Pre-Launch Preparation

Use pre-mortem 2–3 weeks before the official product launch to conduct a comprehensive risk assessment of the PRD or launch plan, identify key factors that could prevent success, and ensure the team has sufficient time to resolve launch-blocking issues.

2. Product Plan Stress Testing

When the product team is overly optimistic about the plan or there is disagreement, expose hidden risks by assuming a failure scenario, validate core assumptions, distinguish real threats from overblown concerns, and help the team reach consensus.

3. Risk Identification and Management

Systematically identify various risks in product development, including technical defects, market acceptance, regulatory compliance, and customer dependencies. Assign an owner and deadline to each risk to establish an actionable risk mitigation plan.

Core Features

1. Intelligent Classification into Three Risk Categories

Accurately classify potential issues based on evidence and experience: Tiger represents evidence-based, real problems that require immediate action; Paper Tiger represents concerns that appear reasonable but are exaggerated, worth documenting but not worth significant resource investment; and Elephant represents unspoken concerns that the team has not discussed sufficiently and that require further investigation. This classification helps teams prioritize the risks that truly matter.

2. Urgency-Based Risk Management

Further categorize identified Tiger risks: Launch-Blocking risks must be resolved before launch, such as core functionality failures or regulatory obstacles; Fast-Follow risks must be resolved within 30 days after launch, such as performance issues or missing secondary features; Track risks can be continuously monitored and addressed as needed. This prioritization ensures that resource allocation matches the urgency of each risk.

3. Structured Action Plan Generation

Automatically generate an action plan for each Launch-Blocking Tiger, including a risk description, mitigation measures, owner, and completion date. Output a formatted PreMortem report to facilitate execution tracking and stakeholder updates on risk mitigation progress.

Frequently Asked Questions

What is pre-mortem analysis, and how does it differ from a traditional post-mortem?

A pre-mortem is a hypothetical failure analysis conducted before product launch. It identifies risks in advance by assuming that “the product has already failed” and determining the reasons why. The primary difference from a post-mortem is timing: a pre-mortem identifies problems while there is still time to take action, whereas a post-mortem summarizes lessons after a failure has occurred. The core advantage of a pre-mortem is its preventive nature—it can eliminate or mitigate risks before launch.

What do the three risk categories—Tiger, Paper Tiger, and Elephant—represent?

These terms come from the pre-mortem methodology: Tiger represents a real risk based on evidence or experience that could keep the project owner up at night and requires action; Paper Tiger is a concern that appears reasonable but has been exaggerated. Although it is worth documenting to align stakeholders, it should not receive significant resource investment; Elephant (the elephant in the room) represents an unspoken concern or unvalidated assumption that the team has not discussed sufficiently and that merits further investigation before launch. By default, classifying an issue as a Tiger is safer—caution is preferable to overlooking an important risk.

When should a pre-mortem analysis be conducted, and how long does it take?

Ideally, conduct the first pre-mortem analysis 2–3 weeks before product launch to allow sufficient time to resolve launch-blocking issues. If the product plan is complex or the team disagrees about the risks, the process can begin earlier. The analysis typically requires 1–2 hours of team discussion, in addition to the time needed to generate the skill’s analysis report. Reassessment before launch is recommended to confirm that mitigation measures are progressing as planned. pre-mortem is particularly suitable for risk assessment before launching a new product, releasing a major feature, or entering a new market.