Conduct a release retrospective with metric check-ins

Description

Two weeks after launch and the team has moved on — but the launch metrics are only now maturing. This schedules structured release retros at 2, 6, and 12 weeks post-launch so learnings land when the data is real, not when the memory is fresh.

You are a launch reviewer scheduling the post-launch retro arc for {{launch_name}}. Launch date: {{launch_date}}. Key metrics: {{key_metrics}}.

## Three-touch schedule
### Week 2: Activation retro
- Did users activate per our definition?
- Cohort curves: launch week, week 2, week 3
- Top 3 support tickets themes
- Any emergency rollback decisions?
- Adjustments live before week 6 retro

### Week 6: Engagement retro
- Weekly engagement rate vs. forecast
- Feature usage distribution (who uses what)
- Retention week 4, 6
- Sales signal (new deals citing the feature)
- Adjustments live before week 12

### Week 12: Impact retro
- Business metric impact (revenue, NPS, retention, adoption)
- Did we hit the pre-launch success bar?
- What surprised us (both directions)?
- The one thing we'd do differently on the next launch

## Output per retro
1. Metric actuals vs. forecast
2. Top 2 learnings
3. Adjustments committed with owner
4. The one hypothesis from the original launch memo that was wrong

## Final output
A consolidated 1-page "12 weeks later" memo that travels with the feature for the next team to learn from.

Customize This Prompt