Читать книгу Root Cause Failure Analysis - Trinath Sahoo - Страница 59

1 Develops the problem statement. Be clear and specific.

2 Assemble a team of people knowledgeable about the processes and systems involved in the problem being discussed. They should have personal knowledge about the non‐conformance of the system.

3 On a flip chart, presentation board, or even paper; write out a description of what you know about the problem. Try to document the Problem and describe it as completely as possible. Refine the definition with the team. Come to an agreement on the definition of the Problem at hand.

4 The team facilitator asks why the problem happened and records the team response. To determine if the response is the root cause of the problem, the facilitator asks the team to consider “If the most recent response were corrected, is it likely the problem would recur?” If the answer is yes, it is likely this is a contributing factor, not a root cause.If the answer provided is a contributing factor to the problem, the team keeps asking “Why?” until there is agreement from the team that the root cause has been identified.It often takes three to Five Whys, but it can take more than five! So keep going until the team agrees the root cause has been identified.

The 5 Whys can help you uncover root causes quickly. However, making a single mistake in any question or answer can produce false or misleading results. You may find that there is more than one root cause for each non‐conformance; corrective actions should be implemented for each of these.