Protocol
Debrief the work, not the person
A useful debrief reconstructs decisions, conditions and actions.
Before you use it
- Use when
- When a result was poor and the team needs to learn without turning review into blame.
Keep this limit in mind
- Team-learning practices consume time. Use them where there is a real performance or coordination question, and do not substitute process rituals for domain expertise.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Review what was expected, what happened, what information was available, what helped or hindered and what should change next time. Personal accountability can remain explicit without replacing system learning.
Steps
- Restate expected outcome.
- Reconstruct what actually happened.
- Identify decision and coordination gaps.
- Choose one or two changes for the next cycle.
An example
After a failed cutover rehearsal, the team traces missing ownership and late validation rather than opening with 'who caused this?'
Check your result
The review produces a change to the next cycle and can still name accountable actions.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingDebrief the work, not the person
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaEscalate process risk without attacking motives
Evidence and sources
A meta-analysis of 46 samples found structured debriefs improved effectiveness on average and identified alignment, facilitation and structure as potentially important design features.
Average effects across training and work settings do not imply that every retrospective meeting is useful or that longer debriefs are better.
Do Team and Individual Debriefs Enhance Performance? A Meta-Analysis · Abstract
Edition and review
Version 0.1.0
No review details are supplied for this edition.