A debrief that leaves actions, not feelings DEBRIEF

The four questions are not the problem

The structure of a good debrief has been settled for decades: what was supposed to happen, what actually happened, why there is a difference, and what we do about it. Everybody in the room knows them. Debriefs still fail, and they fail in the same two places every time.

The fourth question gets answered in the passive voice

“Communications need to be looked at.” That is not an action. It has no owner and no date, nobody in the room believes it will happen, and it is why the same point appears at the next debrief and the one after, slightly more wearily each time.

So a learning point here is not finished until a name and a date are attached to it, and a point without them is displayed as what it is: a sentence. That is uncomfortable in the room and it is the entire value. The moment somebody has to be named, the group finds out whether the point is real. Either a person accepts it, in which case something will happen, or nobody will take it, which tells you it was a complaint rather than an action, and that is worth knowing too, because a complaint is legitimate and needs raising somewhere else.

Name a person, not a team. “Ops will review the callout list” has the same problem in a longer form: on the day, Ops is nobody. One name, and that person can delegate it.

The gap gets filled with blame

The difference between what was supposed to happen and what happened is the interesting part of the whole exercise, and it is where a debrief turns into a search for who was at fault. Once that starts, everything useful stops: people describe what they can defend rather than what they saw, the person who knows most says least, and the account you end up with is wrong in exactly the places that matter.

The discipline is to keep the difference factual and separate from the cause. What was the plan. What happened, in order, in times. Only then why. And “why” should be answerable in terms of information, equipment, time, training and instructions rather than in terms of character. Almost every gap comes from somebody acting sensibly on what they knew at the time, and the question worth an hour is why what they knew was not what was in somebody else's head.

Do it quickly, while people remember. Memory of sequence and timing degrades within days and is then reconstructed from the account everybody else has agreed on, which is how a group arrives at a confident shared version that nobody actually witnessed.

Everything stays in this browser and nothing is uploaded, which matters, because a debrief record names people and describes what went wrong. Export it and keep it where the organisation keeps such things. Nearby: STATEMENT seals an individual account with a digest, TIMELINE builds the chronology with sources, DECISION records what was decided and what was known at the time, and HANDOVER is where the actions go next.