Perform a Pre-Mortem Analysis for Product Launches

Generate a detailed risk assessment by imagining your product launch failed six months from now, categorized by adoption, infrastructure, and team capacity.

Prompt

Prompt
You are a Senior Product Manager. Your task is to conduct a pre-mortem analysis for a product launch. Imagine it is six months after the launch and the project has failed completely. Please ask me these three questions first and wait for my response: 1. What is the name and core goal of the product? 2. Who is the target user? 3. What is the most significant technical or market dependency for this launch? Once I provide the details, write the analysis. Rules: 1. Identify three specific failure drivers for each category: User Adoption, Infrastructure/Technical, and Team Bandwidth. 2. For each driver, provide a concrete 'Why it failed' explanation and a 'Preventative Action' to implement now. 3. Use a neutral, analytical tone. Output format: ## Pre-Mortem Analysis: Product Name. ### 1. User Adoption. [Table with columns: Failure Driver, Why it failed, Preventative Action]. ### 2. Infrastructure & Technical. [Table with columns: Failure Driver, Why it failed, Preventative Action]. ### 3. Team Bandwidth & Operations. [Table with columns: Failure Driver, Why it failed, Preventative Action]. This analysis is for planning purposes only and does not replace actual risk management processes.

Example output

Example for: A new mobile expense tracking app for small businesses. ## Pre-Mortem Analysis: ExpenseFlow Pro. ### 1. User Adoption. | Failure Driver | Why it failed | Preventative Action |
| :--- | :--- | :--- |
| Onboarding drop-off | Users found the initial sync process too complex. | Simplify the first-time setup to three steps. |
| Value gap | Users did not see immediate ROI in month one. | Add a quick-win dashboard summary feature. |
| Low retention | No habit-forming notifications were present. | Implement automated weekly summary alerts. | ### 2. Infrastructure & Technical. | Failure Driver | Why it failed | Preventative Action |
| :--- | :--- | :--- |
| API latency | Third-party bank connections timed out frequently. | Add localized caching for faster data retrieval. |
| Data inaccuracy | OCR failed to read receipts from small cafes. | Add a manual data correction override tool. |
| Scaling bottlenecks | Database locked during peak end-of-month usage. | Perform load testing with 5x expected volume. | ### 3. Team Bandwidth & Operations. | Failure Driver | Why it failed | Preventative Action |
| :--- | :--- | :--- |
| Support backlog | Queries exceeded capacity by 300 percent. | Create a self-service FAQ library before launch. |
| Feature creep | Dev team distracted by non-core requests. | Freeze feature scope 30 days before launch. |
| Knowledge silos | Only one engineer understood the sync logic. | Conduct cross-training sessions this week. | This analysis is for planning purposes only and does not replace actual risk management processes.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Forces the user to visualize failure to expose hidden blind spots.
  • Categorizes risks into distinct areas to ensure comprehensive coverage.
  • Requires specific preventative actions for every identified failure driver.

Use this prompt when you have a finalized launch plan and need to pressure-test your assumptions. Copy and paste the prompt into ChatGPT, Claude, or Gemini, answer the three questions, and receive your risk report.

Common edits

  • Add a fourth category for market competition if your space is crowded.
  • Include a section for 'Early Warning Signals' to help identify these issues sooner.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Product Management
Product Management

Define beta cohorts and launch exit metrics

Build a structured cohort plan and clear release criteria for your upcoming beta launch. Use this to prevent feature creep and ambiguous testing timelines.