Running Crisis Communication Meetings When Things Go Wrong

Crisis meetings — outages, PR incidents, safety events, major client escalations — operate under different rules than routine work meetings. Information is incomplete, decisions have to be made anyway, and the meeting itself needs to produce a defensible record of what was known and decided at each point, because that record often gets scrutinized afterward.

The structural differences from routine meetings

• A named incident commander: one person owns the decision authority for the duration of the crisis — not a consensus process, which is too slow when facts are changing by the minute.
• Defined update cadence, stated up front: 'we reconvene in 30 minutes with an update' gives everyone a predictable rhythm instead of an open-ended standing call nobody knows when to leave.
• Explicit fact-versus-hypothesis labeling: crisis conversations move fast and blur what is confirmed with what is suspected — the facilitator's job includes forcing that distinction out loud.
• A scribe separate from the decision-maker: someone whose only job is capturing what was decided and by whom, so the incident commander can focus entirely on the decisions.

Why the record matters more here than almost anywhere else

Post-incident reviews, regulatory inquiries, and legal exposure all depend on an accurate account of when information was known and what was decided in response. A crisis meeting that produces no reliable record leaves the organization defending its response from memory weeks later, which is a genuinely weak position. Automatic transcription solves this specifically well for crisis meetings — there is no time to assign a dedicated scribe in a fast-moving incident, and no attention to spare for careful note-taking while also making real decisions.

Practical setup for crisis calls

• Use a standing, pre-established meeting link: crisis response is not the moment to be creating and distributing a new meeting link — have an incident-response link ready before you need it.
• Turn on recording and transcription by default: unlike routine meetings, the sensitivity tradeoff usually favors a complete record during an active crisis, when accountability and post-mortem accuracy matter most.
• MeetOye's Oya produces a timestamped, speaker-attributed transcript automatically — which becomes the raw material for the post-incident review without anyone having reconstructed the timeline from memory under pressure.

After the crisis

The post-mortem is only as good as the record it is built from. An accurate transcript of the crisis calls — what was known when, what was decided and why — turns the post-mortem from a defensive reconstruction into an honest review, which is the entire point of running one.