Dig beyond the roots
This little whiteboard sketch has been sitting behind me for all of my video calls for a few months. It was directly inspired by Ivan Pupulidy, PhD 's talk at #LFIConf23. It's been a great way to invite curiosity from my colleagues and introduce them to the concept that analyzing incidents beyond looking for a root cause can be valuable. In essence, if you only talk about #rootcause when reviewing incidents you will likely miss opportunities to learn. You can find a singular event that fits nicely as "the root cause" and move on, but was everything else totally expected and normal? What was exceptional? What stood out to your experts? Recording and sharing these insights is the next evolution of incident analysis and I hope you can have these conversations with your colleagues too. #LearningFromIncidents #WhiteboardBackground
CEO of FireHydrant
1 年This is a good one! I've been using a Jenga tower as my metaphor for multiple contributing factors. That production change that took down service wasn't singularly the cause, but it was the catalyst. The mixture of changes that preceded an outage was already fighting gravity; the latest change made is the one that just took the blame. From: https://www.bobbytables.io/p/your-codebase-is-a-jenga-tower
Engineering Manager taking a gro?e Pause, ex-Spotify
1 年I miss your illustrations! Thanks for sharing…