Rethinking the #FiveWhys: Introducing the ‘Many Whys’ Approach in #Lean #ProblemSolving for #Lean and #LeanStartup

https://www.leanblog.org/2015/11/rethinking-five-whys-lean-problem-solving/

If your only plan for avoiding a process failure in the future is "more training" you're probably doing it wrong. Building smarter humans is not a substitution for improving the process.

Before folks jump on me for that, please note that I'm not saying training isn't important. What I am saying is, it probably shouldn't be the only response.

#DevOps #FiveWhys

I've been thinking about my reactions to #CrowdStrike since, fortunately, we weren't affected - and comparing it to others', both at work and beyond.

Reading their preliminary incident report certainly emphasises the "wait, just relying on an automated test framework without actually running the thing?!" reaction.

But underlying that reaction for me is a hope that there is one simple, obvious, thing they weren't doing. Because if there is, and we're not making the same mistake in our #SDLC, I can reassure my stakeholders - and myself - that we won't be so negligent.

But there's a reason #FiveWhys is useful: if you don't understand the causes, you end up just fixing the symptoms.