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

What are you looking for?

Practice : Second-Order Retrospectives (Reflecting on Retros)

Purpose and Strategic Importance

Second-Order Retrospectives invite teams to reflect not only on their work, but on how they learn and run retrospectives themselves. They build meta-learning capability, helping teams continuously improve their improvement processes.

Without second-order retros, retros risk becoming stale rituals with diminishing value.


Description of the Practice

  • Teams review the effectiveness of their retrospectives.
  • Discussions cover format, facilitation, and outcomes.
  • Adjustments are made to increase impact and relevance.

How to Practise It (Playbook)

1. Getting Started

  • Dedicate time after a few retrospectives to reflect on the format.
  • Ask: “What makes our retros valuable? What should we change?”
  • Document and test adjustments.

2. Scaling and Maturing

  • Build second-order reflection into team cadences.
  • Experiment with new retro formats.
  • Share learnings across teams.

3. Team Behaviours to Encourage

  • Curiosity about process as well as outcomes.
  • Willingness to experiment with facilitation.
  • Shared ownership of improvement.

4. Watch Out For…

  • Meta-discussions that become too abstract.
  • Lack of follow-through on changes.
  • Teams sticking to safe, repetitive formats.

5. Signals of Success

  • Qualitative: Teams adapt retros based on reflection.
  • Quantitative: Increase in actions closed from retrospectives.
Associated Standards
  • Learning wins are recognised and shared
  • Outcomes are the basis of success
  • Experiments validate assumptions early

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

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