P0 Incident War Room: Executive Panic and Blameless Culture
Assert Incident Commander authority; shield on-call responders from interrogation; establish an isolated debug channel; enforce a strict 10-15 minute executive update rhythm; defer root-cause blame to the post-mortem.
You are 12 minutes into an active P0 production incident. Marcus Vance has just unmuted on the primary response bridge, talking over the on-call engineer who is investigating telemetry.
At 2:15 PM on a peak revenue day, the checkout orchestration service began returning HTTP 500 errors across 80% of customer traffic. Transaction conversion has plummeted to 12%. Marcus Vance (VP of Product) joins the incident bridge visibly panicked, demanding a firm ETA every two minutes and aggressively interrogating who deployed the last release.
Your counterpart will test your communication and composure. Expect reactions like:
You can type your own opening or start with this suggested angle in the simulator:
"Marcus, I have Incident Commander authority on this bridge. We have identified a degradation in the checkout orchestration pipeline. Responders are currently isolating the fault domain."
Marcus Vance
PersonaAnxious VP of Product demanding immediate ETAs and assigning blame
Stance: arrogant