RunsheetOperations

Learning Review

ComplexityMedium

Time1-3 h

Participants3-10

FormatWorkshop

MaturityEstablished

Prerequisite

What needs to be finished first

Complete firstBlameless Postmortem

A blameless norm is established in the team or explicitly agreed for this session.

Without: Without a blameless norm the session slips into blame assignment and no learning happens.

Complete firstIncident Timelinenot in catalog

A chronological record of the incident or initiative with timestamps, decisions, and actions is available.

Without: Without a timeline the group speculates about sequence, and learning stays superficial.

Preparation

What needs to be ready before start

Materials

Whiteboard or Miro board with horizontal timeline; columns for decisions, assumptions, systemic factors, learning points, improvement actions; logs and data for the event; timer.

People / roles

One facilitator experienced in learning-oriented moderation; three to ten participants from the initiative; one scribe for learning points and actions; optional neutral observer from outside the team.

Pre-read

Scope and time window of the event or initiative; timeline; known data sources; list of participants; pre-aligned attitude (learning, not blame); privacy rules for statements.

Time needed

1-3 h

Setup

Timeline on the left side of the board, columns on the right. Ground rules visible (blameless, curious, systemic). Phones away. Recording optional, with explicit consent.

Core question

The one question this method answers

Which conditions, assumptions, and decisions made this event possible, and which systemic improvements increase the learning rate?

Flow

Marker: Phase

Step	Duration	Action	Hint
1Phase 1: Scope and mindset	10-15 min	Facilitator introduces scope (event, time frame, participants). Agree ground rules: blameless, curious, systemic. Clarify expected output.	If someone already has a blame narrative, run a short 1:1 beforehand. Otherwise Phase 3 quickly turns into defensiveness.
2Phase 2: Reconstruct timeline	20-30 min	Complete timeline together: what happened when, who was involved, what actions were taken? Mark gaps. No evaluation in this phase.	Different perspectives may run in parallel. Some participants experienced different event aspects, so keep all observations.
3Phase 3: Examine decisions and assumptions	20-40 min	For each decision in timeline ask: what knowledge was available at decision time? What assumptions supported it? What alternatives were visible? Do not allow hindsight bias.	“You should have known” is hindsight bias. Ask instead: what was known and unknown at the decision point?
4Phase 4: Identify systemic factors	20-30 min	Which conditions enabled this event? Pressure, tools, processes, communication channels, incentives? For each factor ask: what would reduce it?	Systemic factors are the most valuable insight. If participants keep jumping to people, they miss the method.
5Phase 5: Learning points and actions	20-30 min	For each systemic factor, create a concrete improvement action with owner and date. Separate detection and prevention. Document learning points even without immediate action.	Not every learning point needs an action. Some insights are awareness building. Keep actions under 5 per review, or they become diluted.

Artifact

What comes out at the end

Form

Learning Review document with scope, timeline, decisions with time-of-knowledge, systemic factors, learning points, and improvement actions with owner and date plus follow-up time.

Versioning / ownership

One entry per event with date and participants. Review action status (open, in progress, done) regularly. Cross-event Learning-Learned aggregation enables pattern detection.

Tool alternatives

Confluence page in postmortem space
Markdown in repo under docs/learning-reviews/
Notion database with linked records
Miro with photo export for visualization

learning-review-working-template.md

Compact working template for Learning Review with context, input, output artifacts, and next step.

Learning Review Working Template

Goal

Reflects on an event or initiative with a focus on learning rather than blame.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

Learning Review Notes:
System Factors:
Improvement Actions:

Assumptions and open questions

Decision / Next step

Owner, date, and success signal.

Example output

Concrete filled scenario, fictional example

learning-review-beispiel.md

Concrete filled scenario, fictional example

Learning Review — Delayed Q1 Activate Launch (06.05.2026)

Scope: Planned onboarding flow launch for 15.03.2026, actual launch 28.04.2026, delay 6 weeks.

Timeline excerpt:

12.01.: Roadmap commitment for 15.03.
02.02.: Dependency on auth refactor known, estimate 1 week.
19.02.: Auth refactor runs 3 weeks, no explicit replanning.
09.03.: Tracking issue, 2 days spike.
14.03.: Launch moved to 03.04.
28.04.: actual launch.

Decisions:

12.01. Roadmap commitment: knowledge at the time was 8 person-weeks estimate for onboarding without auth refactor. Assumption: auth refactor already finished. (Wrong).
19.02. No re-plan: knowledge was auth running 3 weeks. Assumption: 15.03 still feasible. (Wrong).

Systemic factors:

Dependency tracking missing in quarterly plan.
Re-planning routine missing when assumptions break.
Pressure not to change quarter-end commitment.

Actions:

Pre-quarter check for cross-team dependencies, template due 25.05. Owner: @anna.
Re-plan trigger: when an assumption deviates by more than 50%, 30 min replanning. Owner: @ben for Slack reminder.
Quarterly commitments with sponsor sync on deviation, from next quarter onward. Owner: @julia.

Actions are written down but never checked; patterns repeat.

What to do

Fix follow-up in 6-12 weeks. Keep action status visible (tracker, wiki).

Stop criteria

Done signals checkable in under a minute

Blameless norm not established or participants are defensive.

Timeline is missing, reconstruction stays speculative.

Workshop is under 45 min and five phases cannot be completed.

Participants are under performance evaluation and review becomes a statement against them.

Missing participants whose perspective is required for the timeline.

Event is trivial and the method creates unnecessary bureaucracy.

Finished the runsheet?

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

Go to profile More methods