War-game a product packaging matrix before entitlements, SKU boundaries, and upgrade paths harden into how every quote and self-serve plan gets sold.
Product packaging matrices fail when the grid invents feature clarity product never shipped, when plans dual-count the same capability as included and as add-on, when sales still promises custom bundles in private Slack, and when revops cannot show which entitlements actually clear under the published path. A neat packaging table is not evidence.
Freeze one matrix
State the proposed plan bands and entitlement rules, which regions and channels it covers, who owns exception audit and SKU retirements, what success looks like after two quarters of attach rate and support ticket mix, and the kill criteria if shadow bundles or fairness disputes past a named threshold. Attach the current entitlement map, sample quote logs, support macros, and the measured path from plan pick to provisioned features. If product, sales, and finance disagree on whether the matrix buys clarity or just deferred exception fights, reconcile before seating.
Name the decision you will make if the war game finds nothing new, and the hold criteria if any plan still lacks a named owner or a verified entitlement path.
Hostile chairs
- Enterprise buyer. Fear that "standard plan" still means a quiet custom SKU below the published grid.
- Product. Feature claims that look clean while entitlement flags cannot be listed.
- Sales. Talk tracks that invent bundles the matrix never wrote.
- Support. Macros that still host retired plan language.
- Skeptic. The claim that looks strongest and is least sourced.
Optional legal seat if MSA packaging language binds the form. Same pack for every seat.
Private attack sequence
Feed Pingpong the matrix draft and exhibits. First pass steelmans the entitlement ladder. Later passes attack from the seats above. Final pass turns surviving objections into clearer bands, a published exception path, or a hold. Delete invented "customers already understand these plans" claims and dual-counted attach rates.
Force a day-after narrative: what happens if a large account screenshots mismatched entitlements, if sales still teaches unwritten bundles, or if support cannot list the open exception cohort. If those stories are stronger than your mitigation plan, fix the package before you publish it. Separate a product packaging matrix from a packaging change or a SKU rationalization so each decision stays testable.
Ask every seat to mark which entitlements are optional in practice. Optional exception audits become skipped within a month if nobody names the owner and the time box. Related: war-game a pricing add-on, pretend you are the product marketing lead, pretend you are the CPO, and the war-game decisions hub. Process: how to run a Pingpong.