Launch coordination
Key takeaways
- decision clock
- launch spine
- threshold card
Operating data
Playbook
A briefing book should show what changed, which decision is approaching, and who can verify the evidence. Start with a decision clock covering message approval, rollout scope, support capacity, and pause authority. For every window, name the decision maker, latest useful time, expected evidence, and consequence of delay.
Organize the live edition around current phase, cohort, confirmed milestones, material exceptions, and open choices. Attach a source owner, reporting cutoff, and verification state to every consequential claim. When dashboards disagree, display the conflict instead of selecting the more reassuring number.
The briefing source-check guide supplies claim-level controls. Build threshold cards that state the observed condition, confirmation owner, authorized options, communication owner, and next review time. These cards prepare decisions; they do not expand the assistant’s authority.
Timestamp every revision and retire superseded pages from the live view. Atlassian incident communication guidance illustrates disciplined, audience-aware updates during change. Record each launch choice, assumption, audience, and review trigger, then route work through operations follow-through.
FAQ
When should a leader delegate this workflow?
Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.
What should the assistant own first?
Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.