Tabletops fail quietly. Everyone leaves polite. The shared folder gains a PDF. A week later, an auditor asks which decisions were timed, which owners changed, and which vendor contacts were verified live. Silence follows.
Write injects that hurt a little
Severe-but-plausible means your stack’s actual concentrations: the SMS provider, the card processor region, the sole person who can rotate a signing key. Cartoon meteors waste the room’s attention.
Instrument the clock
Assign a scribe who records decision time, not just content. Without timestamps, you cannot compare rehearsal to recovery objectives.
End with an action ledger
Each finding needs an owner, a due date, and a definition of done. “Improve runbooks” is not done. “Publish v3 of payment failover runbook and link it from the incident bridge” can be checked.
Invite the awkward second day
Schedule a thirty-minute follow-up. Ask what felt staged. Ask which phone trees bounced. That conversation is often more valuable than the exercise itself — and it is a core critique habit in Scaleapipro cohorts.