Do you have ever thought about the aftermath for your root cause analysis? What should be done if you have found the real cause of your problem? What do you regularly do after you have made your correction?
By the way – do you know whether your correction really corrects the problem? That it only corrects the problem? And does not introduce a ton of new problems?
In this episode it’s all about what’s coming after the problem’s analysis.
I have given you 3 examples of how to find the root cause of your problem: 5-Whys, Ishikawa and Enhanced Cause-Effect. But finding the root cause is not the end, but the beginning of the whole story. There is so much more in it.
You should listen to this episode if you have to analyse problems with a significant depth. And if you want to know what you can do after you have done the root cause analysis? What are the next steps?
This episode will support you in improving the outcome of your root cause analysis. You will get an idea how to achieve consistent, substantial, and reliable ways to proceed with your analysis.
I have composed a checklist you are free to use to improve your root cause analysis. It will provide you several questions to enlarge your perspective of the problem situation, your correction and your next steps. Feel free to download the checklist here.
Stay tuned and be inspired.
Essential Answers Provided In This Episode For:
- How to get one step ahead of regular root cause-analysis?
- What do we miss after regular root cause analysis?
- What’s this Kaizen and Yokoten about?
- Do you really improve? Or do you only pretend to improve?
- Why you should not stop directly after the root cause analysis
- What kind of questions should you raise to enhance your understanding of the situation?
- How to establish or improve your process?
- And much much more.
Selected Links and Resources From This Episode
- MES009 – Finding root causes with 5-Whys
- MES014 – Finding root-causes with Ishikawa
- MES029 – Find root causes with the Enhanced Cause-Effect approach
- The ESE Kongress – Germany’s Largest Congress for Professional Embedded Software Engineering