Great use of the tool

@learnkaizen

2 жыл бұрын

Thank you!🙏

I want to ensure I understand your usage of the tool. #1 Facilitate development of the Fishbone Diagram #2 prioritize root causes by theme (system, people, etc) #3 Prioritize the potential causes (branches) until you get to a qualitative measure u can test. If the countermeasure doesnt solve the problem does the team go back to the spreadsheet and look at the next themes/causes and take action? This sounds like PDCA

@learnkaizen

Жыл бұрын

Hey Tamika! It’s been a while since I’ve seen a comment from you!!! Nice to see you’re still part of the channel! To be fair, I don’t post often…trying to get better. ☺️ Yes, I think you’ve got it. I’d lean on PDSA versus PDCA since we’re analyzing/studying data to drive the next action but you’ve got the right thought process down! The PDCA/PDSA is applicable to so many CI directions…whether improving or solving problems…Thank you for your continued support! 🙏

Awesome 😎

@learnkaizen

2 жыл бұрын

🙏

Is the Masterclass Membership still free?

@learnkaizen

Жыл бұрын

No…sorry. I had to stop because I didn’t have the capacity to manage the free membership and the Kaizen Masterclass…I took on a new role that required significant travel- which reduced my available time. Thank you for asking a I hope you’ll still visits and get value from my channel. 🙏

👍🙏👍

In another video you say there is only one root cause to a problem. In fishbone diagrams you normally have many contributors to a problem. Which one do you see as the root cause then?

@learnkaizen

Жыл бұрын

The Ishikawa (Fishbone) illustrates POSSIBLE contributors…and it’s possible two or more contributed to the problem…however, the root cause must be process related because if we remedy the process, we prevent recurrences. If we remedy a contributor (or all contributors) we’ll see the problem again. Thanks for the question! Let me know if I can help further! 🙏

@robertshreffler6155

Жыл бұрын

@@learnkaizen contributors I get, they contribute to the cause. But we are not looking at a process chart. So how can you say it's the process we need to address while what we are analyzing here are all the contributors to a defective process? maybe I am not saying this exactly right either

@learnkaizen

Жыл бұрын

@@robertshreffler6155 I think you've asked a great question and I can completely understand where it may get confusing...Let me try to explain (always difficult over text/email but I'll try)... Analyzing contributors is the right thing to do...then you'll drive down to the main contributors and fix those...most of the time this is simply a poka yoke of some sort (which is great) - but then we need to continue the problem solving investigation to understand what in the process allowed the failure. Here is an example: I had a flat tire on the way to work. A very basic level of problem solving would be to replace the tire. A deeper analysis may result in a fishbone: Y=(Flat Tire), X=(nail, old tire, screw, NG tread, leaking air, etc)...(Contributors). We find that it's a nail in tire (Cause), Why: Construction in Neighborhood - loose nails everywhere. No process to examine tires prior to leaving neighborhood to ensure correct pressure in tires (Root Cause)...Fix=Check Air pressure each night and each morning. Record pressure. If pressure decreases by- 2 PSI - examine tires for nails. if we stopped at changing tire, the problem would happen again, if we stopped at removing nail and patching, the problem would happen again. By establishing process to ensure correct air pressure with measurement - we've introduced a process that will help eliminate the flat tire...this is a basic example with plenty of holes in it (no pun intended😀) but hopefully clarifies my intent.

Can i solve any problem with this tool ? Also are you an engineer? Thanks

@learnkaizen

Жыл бұрын

Well, it’s certainly useful for many..I’m have a BSIE and MBA…why do you ask? I’ve been in this field of study for over 2-decades..,

@Hawkfeet

Жыл бұрын

@@learnkaizen I asked because my nephew is a fresh graduate as a industrial engineer Could you please talk about your experience in the field and suggest a road map for fresh graduates Thanks

@learnkaizen

Жыл бұрын

Awesome! I’m an IE as well. I am planning a video around this topic. Should be released in the next couple of weeks be sure to subscribe and turn on the bell notification so you’ll be notified when it releases - or perhaps suggest subscribing to your nephew. Thanks for the support!

@Hawkfeet

Жыл бұрын

@@learnkaizen already subscribed

I am not being rude...but a machinist could have figured out that problem in 1 day

@learnkaizen

Жыл бұрын

That’s not rude at all. I’ve worked with lots of machinists over my career…machinists are great problems solvers. They tend to have a systematic mindset which is needed for systematic problem solving. Not all machinists are great (or even good) problem solvers but I’d say a majority are. Having said that, there were machinists who worked this problem for months. Some awesome machinists and awesome problem solvers employed in aerospace - so they know what they are doing. In this case, not even some great machinists solved the problem in one day. However, they were part of the solution. I could not have solved this on one day. They could not not solve this on one day…however, together, I think we did a great job at systematically solving the problem while keeping impeccable records to understand how each change we made impacted the outcome. I appreciate your input and value your opinion! With sincere respect: the main issue I run in to when I am working with a team who hasn’t solved the problem after trying is that they always know what the problem is…but it’s still reoccurring. If they can’t turn the problem off and on at will, they haven’t gotten to the root cause. Again, that you for the input.