STRATEGYDays to result

The Five Whys

Ask why five times to penetrate from symptoms to root causes, turning every problem into a permanent improvement

Problem it solves

unclear strategic direction

Best for

Any recurring problem where surface-level fixes have failed, or any situation where the true cause is hidden behind more obvious symptoms

Not ideal for

Emergencies requiring immediate action before analysis, or situations where the cause is already obvious and well-understood

Overview

Why this framework exists

The Five Whys is Toyota's scientific approach to problem-solving. When confronted with a problem, you ask why five times, answering each question before proceeding to the next. This systematic drilling reveals the root cause, which is often hidden behind more obvious symptoms. Without this depth of inquiry, you might replace a blown fuse or a pump shaft, only to see the problem recur within months. The Toyota Production System itself was built on the practice and evolution of this scientific approach. Ohno used it not just for machine failures but for fundamental questions about production philosophy: Why can one person operate only one machine? Why are we making too many parts? Each answer opened the door to a transformative improvement.

Core principles

6 total
  1. Underneath the cause of a problem, the real cause is hidden; you must dig it up by asking why repeatedly
  2. Five Why's equal One How: 5W = 1H; the solution becomes clear only when the true nature of the problem is understood
  3. Data are highly regarded, but facts are even more important; if the search for cause is not thorough, actions taken will be out of focus
  4. The practice is simple to understand but difficult to execute consistently
  5. Each why must be answered with a fact, not a guess, before proceeding to the next level
  6. The technique applies to strategic questions about systems and methods, not just machine breakdowns

Steps

4 steps
  1. Identify the Problem Clearly
    Start at the production floor or the point where the problem manifests. Observe the facts directly rather than relying on reports or data alone. State the problem in concrete, observable terms.
    Pro tipGo to the actual place where the problem occurred. Ohno's plant-first principle emphasized that the production plant provides the most direct, current, and stimulating information about management.
  2. Ask the First Why
    Ask why the problem occurred and answer with a verifiable fact. For example: Why did the machine stop? Because there was an overload and the fuse blew. This first answer identifies the immediate cause but not the root cause.
    WarningDo not stop here. Replacing the fuse addresses the symptom, not the cause. The problem will recur within months.
  3. Continue Asking Why Through Five Levels
    For each answer, ask why again. Why was there an overload? The bearing was not sufficiently lubricated. Why was it not lubricated? The pump was not pumping sufficiently. Why? The shaft was worn. Why was the shaft worn? No strainer was attached and metal scrap got in. Each level peels back another layer of causation.
    Pro tipThe number five is a guideline, not a rigid rule. Some problems require fewer levels, others more. The point is to keep asking until you reach a cause that, if addressed, will prevent recurrence permanently.
  4. Implement a Countermeasure at the Root Cause
    Address the deepest cause identified. In the machine example, install a strainer on the lubrication pump. This prevents the chain of failures from ever starting again. The countermeasure should be a permanent change, not a temporary fix.
    Pro tipAlways take countermeasures to prevent recurrence, not just to fix the immediate situation. This is why Ohno made autonomation a pillar of the system: it forces problems to the surface so root causes can be found.

Checklist

Saved in your browser

Examples

2 cases
The Machine Failure Chain

A machine stopped functioning. Asking why five times revealed a chain from blown fuse to overload to insufficient lubrication to worn pump shaft to missing strainer. Each level of why moved from symptom to deeper cause.

OutcomeInstalling a strainer on the lubrication pump eliminated the root cause. Without the Five Whys, someone would have replaced the fuse and the problem would have recurred within months.
Birth of the Kanban Concept

Ohno asked why Toyota was making too many parts. The first answer was that there was no way to hold down or prevent overproduction. This led to the idea of visual control, which led to the idea of kanban. Each question opened a new innovation.

OutcomeThe kanban system was born from asking why, demonstrating that the Five Whys can generate entirely new production systems, not just fix individual problems.

Common mistakes

3 traps
Stopping at the first or second why
If the procedure is not carried through, you will simply replace the fuse or the pump shaft. The problem will recur within a few months because the root cause was never addressed.
Answering with guesses instead of facts
Each why must be answered with an observed, verifiable fact. If the search for cause is not thorough, the actions taken can be out of focus. This is why Ohno valued facts over data.
Applying it only to machine breakdowns
The Five Whys generated the entire Toyota Production System. Ohno used it to question why workers operated one machine each, why parts arrived too early, and why overproduction could not be prevented. Apply it to systemic and strategic questions, not just tactical problems.

Origin story

How this framework came to be

Ohno made the Five Whys the scientific basis of the entire Toyota Production System. He demonstrated it with a simple example: a machine stopped functioning. Why? Overload blew the fuse. Why the overload? Insufficient lubrication. Why insufficient lubrication? The pump was not pumping sufficiently. Why? The pump shaft was worn and rattling. Why was the shaft worn? No strainer was attached and metal scrap got in. Without asking all five whys, someone might simply replace the fuse or pump shaft, and the problem would recur. But the fifth why reveals that installing a strainer is the real countermeasure. This same approach generated the key innovations of the Toyota system: autonomation came from asking why workers could only operate one machine, production leveling from asking why parts arrived too quickly, and kanban from asking why overproduction could not be prevented.

Source

Traced to primary
Source · BOOK
Toyota Production System: Beyond Large-Scale Production
Taiichi Ohno · 1988
Open source →

Related frameworks

Browse all Strategy →