War-game a customer success playbook before CSMs, support, and sales treat a draft as the default motion and customers experience the gaps live.
Playbooks fail when health scores are vanity metrics, when escalation paths contradict support ladders, when renewal language invents product promises, and when "save" offers become permanent discounts. A tidy flowchart is not evidence that the motion survives a careful churn review.
Freeze the playbook
State the segment, the trigger events, the owner at each stage, the offers CS can make without approval, and the success metric after ninety days. Attach sample health inputs, talk tracks, escalation rules, and the exception policy for credits or discounts. If CS, support, and sales disagree on who owns a save, split the package until one motion is under fire.
Write the decision you will make if the war game finds nothing new, and the kill or revise criteria if churn, ticket volume, or margin crosses a named line.
Seats that matter
- Customer. Whether the outreach feels helpful or invasive, and which promises sound fake.
- Support. Ticket load and conflicting guidance when CS and support scripts diverge.
- Sales and renewals. Pipeline risk when playbook language undercuts pricing or packaging.
- Finance. Credit, discount, and margin impact under realistic save rates.
- Skeptic. The claim that looks strongest and is least sourced.
Give every seat the same pack. Secret "we will customize later" notes for CS only create fake agreement.
Loop the review
Feed Pingpong the playbook, sample talk tracks, and health score definition. First pass steelmans the motion. Later passes attack from customer, support, sales, and finance seats. Final pass turns surviving objections into clearer triggers, tighter offer authority, or a delayed rollout. Delete dual-counted saves and invented expansion revenue.
Force a day-after narrative: what happens if a high-value account screenshots the save offer, if support contradicts CS in the same thread, or if a journalist asks how often you discount to retain. If those stories are stronger than your guardrails, fix the package before training. Separate a true playbook from a permanent pricing or packaging change. If the memo blurs them, run the discount or packaging war game as its own move.
Related: war-game a churn response, war-game a support escalation ladder, war-game a customer escalation, war-game a customer advisory board, stress-test a support policy change, and the war-game decisions hub. Process: how to run a Pingpong.