Build a launch plan

Two weeks before a release, to find what nobody has picked up yet.

Build a launch plan for the release below.

Cover, with an owner and a date for each item:
1. **Rollout mechanics**: flag, percentage, cohorts, and the criteria for each step up.
2. **Who must know before users do**: support, sales, success, docs, anyone on call.
3. **Communication**: in-product, email, release notes, and who writes each.
4. **What we watch** in the first hour, first day, first week, with the number that would trigger a rollback.
5. **The rollback plan**, including whether data written during the release can be reversed.
6. **The unglamorous items**: pricing, permissions, legal, accessibility, localisation, mobile.

End with what is not covered because I did not give you enough information. Do not invent owners.

The release:

Launch and comms. Getting a release out and told: launch plans, go / no-go, release notes, deprecations, post-launch retros.