# Run a post-launch review of a feature

A blameless look at whether a shipped feature worked, what we learned, and whether to iterate, scale, or kill it.

- Topic: Product & UX Design
- Framework: RTF
- Level: Standard
- Tags: Write, Analyze, Fill-in Template
- Source: https://www.thinkwithprompt.com/prompts/run-a-post-launch-review-of-a-feature

## Prompt

```text
Help me write a post-launch review of a feature we shipped.

**Feature and launch date:** [DETAILS]
**Original goal and success metric:** [WHAT WE SAID SUCCESS WOULD BE]
**Results so far:** [METRICS VS. TARGET, ADOPTION, RETENTION OF ADOPTERS]
**Qualitative signals:** [FEEDBACK, TICKETS, SALES OR SUPPORT ANECDOTES]
**What went well and badly in delivery:** [SCOPE, TIMING, QUALITY, COORDINATION]
**Cost so far:** [TEAM TIME, ONGOING MAINTENANCE]

Write the review with:
1. Verdict in two sentences: did it achieve the goal?
2. Results versus targets, with caveats on data quality or time since launch.
3. Why: which original assumptions held and which were wrong.
4. Delivery lessons: what to repeat and what to change (process, not people).
5. Decision: iterate, scale, maintain as-is, or sunset. Give the reasoning and the specific next steps for the chosen path.
6. Follow-up questions to research.

Rules: blameless tone. Separate correlation from causation, and say if results cannot be attributed to the feature. Do not invent metrics; mark [ADD DATA]. Under 600 words.
```

## What to fill in

- DETAILS
- WHAT WE SAID SUCCESS WOULD BE
- METRICS VS. TARGET, ADOPTION, RETENTION OF ADOPTERS
- FEEDBACK, TICKETS, SALES OR SUPPORT ANECDOTES
- SCOPE, TIMING, QUALITY, COORDINATION
- TEAM TIME, ONGOING MAINTENANCE
- ADD DATA

Free to copy and use. From ThinkWithPrompt (https://www.thinkwithprompt.com/), a library of 2,663 curated AI prompts.