Gartner has predicted that in 2015, 80% of outages will be caused by people and process issues. Are you considering the Human element when revisiting incidents and outages with your infrastructure? If so, are you approaching it with a blameless mindset? An agenda focused on removing bias in many forms, searching for absolute truth. Do you believe that there is always a root cause to problems or is it more accurate to seek out additional aspects that may have attributed to the incident, especially with regard to the people and processes? Regardless of your approach, the point of a post-mortem is to accurately describe the "story" about what took place in as much detail as possible. The good, the bad, those involved, conversations had, actions taken, related timestamps, who was on-call, etc. You want to know absolutely everything that took place and was related in some degree so that you can review the data and learn from it. How do we ensure that we are asking the right questions and seeking out relevant and important information that will help us understand what took place and ultimately how to become a better team, company, and product as a result? I'll introduce best practices for conducting effective post-mortems and illustrate their importance with statistical data to back up the claims, demonstrating that there are measurable benefits from adopting post-mortems especially those of a "blameless" nature.
jasonhand
fumiyasac0921
shumei_ito
%20(1).jpg){kind=avatar}
giftojabu1
takumiogawa
oracle4engineer
syntasso
minorun365
hirosatogamo
negi111111
sansantech
salaboy
wjessup
tanoku
kneath
shpigford
ufuk
eitanlees
swwweet
chriscoyier
bryan
lauravandoore
maltzj
honnibal
