Five Whys
2 min read · Reviewed 17 Oct 2026
In short
Asking why five times in a row, to get past the symptom to the cause.
In plain English
You take the problem you can see and ask why it is happening. Then you ask why that is happening. Five times, or until the answers stop changing.
The number is not sacred. The point is that the first answer is almost always a symptom, and the thing worth fixing is usually three or four levels down.
A real example
Sales are down this quarter.
Why? Fewer enquiries. Why? The newsletter went out twice instead of eight times. Why? It kept getting pushed back. Why? It takes a full day to write. Why? There is no outline, so every issue starts from nothing.
The visible problem was sales. The fixable one is a missing outline. Fixing the outline is a morning's work; "fix sales" is not a task anybody can start.
Why it matters
Most plans solve the thing that was visible. That is why the same problem keeps coming back wearing different clothes.
A word of caution: the chain is only as good as the evidence under it. It is easy to produce five confident whys that are all guesses, especially with AI, which will happily continue a chain it has no information about. Mark which links you actually know and which you assumed, and go and check the ones that matter.
