From 576eef408a020862adbcb267450a7c1fceb903bd Mon Sep 17 00:00:00 2001 From: "Roland Edwards, AOE GmbH" <39269273+raedwards@users.noreply.github.com> Date: Wed, 16 May 2018 15:06:49 +0200 Subject: [PATCH] Update blameless-post-mortems.md --- radar/2017-10-01/blameless-post-mortems.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/radar/2017-10-01/blameless-post-mortems.md b/radar/2017-10-01/blameless-post-mortems.md index afcc181..f6c5c68 100644 --- a/radar/2017-10-01/blameless-post-mortems.md +++ b/radar/2017-10-01/blameless-post-mortems.md @@ -8,10 +8,10 @@ quadrant: methods-and-patterns > > — Jeff Bezos -Blameless Post Mortems provide a concept of dealing with failures inevitably occuring when developing and operating complex software solutions. After any major incident or outage the team gets together, performing an in-depth analysis of what has happened and what can be done to mitigate the risk of similar issues to happen in the future. +Blameless Post Mortems provide a concept of dealing with failures that inevitably occur when developing and operating complex software solutions. After any major incident or outage, the team gets together to perform an in-depth analysis of what happened and what can be done to mitigate the risk of similar issues happening in the future. -Based on trust and under the assumption that every person involved had good intentions doing the best given the information at hand, Blameless Post Mortems provide an opportunity to continuously improve the quality of software and infrastructure and the processes to deal with critical situations. +Based on trust, and under the assumption that every person involved had good intentions to do the best-possible job given the information at hand, Blameless Post Mortems provide an opportunity to continuously improve the quality of software and infrastructure and the processes to deal with critical situations. -The post mortem documentation usually consist of both a timeline of the events leading to an incident and the steps taken to its remediation, and future actions and learnings for increasing reslience and stability of our services. +The post mortem documentation usually consists of both a timeline of the events leading to an incident and the steps taken to its remediation, as well as future actions and learnings for increasing reslience and stability of our services. At AOE, we strive to conduct a Blameless Post Mortem meeting after every user-visible incident.