Facilitating a Blameless Postmortem

Overview

The facilitator's job

The postmortem facilitator guides the room to system-level causes without letting the conversation drift toward individual blame.

Most postmortems fail not because the facts are wrong but because psychological safety breaks down: engineers get defensive, root-cause analysis gets shallow, and action items become symbolic rather than structural.

> [!IMPORTANT] Findings go to the system, the process or the tooling. The engineer's action is a trigger, not a root cause.

How postmortems break down

• Blame enters the room — Engineers get defensive and withhold detail
• Shallow analysis — The trigger is mistaken for the root cause
• Too many action items — Nothing ships, creating false confidence
• Owners are teams, not people — Items drift without follow-through

Interview questions

• You are facilitating a postmortem for a 2-hour outage caused when an engineer deleted a production Kubernetes namespace by mistake. Three product managers are demanding accountability. How do you run the session?
• The postmortem surfaces 14 action items. How do you prioritize and ensure they actually get done?

More SRE topics

• Disaster Recovery
• Distributed Consensus
• Distributed Tracing
• DoS Attack Mitigation
• Error Budget Exhausted — Mid-Sprint
• Error Budgets
• Five Whys
• Forecasting Models
• Game Days & Chaos Engineering
• GitOps
• Graceful Degradation
• High Availability