Ops Knowledge Garden

The Debrief

Living noteLast tended 5 min read

Some of the most useful conversations I had as an EMS supervisor happened after the call was over.

I called them debriefs, although that word covers several different conversations. What I mean here is a supportive, question-led conversation with a crew member: a chance to recover their reasoning, notice what they learned, and decide what they want to carry into the next call.

What I was trying to do

I did not want the conversation to begin as a performance review. If somebody was replaying a difficult decision, I wanted to understand what they saw and what they were working with before deciding what the call meant.

In my experience, nine times out of ten, the person already had more of the skill and knowledge than they believed they did. They were trying to recover trust in their own judgment. A good conversation could help them find it.

That was not always the answer. Sometimes there was a real knowledge gap, a system problem, or feedback that could not be softened away. The questions helped us determine which situation we were actually in.

The Method: Lead, Don’t Tell

Borrowed from the question-led model in Leadership Philosophy, but applied to crew support:

My default was not to give the answer first.

  1. Open with curiosity, not evaluation. “Walk me through that call.” Not “what did you do wrong.”

  2. Ask what they were thinking in the moment. “What were you working with when you made that decision?” This surfaces their internal reasoning without judgment.

  3. Ask what they’d look for next time. “If that came in again tomorrow, what would you want to pay attention to?” This is forward-facing without implying they failed.

  4. Reflect what the conversation supports. Sometimes that means naming good reasoning they cannot see yet. Sometimes it means identifying a gap plainly. Reassurance is only useful when it is true.

  5. Close with what they can carry forward. One concrete thing. Not a list.

I tried to let the crew member do most of the talking. If I was delivering a long explanation, I was probably teaching or giving feedback rather than helping them reconstruct the call. Those can be useful too. I just wanted to know which conversation I was having.

Timing Matters

Immediately after a call, I usually kept the first check-in short: How are you doing? What do you need right now? Is there anything urgent we need to address before the next call?

A later conversation often allowed for more reflection, but learning does not obey a fixed schedule. A brief team debrief immediately after an event can capture operational details while they are fresh. A private conversation later may be better for a person who is still processing what happened.

Not every call needs both. I looked at the event, the person, the crew, and what the operation required. Someone still carrying the call was one reason to return to it, not the only one.

The Calls That Require Extra Care

Pediatric calls. Traumatic deaths. Calls where things went wrong and the outcome was bad regardless of what the crew did.

For these calls, I would begin with the person rather than forcing an immediate clinical critique. I could acknowledge that the call was hard, ask what they needed, and make room for a later clinical or operational review when appropriate.

After a call that ended badly, I would not lead with “here is what you should have done differently.” Even when the feedback is true and necessary, the timing can bury it.

What I Noticed Over Years of This

My observation was that crews who were regularly debriefed—not punished, actually debriefed—became more reflective over time. They began talking through calls with one another without waiting for a supervisor to initiate it.

I did not run a controlled study of whether those crews made fewer errors. I believed they did, and the mechanism made sense to me, but that is a retrospective operational judgment rather than a measured result. The part I can state more confidently is that the habit began to move from the supervisor into the crew.

What encouraged me was seeing the habit move from the supervisor into the crew. People began asking one another better questions without waiting for me.

A debrief is not an investigation or therapy

These boundaries matter.

A supportive debrief can help someone process a difficult call and recover their reasoning. It does not replace professional mental-health support when that is what the person needs. It also does not replace a formal investigation when patient care, policy, safety, or misconduct requires one.

The conversations may connect. Their purposes are different.

There is also a broader team debrief than the one-on-one practice described here. AHRQ’s TeamSTEPPS material uses debriefing as a short review of team performance: what happened, what worked, what did not, and what should change. That can happen quickly after an event and may serve a different need than the later supportive conversation I used with an individual crew member.

That is the same distinction I am trying to preserve in The Report Was Accurate. It Was Still Incomplete. A conversation can reveal context a formal record did not carry. More context does not erase the need for process, evidence, or accountable review.

The prompts are embedded in the Provider Development Review tools. The same question-led instinct influenced chatIR, although a product-supported incident conversation and a human debrief are not interchangeable.

Graph View

Backlinks