The 5 Whys: A Working Guide to Finding the Real Cause
Of all the tools in the Lean Six Sigma kit, the 5 Whys is the most disarmingly plain. You state a problem, ask why it happened, then ask why again of the answer — five times or so — until you reach a cause you can actually fix. Toyota popularized it on the factory floor, and it has earned its place because it pushes past the first convenient explanation. As organizations spent 2021 untangling supply shocks and processes reshaped by remote work, the temptation to patch symptoms was everywhere. The 5 Whys is the discipline that resists it.
Why surface fixes don't last
A late shipment, a rejected part, a missed approval — each is usually a symptom sitting on top of a chain of causes. Treat the symptom and it returns next week wearing a slightly different face. The 5 Whys works because each answer becomes the next question, forcing you down the chain from what happened to why the system allowed it. The number five isn't sacred; sometimes you reach the root in three steps, sometimes seven. The point is to keep going until the cause is something a process change can address, not a person to blame.
How to run it well
Write the problem as an observable fact. Start with something specific and verifiable — 'the September report went out two days late' — not a vague complaint like 'reporting is slow.'
Ask why, and answer with evidence. Each 'why' should be answered from data or direct observation, not assumption. If you can't point to proof, go and look before you continue.
Follow one chain at a time. Real problems often branch. Track each branch separately rather than blending them, or use a fishbone diagram alongside to keep the threads clear.
Stop at a cause you can act on. The right stopping point is a systemic, controllable cause. If your last answer is 'human error,' you stopped too early — ask why the error was possible.
Confirm the link backwards. Read the chain in reverse with a 'therefore.' If 'no standard hand-off checklist, therefore the step was skipped, therefore the report was late' holds up, your logic is sound.
A short worked example
Problem: a monthly compliance report was submitted late. Why? The data wasn't ready in time. Why? The source figures arrived the afternoon before the deadline. Why? The team that owns them only learned the date the day before. Why? The deadline was never added to the shared calendar. Why? No one owns maintaining that calendar. The root cause isn't a careless analyst — it's a missing ownership for a shared schedule. Fix that, and the late report stops recurring.
Keep the group small and include people who do the actual work
Distrust any answer that ends in blame — keep asking why the conditions existed
Pair the 5 Whys with a quick check of the data so you aren't reasoning from a hunch
Verify the fix by watching the metric over the next few cycles, not just once
Used honestly, the 5 Whys turns firefighting into prevention. It costs nothing but attention, and it consistently surfaces the systemic gaps — unclear ownership, missing standards, broken hand-offs — that quietly generate the same problems again and again.
Building a habit of getting to root cause, rather than living from one fire to the next, is part of the operating discipline we help organizations put in place through XNM's strategic advisory.