Design a 90-day launch metric review

90-Day Reviews: The Honest Launch Post-Mortem

Most launches are declared successes based on activation metrics — and activation is almost always the weakest signal of long-term value. Amplitude's North Star framework writing argues that sustained engagement at 90 days is the minimum credible signal for feature value, and that early activation without retention frequently masks feature failure. Reforge's retention research notes that the 90-day review often produces the opposite call from the week-1 celebration — and the team that runs it saves engineering from investing further in a loser.

How the Design a 90-day launch metric review Prompt Works

The prompt quantifies seven metrics against the pre-committed bar, demands a four-way decision (double down / sustain / reduce / sunset) rather than a vague "continue," and produces a 1-page memo with the flip condition. The flip condition — the one input that would have changed the decision — is the forcing function that makes the decision defensible and updatable.

When to Use It

• A feature launched 3 months ago and no one has reviewed sustained impact.
• Leadership is asking "how did that launch do" and nobody can answer.
• An engineering team is maintaining features with unclear ROI.
• A portfolio prune is coming and you need per-feature data.
• A new PM is inheriting a post-launch portfolio.

Common Pitfalls

• Measuring only activation. Week-1 activation is an almost-guaranteed positive signal. It says little about long-term value.
• No pre-committed success bar. Without a bar, any review will rationalize toward "keep going."
• Avoiding the sunset option. Features that don't clear the bar rarely turn around with time. Keeping them is maintenance debt.

Sources

• The North Star Framework — Amplitude
• Retention, Engagement & Growth: The Silent Killer — Reforge
• Amplitude Blog — Amplitude
• Google re:Work — Google