5 Whys Example: Root Cause Analysis With a Free Template

Listen to this article

When something goes wrong in a small business, the first fix is usually the obvious one. A customer complains, so you apologize and offer a discount. A job runs late, so you tell the crew to hurry next time. The problem goes away for a week, then comes back.

The 5 Whys is a simple way to break that cycle. Instead of fixing the first thing you see, you keep asking “why” until you reach the cause underneath. It takes about fifteen minutes, needs no software, and works for problems in operations, sales, customer service, and your personal life.

This guide explains where the method comes from, walks through a classic factory case and a small business 5 whys example, and gives you a template table you can copy.

What Is the 5 Whys?

The Lean Enterprise Institute defines the 5 Whys as “the practice of asking why repeatedly whenever a problem is encountered in order to get beyond the obvious symptoms to discover the root cause.”

The method comes from Toyota. Taiichi Ohno, the engineer who built much of the Toyota Production System, encouraged his teams to “ask ‘why’ five times about every matter.” The idea was that the first answer to a problem is usually a symptom. Each new “why” peels back another layer until you find something you can actually fix for good.

Despite the name, five isn’t a magic number. As the Lean Enterprise Institute puts it, “The specific number five is not the point. Rather it is to keep asking until the root cause is reached and eliminated.” Sometimes you get there in three questions. Sometimes it takes seven.

The Classic Example: Ohno’s Machine

The most famous 5 whys example comes from Ohno’s 1988 book Toyota Production System and is reprinted by the Lean Enterprise Institute. A machine has stopped working:

Why did the machine stop? There was an overload and the fuse blew.
Why was there an overload? The bearing was not sufficiently lubricated.
Why was it not lubricated? The lubrication pump was not pumping sufficiently.
Why was it not pumping sufficiently? The shaft of the pump was worn and rattling.
Why was the shaft worn out? There was no strainer attached, and metal scraps got in.

The fix is to attach a strainer. Without the five questions, a manager might simply replace the fuse or the pump. The machine would run for a while, and then the same failure would happen again.

Notice how each answer is a physical fact that someone can check. That’s what makes the example work.

A Small Business 5 Whys Example (Illustrative)

Here’s a hypothetical example for a residential cleaning company. The business and details are illustrative.

Problem statement: In the last month, four customers complained that their homes weren’t fully cleaned. Each complaint led to a free re-clean.

Why were homes not fully cleaned? The crews ran out of time and skipped rooms at the end of the visit.
Why did they run out of time? The jobs were booked for two hours, but they took closer to three.
Why were the jobs booked for two hours? The booking form estimates time from the number of bedrooms only.
Why does it only use bedrooms? The form was set up when the company mostly cleaned small apartments, and nobody has updated it.
Why hasn’t it been updated? No one is responsible for reviewing job times against booking estimates.

Root cause: The booking estimate doesn’t reflect actual job size, and no one checks it.

Countermeasures: Add square footage and number of bathrooms to the booking form. Assign the office manager to compare booked and actual times once a month and adjust the estimates.

Look at where this ended up. The first answer pointed at the crews. A quick fix might have been to tell them to work faster. The real problem was in the booking system, which the crews had no control over. That’s typical. Most recurring problems turn out to be process problems, not people problems.

5 Whys Template

Copy this table into a document or spreadsheet. Fill in the problem statement first, then work down one row at a time.

Step	Question	Answer	How do we know?
Problem	What happened, where, and when?
Why 1	Why did the problem happen?
Why 2	Why did that happen?
Why 3	Why did that happen?
Why 4	Why did that happen?
Why 5	Why did that happen?
Root cause	What is the cause we can fix?
Countermeasure	What will we change, who owns it, and by when?
Check	How will we know it worked?

The “How do we know?” column is the most important one. It forces each answer to be backed by something you’ve observed, such as a job log, a receipt, or a conversation with the person involved, rather than a guess.

How to Run a 5 Whys Session

You can do this alone, but it works better with the people closest to the problem.

