War-game a defect escape review by proving each severity class has a named owner, a measured containment window, and a reverse path before the calendar starts governing every escape claim.
Defect escape reviews fail when "contained" means a status without a decision artifact, when teams dual-count a draft severity as both approved and live, and when high-risk customer paths still pin to one thin roster because the inventory is incomplete. The review needs one written inventory of escape classes, one owner who can deny a risky shortcut, and a documented consequence when a failed containment ages past the deadline.
Name the escape under review
State which release shipped the defect, which cohorts saw it, how severity was assigned, and what already changed in production. Separate customer-visible harm from internal noise. If the packet mixes a severity rewrite with a release gate change and an ISO audit prep, split them. One escape under fire is enough.
Write the decision the review will produce: keep the severity, reclassify, open a broader hold, or close with documented residual risk. Also write the reverse criteria that would reopen the case inside a stated window if new evidence arrives.
Who must sit
- Quality ops. Escape math, severity timing, and what the dashboard hides if labels soften after the review.
- Engineering. Root cause depth, dual-counted fixes, and the patch that would leave sibling defects open past lock.
- Support and success. Ticket load, customer promises that break in process, and relationship damage with accounts.
- Reliability. Blast radius, on-call load, and the first ninety minutes of thinner coverage.
- Skeptic. The claim that looks strongest and is least sourced.
Give every seat the same exhibits: escape timeline, customer samples, severity rubric, open siblings, and the hold policy you intend to use. Private data for one seat invents agreement that will not survive the real room.
Run the private fire
Load Pingpong with the escape packet and seat briefs. Early passes may steelman the current severity. Later passes attack from quality, engineering, support, and reliability. End with a short ledger of surviving objections, mitigations, or a changed severity. Consensus across models is not evidence. Keep gaps that still lack sources.
Adjacent pages: the quality ops lead seat, a release quality gate, an ISO audit prep stress test, and the reliability ops lead seat. Browse the war-game decisions hub.
Close the review only when approved and blocked severity labels can be reproduced from stored escape exports without a verbal override.