In nearly every root cause meeting there is a moment when someone asks why three times, lands on something that sounds like an explanation, and closes the list. The defect leaves, comes back the following month, and the explanation stays almost the same.
The 5 whys is a root cause technique: each answer gets followed by another why, chained, until the team reaches the cause that, if removed, keeps the problem from coming back. The number five is a reference. Sometimes the chain closes in three questions, sometimes it needs seven.
The third why feels like the answer
Picture a line that runs 400 parts in an 8 hour shift and starts rejecting for flash. Why is there flash: the mold did not close fully. Why did it not close fully: the pressure dropped. Why did the pressure drop: the operator did not reset the parameter at the shift change. Right there, on the third why, the team already has something it can write into an action plan, and it almost always stops.
It stops because the third why points at something concrete, at someone who did or did not do something. That feels like closure. The action plan reads retrain the operator, the report gets signed, and the meeting ends on time. Nobody lied and nobody did their job badly. An answer that can be written down got mistaken for an answer that solves.
What happens when you close there
The defect drops for two or three weeks. Then it comes back, almost always with a different operator on a different shift, because the cause was never the person. It was that the pressure parameter can be adjusted freely and nothing flags it once it drifts out of range. Retraining never touches that, and the cycle repeats under a new name on the report.
You have seen where most teams stop. Now for the question that actually continues.
The fourth why is the one that changes everything
Why could the operator adjust the pressure out of range: because the parameter has no locked limit on the machine control. Why does it not have one: because nobody defined it as critical when the equipment was installed. Right there the chain stopped talking about a person and started talking about a design nobody ever reviewed.
That is the why almost nobody asks, because it no longer points at anyone in the room. It points at a decision made years earlier that nobody has questioned since.
Root cause almost always lives in the system
Here is the test I use to know whether I have arrived. If the final answer has a person's name attached, I have not arrived yet. If the final answer is a system condition, a missing limit, a control nobody defined, a standard that was never written down, that is where root cause lives.
I run the 5 whys after the fishbone diagram, never before. The fishbone opens the fan of possible causes by category. The 5 whys close it, but only on the branch that already has evidence behind it. Asking why five times over an unverified hypothesis only produces a well told story, not a real cause.
Two traps that stretch or shorten the chain
- Stopping at the first answer that names a person. That is exactly the point where you need to keep asking, not where you are done.
- Continuing to ask after you already reached an actionable system cause. Five is a reference.
- Using the same generic why on every branch without going back to the floor to verify it. Each why needs its own data point, not an assumption chained to the previous one.
Start here
Pull the last action plan you closed for a recurring problem. Read the root cause written on it. If it names a person or a shift, you are still on the third why. Go back to that cause and ask once more why it was possible for it to happen.
This is exactly what I work in the problem solving workshop, on a real case from your plant. If you have a defect that has already come back more than once, tell me which one it is.
Why is it called the 5 whys if sometimes it takes more or fewer?
Because five is a practical reference, not a fixed rule. The chain ends once the answer describes a system condition rather than a person, whether that happens on the third why or the seventh.
Does the 5 whys replace the fishbone diagram?
No. The fishbone opens the fan of possible causes by category. The 5 whys get used afterward, on the branch that already has evidence, to drive down to the origin.
How do I know I have reached the root cause?
When the final answer describes something in the system, a missing limit, an unwritten standard, a control nobody defined, rather than a person. If your last answer has a name attached, you still need one more why.