<!-- Post-launch review · from Chapter 25 of The Product 360 Handbook -->

# Post-launch review · [Launch name] · [30 / 90] days · [Date]

**Owner:** [PM]   **Reviewed by:** [senior reviewer]   **Blameless:** we review systems and decisions, not people.

## Prediction against actual
| Metric | Type | Baseline | Predicted | Actual | Read |
|---|---|---|---|---|---|
| | Leading | | | | Above / on / below |
| | Lagging | | | | |
| | Guardrail | | | | |
| | Reach | | | | Reported only |

## What happened
Timeline of the launch and any incidents, rollbacks or stage changes: [ ].

## Why it differed
[Causes, with evidence. Include customer and support signals, not only dashboards.]

## Was the go/no-go right?
Conditions set: [ ]. Were they met on time? Was any risk acceptance justified?

## AI behavior (AI features only)
Production quality eval trend; behavior complaints from support and community; any model or infrastructure change since launch.

## Changes
| Change | In the product or the launch process? | Owner | Due |
|---|---|---|---|
| | | | |

## Stage decision
[Promote / hold / roll back], decided by [name] on [date]. Shared with [ ] and stored in [ ].
