Expert Debrief¶

Ritual — instantiates Tacit Knowledge Elicitation

A short, recurring after-the-case review in which practitioners talk through what they noticed, considered, and were unsure of — turning tacit judgment into a standing team habit rather than a one-off study.

Most elicitation is a project someone runs on the experts. Expert Debrief is the version the experts run on themselves, as a routine — a brief, structured conversation held right after a case, in which practitioners surface the cues they read, the alternatives they weighed, why they chose as they did, and what they were unsure about. Its defining feature is that it is a recurring ritual, not a study: it fires after every case (or every shift, or every incident), it is cheap and habitual, and its output loops back to the same practitioners who then correct and refine the shared understanding over time. Because it runs while the case is fresh and among peers who were there, it captures the reasoning that a scheduled interview weeks later would have lost — and because it repeats, tacit knowledge accumulates and gets re-checked as a continuous team practice.

Example¶

A wildland fire crew holds an after-action review at the end of a shift on the line — fifteen minutes, standing in the black, while the day is still vivid. The crew boss walks it back: Why did we disengage from the north flank when we did? What were you seeing? A sawyer names a cue — the smoke column had started to lean and "the wind felt like it was about to come around" — that hadn't made it into any radio call. Someone else weighed staying; the boss explains the alternative he rejected and the uncertainty he was carrying about the escape route.

None of this is a formal knowledge-capture project; it's a standing habit. But over a season, the same cues and the same rejected alternatives recur across debriefs, and the crew's shared read of "when the column tells you to leave" sharpens. Crucially, the understanding loops back: a rule of thumb voiced in one debrief gets tested and corrected in the next, by the same people. What the ritual gives up is depth and rigor on any single decision — it's fast and conversational, not a controlled reconstruction — but it captures reasoning while it's warm and keeps the whole crew's judgment converging.

How it works¶

Fire it right after the case. The ritual triggers on a recurring event — end of shift, close of incident, after a procedure — while memory is fresh and the participants who were present are all there.
Probe cues, alternatives, and uncertainty. The standing questions ask what was noticed, what else it might have been, why this call over that one, and what remained unsure — surfacing rationale, not just recounting events.
Keep it short and habitual. The point is repeatability, not exhaustiveness; a five-to-fifteen-minute format that always happens beats a thorough review that happens rarely.
Loop the understanding back. What surfaces feeds a shared read that the same practitioners revisit and correct in subsequent debriefs — an iterative refinement, not a one-shot capture.

Tuning parameters¶

Cadence — every case, every shift, or only notable events. Frequent debriefs capture more and build the habit but risk fatigue and box-ticking; rare ones lose the fresh cases in between.
Facilitation structure — a fixed question set or open discussion. Structure keeps the reasoning-probe from decaying into a status update; too much structure makes it rote.
Psychological safety — how blameless the frame is. Higher safety surfaces honest uncertainty and error, which is where the tacit content is; a punitive frame collapses the debrief into self-justification.
Capture vs. conversation — whether anything is written down. Recording feeds durable artifacts but adds friction and can chill candor; a purely spoken ritual is lighter but leaves no trail.

When it helps, and when it misleads¶

Its strength is freshness and continuity: it catches reasoning while it is still warm, among the people who were there, and — because it recurs — it turns elicitation into an accumulating team habit rather than a one-time extraction. It is also low-cost and self-sustaining once the ritual takes hold.

Its failure modes come from the same informality that makes it cheap. The curse of knowledge bites hard: experts debriefing peers assume shared context and skip the very tacit steps a novice would need spelled out, so the most automatic knowledge stays unspoken.^[1] Without safety, the debrief curdles into justification and blame-avoidance, hiding exactly the errors and uncertainties worth learning from. And a recurring ritual decays — attendance slips, the probe questions go rote, and it becomes a status update wearing a debrief's clothes. The classic misuse is running it to assign responsibility rather than to learn, which kills candor at the root. The discipline that keeps it alive is a blameless frame, a rotating but real question structure aimed at cues-alternatives-uncertainty, and periodically feeding what surfaces into a durable artifact so the loop leaves something behind.

How it implements the components¶

Expert Debrief fills the components suited to a fast, recurring, peer review:

decision_rationale_probe — its standing questions surface why the call was made, what alternatives were weighed, and what remained uncertain, while the case is fresh.
practitioner_feedback_loop — because it recurs with the same people, what surfaces loops back into a shared understanding they iteratively correct, rather than being captured once and frozen.

It is fast and conversational, not a rigorous single-case reconstruction (exception_probe, deep recall — Cognitive Interview) and not artifact-anchored (decision_trace — Decision Trace Review); it does not itself produce the durable representation (provisional_articulation — Judgment Aid / Case Library Capture).

Instantiates: Tacit Knowledge Elicitation — Expert Debrief is the recurring, low-friction ritual that keeps eliciting and refining tacit judgment as a team habit.
Sibling mechanisms: Cognitive Interview · Judgment Aid · Decision Trace Review · Critical Incident Technique · Cognitive Task Analysis · Case Library Capture · Think-Aloud Protocol · Shadowing Session · Apprenticeship Observation · Simulation Replay · Task Analysis

Notes¶

Expert Debrief is where much elicited knowledge is first spoken but not where it is kept. Its natural downstream partners are Case Library Capture and Judgment Aid: pipe the recurring insights from debriefs into those durable artifacts, or the ritual's steady output evaporates between sessions. Left purely oral, a debrief culture can hold knowledge well within a team and transfer none of it beyond it.

References¶

[1] The curse of knowledge — once you know something, it becomes hard to model not knowing it — is why experts debriefing other experts systematically omit the tacit steps a novice would need. Naming it explains the recurring gap in peer debriefs and motivates deliberately probing for the "obvious" moves the participants would otherwise skip. ↩