Question
Start debriefs from expected versus actual
Comparison gives reflection an anchor.
When it fits
- When retrospectives drift into general impressions and recent anecdotes.
When to avoid it
- 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.
A question to ask
What did we expect? · What actually happened? · Which gap matters most? · What explains that gap well enough to change the next attempt?
Why it matters
Write the expected result or process first, then place actual evidence next to it. Investigate the largest meaningful gap instead of collecting every complaint.
An example
The team expected all 500 records to reconcile in 20 minutes; actual result was 420 in 55 minutes with one queue bottleneck.
Check your result
The debrief centers on an observable gap rather than a mood survey.
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.
Connected ideas
Useful withEnd debriefs with one changed behavior
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