How do you conduct a post-mortem after a catastrophic Sev1 outage triggered by a junior engineer's mistake, without succumbing to the blame game?
Answer
Short answer
Analyse the leader's approach to blameless post-mortems, identifying root causes over symptoms, and driving accountability for remediation.
Was this answer helpful?
Likely follow-ups
- How do you keep the post-mortem blameless when the engineer's mistake was a repeat of a nearly identical incident six months earlier?
- How do you prioritise remediation items when the "Five Whys" surfaces ten systemic gaps but the team only has capacity to fix two before the next quarter?
- An executive leaks a version of the incident report externally that names the engineer responsible. How do you respond, and what does it do to the blameless culture you were trying to build?
Related questions
- How do you execute the Inverse Conway Maneuver on a 200-person engineering org that accidentally built a distributed monolith mirroring their dysfunctional silos?hardAlso on engineering-leadership3 min
- How do you isolate a degraded dependency and halt a cascading failure before thread pool exhaustion takes down the entire microservice ecosystem?hardAlso on reliability2 min
- When your infrastructure is heavily coupled to proprietary managed services, how do you design and execute a cloud provider exit strategy without obliterating the business?hardAlso on engineering-leadership2 min
- You want to prove the system survives losing a database, in production, on a Tuesday afternoon. How do you run that without being fired?hardAlso on reliability7 min