TLDR
The 5 Whys is a root cause analysis technique that involves asking “why” repeatedly (typically five times) to move from a surface-level symptom to an underlying systemic cause. It was developed within the Toyota Production System and remains one of the most widely used investigation tools in manufacturing.
This guide explains how the method works, walks through three manufacturing examples, identifies when 5 Whys fails, and describes how to combine it with other root cause analysis tools for better results.
The Simplest Root Cause Analysis Tool
Root cause analysis does not always require complex tools. For many quality problems, the most effective starting point is the simplest one: keep asking “why” until you reach the systemic cause that, if corrected, prevents the problem from recurring.
The 5 Whys method was developed by Sakichi Toyoda and became a standard practice within the Toyota Production System (TPS). Taiichi Ohno, the architect of TPS, described it as the basis of Toyota’s scientific approach to problem-solving. The technique requires no statistical expertise, no special software, and no formal training beyond an understanding of the process being investigated.
How the 5 Whys Works
Start with a clear problem statement. Then ask “why” that problem occurred. Take the answer and ask “why” again. Repeat until you reach a cause that is systemic and actionable. The number five is a guideline, not a rule. Some problems require three iterations. Others require seven. The goal is to move past symptoms to reach the point where a corrective action will prevent recurrence.
Each “why” should be answered with a factual, evidence-based statement, not a guess. The chain of logic must be verifiable. If you cannot support an answer with data or observation, you need to investigate further before proceeding.
Example 1: Dimensional Nonconformance
Problem: Customer rejects a batch of machined shafts for outside diameter (OD) exceeding the upper specification limit.
Why 1: Why are the shafts oversized? Because the lathe is cutting the OD 0.08 mm larger than the programmed dimension.
Why 2: Why is the lathe cutting oversized? Because the tool offset was incorrect.
Why 3: Why was the tool offset incorrect? Because the operator set the offset using the previous job’s reference value instead of measuring the new tool.
Why 4: Why did the operator use the previous job’s reference? Because the setup procedure does not require a fresh tool measurement at each changeover.
Why 5: Why does the setup procedure not require fresh measurement? Because the procedure was written when only one tool type was used on this machine, and it was never updated after a second tool type was added.
Root cause: The setup procedure did not account for the introduction of multiple tool types and did not require a tool measurement at each changeover.
Corrective action: Revise the setup procedure to require tool measurement and offset verification at every changeover, regardless of tool type. Add a verification step to the control plan.
Example 2: Repeat Customer Complaint on Paint Adhesion
Problem: Customer reports paint peeling on a stamped metal housing for the third time in six months.
Why 1: Why is the paint peeling? Because the paint is not bonding properly to the substrate surface.
Why 2: Why is the paint not bonding? Because residual forming oil remains on the surface before painting.
Why 3: Why is forming oil remaining on the surface? Because the cleaning process is not removing all traces of the oil.
Why 4: Why is the cleaning process inadequate? Because the cleaning solution concentration has dropped below the effective range.
Why 5: Why has the concentration dropped? Because there is no scheduled monitoring or replenishment of the cleaning solution. The bath is only changed when an operator notices reduced performance.
Root cause: No preventive maintenance schedule exists for monitoring and maintaining cleaning solution concentration.
Corrective action: Establish a daily concentration check with documented acceptance limits and a replenishment schedule. Add the cleaning bath to the preventive maintenance program. Add cleaning validation to the control plan as a process parameter.
Example 3: Repeated Equipment Downtime
Problem: Hydraulic press on Line 4 has experienced three unplanned stoppages in two weeks due to overheating.
Why 1: Why is the press overheating? Because the hydraulic fluid temperature is exceeding the operating limit.
Why 2: Why is the fluid temperature too high? Because the heat exchanger is not cooling the fluid sufficiently.
Why 3: Why is the heat exchanger underperforming? Because the cooling fins are clogged with debris and dust.
Why 4: Why are the cooling fins clogged? Because the heat exchanger has not been cleaned in over six months.
Why 5: Why was it not cleaned? Because heat exchanger cleaning is not included in the preventive maintenance schedule for this press.
Root cause: The preventive maintenance program does not include heat exchanger cleaning for the hydraulic press on Line 4.
Corrective action: Add quarterly heat exchanger cleaning to the PM schedule. Review all similar presses to verify their PM schedules include this task. Implement a temperature monitoring alarm as a secondary control.
When the 5 Whys Fails
The 5 Whys is powerful for linear cause-and-effect chains, but it has real limitations. Knowing when to use a different tool is just as important as knowing how to use this one.
Complex, multi-cause problems. When a failure results from the interaction of multiple independent factors, the 5 Whys forces a single linear path that may miss contributing causes. For complex failures, a fishbone diagram or fault tree analysis captures multiple branches more effectively.
Bias in the questioning. The person asking “why” influences the direction of the investigation. Different investigators may follow different chains from the same starting point and arrive at different root causes. This is a real weakness when the method is used by a single person without cross-functional input.
Stopping too early. Without discipline, the investigation often stops at a comfortable answer rather than the true root cause. “Operator error” and “training issue” are frequent stopping points that leave the systemic cause unaddressed.
Lack of evidence. Each “why” should be supported by data or direct observation. When answers are based on assumptions rather than facts, the chain of logic breaks down and the resulting root cause may be incorrect.
Combining 5 Whys with Other Tools
The 5 Whys works best as one tool in a broader investigation, not as the only tool.
Start with a fishbone diagram to brainstorm all possible causes across the standard categories (Man, Machine, Material, Method, Measurement, Environment). Then use 5 Whys to drill down on each plausible branch to find the root cause.
Use data to validate. After the 5 Whys chain identifies a suspected root cause, verify it with data. Check inspection records, SPC charts, maintenance logs, or process parameters to confirm that the suspected cause is consistent with the observed failure.
Embed it within the 8D process. In an 8D investigation, the 5 Whys is commonly used within D4 (root cause identification) as the primary analytical method. The 8D structure provides the containment, team formation, and verification steps that the 5 Whys alone does not address.
Best Practices for Running a 5 Whys Session
Do it as a team. A cross-functional group brings diverse perspectives and catches assumptions that a single investigator would miss.
Go to the gemba. Conduct the analysis at the process, not in a conference room. Observe the actual conditions, equipment, and workflow. Physical evidence is more reliable than memory.
Write it down. Document the full chain of whys, the evidence supporting each answer, and the resulting root cause. This record supports audit readiness and provides a reference if the problem recurs.
Test the logic in reverse. Read the chain backward using “therefore” instead of “why.” If the logic holds in reverse (“The PM schedule did not include heat exchanger cleaning, therefore the fins were clogged, therefore the fluid overheated…”), the chain is sound. If it breaks, revisit the weak link.
Frequently Asked Questions
No. Five is a guideline, not a rule. The goal is to reach a systemic, actionable root cause. Some problems require three iterations. Others require more than five. Stop when you reach a cause that, if corrected, would prevent recurrence.
The technique is attributed to Sakichi Toyoda, the founder of Toyota Industries. It was further developed and popularized by Taiichi Ohno as a core practice within the Toyota Production System.
Use a different tool when the problem has multiple independent causes, when the failure mechanism is complex, or when the 5 Whys keeps leading to vague answers. Fishbone diagrams, fault tree analysis, and the “is/is not” method handle complex and multi-cause problems more effectively.
Yes, if the answers are based on assumptions rather than evidence, or if investigator bias steers the chain in one direction. Always verify each answer with data or direct observation. Running the session with a cross-functional team reduces the risk of bias.
Almost never. “Operator error” describes what happened, not why it happened. Keep asking why. Why did the operator make the error? Was the work instruction unclear? Was the process design error-prone? Was training inadequate? The systemic condition that allowed the error is the root cause.
Document the problem statement, each “why” question and its evidence-based answer, the final root cause statement, and the corrective action. Include the names of the team members involved and the date. This record should be attached to the corrective action report or 8D.
Yes. The 5 Whys method applies to any problem-solving situation: IT incidents, service failures, project delays, healthcare events, and more. The principle of asking “why” iteratively to find systemic causes is universal.
Stay Current on Automotive Quality
PPAP updates, GD&T guidance, and practical quality resources delivered to your inbox. No spam, just what quality professionals need to know.
Subscribe
Leave a Comment