War-game a usage cap exception before approval ladders, grant windows, and clawback rules harden into how every overage gets handled.
Usage cap exceptions fail when the policy invents approval speed finance never funded, when grants dual-count the same account as capped and as uncapped, when sales still promises custom ceilings in private Slack, and when billing cannot show which exceptions actually cleared under the published path. A neat exception flowchart is not evidence.
Freeze one exception path
State the proposed approval criteria and durations, which plans and regions it covers, who owns grant audit and clawback, what success looks like after two quarters of exception rate and margin impact, and the kill criteria if shadow grants or fairness disputes past a named threshold. Attach the cap table, sample grant logs, margin samples, and the measured path from request to posted exception. If sales, finance, and product disagree on whether the path buys retention or just deferred margin fights, reconcile before seating.
Name the decision you will make if the war game finds nothing new, and the hold criteria if any grant tier still lacks a named owner or a verified audit path.
Hostile seats
- Power user. Fear that "temporary lift" still means a quiet cut mid-quarter.
- Finance. Margin math that looks clean while grant cohorts cannot be listed.
- Sales. Talk tracks that invent approval speed the ladder never wrote.
- Support. Macros that still host retired exception language.
- Skeptic. The claim that looks strongest and is least sourced.
Optional legal seat if MSA language binds the form. Same pack for every seat.
Private pass
Feed Pingpong the exception draft and exhibits. First pass steelmans the approval ladder. Later passes attack from the seats above. Final pass turns surviving objections into clearer criteria, a published clawback path, or a hold. Delete invented "customers already expect temporary lifts" claims and dual-counted grant rates.
Force a day-after narrative: what happens if a large account screenshots mismatched grant terms, if sales still teaches unwritten ceilings, or if finance cannot list the open exception cohort. If those stories are stronger than your mitigation plan, fix the package before you publish it. Separate a usage cap exception from a usage limit change or a pricing grandfather clause so each decision stays testable.
Ask every seat to mark which grants are optional in practice. Optional clawback audits become skipped within a month if nobody names the owner and the time box. Related: war-game a discount policy, war-game a deal desk rule, pretend you are the RevOps lead, pretend you are the power user, and the war-game decisions hub. Process: how to run a Pingpong.