methodatlas
Method guideOperations

Learning Review

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium
Time1-3 h
Participants3-10
FormatWorkshop
MaturityEstablished
Plan Learning Review
01

Prerequisite

What needs to be finished first

Complete firstConcrete subject

Bound one event by time, impact, and learning purpose; confirm confidentiality and a blame-free rule.

Without a boundary the run becomes generic and untestable.
Complete firstAccess and participation

Facilitator · people with direct experience · scribe · action owners

Missing perspectives or access are made visible before starting.
02

Preparation

What needs to be ready before start

Materials

Timeline, decisions, signals, and available system or process data

People / roles

Facilitator · people with direct experience · scribe · action owners

Pre-read

Bound one event by time, impact, and learning purpose; confirm confidentiality and a blame-free rule. Prepare real cases, sources, and boundaries.

Time needed

90–180 minutes; add time for evidence collection and action follow-up.

Setup

Create a workspace with Review frame · Evidence timeline · Decision view · System factors · Learning plan; keep example values separate from live data.

03

Core question

The one question this method answers

What can we learn from the actual course of events without reducing the analysis to individual blame?

04

Flow

Phases with goal, actions, output and pitfall

Der Rückblick ordnet nicht nur den Verlauf, sondern auch die Annahmen und Signale, die das Handeln geprägt haben. So wird sichtbar, was im System verstärkt oder gebremst hat. Die daraus gewonnenen Einsichten prägen künftige Entscheidungen, statt als reine Erinnerung zu verblassen.

Learning Review · working structure

Fictional example

Fictional values are assigned to explicit method fields.

Review frame

Clarify scope, learning stance, and safe discussion rules

Checkout failures on 14 May, 09:12–09:47; the goal is learning for similar load peaks.

Evidence timeline

Reconstruct a timeline from observable events

09:12 alert, 09:18 restart, 09:31 batch paused, 09:47 stable.

Decision view

Examine decisions with the information and assumptions available at the time

The restart followed the runbook; the batch connection was not visible in the dashboard.

System factors

Connect systemic conditions and contributing factors

A shared pool, missing batch metric, and unclear escalation reinforced one another.

Learning plan

Agree learning and improvement actions with an effect check

Separate pools by 21 May; alert batch metric at 70%; review after seven days.

All details are fictional.

Reference source · original teaching example

  1. 1

    Frame

    Review frame

    Goal

    Review frame: Clarify scope, learning stance, and safe discussion rules.

    Inputs for this step

    • Bound one event by time, impact, and learning purpose; confirm confidentiality and a blame-free rule.
    • Timeline, decisions, signals, and available system or process data

    Actions

    • Clarify scope, learning stance, and safe discussion rules.

    Output

    Review frame

    Clarify scope, learning stance, and safe discussion rules

    Quality check

    Are scope, confidentiality, and a blame-free working rule confirmed?

    Pitfall

    When the blame-free working rule is not explicitly agreed, participants justify themselves instead of reporting openly. State scope, confidentiality, and the blame-free rule explicitly at the start and have them confirmed.

    Timing: Use the time needed within the overall frame; close the step only after its check passes.

  2. 2

    Timeline

    Evidence timeline

    Goal

    Evidence timeline: Reconstruct a timeline from observable events.

    Inputs for this step

    • Review frame

    Actions

    • Reconstruct a timeline from observable events.

    Output

    Evidence timeline

    Reconstruct a timeline from observable events

    Quality check

    Does the timeline separate timestamps, observations, and later interpretation?

    Pitfall

    When timestamps and interpretation are mixed together, the timeline looks more objective than it is. Reconstruct timestamps and observations first and add interpretation only afterward.

    Timing: Use the time needed within the overall frame; close the step only after its check passes.

  3. 3

    Decisions

    Decision view

    Goal

    Decision view: Examine decisions with the information and assumptions available at the time.

    Inputs for this step

    • Evidence timeline

    Actions

    • Examine decisions with the information and assumptions available at the time.

    Output

    Decision view

    Examine decisions with the information and assumptions available at the time

    Quality check

    Is each decision explained using the information available at that time?

    Pitfall

    When decisions are judged with hindsight knowledge, they look incomprehensible or careless. Have every decision explained using the information available at that time.

    Timing: Use the time needed within the overall frame; close the step only after its check passes.

  4. 4

    System

    System factors

    Goal

    System factors: Connect systemic conditions and contributing factors.

    Inputs for this step

    • Decision view

    Actions

    • Connect systemic conditions and contributing factors.

    Output

    System factors

    Connect systemic conditions and contributing factors

    Quality check

    Do factors show interactions rather than naming one person as the cause?

    Pitfall

    When a single person is named as the cause, the systemic conditions behind it stay invisible. Ask for interactions between factors instead of the one person responsible.

    Timing: Use the time needed within the overall frame; close the step only after its check passes.

  5. 5

    Learning

    Learning plan

    Goal

    Learning plan: Agree learning and improvement actions with an effect check.

    Inputs for this step

    • System factors

    Actions

    • Agree learning and improvement actions with an effect check.

    Output

    Learning plan

    Agree learning and improvement actions with an effect check

    Quality check

    Do actions have an owner, date, and observable effect signal?

    Pitfall

    When actions are agreed without an owner or evidence of effect, they quietly fade away. Give every action an owner, a date, and an observable effect signal.

    Timing: Use the time needed within the overall frame; close the step only after its check passes.

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Learning Review · Lessons LearnedEreignisse, Entscheidungen, Annahmen und Systemfaktoren rekonstruieren und in Verbesserungen übersetzen
Learning ReviewDas Visual zeigt Scope und Haltung, eine rekonstruierte Timeline, Entscheidungen, Annahmen, Systemfaktoren und daraus abgeleitete Verbesserungen.Erfahrung rekonstruieren und in systemische Verbesserung übersetzenDer Review trennt Fakten, Entscheidungen und Bedingungen, damit Lernen ohne Schuldzuweisung möglich wird.Fakten zuerstKontext verstehenHebel ableitenScope & Haltunglernen statt bewertenTimeline rekonstruierenSignal09:12Entscheidung09:28Workaround09:44Stabil10:10EntscheidungenWas war plausibel?AnnahmenWas hielten wir für wahr?SystemfaktorenBedingungen, Abhängigkeiten,InformationswegeVerbesserungenExperimente, Owner, Follow-up
Form

