Explain the 5 Whys technique used in root cause analysis.

Explain the 5 Whys technique used in root cause analysis.

• A. A questioning technique that repeatedly asks "Why?" to drill down from the surface symptom to the underlying root cause, typically five iterations or until fundamental cause is found.
• B. A method to map fault trees.
• C. A risk assessment tool for hazard identification.
• D. A method to calculate incident costs.

Answer: (A)

The main idea here is using a simple, iterative questioning process to uncover the underlying cause of a problem rather than stopping at the first symptom. The method involves asking "Why?" about the observed issue, then taking the answer and asking "Why?" again, continuing this cycle typically five times or until you reach a cause that is actionable and fundamental to the system or process. The strength of this approach is its focus on root causes—often latent conditions like gaps in procedures, training, maintenance, or management oversight—so the resulting actions address the real problem rather than just treating the surface symptoms. This technique is straightforward, inexpensive to implement, and often done with the team to bring diverse perspectives to light. It helps teams move from blaming individuals to understanding how processes or systems allowed the problem to occur, which supports sustainable corrective actions. It isn’t about mapping fault trees, which are diagrammatic representations of how failures combine to cause a top event. It isn’t a risk assessment tool for identifying hazards and evaluating risks, nor is it a method for calculating incident costs. Those are different techniques used for hazard identification, risk prioritization, and financial impact analysis.

The main idea here is using a simple, iterative questioning process to uncover the underlying cause of a problem rather than stopping at the first symptom. The method involves asking "Why?" about the observed issue, then taking the answer and asking "Why?" again, continuing this cycle typically five times or until you reach a cause that is actionable and fundamental to the system or process. The strength of this approach is its focus on root causes—often latent conditions like gaps in procedures, training, maintenance, or management oversight—so the resulting actions address the real problem rather than just treating the surface symptoms.

This technique is straightforward, inexpensive to implement, and often done with the team to bring diverse perspectives to light. It helps teams move from blaming individuals to understanding how processes or systems allowed the problem to occur, which supports sustainable corrective actions.

It isn’t about mapping fault trees, which are diagrammatic representations of how failures combine to cause a top event. It isn’t a risk assessment tool for identifying hazards and evaluating risks, nor is it a method for calculating incident costs. Those are different techniques used for hazard identification, risk prioritization, and financial impact analysis.