Debriefs¶
An exercise produces an experience. The debrief is where the experience becomes something the organisation keeps. Skipped or rushed, it leaves the most expensive part of the preparation on the table: the group had the experience and drew little from it.
A few conditions decide whether a debrief lands.
It runs while the events are warm. The gap between what the team expected and what happened is sharpest in the hour after, and fades quickly. A debrief scheduled for the following week recovers a summary, not the texture.
It works in the group’s own words. The useful material is where “how we think we respond” diverged from what the scenario required, named by the people who lived it rather than characterised by an observer.
The facilitator asks rather than tells. What was surprising, what would have made it fail, what detection it created, what would change next time: questions without a marked answer. A participant who reached the outcome by an unexpected route has often learned more than one who followed the intended path, so explaining the right answer tends to turn a debrief into a lecture.
It is safe. A debrief that grades people produces performance rather than honesty. Psychological safety is the precondition here; the conditions for candour are the ones the facilitation and roleplay work sets out, set mostly by how the facilitator responds when something went wrong.
It harvests a little, concretely. Two or three fixes with named owners tend to outlast a long list nobody carries. Next time, last round’s fixes are visible, so the exercise is seen to move things.
The learning-environment version of this, for technical practice, is the CTF debrief and the reflection principle it rests on. The crisis-exercise version, where the debrief also has to settle the disturbance a hard scenario can leave behind, is in facilitator guidance. What a debrief harvests only counts if it then travels, which is where acting on findings picks up.
Last updated: 4 July 2026