What is blameless post mortem
In software development, failure is inevitable.Here's a summarized version of our internal documentation describing how we run postmortems at atlassian.What actions they took at what time, what effects they observed, expectations they had, assumptions they had made, and their understanding of timeline of events as they occurred.A blamelessly written postmortem assumes that everyone involved in an incident had good intentions and did the right thing with the information they had.You ignore the 'this person did that' part, explains pagerduty engineering manager arup chakrabarti.
While running one is not an easy task, the effort is well worth it.This is key to the culture of a team that improves systems quickly.Get the handbook in print or pdfBeing blamed for outages creates a crappy working environment, and people are going to look for.
