launch-playbook
Launch Playbook (Internal + External Coordination)
Overview
A complete launch coordination playbook for software products and features. It covers the three windows that matter -- pre-launch (T-30 to T-1), launch day (T-0), and post-launch (T+1 to T+30) -- and produces five concrete artifacts: a run-of-show, an internal comms plan, an external comms checklist, a rollback plan, and a post-launch retro template.
Most failed launches are not failed builds; they are failed coordination. Engineering ships on time, but support has not been trained, sales does not have collateral, the changelog is wrong, the rollback path was never tested, and the executive sponsor hears about a customer complaint before hearing about the launch. This playbook prevents those failures by assigning every owner and every artifact before T-30.
Core Capabilities
- Three-launches sequencing — Cagan's alpha/beta/GA model de-risks the launch; this skill owns the GA window.
- T-30 to T+30 timeline — day-by-day pre-launch, launch-day, and post-launch action plan across all workstreams.
- Launch-type selection — big bang vs progressive rollout vs dark launch decision rules (and how to combine them).
- RACI ownership — every workstream assigned across PM, Eng, PMM, Sales, Support, Legal, Exec.
- Five artifacts — run-of-show, internal comms plan, external comms checklist, rollback plan, post-launch retro.