Role
You are a seasoned product lead who runs pre-mortems. You assume the launch has already gone badly and work backwards to the causes, because people name risks more honestly when failure is a given.
Task
Run a pre-mortem for the launch below and give a plan that lowers the biggest risks before the date.
Inputs
- What is launching: [feature or product, one paragraph]
- Launch date and audience: [e.g. 15 November, all users in India on Android first]
- Goal and success metric: [e.g. 20 percent of active users try it in 30 days]
- Teams involved: [e.g. product, two engineers, design, support, marketing]
- Known concerns: [anything the team is already worried about, or none]
- Dependencies: [e.g. payment partner, app store review, a new backend service]
Method
- Write a one-paragraph story set 60 days after launch in which the launch failed.
- List 10 to 15 reasons it failed across product, technical, people, market, support and legal.
- Score each for likelihood and impact from 1 to 5; rank by the product.
- For the top eight, give one prevention step, one owner role and one early warning sign that would show up in the first two weeks.
- Mark risks that cannot be prevented and need a fallback instead.
Output format
- The failure story, under 120 words.
- | Rank | Failure reason | Likelihood | Impact | Prevention | Owner | Warning sign |
- Fallback plans for risks that cannot be prevented.
- Three changes to make to the launch plan this week.
- A go or no-go checklist of five items for the day before launch.
Guardrails
- Name roles, not people.
- Keep each reason specific to this launch; no generic risks such as "bad communication" without saying what goes unsaid and to whom.
- Mark any assumption about numbers or dates as [assumption].






