Product Launch Checklist
Write the one sentence, watch five real users, brief support before launch, and decide what success looks like as a number before you ship it.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Product Launch Checklist?
Launches fail quietly rather than dramatically. Nobody could tell what the product was for, support had not been told it was coming, and there was no way to measure whether anything happened. The technical release is the easy part and the only part most checklists cover.
Two items do disproportionate work. Writing what it does and who it is for in one sentence, which exposes disagreement before the copy does. And writing down what success looks like as a number before launching, because afterwards any outcome can be presented as a success.
- Covers the non-technical half: messaging, people and measurement
- Puts accessibility and data protection before launch, where they are cheap
- Treats a launch as a planned incident window with a tested rollback
- Requires a success number written down in advance
- Editable and exportable as PDF, CSV, Markdown or a Google Form
Updated
How to use the Product Launch Checklist
- Write what it does and who it is for in one sentence, and check the team agrees.
- Watch five real users complete the main task, test on a real phone, and check accessibility.
- Settle the data protection questions and confirm pricing, tax and refunds work end to end.
- Brief support and anyone customer-facing, including what not to promise, and test the rollback.
- Write down what success looks like as a number, verify tracking yourself, and review on a set date.
Worked examples
A fortnight before launch
Input
Ready and findable sections
Output
One sentence agreed, five users watched, docs written, indexable
User testing is the first thing dropped and the most valuable.
Launch week
Input
People ready section
Output
Support briefed, escalation agreed, rollback tested
A launch is a planned incident window.
Two weeks after
Input
Measure section
Output
Reviewed against the pre-written number
Deciding success afterwards teaches nothing.
Background and insight
Watching five real users complete the main task without help finds the obvious problems, and it is the step most often dropped under deadline pressure, which is exactly when it is most valuable. The same applies to testing the whole journey on a real phone on a slow connection rather than a resized browser on office wifi.
Accessibility belongs before launch rather than in a later milestone, both because an inaccessible product excludes people and because it carries legal risk in many jurisdictions. Keyboard navigation and screen reader use are the two checks that find most of it.
Data protection is also far cheaper before launch. Working out what personal data the product collects, whether there is a lawful basis, how long it is kept and whether the privacy notice says so is substantially harder to retrofit once there is live data.
On the people side, support finding out from a customer is the clearest sign of an uncoordinated launch, and the commitments made by customer-facing staff in the first week tend to become the roadmap. Both are prevented by a briefing that includes what not to promise.
A launch is a planned incident window, which is why a tested rollback or feature flag and an agreed decision-maker belong on the list. Being able to turn it off is more valuable than being confident it works.
Finally, the measurement items. Verifying the tracking by completing the journey yourself beats trusting a setup screen, an obvious feedback route read daily for a fortnight catches what analytics cannot, and reviewing against the pre-written number at a date set in advance is what turns a launch into something you learn from.
Common use cases
Launching a new product
The non-technical half that decides whether it lands.
Shipping a significant feature
The same checks at a smaller scale, especially support and rollback.
A small team without a launch process
Something repeatable that fits in a day of preparation.
Learning from a launch
Defining success in advance so the review means something.
Tips and limitations
- If three people write three different one-sentence descriptions, fix that before the copy.
- Test a real refund. It is the path nobody tests and everybody eventually uses.
- Check how the link renders when shared; the preview is most of the click decision.
- Brief support with the known issues and the answers, not just the announcement.
- Watch support volume as well as error rates. A wave of confused questions is a messaging failure.
Sources and further reading
- Search Essentials, Google Search Central. Making a new product findable in search
- Web Content Accessibility Guidelines (WCAG) 2.2, W3C. The accessibility baseline to meet before launch
- Data protection, UK Government. Lawful basis, retention and privacy notices
Frequently asked questions
What makes product launches fail?
Usually not the technology. Unclear messaging so nobody could tell what it was for, customer-facing staff who were not briefed, no obvious feedback route, and no agreed measure of success, so the launch produced no decision either way.
How many users should I test with before launch?
Five is enough to find the obvious problems in a main task, which is the point before launch. Watch them without helping, because the moment you explain how it works you have lost the information you were gathering.
How do I measure whether a launch worked?
Write down the number that would mean success before you launch, verify the tracking by completing the journey yourself, then review against that number on a date you set in advance. Deciding success afterwards means any outcome can be a win.
What does support need before a launch?
What the product is, who it is for, the known issues with the answers, and explicitly what not to promise. Support hearing about a launch from a customer is the clearest sign that the launch was not coordinated.
Do I need a rollback plan for a launch?
Yes, and a tested one. A feature flag or a rollback path you have actually exercised matters more than confidence that it works, because a launch is a planned incident window and being able to turn it off is the cheapest insurance available.
Is there an in-depth guide to the Product Launch Checklist?
Yes. “Why Checklists Work, and How to Use One Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.