• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Practice : Retrospectives Focused on Learning Wins

Purpose and Strategic Importance

Retrospectives that focus on learning wins shift reflection from purely process optimisation to celebrating insights, pivots, and validated assumptions. This reinforces a culture where learning is valued as progress.

Without this practice, teams risk treating retros as procedural, missing opportunities to embed curiosity and resilience.


Description of the Practice

  • Retros highlight discoveries, failed experiments, and insight-driven pivots.
  • Teams capture not just “what went wrong” but “what we learned.”
  • Outputs feed into backlogs, playbooks, and future experiments.

How to Practise It (Playbook)

1. Getting Started

  • Add a “What did we learn?” column to retrospective formats.
  • Encourage teams to bring examples of experiments or discoveries.
  • Document learning alongside actions.

2. Scaling and Maturing

  • Standardise learning-focused retros across squads.
  • Share insights across product and portfolio levels.
  • Create a knowledge repository of “learning wins.”

3. Team Behaviours to Encourage

  • Celebrating learning, not just delivery.
  • Openness about failed assumptions.
  • Pride in progress through insight.

4. Watch Out For…

  • Retros dominated by delivery metrics.
  • Teams fearing to share failed experiments.
  • Learnings not fed back into strategy.

5. Signals of Success

  • Qualitative: Teams talk about learning as much as delivery.
  • Quantitative: Increase in documented learnings influencing decisions.
Associated Standards
  • Learning wins are recognised and shared
  • Discovery operates in psychological safety
  • Outcomes are the basis of success

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering