5-Whys is a simple root-cause analysis method that repeatedly asks “why?” to trace a problem back to specific, actionable causes.
5-Whys is a structured root cause analysis technique that investigates a problem by repeatedly asking the question **“why?”** and using the answer as the basis for the next “why.” The goal is to move past symptoms and identify specific, evidence-based, and actionable underlying causes.
Despite the name, the number of iterations is not fixed. The questioning continues until the team reaches causes that:
– Are supported by data or observable facts
– Are specific (not vague statements like “human error”)
– Can be influenced or corrected by the organization through defined actions
In industrial and regulated environments, 5-Whys is commonly used to:
– Go beyond the first, surface-level explanation of a deviation, defect, or downtime event
– Trace causal chains back to process, design, training, or organizational factors
– Document the logic of a root cause analysis in a simple, reviewable format
A 5-Whys analysis is typically performed by a small, cross-functional group that:
– Clearly defines the specific problem or event (time, place, scope)
– Uses logs, batch records, equipment data, and other objective evidence to support each answer
– Records each “why” and its answer in sequence to preserve the reasoning trail
– Stops when the identified cause is within the organization’s control and can be addressed by corrective and, where appropriate, preventive actions
In more rigorous investigations (for example, where safety, compliance, or high-cost impacts are involved), 5-Whys is often combined with other methods such as fault tree analysis, FMEA, or structured incident investigation frameworks to validate that identified causes are consistent with system-level requirements and controls.