How to Run a 5 Whys (with Humans, not Robots)(slideshare.net) |
How to Run a 5 Whys (with Humans, not Robots)(slideshare.net) |
'Root cause' can absolutely refer to a collection of events. In the example given, clearly both things were causal, clearly you fix both - you don't pick one and label it 'THE root cause' and forget about the other (yes I know he talks about prioritisation, but again that's perfectly valid when addressing a root cause that happens to be a collection).
Re: 'root causes' -- I find the words somewhat important. Like, if you say you're looking for a root cause, then people tend to be in the sort of moral mindset, and have a harder time seeing it as a collection of contingent events.
Also, in the (truly amazing) "How Complex Systems Fail", he's pretty down on "root cause":
http://www.ctlab.org/documents/How%20Complex%20Systems%20Fai...
"7) Post-accident attribution accident to a ‘root cause’ is fundamentally wrong"
The point of the exercise is to identify economical interventions that will get the system to produce better results. If you go much beyond that, people can get off into moral, analytical, or philosophical weeds and get lost.
As long as you do retrospectives and five-whys frequently, you can count on useful analytical depth to come over time. If an issue is really both important and subtle, it will crop up again. The next time you'll have another perspective, so it will be easier to find. And by waiting, you'll have avoided examining all the equally subtle but unimportant things.
http://www.amazon.com/Toyota-Production-System-Beyond-Large-...
Does anybody have a solution to this?
Now, having said that, this particular slide deck suffers very little from this problem.
Because I have that same problem -- if someone has nice visual slides, the Slideshare is often kind of useless.