Five-Why Root Cause Analysis
Ask why five times to find the real cause, not the symptom
Five-Why Root Cause Analysis is Toyota's deceptively simple method for moving past surface-level symptoms to find the true cause of any problem. You start with the observable problem and ask why it occurred. Then you take that answer and ask why again. You repeat this process five times (or as many as needed) until you reach a systemic root cause that, when addressed, prevents the problem from recurring.
The method works because most organizations stop at the first or second why, implementing countermeasures that address symptoms rather than causes. A factory floor has oil on it. Most companies would clean it up (first why) or fix the leaking machine (second why). Toyota keeps going until it discovers that the purchasing department's reward structure incentivizes buying cheap gaskets, which is the systemic issue that produces dozens of similar problems.
The five-why is embedded within Toyota's broader seven-step Practical Problem Solving process, which adds crucial steps before and after the analysis: grasping the situation thoroughly, setting improvement targets, identifying the point of cause, then implementing countermeasures, evaluating results, and standardizing the new process.
- The root cause lies hidden beyond the source where the problem is observed
- Each why takes you further upstream in the process and deeper into the organization
- Countermeasures change completely depending on how deeply you dig
- Surface fixes are temporary; only root cause fixes prevent recurrence
- Grasping the situation thoroughly must precede any analysis
- Grasp the Situation at the SourceGo to where the problem is occurring (genchi genbutsu). Observe the actual conditions with an open mind. Compare what you see to the standard. If there are multiple problems, use Pareto analysis to prioritize the most impactful one.Pro tipToyota trainers say the hardest part to learn is grasping the situation thoroughly before jumping into analysis. Resist the urge to solve before you fully understand.WarningNever start a five-why analysis from a conference room. You must observe the actual problem at the actual location.
- Clarify the Problem and Set a TargetDefine the gap between the current state and the expected standard. Be specific and measurable. Set a clear improvement target so you know when the problem is solved.Pro tipA vague problem statement leads to vague root causes. Instead of 'quality is bad,' specify 'part X has a 3% defect rate versus the 0.1% standard.'
- Ask Why Five TimesStarting from the observed problem, ask why it occurred. Take that answer and ask why again. Continue for five iterations or until you reach a systemic organizational cause. Each why should move you further upstream and deeper into the system.Pro tipIf your five-why chain stays at the same organizational level, you are not digging deep enough. True root causes usually involve management systems, incentive structures, or cultural norms.WarningDo not skip levels or make logical leaps. Each why must be directly and causally linked to the previous answer.
- Implement Countermeasures at the Root LevelDevelop and implement a countermeasure that addresses the deepest feasible root cause. Toyota uses the term countermeasure rather than solution because no fix is considered permanent; it is the best known approach until a better one is found.Pro tipImplement countermeasures at the deepest level that is practically feasible. Sometimes you also need temporary countermeasures at surface levels while the root cause fix takes effect.
- Evaluate Results and StandardizeVerify that the countermeasure actually resolved the problem by measuring against your target. If effective, standardize the new process so the improvement is preserved and available for further refinement.Pro tipThe seventh step of Toyota's practical problem solving, standardization, is critical. Without it, learning falls into a black hole, forgotten and unavailable for further improvement.WarningIf you skip standardization, you will solve the same problem repeatedly as different teams encounter it independently.
Toyota's classic training example: oil is found on the shop floor. Why? Machine is leaking. Why? Gasket deteriorated. Why? Bought gaskets made of inferior material. Why? Got a good price on them. Why? Purchasing agents are rewarded for short-term cost savings. The countermeasure at each level is completely different, from mopping the floor to restructuring the purchasing incentive system.
After installing a new email system, employees complained they could not understand its functions. Training was provided but complaints continued. Five-why analysis revealed the manager had not practiced genchi genbutsu, had not piloted the system with real users, and had skipped nemawashi (consensus building). The deeper root cause was that senior management had failed to build a culture supporting Toyota Way principles in technical processes.
Taiichi Ohno, the creator of the Toyota Production System, developed the five-why method as a core discipline. He emphasized finding root causes rather than sources, noting that the source is where a problem is observed but the root cause is hidden beyond it. When asked about Toyota's secret to product development success, a Toyota VP responded with deliberate sarcasm that their sophisticated technique was simply asking why five times.
Toyota does not use Six Sigma's complex statistical tools for most problems. Liker found that problem solving at Toyota is 80% thinking and 20% tools, the inverse of what he observed at many Six Sigma organizations.