how to run a war room with support and engineering

TL;DR

A war room needs five roles (incident commander, support liaison, engineering lead, comms owner, scribe), a 15-minute cadence, and one rule: no troubleshooting in the main channel. Support owns customer truth, engineering owns the fix, and the liaison is the only bridge. War rooms fail from too many voices, not too few.

The query

how to run a war room with support and engineering

Use this when

• A SEV1 or SEV2 incident is active
• Writing incident response playbooks
• War rooms devolve into chaos or silence
• Training incident commanders

Not for

• Routine bugs
• Postmortems
• Project status meetings
• Incidents with no customer impact

Steps

1. Assign the five roles immediately

Incident commander (runs the room, makes calls), support liaison (only bridge to the support floor), engineering lead (owns the fix), comms owner (writes status updates), scribe (logs decisions and timestamps). One person per role. No role, no voice in the main channel.

Expected output: five named people in five roles.

2. Set the 15-minute cadence

Every 15 minutes: what do we know, what changed, what is next, when is the next update. The commander runs it in 3 minutes. Cadence replaces ad-hoc "any updates" noise.

Expected output: updates on a predictable rhythm.

3. Split the channels

Main channel: decisions and status only. Separate threads or channels for debugging, customer tickets, and speculation. Troubleshooting in the main channel buries the decisions.

Expected output: a quiet main channel with signal only.

4. Let support own customer truth

The support liaison reports: ticket volume, top customer questions, sentiment, VIP impact. Engineering does not guess what customers experience; support tells them. The comms owner turns it into status updates.

Expected output: customer reality in every cadence update.

5. Declare the end explicitly

The commander declares the incident mitigated, assigns the postmortem owner and date, and closes the room. War rooms that fade out leave tickets unclosed and nobody owning follow-up.

Expected output: a declared end with postmortem owner and date.

Template: the war room setup

WAR ROOM - [incident name] - [date time]
Commander: __  Support liaison: __  Eng lead: __  Comms: __  Scribe: __
Severity: __  Customer impact: __

Cadence: every 15 min - what we know / what changed / next / next update at
Channels: #incident-main (decisions only), #incident-debug, #incident-customers
Customer status page: [link] - comms owner updates every 30 min

Rules:
- No debugging in main. No "any updates" - wait for cadence.
- Support liaison is the ONLY bridge to the support floor.
- Commander declares the end. Postmortem owner: __ Date: __

Variant phrasings

incident war room roles

Step 1. Five roles, one person each.

running a major incident call

Steps 1 through 3. Roles, cadence, channels.

support engineering incident coordination

Full sequence. Step 4 is support's specific job.

Why it works

Incidents create two scarcities: attention and coordination. Roles ration attention (only five voices matter), cadence rations coordination (everyone syncs on rhythm, not on demand), and channel splits keep debugging from drowning decisions. Support's seat at the table matters because engineering otherwise optimizes for the fix while customers drown in silence.

Edge cases

• Small team, five roles is everyone: combine scribe with comms, and commander with liaison. Never combine commander with eng lead.
• The incident lasts many hours: rotate roles every 4 to 6 hours. Tired commanders make bad calls.
• Vendor incident: add a vendor liaison role. Do not let ten people open vendor tickets.
• It turns out to be minor: the commander downgrades explicitly. Do not let a war room run on embarrassment.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_mfHxBoDScErui8gV69Nsnw

Resolved from the public thread: https://vectle.com/posts/pst_mfHxBoDScErui8gV69Nsnw

Thread query: how to run a war room with support and engineering

TL;DR: A war room needs five roles (incident commander, support liaison, engineering lead, comms owner, scribe), a 15-minute cadence, and one rule: no troubleshooting in the main channel. Support owns customer truth, engineering owns the fix, and the liaison is the only bridge. War rooms fail from too many voices, not too few.