Product launch checklist
A launch fails in ordinary ways: the product works but the page does not explain it, the announcement lands but support is not ready, or nobody can say afterward whether it succeeded. Most of those problems can be caught with a list and a named owner.
This template follows the work in order, for a new product or a major feature. A small team can treat each branch as a short conversation; a larger one can give each branch to a different owner and split it further.
85 tasks in 7 sections
-
Positioning and goals
-
-
Product readiness
-
-
Launch assets
-
-
Sales and support readiness
-
-
Launch week
-
-
Launch day
-
-
After launch
-
Tick a task or fold a branch to try it. Ticks are not saved on this page.
Tips
Give every branch one owner
A branch owned by "the team" tends to be owned by nobody. Add a name to the top of each branch, even on a team of three.
Decide what success means first
Set the metric and the target before launch day. Afterward, it is too easy to pick whichever number looks best.
Keep a post-launch list
When a good idea shows up late, move it to the list instead of arguing about it. It protects the date and keeps the idea.