The 5 Why Analysis Template That Stops You at Operator Error
Most 5-Why analysis fails because it ends at blame instead of a system cause you can fix. Here are the discipline rules and a fill-in template that forces past operator error.
I have read hundreds of 5-Why investigations on the plant floor, and most of them die in the same place. Why did the part ship out of spec? Operator error. Why did the operator make an error? They did not pay attention. Why did they not pay attention? Well, you know how it is on second shift.
Then somebody writes “retrain the operator” in the corrective action box, everybody signs it, and the same defect comes back in six weeks. You retrain the same operator, or a different one, and you have learned nothing.
That is not root cause analysis. That is blame with a worksheet stapled to it. The whole point of a 5-Why is to walk a chain of causes until you reach something a process change can fix. “Operator error” is never that thing. People are not a root cause you can change. Conditions, processes, and decisions are.
This is the version of the 5-Why I actually use, with the rules that force you past the dead end, plus a worked example and a fill-in template you can take to your next investigation.
Why “Operator Error” Is a Stopping Failure, Not an Answer
Here is the uncomfortable truth: in almost every “operator error” case, the operator did exactly what the system made easy and the system made the wrong thing easy.
If a part can be loaded backward, eventually it will be loaded backward. If two fittings look identical and only one is correct, eventually the wrong one goes on. If the work instruction lives in a binder three stations away, eventually nobody walks over to read it. The operator is the last person to touch the defect, so they are the easiest one to name. But naming the person who was standing closest to the failure is not the same as finding the cause of it.
When your 5-Why ends at a name or a personal trait (“careless,” “rushed,” “new”), you have not finished the analysis. You have just found the place where the system handed a hard job to a human and the human did the human thing.
The Five Rules That Force You Past Blame
These are the rules I hold every 5-Why to. They are simple, and they are strict on purpose.
-
Every “why” must point to a process or a condition, not a person. If the answer to any “why” is a name or a personality trait, it is not a valid link in the chain. Reword it as a condition. “The operator loaded it backward” becomes “the fixture accepts the part in two orientations and only one is correct.” Now you have something to fix.
-
If the answer is a name, you stopped too early. A name is a signal, not a conclusion. It tells you where the failure surfaced, and that is your cue to ask the next why about the conditions around that person, not to close the case.
-
Test every link by reading it backward with “therefore.” Start at the bottom of your chain and read up. “The fixture accepts the part in two orientations, therefore the part was loaded backward, therefore the seal did not seat, therefore the unit leaked.” If the “therefores” hold, your logic is sound. If one of them makes you wince, that link is weak and you need to dig there.
-
Stop when you reach something a process change can fix. Not five whys because the tool is called Five Why. You stop when the answer is something you have the authority and the means to change: a fixture, a check, a spec, a sequence, a piece of training built into the standard work rather than bolted on after the fact. Sometimes that is three whys. Sometimes it is seven.
-
Watch for the single-track trap. Real defects on a real line usually have more than one cause chain running in parallel. The part was loadable backward (design condition) and the leak test was set to a pressure that missed slow leaks (verification condition). Fix only one and the defect changes shape but does not leave. If your investigation produced exactly one tidy line of whys, be suspicious. Ask “what else had to be true for this to escape?”
That last rule is the one most templates ignore, and it is the one that separates an investigation that holds from one that comes back.
A Worked 5-Why on a Real Defect
Let me walk one the way it should go. The defect: a hydraulic unit shipped, and the customer found it leaking at the housing seal.
The lazy version stops at why number two. Here is the disciplined version.
- Why did the unit leak? The housing seal did not seat fully.
- Why did the seal not seat? The housing was loaded into the press fixture backward, so the seal groove faced the wrong way.
- Why was it loaded backward? The fixture physically accepts the housing in both orientations, and the correct orientation is not obvious at the loading station.
- Why is the correct orientation not enforced? The fixture was carried over from an older housing that was symmetrical, and it was never updated when the new asymmetrical housing was introduced.
- Why was the leak not caught before shipment? The end-of-line pressure test runs at a pressure and dwell time that a slow seal leak can pass.
Read it backward with “therefore” and it holds. Now look at what we found: two parallel root causes, not one. A design condition (the fixture allows a wrong orientation) and a verification condition (the test misses slow leaks). Either one alone explains part of the failure. Both together explain why this unit reached a customer.
The corrective actions write themselves now, and not one of them is “retrain the operator.” Add a locating pin so the housing only fits one way. Re-evaluate the pressure test dwell time against the seal’s known leak profile. Those are process changes. They survive turnover, they survive a bad night on second shift, and they do not depend on anyone remembering anything.
If you are turning findings like these into a formal corrective action, the way you scope and write it matters as much as the analysis. I walk through that in right-sizing the CAPA process for a small shop and how to write a CAPA report so the document earns its keep instead of sitting in a binder.
The Fill-In Template, With the Checkpoints Built In
A blank five-line worksheet is exactly what gets you to “operator error,” because nothing on it pushes back. The template I use has the anti-blame checks baked into the form so you cannot skip them.
For each problem, work down the chain and answer the checkpoint at every level:
- Problem statement (be specific): What was the defect, where was it found, and what is the measurable symptom? “Unit leaked at housing seal, found at customer, fails 30 psi hold.”
- Why 1, and the check: State the cause. Then ask: is this a process or condition, not a person? If it names someone, reword it.
- Why 2, and the check: Same. Read it backward to Why 1 with “therefore.” Does it hold?
- Why 3, and the check: Same. Have you reached something you can actually change yet? If yes, you may be done. If the answer is still a behavior, keep going.
- Continue as needed: There is no rule that says exactly five. Stop at the actionable condition.
- Parallel chains: What else had to be true for this defect to escape to the customer? Run a second short chain on detection and verification, separate from the cause of the defect itself.
- Root causes identified (expect more than one): List every condition a process change can address.
- Corrective actions: One per root cause. Each one must be a change to a process, fixture, spec, or check, never “retrain” or “remind” on its own.
The two questions that do the heavy lifting are “is this a person or a condition?” at every level, and “what else had to be true?” at the end. Print them at the top of the form if you have to. They are the difference between a 5-Why that closes a problem and one that just closes a ticket.
Where This Sits in the Bigger Picture
A clean 5-Why is the engine inside almost every corrective action you will ever file, and it feeds directly into the rest of the quality system I write about in this series: how you scope a CAPA, how you write it up so it survives an audit conversation, how you keep the whole thing right-sized for a shop that does not have a dedicated quality department.
The discipline is the same every time. Stop blaming the last hand that touched the part. Keep asking why until you reach a condition you can change. Then change it, and watch whether the defect comes back. If it does, you stopped too early or you missed a parallel chain, and you go again.
If you want the worksheet with the anti-blame checkpoints already built into it, I put together a fill-in 5-Why template you can download and bring to your next investigation. It is the same form I described above, set up so the checks are hard to skip. It pairs with the CAPA material in this series if you want the full thread from defect to closed corrective action.
Liked this? Get the free SOP Writing Cheat Sheet.
The 6-step SOP format on one page. Free.