What are the Five Whys? Root Cause Analysis Technique with Examples
The Five Whys is one of the most powerful and accessible root cause analysis techniques in quality management. Used in lean, Six Sigma, and everyday problem-solving, it helps teams move beyond symptoms to find the true underlying cause of a problem. This guide explains how Five Whys works, when to use it, its limitations, and provides step-by-step examples from manufacturing and service environments.
Five whys Definition
The Five Whys is a root cause analysis technique that involves repeatedly asking 'Why?' in response to each answer, typically five times, to trace a problem back to its fundamental underlying cause.
- Simple, accessible technique requiring no statistical tools
- Asks 'Why?' repeatedly to trace symptoms to root causes
- Typically five iterations, but can be more or fewer
- Works best for problems with a single root cause
- Commonly used in kaizen, DMAIC Analyse phase, and 8D
Explanation of Five whys
The Five Whys technique was developed by Sakichi Toyoda, the founder of Toyota Industries, and became a central element of the Toyota Production System. The premise is elegantly simple: most visible problems are merely symptoms of deeper underlying causes. By repeatedly asking 'Why?', a team can peel away layers of symptom until the fundamental root cause is reached — the cause that, if permanently eliminated, will prevent the problem from recurring.
The technique works because human beings naturally explain problems at the level of immediate cause rather than root cause. A machine stopped? The fuse blew. Why did the fuse blow? The motor overloaded. Why did the motor overload? The pump was blocked. Why was the pump blocked? Inadequate filter maintenance. Why was maintenance inadequate? No scheduled maintenance procedure existed. The fifth why reveals the systemic gap — the absence of a maintenance procedure — whose elimination will prevent the entire chain of events from recurring.
Five Whys is most effective for problems with a relatively linear causal chain — one cause leads to one effect. For complex problems with multiple interacting causes, the fishbone (Ishikawa) diagram is more appropriate, as it allows multiple causal branches to be explored simultaneously. In practice, the best approach is often to use a fishbone diagram to identify candidate root causes and then apply Five Whys to each candidate to confirm the true root cause.
A critical discipline of Five Whys is answering with evidence, not assumption. Each 'Why?' should be answered with an observed fact or measured data point, not a hypothesis. When teams follow this discipline, Five Whys produces root causes that are verified and actionable. When they skip it, they often arrive at plausible-sounding but incorrect root causes that lead to ineffective countermeasures.
How to Apply the Five Whys
-
1State the problem clearly
Write a precise problem statement that describes what happened, where, when, and to what extent — supported by data, not opinion.
-
2Ask the first Why
Ask 'Why did this problem occur?' and write down the most proximate, observable cause supported by evidence.
-
3Ask subsequent Whys
For each answer, ask 'Why did that happen?' Continue tracing the causal chain, keeping each answer grounded in verifiable facts.
-
4Stop at the root cause
Stop when you reach a cause that can be acted upon with a countermeasure, the elimination of which will prevent the problem from recurring.
-
5Verify the root cause
Confirm the root cause by working the logic forward: if this cause is present, does it necessarily lead to the problem? If you fix it, will the problem be prevented?
-
6Implement and validate
Develop a countermeasure that addresses the verified root cause, implement it, and verify through follow-up measurement that the problem does not recur.
Five Whys Example: Equipment Failure at a Paper Mill
A paper mill experienced an unplanned shutdown when a key conveyor belt motor failed. Rather than simply replacing the motor and resuming production, the maintenance supervisor applied the Five Whys: Why did the motor fail? It overheated. Why did it overheat? The cooling fan was not running. Why was the cooling fan not running? The fan belt had broken. Why had the fan belt broken? It was worn beyond its service life. Why was it worn beyond its service life? There was no preventive maintenance schedule for fan belt inspection and replacement.
The root cause — the absence of a preventive maintenance procedure — was fundamentally different from the apparent cause (motor failure) and the immediate fix (motor replacement). The countermeasure was to establish a quarterly fan belt inspection procedure for all motors on the conveyor system. Within three months, two additional fan belts in early-stage wear were identified and replaced proactively, preventing two more potential unplanned shutdowns. The Five Whys analysis cost 20 minutes; the countermeasure cost $80 in belts and two hours of labour, preventing an estimated $40,000 in downtime costs annually.
Importance of Five whys in Quality Management
The most expensive thing an organisation can do with a quality problem is fix the symptom and leave the root cause in place. The problem will recur — often in a more damaging form — consuming additional resources, frustrating customers, and eroding confidence in quality. The Five Whys prevents this cycle by ensuring that at least one analysis passes through the symptom layer to the underlying systemic failure that requires permanent correction.
Five Whys also builds a quality culture by teaching everyone in an organisation to think causally rather than reactively. When a team leader habitually responds to problems with 'Why did that happen?' rather than 'Just fix it', they model the analytical mindset that compounds into a continuously improving organisation over time. This cultural habit — asking why, not just who — is one of the most important and most difficult aspects of building a genuine quality culture.
- Simple and accessible — no statistical tools required
- Traces symptoms to actionable root causes
- Prevents recurrence by addressing underlying systemic causes
- Applicable to any type of problem in any industry
- Builds analytical thinking culture organisation-wide
- Fast to apply — can be done in under 30 minutes for simple problems
Manufacturing defect investigation, equipment failure analysis, healthcare adverse event review, customer complaint root cause analysis, software incident post-mortems, service delivery failures, and any problem-solving situation requiring root cause identification.
Five whys in ASQ Certifications
Professionals working in quality, process improvement, operations, and organisational excellence often encounter this concept in real-world applications. Many ASQ certifications cover related principles,
tools, and methods as part of the Body of Knowledge.
Frequently Asked Questions
The concept of Five whys is rigorously covered in the following ASQ certifications: Six Sigma Green Belt, Certified Six Sigma Black Belt.
The number five is a guideline, not a rule. Sakichi Toyoda and Toyota found that five iterations was typically sufficient to reach the root cause of most manufacturing problems. Some problems require only three iterations; complex systemic issues may require seven or more. The number matters less than reaching a cause that is actionable and systemic.
The most common mistake is answering Whys with assumptions or opinions rather than evidence. Each answer should be grounded in observed facts or measured data. Without this discipline, teams often convince themselves of a root cause that sounds plausible but is not actually the cause, leading to countermeasures that do not prevent recurrence.
Use Five Whys for problems with a relatively linear, single causal chain. Use a fishbone diagram when multiple potential causes need to be explored simultaneously across different categories (People, Machine, Method, Material, Measurement, Environment). In practice, the two techniques complement each other well.
Yes — this is sometimes called 'positive Five Whys' or 'appreciative Five Whys'. Asking why a process performed exceptionally well can reveal the contributing success factors, enabling them to be standardised and replicated in other areas of the organisation.