Learning plan with evidence, open points, owner, and review.

Versioning / ownership

Record date, owner, source state, and review date; preserve earlier versions.

Tool alternatives
  • Shared workspace
  • Timeline, decisions, signals, and available system or process data
  • Versioned result repository

learning-review-working-template.md

Plan subject, participation, complete flow, and review.

Learning Review: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete run Time: 90–180 minutes; add time for evidence collection and action follow-up.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Timeline, decisions, signals, and available system or process data
  • Roles: Facilitator · people with direct experience · scribe · action owners
  • Advance information: Bound one event by time, impact, and learning purpose; confirm confidentiality and a blame-free rule. Prepare real cases, sources, and boundaries.
  • Overall time needed: 90–180 minutes; add time for evidence collection and action follow-up.
  • Setup: Create a workspace with Review frame · Evidence timeline · Decision view · System factors · Learning plan; keep example values separate from live data.

Prepare for the work steps

Frame: Review frame

  • Bound one event by time, impact, and learning purpose; confirm confidentiality and a blame-free rule.
  • Timeline, decisions, signals, and available system or process data

Timeline: Evidence timeline

  • Review frame

Decisions: Decision view

  • Evidence timeline

System: System factors

  • Decision view

Learning: Learning plan

  • System factors

Learning Review · working structure

Review frame

Clarify scope, learning stance, and safe discussion rules

...

Evidence timeline

Reconstruct a timeline from observable events

...

Decision view

Examine decisions with the information and assumptions available at the time

...

System factors

Connect systemic conditions and contributing factors

...

Learning plan

Agree learning and improvement actions with an effect check

...

The blank worksheet contains prompts only.

Reference source · original teaching example

Frame: Review frame

Expected artifact: Review frame

Clarify scope, learning stance, and safe discussion rules

Entry:

...

  • Are scope, confidentiality, and a blame-free working rule confirmed?

Timeline: Evidence timeline

Expected artifact: Evidence timeline

Reconstruct a timeline from observable events

Entry:

...

  • Does the timeline separate timestamps, observations, and later interpretation?

Decisions: Decision view

Expected artifact: Decision view

Examine decisions with the information and assumptions available at the time

Entry:

...

  • Is each decision explained using the information available at that time?

System: System factors

Expected artifact: System factors

Connect systemic conditions and contributing factors

Entry:

...

  • Do factors show interactions rather than naming one person as the cause?

Learning: Learning plan

Expected artifact: Learning plan

Agree learning and improvement actions with an effect check

Entry:

...

  • Do actions have an owner, date, and observable effect signal?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/learning-review/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

learning-review-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Learning Review · working structure

Review frame

Checkout failures on 14 May, 09:12–09:47; the goal is learning for similar load peaks.

Evidence timeline

09:12 alert, 09:18 restart, 09:31 batch paused, 09:47 stable.

Decision view

The restart followed the runbook; the batch connection was not visible in the dashboard.

System factors

A shared pool, missing batch metric, and unclear escalation reinforced one another.

Learning plan

Separate pools by 21 May; alert batch metric at 70%; review after seven days.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Review frameWhen the blame-free working rule is not explicitly agreed, participants justify themselves instead of reporting openly.View in phase
  2. Evidence timelineWhen timestamps and interpretation are mixed together, the timeline looks more objective than it is.View in phase
  3. Decision viewWhen decisions are judged with hindsight knowledge, they look incomprehensible or careless.View in phase
  4. System factorsWhen a single person is named as the cause, the systemic conditions behind it stay invisible.View in phase
  5. Learning planWhen actions are agreed without an owner or evidence of effect, they quietly fade away.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Do not close “Review frame” while this check remains open: Are scope, confidentiality, and a blame-free working rule confirmed?
Do not close “Evidence timeline” while this check remains open: Does the timeline separate timestamps, observations, and later interpretation?
Do not close “Decision view” while this check remains open: Is each decision explained using the information available at that time?
Do not close “System factors” while this check remains open: Do factors show interactions rather than naming one person as the cause?
Do not close “Learning plan” while this check remains open: Do actions have an owner, date, and observable effect signal?

Method after Praxisgemeinschaft. The method emerged as a widespread practice and is not clearly attributed to a single originator or organization. Curated with 1 sources.

Sources: Learning Review

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.