Guide
Old, simple, unfashionable — and still the fastest way to a cause you can actually fix.
How to run a 5 WHY that finds something, the test that separates a cause from a guess, the three traps that kill most investigations, and the free tool that prints the record.
And the tool has more to it than meets the eye. Work through it properly and there is a step at the end you will not see coming — the one that turns an event nobody wanted into a genuine learning opportunity for the business.
If you've raised kids, the word 'why' does something to your nervous system. Why is the sky blue. Why does the dog do that. Why do I have to. Why. Why. Why. The suggestion that you now sit in a meeting room and voluntarily run a process built entirely out of the word may have you quietly reaching for ear plugs while a small voice echoes — why dad, why mum, WHY.
Be assured: the 5 WHY is not an infinite loop. It has an end. With a decent subject and a bit of sense it stops in three to five moves, and it regularly turns up something you weren't looking for but badly needed to know.
The other difference: a four year old asks why to keep you talking. A crew asks why to stop the same thing happening again next month.
The method came out of Toyota — Sakichi Toyoda's, and later a core habit of the Toyota Production System. Taiichi Ohno's line was that repeating why five times makes the nature of the problem, and its solution, become clear. It predates every root cause platform on the market and it still outperforms most of them on the small stuff.
The wider quality literature agrees on why it survives: it needs no software, no statistician and no budget, it can be run in twenty minutes at the point of work, and it forces a group to move past the first plausible answer. Lean and Six Sigma teams still teach it as the entry-level root cause tool for exactly that reason.
The same literature is honest about the limits. It's a single-thread tool. Complex failures with several interacting causes need more than one chain, or a fishbone or fault tree alongside it. And it's only as good as the knowledge in the room — five people guessing five times produces a confident, well-formatted wrong answer.
Which is the whole point of the test on each level. That one habit is the difference between gold and paperwork.
The training trap. Somewhere around level three an answer appears: 'the operator wasn't trained properly.' The action becomes 'retrain the operator' and the file closes. Training is nearly always an output of a good investigation, not the cause. Push past it — what about the process, the tool, the handover or the information let this through even with a trained person standing there?
The communication trap. 'It wasn't communicated.' Communicating always has to happen, so it's always technically true and never a cause. Ask what made the information hard to get, late, wrong, or easy to skip.
The blame trap. If a name appears in a why level, the chain has stopped. People are part of every system and none of them turn up wanting to break something. Sacking the person leaves the conditions exactly where they were.
Our free tool flags all three as you type — not to nag you, but because they're the three exits people take right before the useful part.
Outcome: a roof access job stopped halfway through because the ladder brought to site couldn't safely reach the upper level.
Why 1 — the ladder specified for the job didn't suit a 5.2m rise. Why 2 — the rise was taken from an old site sketch, not measured. Why 3 — nobody was required to verify dimensions before the equipment list was locked. Why 4 — the job setup checklist has a field for equipment but no field for verified dimensions.
Root cause: the pre-job process lets an equipment list be approved off unverified measurements. Four levels, and the fix is a change to one form plus a check on who signs it — not 'remind the crew to measure things.'
Note what happened there. Nobody got blamed, nothing got 'retrained', and the corrective action is something you can point at in six months and prove.
The version most people never run: 5 WHY on a success. A job that went unusually well, a delivery that beat the schedule, a save on site. Same process, same testing, and at the end you've documented the conditions that made it happen instead of assuming it was luck or a good day.
Our form supports it directly — set the outcome as a success and work the chain the same way. It's the cheapest continuous improvement input you'll ever run.
An investigation that lives in someone's notebook isn't evidence. A finished 5 WHY should show the outcome, every level and its test, the root cause, the actions with owners and dates, and how the result was communicated. That's what an auditor, an insurer or a client asks for — and what your own team needs when the same thing surfaces again next year.
That structure is baked into our free tool. Fill it in, print or copy the record, drop it into your system. Nothing is stored on our side.