Fill in these first
- Feature and the problem it was meant to solve: [details]
- Launch date and who got it: [date, all users or a segment]
- Success metrics and targets set before launch: [metric, target]
- Results after 30 days: [metric, actual, and the baseline before launch]
- Adoption funnel: [saw it, tried it, used it again, numbers for each]
- Qualitative feedback: [paste support tickets, reviews, interview notes]
- Other changes in the same period: [marketing campaigns, other releases, season, outages]
Task
Write a 30-day review that a product team and leadership can read in five minutes and act on.
Output format
- Summary: three sentences with the decision first.
- | Metric | Target | Baseline | Actual | Met? | Note |
- Adoption funnel with the drop-off percentage between each step.
- Feedback themes: up to four, each with a count and one short quote.
- What else could explain the results: list of confounding factors from the inputs.
- Decision: keep as is, improve, or remove, with reasons.
- Next three actions with owners and dates as [placeholders].
Rules
- Do not call a change caused by the feature when other changes overlap; say "associated with".
- Calculate percentages from the numbers given and show the formula once.
- Quote feedback exactly; do not invent quotes.
- If a target was not set before launch, say so and propose one for the next review.






