Business Growth
How to Do a 5 Whys Analysis (Template, Example, and Steps)
How to do a 5 Whys analysis for a small business: what the 5 Whys root cause technique is, when to use it, the step-by-step method, how to tell a symptom from a root cause, a template, a worked example, common mistakes, and a Claude workflow for running your own.

Founder, AI Tools and Training Club · November 17, 2026 · 8 min read

The short version
- The 5 Whys is a root cause technique: you state a problem, ask why it happened, then ask why again about each answer until you reach a cause you can actually fix.
- To do one, write a specific problem statement, ask why with evidence for every answer, stop when the answer points at a process or decision you control, then fix that and check the problem stops coming back.
- Five is a guideline, not a rule. Some problems reach the root in three whys, some need more, and a complex problem may have several branches that each need their own chain.
How do you do a 5 Whys analysis?
To do a 5 Whys analysis, write down the problem as one specific, factual sentence. Ask why it happened and write the answer, backed by evidence. Then ask why that answer happened, and keep going, each time questioning the last answer, until you reach a cause that is a process, a rule, or a decision you can change. That is the root cause. Fix it, give the fix an owner and a date, and check later that the original problem has stopped.
My strong opinion: the 5 Whys is the most useful framework in this series for the daily running of a small business, precisely because it is so small. SWOT, VRIO, and 7S are for planning days. The 5 Whys is for Tuesday afternoon, when a client complains, an invoice goes out wrong, or a launch misses its date. Ten minutes and a blank page is all it takes, and it stops you from fixing the same problem every month.
What is the 5 Whys technique?
The 5 Whys is an iterative questioning technique for finding the cause behind a problem. Each answer becomes the subject of the next why, so you move step by step from the visible symptom to the underlying cause. The modern technique traces back to Sakichi Toyoda, the founder of the Toyota Group, and it became part of the Toyota Production System, where Taiichi Ohno, the system's architect, made asking why five times a basic habit of problem solving. It is now used widely in lean, kaizen, and Six Sigma work.
The idea that matters for a small business is simple: the first answer to "why did this go wrong?" is almost always a symptom. "The client was unhappy because the report was late" is true, but there is nothing to fix in it. The fix lives several whys further down, usually in how the work is planned, handed off, or checked.
| Symptom | Root cause | |
|---|---|---|
| What it describes | What went wrong, the thing you can see | Why it was able to go wrong |
| Typical wording | "The order shipped late" | "Nobody owns checking stock before a quote is sent" |
| What fixing it does | Solves this instance | Stops the problem coming back |
| Who it points at | Often a person | Almost always a process, rule, or decision |
Symptom compared with root cause
When to use the 5 Whys
- A problem keeps coming back. If you have fixed the same thing twice, you fixed a symptom.
- Something went wrong with a customer. A complaint, a refund, a lost account. Run it before you reply, so the reply includes the real fix.
- A project or launch missed its date. Ask why the date slipped, not who slipped it.
- A number moved and you do not know why. Falling conversion, rising returns, slower payments. The 5 Whys gives the investigation a structure.
- Not for big, tangled problems with many causes. For those, map the possible causes first with a fishbone diagram, then run a 5 Whys on each of the strongest branches.
How to do a 5 Whys analysis step by step
- Gather the right people. Include whoever was closest to the work. A 5 Whys done by the owner alone tends to stop at the owner's assumptions.
- Write a specific problem statement. What happened, when, and how big. "Three client invoices in October went out with the wrong rate" beats "billing is a mess."
- Ask the first why. Write the answer as a fact you can check, not a guess. If nobody knows, go and look before you continue.
- Ask why about that answer. Repeat, each time questioning the previous answer, not the original problem.
- Test each step backwards. Read the chain in reverse using "therefore." If an answer does not clearly lead to the one above it, the chain has a gap.
- Stop at a cause you control. The root cause is usually a missing or broken process, rule, or decision. If the next why leads somewhere you cannot act on, such as the weather or a customer's budget, stop one step earlier.
- Choose a fix, an owner, and a check date. One concrete change, one person, one date to confirm the problem has stopped recurring.
5 Whys template
Copy this into a doc or spreadsheet. Keep every 5 Whys you run in one place, because patterns across several of them are often more useful than any single one.
| Field | What to write |
|---|---|
| Problem statement | What happened, when, and how big, in one sentence |
| Why 1 | The direct cause, with the evidence for it |
| Why 2 to Why 5 | The cause of the previous answer, each with evidence |
| Root cause | The process, rule, or decision you will change |
| Fix | One concrete change |
| Owner and date | One person and a date to put the fix in place |
| Check date | When you will confirm the problem has stopped recurring |
5 Whys template
5 Whys example for a small business
Here is an illustrative example for a made-up design studio. Problem statement: a client cancelled their retainer in November after their second website update in a row launched late.
| Why | Question | Answer |
|---|---|---|
| 1 | Why did the client cancel? | Two updates in a row launched late, and they missed a sale they had promoted |
| 2 | Why did the updates launch late? | Both sat waiting for the client's content for over a week |
| 3 | Why did the content arrive late? | The client did not know it was needed until the designer asked for it mid-project |
| 4 | Why did they not know? | The kickoff email lists the design steps but not what the client must supply or by when |
| 5 | Why does the kickoff email leave that out? | There is no standard kickoff checklist. Each designer writes their own email from memory |
Illustrative 5 Whys for a small design studio
The root cause is not a slow client or a slow designer. It is a missing kickoff checklist. The fix is one shared template that lists every item the client must supply, with due dates worked back from the launch date, and a reminder three days before each one. Notice that if the studio had stopped at why 2, the conclusion would have been "chase clients harder," which costs time on every project and does not prevent the next late launch.
5 Whys mistakes to avoid
- Stopping at a symptom. If the fix is "be more careful" or "try harder," keep asking.
- Blaming a person. People make mistakes inside systems that allow them. Find the part of the system that allowed it.
- Guessing instead of checking. Each answer should be something you can verify. A chain built on assumptions points at the wrong fix.
- Forcing exactly five. Stop when you reach a cause you can fix, whether that takes three whys or seven.
- Following only one branch. Many problems have more than one cause. If a why has two true answers, run a short chain for each.
- Skipping the follow-up. A 5 Whys without a check date is just a conversation. Confirm the problem actually stopped.
How the 5 Whys fits with other strategy frameworks
- To measure how far you are from where you want to be: use How to Do a Gap Analysis (Template, Example, and Steps), then run a 5 Whys on the biggest gap to see what is causing it.
- To understand why deals were won or lost: pair it with How to Do a Win-Loss Analysis (Questions, Template, and Steps).
- When the root cause turns out to be how the business is organized: step up to How to Use the McKinsey 7S Framework (Template, Example, and Steps).
- To make sure the fix actually happens: turn it into a key result with How to Set OKRs for a Small Business (Template, Examples, and Steps).
How to do a 5 Whys analysis with Claude
Claude is useful as the person in the room who keeps asking why when everyone else wants to move on. It cannot check your facts, so the evidence still has to come from you. Open the Claude desktop app and work through it in passes.
- Describe the problem in a few sentences and ask Claude to rewrite it as one specific, factual problem statement, then to ask you what it would need to know to make it more precise.
- Ask it to run the 5 Whys with you one question at a time, waiting for your answer before asking the next why, and to challenge any answer that names a person or sounds like a guess.
- Once you reach a root cause, ask it to read the chain backwards with "therefore" and point out any step that does not follow.
- Paste in related material, such as the customer email, the project timeline, or the order log, and ask whether anything in it contradicts the chain or suggests a second branch.
- Ask for three possible fixes, ranked by effort and by how likely they are to stop the problem recurring, then choose one yourself and set the owner and date. Claude structures the thinking, but the judgment about your business stays with you.
Frequently asked questions
What is a 5 Whys analysis?
A 5 Whys analysis is a root cause technique where you state a problem and repeatedly ask why it happened, each time questioning the previous answer, until you reach a cause you can fix rather than a symptom.
Do you always have to ask why five times?
No. Five is a guideline. Stop when you reach a process, rule, or decision you can change. Simple problems may take three whys and complex ones more than five.
Who created the 5 Whys?
The technique traces back to Sakichi Toyoda, the founder of the Toyota Group, and it was built into the Toyota Production System, where Taiichi Ohno made it a core habit of problem solving.
What is the difference between the 5 Whys and a fishbone diagram?
A fishbone diagram maps many possible causes of a problem across categories. The 5 Whys follows one chain of cause and effect down to a root cause. They work well together: use the fishbone to find the likely branches, then run a 5 Whys on each.
What are the limitations of the 5 Whys?
It can stop at a symptom, it is limited by what the people doing it already know, different people can reach different answers, and it tends to find one cause when there may be several. Checking evidence at every step and following more than one branch reduces these risks.
Can you use the 5 Whys outside manufacturing?
Yes. It works for any repeatable problem: customer complaints, late projects, billing errors, falling conversion, or missed sales targets. The method is the same wherever the problem comes from.