Run a Post-Launch Retrospective Comparing Goals to Actual Results
Get a blameless launch retrospective with a goal-versus-actual table, facts kept apart from causes, and lessons that each carry an owner and a change for the next launch.
You getSummary, goal vs actual table and what happened
Prompt
You are a senior product manager who runs blameless post-launch retrospectives.
I will paste my launch material right after this prompt: the original goals or success metrics, the actual results, and any notes, timelines or team feedback. If the goals or the actual numbers are missing, ask me up to 3 numbered questions in one message and wait for my answers before writing anything.
Rules:
1. Compare every stated goal to its actual result, show the gap as a number or percent, and mark each Hit, Partial or Missed.
2. Keep "What happened" (observable facts, dates, numbers) separate from "Why it happened" (causes). Tag each cause as Confirmed by data or Hypothesis.
3. Blame decisions and processes, not people.
4. Every lesson ends with one owner (a role) and one specific, checkable change for the next launch.
5. Use only the numbers I provide. Never invent metrics, benchmarks or quotes.
Output format:
1. Summary (3 sentences max)
2. Goal vs actual table: Goal | Target | Actual | Gap | Status
3. What happened (dated bullet timeline)
4. Why it happened (causes, each tagged Confirmed or Hypothesis)
5. Lessons table: Lesson | Owner | Change for next launch
6. Open questions
End with one line naming the biggest data gap or assumption that could change these conclusions.Example output
Tips and common edits
Why this works
- The Gap and Status columns force a numeric comparison, so missed goals cannot hide behind vague wording.
- Separating facts from causes and tagging each cause Confirmed or Hypothesis stops guesses from becoming conclusions.
- Requiring an owner and a next-launch change for every lesson turns the retro into action items.
Use 4-8 weeks after a launch. Have your original goals, the actual metrics and any launch notes ready to paste into ChatGPT, Claude or Gemini. Works for features, pricing changes or full products.
Common edits
- Ask for a one-paragraph executive version to share with leadership.
- Add a column for impact on revenue or retention if you track it.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Analyze Your Product Funnel and Find the Biggest Drop-Off to Fix First
Paste your funnel step counts and get a conversion table, the largest leak flagged with reasoning, and one testable fix per step with an expected lift range.
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.
Interpret A/B Test Results and Decide Whether to Ship, Iterate or Kill
Paste your A/B test numbers and get a Ship, Iterate or Kill verdict backed by significance, sample ratio, guardrail checks and a list of what the data cannot prove.
Diagnose a Sudden Metric Drop with a Ranked List of Likely Causes
Get a ranked table of likely causes for a metric drop, covering tracking, segments, platforms, releases, seasonality and external factors, each with an exact check.
Write a Go-to-Market Launch Plan with Owners, Dates and Go/No-Go Criteria
Get a tiered launch plan with a T-minus timeline, one owner role per task, measurable go/no-go criteria, an hour-by-hour launch-day checklist and week-one metrics.
Write an Event Tracking Plan Where Every Event Maps to a Success Metric
Get a tracking plan table with object_action event names, exact triggers, typed properties and the success metric each event feeds, plus a list of events to cut.