3 ms·
If you get the iceburg as a root cause then you are really doing something wrong; in fact I would suggest the point of a 5-Whys would be to move people past thi
by roenxi 9y ago
If you get the iceburg as a root cause then you are really doing something wrong; in fact I would suggest the point of a 5-Whys would be to move people past thinking that the iceburg is the problem and get to the actual root cause :P.
Why is the ship sinking? Hit an Iceburg.
Why did we hit an iceburg? [Equipment or command failure]
What is wrong with [maintenance strategy/command structure] that allowed this mistake to slip through?
[technical details]
If you have a team of people and something goes wrong, it is overwhelmingly likely that a human could make a decision differently or do some task that is not being done that would mitigate the worst of the damage.
People absolutely are saved by the committee process, in the same way that items tend to roll downhill. Pretending that humans have perfect control over their environment and could have done something more has proven remarkably successful at getting results. It isn't very impressive, it feels very unreasonable, and it isn't going to work on its own, but it is a very useful tool to let people to stand up and ask "sure something is going on that is out of our control, so why aren't we ready for it? This happens sometimes and we need to be prepared".
Basically, if you just ask why 5 times without any sense of personal responsibility you'll get stupid results. True of any process. But if an uncontrollable event has impacted your endeavor, it is absolutely worth asking "why are we exposing ourselves to a risk we can't control? could we somehow have avoided this".
- jjoonathan 9y agoExactly which part of this is supposed to help the ship that just hit an iceberg and is in the process of sinking? If your answer is "the relevant committee would have met before the accident" or "the committee would reduce / mitigate future accidents," you have missed GP's point.
- Moto7451 9y agoRoot Cause Analysis isn’t really meant for active emergencies like that where you can’t take time to analyze “why”. It’s a retrospective tool. If you’d like a mental model in your toolbox for an active emergency the OODA loop[0] is well tested. RCA is good for figuring out how to keep others out of the mess you’re in after the fact. [0] https://www.fs.blog/2018/01/john-boyd-ooda-loop/ https://www.fs.blog/2018/01/john-boyd-ooda-loop/
- jschwartzi 9y agoWhile the article starts to digress into a pseudoscientific mess at the end, this method of problem solving is pretty damn effective when you're under the gun. While you don't have time to deeply analyze the situation, you must make some time for information gathering and analysis, whether your deadline is in 5 minutes or 5 days. And the higher the stakes, the more important it is that you don't take shortcuts.
- jwatte 9y agoA good 5y is run after all immediate damage has been patched and triaged, and preparation for the 5y is gathering all the evidence needed for the various theories. 5y is expensive to do right. It means that organizations with lots of failure must spend time reflecting and investigating and fixing, rather than shipping new features. That is the point!
- hinkley 9y agoThe rule of thumb I give people is that if there is a different path that gets you to the 5th why in two steps it’s not really the 5th why. However, it’s still very possible to set a narrative with the five whys, because you can steer it to different contributing factors (most problems really do have more than one cause).