Turns workflows, data, causes, and improvements into a tangible result by clarifying scope and stance, reconstructing the timeline, and deriving learning actions.
Which conditions, assumptions, and decisions made this event possible, and which systemic improvements increase the learning rate?
The method helps clarify workflows, data, causes, and improvements concretely. It looks for patterns, causes, weaknesses, or bottlenecks and derives actions. The result is captured as learning review notes, system factors, and improvement actions.
The team follows the steps: clarify scope and stance, reconstruct the timeline, examine decisions and assumptions, identify systemic factors, and derive learning and improvement actions. Each step is captured visibly. At the end, learning review notes, system factors, and improvement actions are available so decisions, tests, or actions can follow directly.
Method sketch for a quick mental model.
The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.
Open runsheetLearning Review follows a clear working logic: clarify scope and stance, reconstruct the timeline, examine decisions and assumptions, identify systemic factors, and derive learning and improvement actions. This turns the method into a visible thinking process rather than only a conversation. Participants move step by step from raw material, observations, or options toward a shared structure. The result is learning review notes, system factors, and improvement actions that make decisions, learning, or further planning actionable.
Prepare a clear guiding question, the right information, and a visible workspace. Plan about 1-3 h with 3-10 people and use the format in a facilitated workshop. The method needs clear structure and preparation; short timeboxes, visible intermediate results, and a parking lot for open questions help.
Compact working template for Learning Review with context, input, output artifacts, and next step.
Reflects on an event or initiative with a focus on learning rather than blame.
When and for what do we use this method?
Which data, observations, decisions, or materials are available?
Short notes along the runsheet.
Owner, date, and success signal.
Short decision aid for existing alternatives.
Statt Learning Review, wenn ihr nach einem Ereignis rasch lernen und konkrete Verbesserungen festhalten wollt.
Turns workflows, data, causes, and improvements into a tangible result through naming objectives, describing actual execution, and defining actions.
Statt Learning Review, wenn ihr nach einem Ereignis rasch lernen und konkrete Verbesserungen festhalten wollt.
Clarifies workflows, data, causes, and improvements by framing the problem precisely, branching possible causes, and defining countermeasures.
Turns workflows, data, causes, and improvements into a tangible result through defining the problem, asking why, and defining countermeasures.
Turns workflows, data, causes, and improvements into a tangible result by defining the problem, choosing cause categories, and prioritizing likely causes.
Turns sprint backlog, sprint execution, and team flow into a tangible result through reflecting on the sprint, collecting positives and challenges, and carrying actions into the next sprint.
Turns incident work, roles, and countermeasures into a tangible result by collecting sources, ordering events chronologically, and deriving lessons and actions.