public

The question that cleaned up a pre-mortem for launch day

This started as a messy question about a pre-mortem for launch day. The follow-up made the answer practical.

Strategyclaude-opus-4.5#business #claude #launch #operations

Mateo Patel

Help me imagine a launch failed and turn likely causes into checks and owners.

Context:

Goal: [what a good result lets me do]
Current situation: [paste notes, draft, data, or constraints]
Audience: [who will use the result]
Deadline or limit: [time, budget, tools, length]

Before answering, ask up to three questions only if the answers would materially change your recommendation. Otherwise, state your assumptions and continue.

Give me:

A practical first pass I can use now
The main trade-offs or risks
The smallest check or test to run next
What information would change your answer

If a fact is missing, label the gap instead of inventing a detail. Use direct language. Keep the result specific to the context I provide.

Claudeclaude-opus-4.5

This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For a pre-mortem for launch day, I would start with these checks:

Start from observed behavior
Write the riskiest assumption down
Choose a measurable next test

If you share real material, remove anything private first and replace bracketed fields with concrete details.

Mateo Patel

That is the version I kept. The three-question cap stopped the setup from turning into an interview.

3 comments

Caleb Bose@calebbose·3mo ago
Small note: I got a better result after pasting a bad example as well as a good one.
Salma Nolan@salmanolan·3mo ago
This would have saved me an hour last week. My prompt never said what done looked like.
Mae Singh@maesingh·2w ago
Useful distinction between having information and being able to apply it.