Templates For teams
Launches slip when the work outside the code is nobody's job: the docs, the announcement, support's briefing. This plan lays out the three or four weeks before launch day, starting from a one-page brief everyone can point to.
Free on Workel's free plan. For small product teams shipping a feature, a product or a new plan.
Due dates count from the day you add the template, so the first week's work is already on your calendar.
Write the one-page launch brief
In 2 daysHigh priority
Pick the launch date and tell the team
In 3 daysHigh priority
Finish the release checklist
In 2 weeksHigh priority
Draft the announcement email
In 2 weeksMedium priority
Update the help docs and screenshots
In 2 weeksMedium priority
Brief support on what's changing
In 3 weeksMedium priority
Schedule the social posts
In 3 weeksLow priority
Launch day check-in
In 3 weeksHigh priority
Post-launch review: what worked, what didn't
In 4 weeksMedium priority
Doc
Launch brief
What we're launching
One paragraph a customer would understand. If it needs a second paragraph, the launch is two launches.
Who it's for
The customers who asked for it, and the ones we hope it wins.
How we'll know it worked
Owners
Doc
Announcement draft
Subject line
Say what changed and why it matters, in under 60 characters.
Body
Start with the problem it solves, show it in one image, and end with one link.
Project chat
Product launch plan
Launch-week updates and blockers, all in one thread. Everyone you add to the project is in it.