Orchestrated launch runbook (L4)
Launches run from an orchestrated runbook: assets generated from one source of truth, tasks created with owners and dates, readiness checked automatically, and a single dashboard showing what is blocking go live.
The steps
- 01
Single source launch narrative
Tool: Notion
One approved narrative document with positioning, claims, and evidence. Every asset is generated or written from it, so a change propagates instead of fragmenting. Owner: product marketing. DoD: narrative approved before any asset work starts.
- 02
Generate the task graph
Tool: Asana
The runbook creates every task with owner, dependency, and date from a launch tier template. Tier one and tier three launches should not carry the same task load. Pitfall: one template for every launch size, which trains teams to ignore tasks. DoD: at least two launch tiers exist.
- 03
Automate readiness checks
Tool: Claude
Check that pricing page, enablement one pager, support macros, and legal review all exist and reference the approved claims. Missing items block go live status. Owner: product marketing ops. DoD: readiness check runs and can block.
- 04
One blocking view in the channel
Tool: Slack
Daily post in the launch channel showing only blockers with owners. Status decks are not a coordination mechanism. Owner: launch lead. DoD: daily blocker post through launch week.
Tools in this playbook
Building the team behind this workflow?
Next playbooks
Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.