Feature launch checklist template
Everything that has to happen before, on and after launch day, with an owner for each item.
Use this templateFree, opens in your browser. No sign-up.
What is a feature launch checklist?
A feature launch checklist lists everything that has to happen for a feature to reach customers well: a goal to measure, a way to turn it off, help content, a trained support team, the announcement and a review afterwards. Launches rarely stumble on the code. They stumble because the help article wasn't ready, sales heard about the feature from a customer, or nobody checked the numbers two weeks later.
This template is a timeline in four columns: four weeks before (plan), one week before (ready), launch day, and two weeks after (learn). Every item has an owner in brackets, such as PM, Eng, Support or Marketing, so it's clear who is responsible for it.
What's on the board
- T−4 weeks: plan
- Launch goal + success metric (PM) · Pricing / packaging decided (PM) · Beta customers lined up (CS)
- T−1 week: ready
- Feature flag + kill switch (Eng) · Help article + video (Docs) · Support trained, macros ready (Support) · Sales one-pager (PMM)
- Launch day
- Flip flag to 100% (Eng) · Blog post + email (Marketing) · Watch dashboards and errors (Eng) · In-app announcement (PM)
- T+2 weeks: learn
- Metric vs goal review (PM) · Top feedback themes (CS) · Remove flag, clean up (Eng) · Retro (all)
How to fill in the feature launch checklist template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser. Double-click any box to change its text.
- Put real dates on the columns. Rename T−4 weeks, T−1 week and the rest to calendar dates, so every deadline is visible.
- Write the goal first. The first item, the launch goal and success metric, decides what you'll review afterwards. Make it a number, such as “30% of active teams use it within 14 days”.
- Give every item one owner. Replace the role in brackets with a person's name. Items owned by “everyone” are the ones that get missed.
- Keep the kill switch. Leave the feature flag item in even for small launches. Being able to turn a feature off in seconds is what keeps launch day calm.
- Book the follow-up now. Schedule the two-week review and the retro before launch day, then compare the metric with the goal and remove the flag once things are stable.
When to use it
- Shipping anything customers will notice: a new feature, a pricing change, a redesign
- Several teams (engineering, support, marketing, sales) need to be ready on the same day
- Past launches went out without docs, an announcement or a follow-up
When to skip it
- Small fixes and internal changes that ship continuously without an announcement
- Launches with dozens of dependencies: plan those on a project timeline and keep this board as the summary
Working on a product board in Kelvo
- Add notes fast
- Press S for a sticky note in the middle of your view. A sticky is a box like any other: link it, recolour it, resize it.
- Paste a table
- Paste comma- or tab-separated text and it becomes a table. Tab moves to the next cell and adds rows as you go.
Questions
What should be on a product launch checklist?
A measurable goal, pricing and packaging decisions, beta customers, a feature flag with a kill switch, help docs and support training, sales and marketing material, the announcement itself, monitoring on launch day, and a review of the results a few weeks later.
How far ahead should you plan a feature launch?
Four weeks is enough for most features, which is how this template is laid out. Bigger launches involving press, partners or pricing changes often start six to eight weeks ahead.
What's the difference between a launch checklist and a release checklist?
A release checklist covers shipping the code: builds, tests, deploys and rollbacks. A launch checklist covers getting customers to use it: messaging, docs, support, sales and measuring the result. Most launches need both.
Related templates
Now / Next / Later roadmap
An outcome-based product roadmap without fake dates: what we're doing now, next, later, and what we're not doing.
PRD one-pager
A product requirements doc on one board: problem, goals, non-goals, users, requirements, metrics, risks and timeline.
RICE prioritization
Score features by Reach, Impact, Confidence and Effort to rank a backlog with numbers instead of opinions.
MoSCoW prioritization
Split a release's scope into Must, Should, Could and Won't-have-this-time so everyone agrees what ships.
Release process checklist
From code freeze to 100% rollout: the go/no-go gate, canary checks, rollback path and a checklist for every phase.
Go-to-market plan
Positioning, pre-launch, launch week and the first 90 days, with the metrics that define success.