Protocol

End debriefs with one changed behavior

Reflection should alter the next attempt.

About 1 min read

Before you use it

Use when
  • When teams produce good retrospective discussion but the next cycle looks identical.

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.

Keep reading

Why it matters

Convert the most important lesson into a specific behavior, owner and trigger. Prefer one implemented change over ten unowned observations.

Steps

  1. Choose the lesson with highest expected leverage.
  2. Translate it into an observable behavior.
  3. Assign owner and first use.
  4. Check it in the next cycle.

An example

The next rehearsal begins with a dependency-readiness check 24 hours earlier, owned by the cutover lead.

Check your result

At least one reviewed lesson is visible in the next work cycle.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingEnd debriefs with one changed behavior

Evidence and sources
Supports

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

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details