War-game a churn playbook before eligibility rules, discount ladders, and success metrics harden into company policy.
Churn playbooks fail when every cancel threat gets the same offer, when root-cause tags stay optional, when "saved" logos are pauses that churn ninety days later, and when CS capacity cannot clear the claimed volume. A polished flowchart is not evidence.
Freeze the package
State the triggers that open the playbook, the segments in scope, the offer ladder with duration caps, the owners for product fixes versus commercial saves, and the success metric after thirty and ninety days. Attach reason-code quality, margin after discounts, contractual notice rules, and CS and support headcount. If product, sales, and finance disagree on why logos leave, reconcile before the seating pass.
Name the decision you will make if the war game finds nothing new, and the kill criteria if the ladder destroys margin without changing retention.
Seats
- Canceling customer. What still feels broken after the scripted save.
- Finance. Margin after discounts, cash timing, and fake saves.
- CS and support. Workload, playbook clarity, and escalation paths.
- Product. Which root cause the playbook ignores or dual-counts.
- Skeptic. The claim that looks strongest and is least sourced.
Optional counsel seat if regulated cancel rights or auto-renew rules bind the language. Give every seat the same pack.
Run the loop
Feed Pingpong the playbook memo and exhibits. First pass steelmans the ladder. Later passes attack from the seats above. Final pass turns surviving objections into narrower eligibility, clearer duration caps, or a product-first fix. Delete invented save rates and dual-counted pauses.
Force a day-after narrative: what canceling customers post publicly, which enterprise accounts demand side letters, and what competitors publish about your discount habit. If those stories are stronger than your root-cause plan, fix the package before the playbook ships. Separate win-back of already-churned logos from save-in-flight. If blended dashboards hide a soft segment, ask finance and CS seats to attack until each path has owners and kill criteria.
Ask every seat to mark which playbook steps are optional in practice. Optional steps that never run still appear in the flowchart. If CS skips root-cause tagging under load, finance and product seats should treat that skip as a design failure, not a training gap. Write the mandatory steps into the package, then attack whether capacity can actually clear them.
When the playbook leans on a standing discount, force finance to price the next cohort that will demand the same deal without a cancel threat. Write eligibility, clawbacks, and exception owners into the package, then ask the finance and CS seats to attack those rules. A playbook that only works by forever matching the lowest offer is margin erosion with better reporting. Related: war-game a churn response, pretend you are the customer success lead, war-game a discount policy, stress-test a support policy change, and the war-game decisions hub. Process: how to run a Pingpong.