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
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
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.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Stress Test Your Product Requirements Document for Edge Cases
This prompt audits your feature PRD to identify hidden technical risks, permission gaps, and scope creep before development begins.
Create a quarterly win-loss brief for sales teams
Summarize win-loss trends into a sales-facing digest that highlights product fixes, winning tactics, and pipeline roadblocks. Use it to keep reps logging CRM data.
Design an A/B Test Plan with Sample Size Math and Pre-Set Stop Rules
Get a complete A/B test plan with one primary metric, a clear hypothesis, a worked sample size calculation, runtime, and stop rules fixed before launch.
Write a Stakeholder Update That Leads with Decisions, RAG Status and Risk Owners
Turns your raw product notes into a short stakeholder update: decisions needed first, red/amber/green status per initiative, and every risk with an owner and next step.
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.
Draft high-usage account outreach for product deprecation
Generate a personalized, low-friction outreach email to alert high-usage customers about an upcoming product deprecation.