Learning Review
- Typical duration:
- 30m
A quick reflection format to capture what was learned, what worked, and what to change after any event or period.
Purpose
The Learning Review is a lightweight reflection format that can be applied after any event, sprint, training, or time period. It captures insights while they are fresh, reinforces a learning mindset, and prevents the same mistakes from repeating.
At a glance
| Detail | Value |
|---|---|
| Group size | 2–12 |
| Duration | 30 minutes |
| Difficulty | Easy |
| Facilitation style | Open reflection |
| Setting | In-person or virtual |
How to run
- Frame (3 min): Name what is being reviewed. State: "This is about learning, not evaluation."
- What worked well? (7 min): Each person shares one thing that went well and why. Capture on a shared board.
- What did we learn? (7 min): Each person shares one insight or surprise. This is the core of the review — new knowledge the team did not have before.
- What would we do differently? (7 min): Forward-looking: If we did this again, what would we change? Be specific.
- One action (3 min): Agree on one concrete action the team will take based on the learning.
- Close (3 min): Each person shares one word summarising their experience.
Materials needed
- Three-column board (Worked Well / Learned / Do Differently)
- Sticky notes or digital board
- Timer
Pitfalls & common mistakes
- Skipping it because time is short: A 15-minute version is better than no review at all.
- All positives, no learning: Push for genuine insights, not just celebration.
- No action: Without at least one committed action, the review is a conversation, not a catalyst.
- Doing it too late: Run within 1–2 days of the event for maximum recall.
Inclusion & accessibility
- Allow written contributions for quieter participants.
- Rotate the facilitator role.
- In virtual settings, use a digital board so everyone contributes simultaneously.
- Keep the format consistent so it becomes a team habit, not a special event.
Variations
- Individual learning journal: Each person writes their own learning review in a journal, then optionally shares key insights.
- Retrospective hybrid: Combine with a sprint retrospective for deeper team reflection.
- Cross-project learning: Review multiple projects together to spot systemic patterns.
When NOT to use this
- When the review replaces deeper analysis needed for a major failure — use a postmortem instead.
- When there is no genuine openness to change — it becomes a ritual without impact.
Source & further reading
- Chris Argyris & Donald Schön, *Organizational Learning* (Addison-Wesley, 1978)
- Peter Senge, *The Fifth Discipline* (Doubleday, 2006)
- Esther Derby & Diana Larsen, *Agile Retrospectives* (Pragmatic Bookshelf, 2006)
Turn the building blocks into an agenda
Create the day, drag the blocks into the order you have in mind, and let the times work themselves out. Or describe what you are planning to your AI and let it write the first draft.
Try it free for 14 days