Definition
A post-launch review is the meeting that formally closes a product or feature launch by comparing its results with the goals and measures agreed before work began. It happens once those measures have had time to show a result, which depends on the size of the launch, and it brings together the owners of the launch's workstreams, a fuller group for a major launch than for a feature launch.
It looks back on one launch and forward to the next. Looking back, it records whether the goals were met and what helped or hurt, with evidence rather than impressions. Looking forward, it agrees what the business will do differently. The guide to measuring launch success owns the detail: when to hold it, who comes, the questions it asks in order and the measures each launch tier is read on. This entry covers what the review is and where it sits.
What it closes and what it feeds
The review closes the launch as a piece of work. Results are written down beside the goals, follow-ups that are still open, for instance more content or an adoption push, get named owners, and the record is stored with the plan rather than in someone's inbox.
What it feeds matters more. The measurement guide expects the lessons to land as changes to three shared things: the launch template, the criteria that decide each launch's tier, and the bill of materials listing what each tier produces. A review that ends in good intentions changes nothing; one that edits those shared materials carries into the launches after it. Kept together over time, the written reviews show what each tier can be expected to deliver, which gives later plans targets grounded in the business's own record.
In practice: tiers, intake, the launch playbook and launch plans
The guide to launch planning and tiers treats the weeks after launch as a phase of their own, with adoption campaigns and sales follow-up, and ends that phase with a review that closes the launch formally and sends its lessons back into the template. The tutorial on running launch intake adds one standing question to every review: did the release reach product marketing early enough, was its tier right, and was it re-tiered when its scope or date moved? When reviews keep finding the same gap, the intake form or the criteria change.
The product launch playbook books the review at a checkpoint agreed at kick-off. There the analyst sets results beside the goal, drawing on the launch dashboard, the feedback log and the readiness tracker's history, and the launch owner adds a short look at the process: which gates earned their place and where the timeline slipped. The SOSTAC page for launches separates launch-window targets from later adoption targets and warns that the quick launch-window numbers tend to crowd the slower adoption picture out of the review.
A language app closes a feature launch
Gidduan Languages, an invented language-learning app, launched a speaking-practice feature with two goals: 8,000 new sign-ups in the launch fortnight and 25% of active learners completing 3 speaking lessons within 6 weeks. At the review, held 6 weeks after launch day, sign-ups stood at 11,400, but only 9% of active learners had completed 3 lessons; 41% had opened the first, and most of those who had not opened it stopped at the microphone permission screen. Support noted that it had been briefed 2 days before launch and spent the first week answering microphone questions. The team added a short in-app sequence that explains the microphone permission before the first spoken lesson to the bill of materials for feature launches, and moved the support briefing in the launch template to a week before launch day.
Related terms
A Readiness GateA go-live check that confirms the work is built, such as tracking, pages, stock, support and legal review, before a launch, market entry or peak goes ahead. is checked before anything goes live; the review is where the team asks which gates proved their worth and which were missing. A ReadoutThe meeting or short document where a study's or test's results are presented against the decision it was run for, ending in a recorded decision. presents one study's or test's results against the decision it was run for, whereas the review covers a whole launch across many workstreams. A Team RetrospectiveA planned look at how a team worked over a period, separate from what its campaigns achieved, ending in one or two owned changes with a date. reviews the team's own way of working across a stretch of time, apart from results; a post-launch review can include a brief process look of that kind, but it is tied to one launch and its results. The review checks the launch part of a Go-to-Market StrategyThe plan for how a product or offer reaches and wins its target customers. plan against its goals, and each KPIA metric tied directly to an objective. agreed before launch is one of the measures it reads.
Common confusions
- It is the campaign wrap-up. Wrapping up the paid campaigns confirms they have stopped and their figures are final; the review then reads those figures alongside adoption, sales and support.
- It is a test readout. A readout settles one test's decision; the review closes a launch with many moving parts.
- It is the team's regular retrospective. The review may take a short look at the launch process, as the product launch playbook does, but a periodic retrospective covers how the team worked over a stretch of time, whatever it was working on.
- It checks the launch page before go-live. Checks before launch belong to readiness gates and QA; the review comes afterwards.
- It can be held in launch week. In launch week attention and first sign-ups are visible, while adoption, the better guide to whether the product lasts, has had little time to show.
