Code being merged and a feature being 'launched' are two different events, separated by everything that has to be true for the rest of the company to not be blindsided.
1The Four Functions That Must Sign Off
A launch checklist is really four mini-checklists in a trench coat: Engineering confirms monitoring and a kill switch exist; Support has FAQ docs and canned responses ready; Marketing has confirmed timing doesn't collide with another announcement; Sales has talking points so a prospect doesn't hear about the feature from a competitor first.
2Staged Rollouts Beat Big-Bang Launches
A 100%-at-once launch turns any bug into an incident affecting your entire user base simultaneously. Feature-flagged, staged rollouts (1% -> 10% -> 50% -> 100%) let real usage surface edge cases while the blast radius is still small enough to fix quietly.
3Step-by-Step Breakdown
Introduction. A launch plan is not a press release calendar — it's a cross-functional checklist that ensures support can answer tickets, sales can position the feature, and engineering has a rollback plan, all before a single user sees the button.
Tiered Launches. Most mature teams don't flip a switch to 100% of users at once. A typical tiering: internal dogfood, then a 1-5% canary/soft launch to catch bugs at low blast radius, then staged rollout, then General Availability (GA) with the marketing push.
The Rollback Plan. Every launch checklist needs an explicit answer to 'what do we do if this breaks in production at 2 AM?' — a feature flag to instantly disable the feature, a named on-call owner, and a pre-agreed threshold (e.g. error rate above X%) that triggers the rollback automatically, not by committee.
Knowledge Check. Why do mature teams launch to 5% of users behind a feature flag before rolling out to everyone?
- →It limits the blast radius of an unknown bug and lets the team catch problems before most users are affected
- →It builds hype by making the feature feel exclusive to early users
Summary. A launch checklist covers four owners: Engineering (rollback + monitoring), Support (FAQ + macros), Marketing (announcement + timing), and Sales (talking points). Missing any one of them turns a good feature into a bad launch.
