Protocol

Ask what helped, what hindered and what changes next

A useful review connects observation to a specific next change.

About 1 min read

Before you use it

Use when
  • A retrospective is drifting into a list of complaints or generic lessons.

Keep this limit in mind

  • This is a reflection scaffold, not a causal proof. A promising explanation may still need a test.

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

Run three passes: what supported the result, what obstructed it, and what should change next time. Keep statements close to behaviors, interfaces, conditions and decisions. Preserve successful controls as deliberately as you fix failures.

Steps

  1. Every proposed change points back to an observed condition rather than a generic slogan.

An example

Helped: a dry-run file. Hindered: validation happened only after the full batch. Next change: validate the first 20 records automatically. Keep: dry-run checklist.

Check your result

Every proposed change points back to an observed condition rather than a generic slogan.

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 readingAsk what helped, what hindered and what changes next

Evidence and sources
Supports

Structured debriefs or after-action reviews have been studied as a way to support learning from experience, with meta-analytic evidence of improved performance on average across varied settings.

Average effects across studies do not predict the benefit of a particular review; facilitation, task and implementation matter.

Do Team and Individual Debriefs Enhance Performance? A Meta-Analysis · Abstract: objective, method, results and application

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