War-game a launch checklist before teams treat a soft checkbox list as proof that go-live is safe.
Launch checklists fail when owners are missing, when "done" means a slide not a test, when rollback is theoretical, and when support and status pages still assume the old product. A green sheet is not evidence that the first failure mode has an owner with authority.
Freeze the scenario
State the launch date, the audience, the success metric, and the rollback trigger. Name the systems and queues that feel the change first. If the memo mixes a checklist, a pricing change, and a marketing campaign, split them. A war game needs one move under fire at a time.
Write the decision you will make if the war game finds nothing new. Also write the kill criteria: the error rate, support spike, or payment failure that would force a hold within a stated window.
Seats that matter
- Product. Scope still open and items marked done without a proof link.
- Engineering. Monitoring, feature flags, and rollback that only exist as intent.
- Ops and support. Macros, staffing, and status copy that lag the ship.
- Marketing or sales. Claims that outrun what the checklist actually gates.
- Skeptic. The claim that looks strongest and is least evidenced.
Attach the same source pack to every seat: checklist, owners, proof links, runbooks, and the last three near-miss launches. Secret data for one seat creates fake agreement.
Loop the review
Feed Pingpong the checklist, owners map, and seating briefs. First pass steelmans readiness. Later passes attack from engineering, support, and skeptic seats. Final pass turns surviving objections into missing owners, new gates, or a hold. Agreement across passes is not proof. Keep the objections that still have evidence gaps.
Force a day-one failure drill: pick the top three failure modes and ask each seat who pages whom, what customers see, and what gets rolled back first. If those answers disagree, the checklist is not ready. Write the drill results into the package before any "ready" stamp.
If marketing claims are on the checklist as a single checkbox, split them. A claim about uptime, pricing, or data handling needs its own owner, proof link, and legal review status. Treat "comms ready" as incomplete until the status page draft, support macros, and sales talk track all point at the same version of the product.
Pair with war-game a product launch, pretend you are the ops lead, stress-test a feature flag rollout, stress-test a status page update, and the war-game decisions hub. See how to run a Pingpong.