Lightning Talk: Incidents are new normal - Kasia Balcerzak

./resources/talk-incidents-are-new-normal-kasia-balcerzak.resources/screenshot.png

blameless incident review (1) gather facts ./resources/talk-incidents-are-new-normal-kasia-balcerzak.resources/screenshot.1.png facts events everything related to incident -logs

how our org behaved before, during, after the incident

./resources/talk-incidents-are-new-normal-kasia-balcerzak.resources/screenshot.2.png not: when did you discover yes: How did you discover…

./resources/talk-incidents-are-new-normal-kasia-balcerzak.resources/screenshot.3.png led to the incident or made the incident worse

causal factors by themselves are not a problem

incident = when causal factors are combined

eg. “not enough time for testing”

Root Causes ./resources/talk-incidents-are-new-normal-kasia-balcerzak.resources/screenshot.4.png anything that allowed to happen + be ignored

./resources/talk-incidents-are-new-normal-kasia-balcerzak.resources/screenshot.5.png

serious incidents are combination

./resources/talk-incidents-are-new-normal-kasia-balcerzak.resources/screenshot.6.png Don’t prevent things from going wrong! Try to make things go right!

risk management: “Can we handle this when it fails”

./resources/talk-incidents-are-new-normal-kasia-balcerzak.resources/screenshot.7.png

building a learning org is the only way to be proactive

./resources/talk-incidents-are-new-normal-kasia-balcerzak.resources/screenshot.8.png failing things are normal broken production is not normal

never waste a good incident to improve your org/product