wowprompt

Pre-mortem for a product launch with risks and warning signs

Runs a pre-mortem on a feature or product before it ships: imagines the launch has already failed, lists the most likely reasons, and turns each into an owner, a prevention step and an early warning sign. Use it a week or two before launch, while there is still time to change the plan.

A ranked table of failure reasons with likelihood, impact, prevention steps and owners, a list of early warning signs to watch after launch, and three changes to make to the plan now
The output this prompt produced, unedited.

The prompt

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

  1. Write a one-paragraph story set 60 days after launch in which the launch failed.
  2. List 10 to 15 reasons it failed across product, technical, people, market, support and legal.
  3. Score each for likelihood and impact from 1 to 5; rank by the product.
  4. 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.
  5. Mark risks that cannot be prevented and need a fallback instead.

Output format

  1. The failure story, under 120 words.
  2. | Rank | Failure reason | Likelihood | Impact | Prevention | Owner | Warning sign |
  3. Fallback plans for risks that cannot be prevented.
  4. Three changes to make to the launch plan this week.
  5. 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].
pre mortemlaunch riskproduct launchrisk registerproduct managementlaunch readiness

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity