Leadership & Management 👥, Lean Methodology

Avatar for Nelson FernandesBy • 17 minutes of reading • Sep 2026

Senior Store ManagerWriting since 2019, still in the job

5 Whys examples: a store manager and colleague work a five-step why chain on a stockroom whiteboard

5 Whys Examples and Free Tool

Find the real cause of a problem in about fifteen minutes. Answer one why at a time, and an AI coach checks your chain before you finish.

FreeNo sign-upAI coach12 real examples

Did you check this where the work happens?

In short

The 5 Whys (also written five whys, 5-why analysis, or why-why analysis) is a root cause analysis method from the Toyota Production System. You state a problem you can see, ask why it happened, then ask why of each answer until you reach a condition in the process that, once changed, stops the problem coming back. Five is a guide, not a rule. The output is one root cause, one countermeasure, one owner and a review date.

The first 5 Whys I ever ran was in a stockroom, not a classroom. A bestseller kept missing from the shelf on Saturday mornings, and the easy answer was the Friday team. Five questions later the rota was the problem, and nobody on that shift had done anything wrong. Most 5 whys examples you find online start on a factory line. The ones below start where most of us actually work: a team, a shop floor, a customer inbox, a morning routine. You get twelve worked examples and a free online 5 Whys template you can share by link, with built-in hints that catch the mistakes a Lean Six Sigma Green Belt would look for.

5 Whys Template: Free Online Tool

This 5 Whys template runs in your browser, with nothing to sign up for. Type the problem, answer one why at a time, then name the root cause and one countermeasure. As you type, built-in hints flag the classic failures: a why that repeats the line above it, a why that stops at a person, and words like always and never that hide the real pattern. Your finished analysis includes the “therefore” test, read from the root up, so you can hear whether each link holds. Copy link puts the whole analysis into the address, so you can paste it into a chat or a retro doc, and Print or save as PDF gives you a one-page sheet.

What Is the 5 Whys Technique?

The 5 Whys is a way of refusing the first answer. Sakichi Toyoda, the founder of Toyota Industries, used it on the factory floor, and Taiichi Ohno later made it the backbone of Toyota’s problem solving. In Toyota Production System: Beyond Large-Scale Production (1988), Ohno describes asking why five times as the basis of the company’s scientific approach: repeat the question until the nature of the problem, and its solution, becomes clear. The Lean Enterprise Institute still lists it as one of the core lean tools, alongside mura, muri and muda.

The method works because it separates two things people usually blur: the symptom you noticed and the condition that produced it. The symptom is a late delivery, a missed target, a repeated mistake. The condition is a rota built on the wrong number, a checklist nobody owns, a decision nobody has the authority to make. Fix the symptom and it comes back next week. Fix the condition and it stays fixed.

In the best part of twenty years leading retail teams, I have watched the same thing happen every time I skipped the whys: I solved the person in front of me and the problem walked back in wearing a different name badge. The chains below are the ones I wish someone had shown me in my first year as a supervisor.

How to Do a 5 Whys Analysis (Step by Step)

A good 5 Whys takes fifteen minutes with the right people in the room. It fails for one of two reasons: the problem statement already contains the answer, or the chain stops the moment a person appears. The steps below guard against both.

  1. Write the problem as an event, not a judgement. “The Saturday delivery was not on the shelf by 9am, three weeks running.” Not “the Friday team is slow”. If the word because appears in the statement, you have started answering before you have started asking.
  2. Get the people who touch the process, not just the manager. The person who works the delivery knows why it sits in the cage. The person who writes the rota knows why the cage is unattended. You need both in the room.
  3. Ask why, and answer with a fact you could check. Each answer should describe a condition you could go and see. “The evening shift is two people” is a fact. “Nobody cares” is a feeling, and it ends the chain.
  4. When the chain lands on a person, ask the system question. “What made it easy for a capable person to do that?” Nine times out of ten the answer is a missing standard, a missing owner or a missing signal.
  5. Stop when you reach something you can change. Five is a guide. Some chains need three whys, some need seven. You are done when the last answer is a process condition that is within your authority to alter.
  6. Run the therefore test, then write the countermeasure. Read the chain backwards with “therefore” between each line. If it holds, write one countermeasure that changes the process, name an owner, and set a date to check whether the problem came back.

Twelve 5 Whys Examples: Leadership, Retail and Everyday Life

Every example below follows the same shape: a problem you could see, the chain, the root cause, and a countermeasure that changes the process. Tap one to open the full chain. None of them ends with “be more careful”.

5 Whys Examples for Leaders and Teams

1. The project missed its deadlineRoot cause: No agreed home for scope changes, so the plan moved without the order moving with it.

Problem: The store refit plan went live eleven days after the date agreed with the region.

  1. Why? The fixture order went in two weeks late.
  2. Why? The layout changed twice after the order was drafted.
  3. Why? Two different people asked for changes in two different meetings.
  4. Why? There is no single place where a scope change is agreed and recorded.
  5. Why? The project started from a conversation, not a brief, so nobody set that place up.

Root cause: No agreed home for scope changes, so the plan moved without the order moving with it.

Countermeasure: A one-page change log for every project over two weeks, reviewed in the weekly one-to-one. Owner: project lead. Review after the next project.

2. A team member escalates every decisionRoot cause: Decision rights live in people, not in the role.

Problem: The duty manager messaged me four times on Sunday for decisions under £50.

  1. Why? They were not sure they had the authority to decide.
  2. Why? Nobody has written down what a duty manager can decide alone.
  3. Why? The limits were in the previous store manager’s head and left with them.
  4. Why? Decision rights were never treated as part of the role, only as a habit of the person.
  5. Why? We onboard managers to tasks, not to authority.

Root cause: Decision rights live in people, not in the role.

Countermeasure: A one-page decision-rights sheet per role, with money limits and the three calls that always come to me. Owner: store manager. Review quarterly. This is the kind of gap the new manager checklist closes in the first thirty days.

3. The new starter left in week sixRoot cause: Onboarding depends on one person’s availability rather than a standard.

Problem: Our third new starter this year resigned before the end of probation.

  1. Why? In their exit chat they said they felt lost from week two.
  2. Why? Their buddy went off sick in week two and nobody picked it up.
  3. Why? The onboarding plan is a person, not a document.
  4. Why? We built onboarding around whoever was good at it, and never wrote it down.
  5. Why? Onboarding has no owner in the role structure, so it defaults to goodwill.

Root cause: Onboarding depends on one person’s availability rather than a standard.

Countermeasure: A 30-day onboarding checklist owned by the role “shift leader”, not by a named person, with a day-10 and day-30 check-in in the diary. Owner: store manager. Review after the next two starters.

4. The same mistake in the same report, three months runningRoot cause: An unowned checklist that has grown past the point where people follow it.

Problem: The month-end waste report has gone up with the wrong period total three times.

  1. Why? The reconciliation step gets skipped at the end.
  2. Why? It is item 38 on a 41-item checklist and month-end runs late.
  3. Why? The checklist has grown for four years and nobody has removed anything.
  4. Why? The checklist has no owner, so everyone adds and nobody trims.

Root cause: An unowned checklist that has grown past the point where people follow it.

Countermeasure: Assign an owner, cut the list to the twelve steps that change the result, and move reconciliation to step three. Owner: assistant manager. Review at the next two month-ends. Four whys were enough here.

5 Whys Examples in Retail and Operations

5. The bestseller is missing from the shelf every SaturdayRoot cause: Staffing follows sales, not workload, so the busiest replenishment window is the thinnest shift.

Problem: The top-selling line shows a shelf gap at 9am on Saturday, three weeks in a row.

  1. Why? The Friday afternoon delivery is still in the cage at opening.
  2. Why? The Friday evening shift does not finish working it.
  3. Why? Friday evening runs with two people.
  4. Why? The rota sets hours from sales, and Friday evening sales are low.
  5. Why? The rota model has no line for replenishment workload.

Root cause: Staffing follows sales, not workload, so the busiest replenishment window is the thinnest shift.

Countermeasure: Set Friday evening hours from the delivery note, with a minimum of three when volume passes the threshold. Owner: store manager. Review after four Fridays. The 7 wastes in retail calls this waiting waste, and the fix is nearly always in the rota.

6. The stock count keeps failing on accuracyRoot cause: No standard location for returns, so the process ends at a trolley.

Problem: Two consecutive stockroom audits scored under target on location accuracy.

  1. Why? Around a fifth of counted items were in the wrong location.
  2. Why? Most of those were customer returns.
  3. Why? Returns go into a “sort later” trolley and later rarely comes.
  4. Why? Returns have no defined home in the stockroom.
  5. Why? The stockroom layout was designed for inbound stock only.

Root cause: No standard location for returns, so the process ends at a trolley.

Countermeasure: A labelled returns bay and a ten-minute daily sort at close. Owner: stockroom lead. Review at the next audit. This is the “set in order” step of 5S applied to one problem, and it is where most kaizen examples in retail begin.

7. Long queues at 12:30, every dayRoot cause: Breaks are planned by clock, not by customer flow.

Problem: Queue length passes six customers at 12:30 on weekdays, with one till open.

  1. Why? Two of the three till-trained colleagues are on break at 12:30.
  2. Why? Breaks are set at 12:00, 12:30 and 13:00 by habit.
  3. Why? The morning manager writes breaks at open, before seeing footfall.
  4. Why? There is no rule that links breaks to the footfall curve.

Root cause: Breaks are planned by clock, not by customer flow.

Countermeasure: Break windows set from last month’s footfall by half hour, with no two till-trained people off between 12:00 and 13:30. Owner: duty manager. Review in two weeks.

5 Whys Examples for Customer Problems

8. The customer received the wrong itemRoot cause: Lookalike products with lookalike labels in adjacent bins.

Problem: Four wrong-item complaints this month, all on the same two products.

  1. Why? The picker took from the bin next to the right one.
  2. Why? The two products sit side by side and look identical in the box.
  3. Why? The bin labels show only the SKU code, and the codes differ by one digit.
  4. Why? Labels were designed for the stock system, not for the person picking at speed.

Root cause: Lookalike products with lookalike labels in adjacent bins.

Countermeasure: Separate the two bins and add a colour block and a product image to the labels of every lookalike pair. Owner: warehouse lead. Review after 200 picks.

9. A customer waited three days for a replyRoot cause: A rota that predates seven-day trading, with no review trigger.

Problem: A refund query sent on Saturday got its first reply on Tuesday.

  1. Why? It sat unread in the shared inbox until Tuesday morning.
  2. Why? Nobody checked the inbox on Monday.
  3. Why? Inbox ownership runs on a rota that stops on Friday.
  4. Why? The rota was written when the shop closed on Sundays and never revisited.
  5. Why? There is no trigger to review rotas when opening hours change.

Root cause: A rota that predates seven-day trading, with no review trigger.

Countermeasure: Named inbox owner for every trading day and a one-day reply standard, with rota review added to the opening-hours change checklist. Owner: customer service lead. Review in one month.

5 Whys Examples for Personal Habits

The method works on your own week as well as it works on a warehouse. The rule is the same: the chain should end in how the day is designed, not in a verdict on your character.

10. I keep skipping the gymRoot cause: The session is scheduled at the lowest-energy point of a day with no margin in it.

Problem: Three planned sessions a week, one completed, for a month.

  1. Why? By 7pm I am too tired to go.
  2. Why? I plan sessions for after work.
  3. Why? Mornings felt too rushed to fit anything in.
  4. Why? I get up at the last possible minute.
  5. Why? The evening runs late, so the alarm keeps moving.

Root cause: The session is scheduled at the lowest-energy point of a day with no margin in it.

Countermeasure: Move sessions to 6:45am on two fixed days, bag by the door the night before, screens off at 10pm. Owner: me. Review in three weeks.

11. I have put off the same report for two weeksRoot cause: A vague brief plus no safe, routine way to clarify it.

Problem: The quarterly review has been on the list for ten working days without a first draft.

  1. Why? I do not know where to start.
  2. Why? The brief was one line in an email.
  3. Why? I did not go back and ask what was wanted.
  4. Why? Asking felt like admitting I should already know.
  5. Why? There is no normal moment to check a brief before starting work on it.

Root cause: A vague brief plus no safe, routine way to clarify it.

Countermeasure: A three-question brief check before any report over an hour: who reads it, what decision it supports, what good looks like. Owner: me. Review after the next three reports.

12. Late for the 9am, most daysRoot cause: A morning designed for the best case, not the normal case.

Problem: Arrived after the 9:00 huddle started on seven of the last ten days.

  1. Why? I leave the house at 8:40 and the journey takes twenty minutes on a good day.
  2. Why? 8:40 is the time that works if nothing goes wrong.
  3. Why? The morning routine has no slack in it.
  4. Why? I planned it backwards from the start time with zero buffer.

Root cause: A morning designed for the best case, not the normal case.

Countermeasure: Leave at 8:25 and treat the fifteen minutes as reading time at the other end. Owner: me. Review in two weeks.

5 Whys vs Fishbone vs Pareto: Which Root Cause Tool to Use

The 5 Whys is the fastest of the root cause tools and the easiest to misuse. It suits one problem with one main cause, worked by a small group. When causes branch, or when you need to know which of many problems to attack first, reach for one of the others.

5 Whys

Best for
One specific, recurring problem with a single dominant cause. Team huddles, incident follow-ups, personal habits.
Time
15 to 30 minutes
Watch out
Stopping at a person. Following one chain when there are three.

Fishbone (Ishikawa)

Best for
Problems with several possible causes across people, process, equipment, materials, environment.
Time
45 to 90 minutes
Watch out
Producing a wall of possibilities and no decision. Pair it with a 5 Whys on the top two bones.

Pareto analysis

Best for
Deciding which problem matters most when you have data on frequency or cost.
Time
1 to 2 hours with data
Watch out
It ranks problems, it does not explain them. Run a 5 Whys on the top bar.

DMAIC

Best for
Larger, measurable problems that justify a project, typically Lean Six Sigma work.
Time
Weeks
Watch out
Using a project where a conversation would do.

Common 5 Whys Mistakes (and the Fix for Each)

Stopping at a person. “Because Sam forgot” feels like an answer. It is a symptom. The fix is the system question: what made it easy for a capable person to forget? The tool above flags this automatically.

Restating the problem. “Why was the shelf empty? Because the stock was not on it.” That is the same sentence twice. Each why should add a fact you could go and check.

Following one chain when there are three. If your second why has two honest answers, run both chains. Pick the one you can change first.

Treating five as a rule. Some chains end at three. Some need seven. You stop when you reach a condition inside your authority to change.

Finishing without a countermeasure. A root cause with no owner and no date is a good conversation. The kaizen habit is the follow-up: check in a month whether the problem came back. Most of the value is in that check.

How lean is your way of working?

The 5 Whys is one habit. The free Lean Quiz shows which of the lean habits you already have and which one to build next, in about three minutes.

Take the free Lean Quiz

Share, Embed or Cite the 5 Whys Tool

Everything on this page is free to use with your team, in training, or on your own site.

Embed the tool

Paste this into any page. It carries a plain link back here so your readers can find the examples.

<iframe src="https://tools.bestofmotivation.com/five-whys" title="5 Whys root cause analysis tool" width="100%" height="980" style="border:0;max-width:760px;display:block" loading="lazy"></iframe>
<p>Free <a href="https://bestofmotivation.com/5-whys/">5 Whys tool and examples</a> from Best of Motivation.</p>

Cite this page

Fernandes, N. (2026). 5 Whys Examples: 12 Real Root Cause Analyses (Free Template and Tool). Best of Motivation. https://bestofmotivation.com/5-whys/

Each example above has its own link, so you can send a colleague the one that matches their week rather than the whole page.

5 Whys FAQ

What is a good 5 Whys example?
A good 5 Whys example starts with a problem you can see, such as a bestseller missing from the shelf every Saturday, and ends with a process condition you can change, such as a rota that sets hours from sales rather than delivery volume. Each why adds a checkable fact, none of them ends on a person, and the last line comes with a countermeasure, an owner and a review date.
Do you always have to ask why exactly five times?
No. Five is a guide from Toyota’s experience, not a rule. Some problems reach a changeable root cause in three whys, others need six or seven. Stop when the last answer describes a condition in the process that is within your authority to change.
What do you do when the 5 Whys ends on a person?
Ask the system question: what made it easy for a capable person to do that? Blame ends the chain early and leaves the condition in place, so the same mistake returns with a different name on it. Rewrite the answer as a condition, such as a missing standard, a missing owner or a missing signal, and keep asking.
Is the 5 Whys the same as root cause analysis?
The 5 Whys is one root cause analysis method, and the quickest. Root cause analysis is the wider family that also includes fishbone diagrams, Pareto analysis and DMAIC. Use the 5 Whys for a single recurring problem, a fishbone when causes branch across people, process and equipment, and Pareto when you need to decide which problem to attack first.
Can I use the 5 Whys for personal problems?
Yes, and it works well for habits like skipping the gym, putting off a report or running late, as long as the chain ends in how your day is designed rather than in a verdict on your character. The countermeasure should change a time, a place or a trigger, not ask you to try harder.

More Articles You Will Like