Stress-test a feature freeze before the window starts and proves the exception path is vague, the release train is soft, or the freeze was theater.
Feature freezes fail when exceptions are informal, when hotfixes and "small" ships still land without criteria, when sales already promised dates inside the freeze, and when engineering hears a hard stop while product still has a soft list. A calendar invite labeled freeze is not evidence that the company can hold the line without chaos.
What to put on the table
One sentence for why the freeze exists, the start and end dates you will honor, who owns exceptions, and the rollback trigger if the freeze cannot meet the release goal. Attach the exception criteria, the release checklist, the open risk list, and the customer or sales language you would use. If product, eng, and support disagree on what "frozen" means, stop and reconcile first.
Name the decision you will make if the stress test finds nothing new, and the delay criteria if exception criteria or release owners are missing.
Attack surfaces
- Shadow ships: work that renames itself as hotfix, flag flip, or docs-only.
- Exception theater: approvals that exist on paper and fail under time pressure.
- Promise collisions: sales, partners, or launches already booked inside the window.
- Morale gaps: teams that hear a freeze as punishment without a clear release goal.
- Domain overlap: freezes that share fate with a migration or vendor exit already in flight.
Optional customer seat if SLAs or launch dates sit inside the freeze. Optional finance seat if revenue recognition or campaign spend depends on ships you just blocked.
How to run it
Feed Pingpong the freeze memo, exception criteria, and open risk list. Early passes steelman the plan. Later passes attack from product, eng, sales, and support seats. End with a pass that turns surviving objections into a clearer exception ladder, a named owner, or a hold. Delete invented "just this once" paths and dual-counted release capacity.
When the freeze coincides with a flag rollout or roadmap cut, force product and eng seats to map every path that still assumes quiet ships. Flags, docs, and partner enablement count. A feature freeze that looks clean in a deck while sales still demos unfinished work will fail on the first escalated deal.
Force a day-after narrative: what happens if a Sev-1 needs a ship, if a partner deadline slips into the window, or if two teams disagree on whether a change is a hotfix. If those stories are stronger than your mitigation plan, fix the package before you lock dates. Related: stress-test a feature flag rollout, war-game a roadmap cut, war-game a scope cut, war-game a launch checklist, and the war-game decisions hub. Process: how to run a Pingpong.