The five whys

The five whys is a way to find the root cause of a problem by asking why it happened, then asking why again of each answer. This guide follows Taiichi Ohno's example of a machine that stopped.

Matt Savas · Reviewed October 2026 · About 6 minutes

What the five whys is

When a problem happens, you ask why. You take the answer and ask why again. You keep going until you reach a cause you can fix, so the problem does not come back. Five is a rule of thumb. Some chains need three questions and some need seven.

The method comes from Taiichi Ohno and the Toyota Production System. Ohno used the example of a machine that stopped in his book Toyota Production System: Beyond Large-Scale Production (Productivity Press, 1988).

Why it matters

The first answer to a problem is usually a symptom. If you fix only the symptom, the problem returns and you fix it again. Asking why a few more times leads to the cause underneath. A fix there stops every problem the cause was producing.

How to do it

  1. Write the problem as what happened, where and when.
  2. Ask why it happened. Write one answer that you can check.
  3. Go to where the work happens and check the answer before you write it down.
  4. Ask why of that answer. Repeat.
  5. Stop when you reach a cause you control that would stop the problem coming back.
  6. Choose a fix for that cause, give it an owner and a date, and check later that it worked.

A worked example

This is Ohno’s example. A machine on the line has stopped.

  1. ProblemThe machine stopped
  2. Why 1Overload blew the fuse
  3. Why 2Bearing not lubricated enough
  4. Why 3Lube pump not pumping enough
  5. Why 4Pump shaft worn and rattling
  6. Why 5No strainer, so scrap got in
Why 1

Why did the machine stop?

There was an overload and the fuse blew. Most teams stop here. They replace the fuse and restart the machine.

Why 2

Why was there an overload?

The bearing was not lubricated enough. The fuse was what you could see. The dry bearing caused it.

Why 3

Why was the bearing not lubricated enough?

The lubrication pump was not pumping enough. The question has moved from the machine that stopped to the pump that feeds it.

Why 4

Why was the pump not pumping enough?

The pump shaft was worn and rattling. A new shaft would wear out again for the same reason, so the team asks once more.

Why 5

Why was the shaft worn?

There was no strainer on the pump, so metal scrap got into the oil and wore the shaft. This is the root cause, and you can check it by looking at the pump.

The fix

Two fixes

A new fuse gets the machine running, but the scrap is still in the oil, and the machine will stop again. A strainer keeps the scrap out, so none of the causes above it happen again.

Common mistakes

  • Blaming a person. “The operator wasn’t paying attention” ends the investigation. Ask why the process allowed the error. If most people in the same spot would have done the same thing, the cause is in the process.
  • Naming a fix before the cause. “We need more training” and “we need a backup machine” are fixes. Hold them until you know what they would fix.
  • Going vague. “Our equipment is old” or “management doesn’t care” can’t be checked or fixed. Write what you saw.
  • Guessing in a meeting room. Every why gets an answer, true or not. Five guesses in a row give you a made-up root cause. Check each answer where the work happens.
  • Stopping too early. Replacing a worn part or a blown fuse brings the problem back later.
  • Following one chain when there are several causes. If the problem still happens on days your root cause was absent, there is more than one cause.

Related methods

The five whys follows one chain of causes. A fishbone diagram lists all the possible causes first, sorted into categories such as method, machine, material, people, measurement and environment. When a problem may have several causes, draw the fishbone first, then run a five whys on each cause you have evidence for.

A root cause still needs a fix, an owner and a follow-up date. An A3 carries all of that on one page, and the five whys sits in its analysis section.

To run your own, use the free 5 Whys tool or the free fishbone tool.

Frequently asked questions

What is the Five Whys technique?
The five whys is a way to find the root cause of a problem. You ask why the problem happened, then ask why again of each answer, until you reach a cause you can fix so the problem does not come back. It comes from Taiichi Ohno and the Toyota Production System. In Ohno's example, a blown fuse leads back to a pump with no strainer. Replacing the fuse only restarts the machine. Fitting a strainer stops the failure.
Is it always exactly five whys?
No. Five is a rule of thumb. Some problems reach a root cause in three questions and some need seven. Stop when you reach a cause you control that would stop the problem coming back. If you stop too early, you fix a symptom. If you go too far, you reach answers like "the economy" that no one can act on.
What is the difference between Five Whys and a fishbone diagram?
The five whys follows one chain of causes. A fishbone (Ishikawa) diagram lists all the possible causes first, sorted into categories such as method, machine, material, people, measurement and environment. When a problem may have several causes, draw the fishbone first, then run a five whys on each cause you have evidence for.
How do you keep a Five Whys from blaming people?
Ask why the process allowed the problem. An answer like "the operator wasn't paying attention" ends the investigation, because there is no useful next why. If most people in the same spot would have done the same thing, the cause is in the process. Write what happened instead, and ask why again.
Why do Five Whys investigations fail?
The common reasons are blaming a person, naming a fix such as "more training" before the cause is known, and giving vague answers such as "management doesn't care" that can't be checked. Another is running the whole thing in a meeting room. Each unchecked answer is a guess. Check every answer where the work happens before you write it down.
What do you do after finding the root cause?
Choose a fix for the root cause, give it an owner and a follow-up date, and check later that it worked. Show the people who own the process the chain of evidence. An A3 problem-solving sheet holds all of this on one page, with the five whys in its analysis section.