Write a specific problem statement. “Customers are unhappy” is too vague. “Four customers requested re-cleans in October” is specific.
Gather the right people. Include someone who actually does the work. They often know the answer to the third or fourth why.
Go to where the problem happened. Look at the job, the form, or the receipt. Toyota calls this going to the gemba, the place where the work happens.
Ask why, and answer with facts. If you don’t know an answer, stop and find out before moving on.
Stop when you reach something you can fix. A good root cause is something within your control that, if changed, would prevent the problem.
Assign a countermeasure. Name the change, the person responsible, and a date.
Check that it worked. Look at the same measure a few weeks later. If the problem is back, run the 5 Whys again.

Common Mistakes

The 5 Whys is simple, which makes it easy to do badly. Watch for these:

Stopping at a person. “Because Sam forgot” isn’t a root cause. Ask why the process made it easy to forget. Blaming people makes them less willing to report problems.
Guessing. If an answer is a hunch, mark it and check it. One wrong guess sends every later “why” down the wrong path.
Following only one path. Many problems have more than one cause. If a “why” has two honest answers, follow both.
Going too far. “Why did the customer want a clean house?” isn’t useful. Stop when you reach a cause you can change.
Skipping the countermeasure. A root cause without an owner and a date is just a discussion.

When the 5 Whys Isn’t Enough

The 5 Whys works best for problems with a fairly clear chain of cause and effect. It’s weaker when a problem has several causes interacting, when the team doesn’t have the technical knowledge to answer the questions, or when the stakes are high.

For those situations, use a more structured method. A fishbone (Ishikawa) diagram helps you map many possible causes at once, sorted into groups like people, methods, materials, and equipment. For serious or repeated problems, the 8D problem solving method adds team formation, containment, verification, and prevention steps. The 5 Whys often sits inside an 8D as the root cause step.

The 5 Whys is also a core tool in lean principles for small business operations, where the goal is to remove waste by fixing problems at their source rather than working around them.

Using the 5 Whys Beyond Operations

The method works for personal problems too. If you keep missing workouts, ask why. Maybe you’re too tired in the evening. Why? You stay up late. Why? You check your phone in bed. The fix might be charging your phone in another room, not more willpower.

It’s one of many thinking tools that help you see a problem more clearly. For others, see this guide to mental models for better decision making, or this one on how to improve problem solving skills.

Final Thoughts

The 5 Whys is one of the cheapest tools a small business can use. It needs a clear problem statement, honest answers, and the discipline to keep asking past the first easy fix. Use it the next time a problem comes back for the second time. Fill in the template, back every answer with a fact, and assign a fix with an owner and a date.

Done well, it moves your attention from blaming people to improving the process, which is where most lasting fixes are found.

Frequently Asked Questions

What is a simple 5 whys example?

A classic example comes from Taiichi Ohno at Toyota. A machine stopped because a fuse blew. Asking why five times traced the problem to a worn pump shaft caused by metal scraps, because no strainer was attached. Attaching a strainer fixed the real cause instead of just replacing the fuse.

Do you always have to ask why exactly five times?

No. Five is a guideline. The Lean Enterprise Institute notes that the specific number isn’t the point. Keep asking until you reach a root cause you can fix. That might take three questions or seven.

Who created the 5 Whys technique?

The technique is associated with Toyota and Taiichi Ohno, who helped build the Toyota Production System. Ohno encouraged his teams to ask why five times about every problem to get past symptoms to the underlying cause.

What are the limitations of the 5 Whys?

It can follow only one path when a problem has several causes, it depends on the knowledge of the people answering, and it can turn into blame if answers stop at a person. For complex problems, combine it with a fishbone diagram or a structured method like 8D.

How do I use a 5 whys template?

Write a specific problem statement at the top, then answer each “why” in order, noting the evidence for every answer. When you reach a cause you can fix, record it as the root cause, assign a countermeasure with an owner and a date, and check later whether it worked.