DEFINITION
A 5-Why analysis is a structured root cause method that asks "why" repeatedly, typically five times, to drive past surface symptoms until an actual cause is identified. The method was developed inside Toyota and is now standard in lean manufacturing problem solving. It is a low-cost, high-discipline tool that any operator or supervisor can run with no software and no training overhead beyond an hour of practice.
The output of a 5-Why is a chain of cause-and-effect statements that ends at a finding the team can actually fix. If the final answer to "why" is something the team cannot change, the 5-Why has been run incorrectly or has hit a system constraint that requires a different conversation.
WHY 5-WHY ANALYSIS MATTERS
Manufacturing problems usually present as symptoms. A part fails inspection. A machine goes down. A shipment misses promise. The instinct is to fix the symptom and move on. The 5-Why prevents that. It forces the team to keep asking why until the underlying mechanism is exposed, which is the only level at which a durable fix can happen.
Plants that solve problems at the symptom level fight the same fires repeatedly. Plants that solve at root cause see the problem return half as often. The cumulative effect across a year, on a plant running thirty significant problems a month, is meaningful: hundreds of hours of supervisor time recovered, less scrap, fewer customer escalations, lower overtime.
HOW A 5-WHY IS RUN
Start with the problem statement. Make it specific and measurable. Not "quality is bad" but "Press 5 produced 65 scrap parts on Tuesday." Then ask why. Each answer becomes the next problem statement. Continue until the root cause surfaces, typically on the fourth or fifth iteration.
A worked example. The symptom: Press 5 produced 65 scrap parts on Tuesday. Why? Because the die was not seated correctly. Why? Because the operator skipped the seating verification step. Why? Because the standard work card was missing from the station. Why? Because the laminated card was damaged last week and never replaced. Why? Because there is no process to replace damaged standard work cards. The fix is to install a process for refreshing damaged work instructions, not to discipline the operator.
The 5-Why does not have to stop at exactly five questions. Stop when the answer points to a system or process change you can actually implement. If it points to "operator made a mistake," keep asking why; you have not reached root cause yet.
COMMON MISTAKES
The biggest mistake is stopping at human error. "The operator did not follow the procedure" is rarely the root cause. Procedures that are unclear, missing, or contradicted by management pressure are usually the actual issue, and a thorough 5-Why surfaces that.
The second mistake is making the chain of cause-and-effect implausible. Each "why" answer should be the actual cause of the prior one, not a related observation. If you cannot trace a clean cause-and-effect line back up the chain, the analysis has drifted.
The third is running the 5-Why alone. The most useful 5-Whys happen with the operator who saw the problem, the supervisor who owns the area, and an engineer or quality lead. Ten minutes, a whiteboard, and the right people in the room.
WHEN TO USE IT
A 5-Why is the right tool for problems with a clear single trigger. For complex problems with multiple interacting causes, a fishbone diagram or a more structured A3 analysis is usually better. The 5-Why pairs well with a Pareto chart: use the Pareto to identify the top three problems worth solving, then run a 5-Why on each.
The Sharpen implementation guide library covers structured problem solving in detail, including A3, fishbone, and PDCA methods for the cases where 5-Why is not enough.