How to run a great incident post-mortem

In building software, continuous learning and blameless culture are mainstays of high-performing teams.

From Accelerate, to the Agile Manifesto, to Google’s research, psychological safety and learning from mistakes are the key attributes of great teams. But what about when things go seriously wrong? How do strong teams overcome these failures in one piece? The answer lies within ‘the blameless post-mortem’: a process nicely defined by Google’s SRE culture guide as ‘focused on identifying the contributing causes of the incident without indicting any individual or team for bad or inappropriate behavior’.

These contributing causes that we seek to identify are ones that stem from the system in which we work, and not from any individual actor.

Join LeadDev.com for free to access this content