War-game a scope cut before customers, sellers, and builders learn the hard way that the promised surface just got thinner.
Scope cuts often solve a calendar problem and create a trust problem. Features vanish from demos, contracts still name old work, and support keeps answering as if the cut never happened. Announcing before you can name what still ships, what moves, and who owns the apology is how goodwill drains in the first week.
Name the cut in one sentence
Write what leaves the release, what stays, and the date customers will notice. Examples: the admin export slips a quarter, the mobile offline mode is cut, or the partner API stays but webhooks move. Then write the post-cut owner for each deferred item. If you cannot name the owner, the cut is a rumor with a deck.
Freeze the customer-facing changelog, the contract and SOW deltas, the sales talk track, and the first ninety-day outcomes you still promise. Attach the before-and-after roadmap, the dependency list, and the handoff for open tickets. Split any secondary goals into separate decisions. One scope cut under fire at a time.
Hostile seats
- Customer seat: what they bought that no longer arrives on the promised date.
- Engineering seat: what still blocks the reduced release and what technical debt the cut hides.
- Sales seat: deals and renewals that assumed the cut scope.
- Support seat: tickets and docs that will keep teaching the old story.
- Skeptic seat: the claim that looks cleanest and has the least evidence.
Ask each seat for material objections, missing owners, and the smallest change that keeps the intent without the quiet damage. Optional counsel seat if contracts or SLAs name the cut work.
Private pass
Run that package in Pingpong. Sequential review helps because an early pass can defend the schedule while later passes try to kill soft customer-impact claims. Keep a change log of promises clarified, talk tracks rewritten, and risks accepted. If survival requires silence about a contracted deliverable, stop. Rewrite the plan or delay the announce.
Publish the customer calendar inside the package: who gets the first heads-up, when docs flip, and when sales stops pitching the cut work. A scope cut without a dated handoff is a soft launch of disappointment. Ask the customer and sales seats to break that calendar before anyone sees the announce draft.
Related: war-game a roadmap cut, before you kill the feature, stress-test a product sunset, war-game a launch checklist, and AI for high-stakes decisions. Mechanics: how it works.