|
Please register now to read all responses and to join this discussion yourself. It's easy and 100% free.
|
|
8D Problem Solving : D2 Phase (Describing the Problem)
sirelkhatim ibrahim nugud, Coach, Sudan, Member
When we are searching for the problem root cause, as far as I know from previous knowledge, we should avoid asking: who?
Because the intention is not to blame people, but to fix the system. (...) Read more? Sign up for free
|
|
|
|
Please register now to read all responses and to join this discussion yourself. It's easy and 100% free.
Sign up for free Log in
|
| |
|
8D and 5Why
Antonio J. Garcia, Spain, Member If root cause is not very obvious, use the 5 whys is a good method.
|
|
| |
|
8D Training
Leo Duron For training in 8D it's always better to work on real problems from the factory floor, rather than hypothetical problems with a known resolution.
|
|
| |
|
8D Problem Solving
Robert Napoletano, Manager, United States, Member I use the "5 Whys" at every step. Even if you think you have reached a good conclusion you should continue to ask why. At the end you need to know why this is the right conclusion. I even ask why for the team members to make sure I have the best possible group to solve the problem.
|
|
| |
|
8D's & 5Why's
John Muka, Consultant, Australia, Member The use of 5 Why's or 8D will ultimately give you the list of key root causes to eliminate or minimise the impact of the problem.
However if you really want to quantify the level improvement effort and measure the impact you are creating than you may want to separate if the causes are "common" or "special" causes. Then develop a data gathering plan to understand the impact before and after so you can quantify the impact you create in solving the problem.
Some statistical tools to look at would be, Pareto charting, Hypothesis testing, Regression analysis, Process capability etc...
|
|
|
