5 Why Tips and Tricks from practical experience
Вставка
- Опубліковано 23 бер 2021
- If you're interested in my 6-step problem solving template, it's available for free through this link: www.tommentink.com/ProblemSol...
Some thoughts and take-aways from my experience with 5 Why root cause analysis.
What type of answers and knowledge are you actually looking to gain from a Five Why.
How does it link to Correction, Corrective action and Preventive action.
How to check the logical flow of your 5 Why's.
And many minor pointers along the way. - Наука та технологія
If you're interested in my 6-step problem solving template, it's available for free through this link: www.tommentink.com/problemsolvingtemplate
I really liked the threshold of corrective to preventive when going deeper into the 5 whys!
¡Gracias, amigo!
That's cool, ey. It works really well when coaching people who are just getting into 5 Why analysis too - very often, if you reflect on a problem that they had previously solved (and go over the thinking steps again, but now with your 5 Why guidance) it's pretty easy to get to that 4-5-6 level of causes, then define actions that they would take based on the full 5 Why, and when you check those actions against the actions that they had already taken, you'll most likely see that they had taken a lot of actions at the top level causes (thinking that these are already preventive actions) and (almost) no actions on those deepest level root causes. Immediately drives home the benefits of 5 Why for them 😃
Dear Tom, this is by far the best explanation of 5Why's analysis. Thanks for this video.
Thank you Mali, for your kind words. I’m glad my video adds value for you.
Is there any other Lean-CI topic you’d like me to discuss in my videos?
This is terrific! Thanks--also loved the "don't use fishbone for RCA"!
Thanks for sharing that - it’s always nice to hear when somebody gets value from my videos
Yeah thank you for that Tom
Thank you so much
My pleasure - I'm glad you enjoyed the video. Thanks for taking the time to share that ☺
If you have questions or suggestions for other videos, don't hesitate to ask.
Hi Tom. Thanks a lot. Explanation about correction, corrective action and preventive action really answer my confusion all these year. Your channel deserve a lot more view!
Can we have more than one cause for each step in 5-why?
Thanks for sharing that praise - I’m happy that my content is helpful for you. Please do share it with your friends and colleagues 😉
Yes, you can branch out to multiple answers when going through the 5 why’s. It does complicate your picture a bit, that’s why I don’t usually show the branches. But I wouldn’t advice using them too much in root cause problem solving. I like it more to put actions on direct causes as well as on root causes (this usually takes care of taking effective corrective and preventive actions).
When we’re using the 5 why’s in a real improvement project (where we’re not chasing a single root cause, but working on improve a couple of aspect of the system to make the process more effective then previous operational results), it makes much more sense to branch out in the 5 why’s (it’s sometimes called a “why-why-because logical analysis” if you take this route), because you want to explore the most (cost-)effective way to stabilize your process or solve some issue.
As well, you are the best. Thanks a lot Tom
Thanks for your kind words Dheeraj.
I’m working on building out this root cause analysis / problem solving content to a structured online course too - what content would help you be successful with probleM solving teams?
(and no worries, the UA-cam videos will of course also keep coming 😉)
@@TomMentink from my experience people doesn’t understand where to stop 5why’s. I will recommend to add different kind scenarios. One more thing is when start using problem solving? When you see first defect ?? What is over react, under react for problem ? What if you have one machine with 20 process built in and variation is every process ??? And few processes are depend on the pervious process. I am more then happy to provide situations what I have faced. Please let me know.
Hi @@dheerajvarapana1124, would love to understand a couple of the practical situations you've faced and from which we in the CI field could learn. You're welcome to post it as comments here on UA-cam (also good for the algorithm 😉), but you should have received an email from me today or yesterday: feel free to react to that mail address.
I like the questions in your reply, the mental cogs are already turning on how to make interesting video's out of them - thank!
So, if you were going to write a white paper describing your 5Y analysis, what is the bluff or bottom line, upfront, or thesis that you start with? Do you start with the problem as the bluff or the corrective action at the root cause? In my process flow I’ve identified the problem and the whys and I understand the root cause. I do not know how to frame that in a paper. I don’t know the correct BLUF or bottom line upfront and or thesis? I could really use your input or suggestions on this based on this video.
I'm not sure I fully understand your question - if you're talking about how to present your 5 Why after you've made it, that's different from actually doing the 5 Why analysis.
When you're doing the analysis, you don't know the root causes yet. So start off with the problem statement and work you way through each next level of why it happened.
If you're looking at how to present your conclusions, the summary (on a slide this would be your title, in a white paper this would be one of your first sentences) should look something like this: was caused by , which was allowed to happen because (example: the conveyor belt snapping was caused by misalignment of the feeder and moulder, which was allowed to happen because we don't check for proper alignment after monthly cleaning).
So the answer is sort of 'both'
@@TomMentink that’s perfect and exactly what I was looking for! Thank you.
Your content is excellent. Thank you.
Thanks for your nice words, Joe
Thank you tom. Helps me a lot
I’m glad my videos help you and bring value to the CI community.
Thanks for sharing that, that’s what motivates me 😉
Awesome explanation 🎉
Thanks for sharing your kind words - I'm happy that my video was useful for you!
If you ever have some other topic you'd like me to cover - let me know 😉
Great video, thank you for it :)
Happy to hear that you like it. Thanks for sharing that.
If there are any topics you’d like me to cover, I welcome questions and suggestions 😉
@@TomMentink You are doing a great job, keep going.
I'm looking for something about "Is Is Not Analysis" and I see you didn't touch yet this topic in your films, maybe it is an idea for the next film.
Sir If we find two or three possible causes from fishbone diagram, so for each of these will we have to make 5 why's analysis?? let say temperature, unskilled man, dusty environment .For all of three we will do 5 Why's??
similarly instead of 5 why's, through validation method can we find out root causes??
If those 3 causes are equally important - yes, make 3 5Why’s to get to the root cause of each of them. More often than not, one or two of those causes will have been there for a long time or you already know that it’s way more expensive to solve, then it’s more interesting to investigate the other causes first.
As to finding root causes by elimination or validation of ‘1st level causes’ - no, not really. You should make sure that an expected 1st level cause (the direct, often physical, thing or action causing the problem) are actually happening, so you’ll want to validate their existence in any case. If you’re sure that ‘unskilled man’ was a main cause of your problem, that’s not the root cause -> you the go into the 5 Why’s to research and describe why the person wasn’t skilled (i.e. what were the reasons why there was an unskilled man operating the line; what parts of your training, operational control and procedures allow this to happen).
Keep Going!
Thank you! Glad to hear that you kind my videos. Which type of videos are most useful for you?