A crisis debrief held too late, led by the wrong person or reduced to a form-filling exercise can do more harm than good. People remember what was said, who was blamed and whether anyone listened. Knowing how to run crisis debriefs properly means turning a difficult event into better judgement, clearer decisions and practical changes that hold up when pressure returns.

The purpose is not to establish a perfect account of events. It is to understand how the team perceived the situation, what information they had, what decisions they made and what helped or hindered their response. That distinction matters. Hindsight makes every missed sign appear obvious. A useful debrief puts people back in the conditions they faced at the time.

Set the conditions before the discussion

Do not convene a full debrief while the incident is still consuming the team. Immediate welfare, safety, continuity and evidence preservation come first. There may be an urgent need for a short operational hot debrief, but this is not the same as a detailed review.

A hot debrief should take place as soon as reasonably possible, often at the end of a shift or operational period. Keep it focused on immediate facts: what is still unresolved, what risks remain, what needs recording and what support people require. It may identify an unsafe procedure or a communications failure that needs correcting before the next shift.

The structured debrief should follow once there is sufficient information and people have had time to regain perspective. The timing depends on the incident. For a contained disruption, this may be within 24 to 72 hours. A more serious event, particularly one involving investigations, significant distress or multiple agencies, may require staged sessions. Do not wait so long that memory fades and informal versions of events become accepted as fact.

Choose who needs to be in the room with care. Include those who made decisions, received information, carried out key actions or were affected by handovers. Seniority alone is not a reason to attend. A crowded room encourages people to perform for an audience rather than speak candidly.

The facilitator is equally important. In a small team, a manager may be the right person if they can stay neutral and create psychological safety. If that manager was central to disputed decisions, or there is a clear power imbalance, use an independent facilitator. The objective is candour, not comfort.

Start with facts, then examine judgement

A common failure is to begin with the question, “What went wrong?” It invites defensiveness and assumes failure before the evidence has been examined. Start instead by building a shared timeline.

Ask what was observed, reported or known at each point. Establish who received the information, through which channel and how quickly it was understood. Identify decisions, actions and handovers. Separate confirmed facts from assumptions and later discoveries. A whiteboard, incident log or simple timeline is usually more useful than a polished slide deck.

Once the timeline is credible, examine the decisions. Ask what people believed at the time, what options they considered and what constrained them. Those constraints may include poor information, unclear authority, competing priorities, fatigue, equipment limitations or a plan that made sense on paper but not at the point of use.

This is where many organisations discover the difference between procedure and capability. A response plan might state that a team leader must escalate a concern, but a debrief may reveal that the duty manager could not be contacted, staff were unsure what threshold justified escalation or the radio terminology was misunderstood. The document existed. The operating capability did not.

Avoid turning every issue into a training need. If an experienced team repeatedly makes the same decision under pressure, the cause may be flawed supervision, an impractical process or a poorly designed environment. Training cannot compensate indefinitely for a system that makes the right action difficult.

Ask questions that reveal the real response

Good questions do not lead witnesses towards a preferred answer. They help people describe their experience accurately. “What did you see first?” is better than “Why did you fail to spot the warning sign?” “What information would have changed your decision?” is more useful than “Did you follow the procedure?”

Explore the points where the response accelerated, stalled or changed direction. A useful debrief should establish whether those moments were caused by clear leadership, good situational awareness, an informal workaround, conflicting instructions or sheer luck.

Pay attention to normalisation. Teams often adapt to recurring defects without formally reporting them. A gate that does not close reliably, incomplete contact details, delayed contractor support or an unclear control-room handover can become accepted as normal until an incident exposes the consequence. These are not minor observations. They are often the conditions that shape a crisis response before the crisis begins.

Behaviour matters as much as process. Did someone challenge an unsafe assumption? Did a supervisor create space for a junior colleague to report uncertainty? Did people freeze because they feared criticism for making the wrong call? The answers show how the organisation performs under pressure, not merely what it says it values.

Keep accountability without creating blame

A blame-free debrief is often misunderstood. It does not mean that poor conduct, negligence or deliberate non-compliance should be ignored. It means the debrief should not use blame as a shortcut for analysis.

Most operational failings are not explained by one person making one poor choice. They arise from a combination of signals, priorities, workload, supervision, knowledge and environment. If a person failed to act as expected, establish whether expectations were clear, realistic, practised and supported. Then address individual accountability through the appropriate management process where the evidence warrants it.

This approach protects standards. It also protects reporting. Staff who believe every error will be used against them will conceal uncertainty, avoid raising near misses and give rehearsed answers. That creates a reassuring report and a less safe organisation.

The facilitator should challenge vague language. “Communication was poor” is not a finding. Was the message absent, delayed, misunderstood, sent to the wrong person or impossible to hear? “Staff need to be more aware” is equally weak. A finding should describe an observable gap and its operational consequence.

Turn findings into controlled action

A debrief has failed if its actions read like this: improve communication, review procedures, remind staff. These are intentions, not controls. Each action needs an owner, a deadline, a defined outcome and a way to verify whether it worked.

For example, if the incident exposed uncertainty over who can authorise an evacuation or lockdown decision, the answer may be to clarify authority, revise call-out arrangements and test the decision process during a short scenario exercise. If the issue was delayed information from a contractor, the solution may involve a revised notification route, named contacts and a monitored test. The appropriate action depends on the cause, not on what is easiest to write down.

Prioritise findings by consequence and likelihood, but do not use a scoring system to hide judgement. Some changes are simple and immediate. Others require investment, redesign or senior ownership. Be honest about that. A risk does not disappear because it has been entered on an action tracker.

Share a concise record with the relevant people. It should capture the agreed timeline, principal findings, actions, owners and review dates. It should not become a transcript of every comment or an uncontrolled document containing sensitive operational detail. People need to know what will change, not receive pages of meeting notes.

Test whether the lesson was learned

Closing an action is not proof of improvement. The only meaningful test is whether people can apply the change in realistic conditions. That may mean a tabletop discussion for senior decision makers, a shift briefing with a practical check, or a scenario-based exercise that tests communications and authority.

Measure what changed. If a revised escalation process is introduced, can staff explain it and use it? If a new incident reporting route is created, are reports arriving more promptly and with better information? If leaders were identified as a weakness, do they now make decisions clearly and communicate intent under pressure?

Mildot Group’s approach to capability is simple: evidence of learning must be visible in performance. Policies, certificates and completed actions have value, but they are not the end point. The real question is whether the organisation is better prepared for the next difficult decision.

The best crisis debriefs leave people with a clear understanding of what happened and what they will do differently. More importantly, they build the habit of examining performance honestly before the next incident forces the issue.