The 5 Whys: Getting Past Symptoms to Root Cause

Key takeaways

• The 5 Whys is the simplest root cause technique: ask "why" repeatedly, each answer becoming the next question, until you reach a cause you can actually change in the process.
• "Five" is a guideline, not a rule. Stop when you hit a root cause you can act on, whether that takes three whys or seven.
• The discipline is to follow evidence, not opinion, and to keep going past the first comfortable answer, which is usually a symptom or a person to blame.
• It works best on focused, single-chain problems. When a problem has many possible causes at once, a fishbone diagram is the better starting tool.

What the 5 Whys is

The 5 Whys is a questioning technique for getting from a symptom to its underlying cause. You state the problem, ask why it happened, then ask why of that answer, and so on. Each step peels back a layer. The aim is to stop treating the visible symptom and reach the real driver, the thing that, if fixed, stops the problem from recurring.

Its appeal is that it needs no software and no training beyond discipline. Its weakness is that the same simplicity makes it easy to do badly.

A worked example

Problem: the line stopped.

• Why? A fuse blew.
• Why? The motor was overloaded.
• Why? The bearing seized.
• Why? It ran dry of lubricant.
• Why? The lubrication task was not on the maintenance schedule.

Replacing the fuse (the symptom) fixes nothing; the line will stop again. Adding the lubrication task to the preventive maintenance schedule (the root cause) actually solves it. Notice the chain ended at something changeable in the system, not at "the operator should have noticed."

The traps

• Stopping too early. The first plausible answer is usually still a symptom. Push past it.
• Ending on blame. If your last why is "someone did not do their job," you have not reached the root. Ask why the system allowed that.
• Opinion over evidence. Each answer should be verifiable, not a guess. An unverified chain leads confidently to the wrong fix.
• Forcing one chain. Some problems have several contributing causes. A single linear why-chain can miss them.

5 Whys versus fishbone

The two are complementary. The 5 Whys follows one chain deep; the fishbone diagram spreads wide across many possible cause categories. Use the fishbone when the cause could be anywhere and you need to explore the whole space; use the 5 Whys to drill down once you have a likely branch. Both sit inside the broader discipline of root cause analysis.

Common mistakes

• Treating "five" as mandatory. Stop at the actionable root, whether that is the third why or the seventh.
• Doing it from memory. Run it with the people who saw the event and the data, not from a conference room a week later.
• No action. A root cause identified but not turned into a tracked fix changes nothing.

How Fabrico fits

The 5 Whys is only as good as the facts feeding it, and the first why ("why did the line stop?") is exactly what Fabrico captures automatically, with the true cause attached rather than a guessed code. Because every event is logged with its context and history, the chain starts from evidence instead of memory, and the resulting fix can become a work order or a PM change in the same system. See automatic downtime tracking. Fabrico is built and hosted in the EU with data residency in mind and is ISO 27001 certified. To start your 5 Whys from facts, book a demo.

Related reading

• Root cause analysis
• Fishbone diagram
• Automatic downtime tracking
• Preventive maintenance schedule

Teams putting this into practice often review our roundup of the root cause analysis software.

Frequently asked questions

Does it have to be exactly five whys?

No. Five is a guideline for roughly how deep you usually need to go. Stop when you reach a cause you can actually change in the process or the asset, whether that takes three iterations or seven.

How do I know I have reached the root cause?

When the answer is something changeable in the system and fixing it would prevent recurrence. If your last answer blames a person or is still a symptom, keep asking why the system allowed it.

When should I use a fishbone instead of the 5 Whys?

Use a fishbone when a problem could have many causes across different categories and you need to explore the whole space. Use the 5 Whys to drill deep down one likely chain. They work well together.

Why do 5 Whys analyses go wrong?

Usually by stopping too early, ending on blame rather than a system cause, or building the chain on opinion instead of verified evidence. Each leads confidently to a fix that does not address the real driver, so the problem returns.