Learning Reviews

Facilitated reviews, psychological safety, near misses, and sharing lessons across teams.

7 min readSRE PlaybookOperate

What Are Learning Reviews?

Learning reviews are facilitated discussions focused on organizational improvement. Unlike postmortems (which focus on specific incidents), learning reviews look across multiple incidents to find systemic patterns and shared lessons.

Learning reviews are systemic, not incident-specific

A postmortem asks 'what happened here?' A learning review asks 'what patterns do we see across incidents?' Learning reviews identify systemic issues that individual postmortems cannot.

Facilitation

Learning reviews require skilled facilitation. The facilitator creates a safe space, guides the discussion, and ensures all perspectives are heard. The facilitator should be neutral — not involved in the incidents being discussed.

Facilitation guidelines


facilitation_guidelines:
  before:
    - "Select incidents to discuss (3-5 related incidents)"
    - "Invite participants from relevant teams"
    - "Share pre-reading (postmortems, timelines)"
    - "Set ground rules (blameless, confidential)"

  during:
    - "Start with ground rules reminder"
    - "Review each incident briefly"
    - "Identify patterns across incidents"
    - "Discuss systemic contributing factors"
    - "Generate improvement actions"
    - "Ensure all voices are heard"

  after:
    - "Document findings and action items"
    - "Share summary with broader organization"
    - "Track action item completion"
    - "Schedule follow-up review"

  skills:
    - "Active listening"
    - "Asking open-ended questions"
    - "Managing dominant personalities"
    - "Ensuring psychological safety"
    - "Synthesizing diverse perspectives"

Psychological Safety

Psychological safety is the belief that you will not be punished for speaking up. It is essential for learning reviews. Without it, people hide mistakes, avoid honest discussion, and the organization cannot learn.

Building psychological safety


psychological_safety:
  practices:
    - "Blameless language throughout"
    - "No performance reviews based on incident involvement"
    - "Leadership models vulnerability"
    - "Celebrate learning from failures"
    - "Protect people who speak up"

  ground_rules:
    - "Focus on systems, not people"
    - "All perspectives are valuable"
    - "What is said here stays here"
    - "No retaliation for honest feedback"
    - "It is okay to say 'I don't know'"

  leader_behaviors:
    - "Admit own mistakes openly"
    - "Ask for feedback regularly"
    - "Respond to bad news with curiosity, not anger"
    - "Give credit for identifying problems"
    - "Do not shoot the messenger"

Near Misses

Near misses are incidents that almost happened but were caught before causing impact. They are free learning opportunities. Analyze near misses with the same rigor as real incidents.

Near miss analysis


near_miss_analysis:
  definition: "An event that could have caused an incident but did not"

  sources:
    - "Close calls caught by monitoring"
    - "Deploy rollbacks before user impact"
    - "Capacity issues caught in testing"
    - "Security vulnerabilities caught in code review"

  value:
    - "Same lessons as real incidents, zero user impact"
    - "More frequent than real incidents"
    - "Easier to discuss (no blame pressure)"
    - "Free learning opportunities"

  analysis_process:
    - "Treat near misses like real incidents"
    - "Reconstruct timeline"
    - "Identify contributing factors"
    - "Write action items"
    - "Share lessons across teams"

  tracking:
    - "Log near misses in a shared system"
    - "Categorize by type and team"
    - "Review patterns monthly"
    - "Share trends in learning reviews"

Cross-Team Learning

Cross-team learning shares lessons across the organization. A learning review with multiple teams reveals patterns that single-team postmortems cannot. It builds shared understanding and prevents silos.

Cross-team learning program


cross_team_learning:
  format: "Monthly learning review"
  participants: "SRE leads from all teams"
  duration: "90 minutes"

  agenda:
    - time: "0-15 min"
      item: "Review incidents from the past month"
    - time: "15-45 min"
      item: "Identify patterns across incidents"
    - time: "45-75 min"
      item: "Discuss systemic contributing factors"
    - time: "75-90 min"
      item: "Generate cross-team action items"

  sharing_mechanisms:
    - "Monthly reliability newsletter"
    - "Quarterly reliability review meeting"
    - "Shared postmortem repository"
    - "Cross-team game days"
    - "Reliability engineering community of practice"

  metrics:
    - "Number of cross-team action items"
    - "Reduction in incident recurrence"
    - "Knowledge sharing score (survey)"
    - "Cross-team game day participation"

Learning Review Template

Learning review template


# Learning Review: [Topic]

## Date: YYYY-MM-DD
## Facilitator: [name]
## Participants: [names and teams]

## Incidents Reviewed
| ID | Title | Team | Severity | Date |
|----|-------|------|----------|------|
| INC-001 | [title] | [team] | SEV[X] | [date] |
| INC-002 | [title] | [team] | SEV[X] | [date] |

## Patterns Identified
1. [Pattern 1]: [description]
2. [Pattern 2]: [description]

## Systemic Contributing Factors
- [Factor 1]: [description]
- [Factor 2]: [description]

## What We Learned
- [Lesson 1]
- [Lesson 2]

## Cross-Team Action Items
| ID | Title | Owner | Due | Teams Affected |
|----|-------|-------|-----|----------------|
| CL-001 | [title] | [owner] | [date] | [teams] |

## Next Review
- Date: [date]
- Focus: [topic]

Learning reviews compound

Learning reviews compound over time. Each review builds on previous ones. Patterns become clearer, systemic fixes more comprehensive, and organizational learning deeper. Start small and scale as you see value.

Mark this lesson complete to store local progress and unlock a cleaner resume path the next time you visit.

Stage 6 · Operate

Blameless Postmortems & Learning