Five Whys
Most people stop asking 'why' at the first answer that sounds plausible — which is usually a symptom, not a cause.
Why PMs should care
The feature someone requests is usually the what — the visible thing a team wants to build. The actual job the user is trying to do is several whys underneath that surface request.
Five isn't magic. Sometimes three whys gets you to the real cause, sometimes seven, sometimes the chain breaks after two and you need a different angle entirely. The skill isn't about the number of questions — it's about refusing to stop at the first answer that sounds plausible. The first answer is almost always a description of the symptom dressed up as a cause.
Done well, Five Whys moves a team from shipping a better version of the wrong thing to shipping a smaller, correct thing. Done badly, it turns into a kind of Socratic bullying — so in practice, run it with data next to you, not just a whiteboard.
Example in product work
Why did the user churn? They cancelled after week 3.
Why? They never funded their account.
Why? The bank transfer initiated but never settled.
Why? They had a typo in the IBAN.
Why did they never retry after the failure? The error message said 'payment unsuccessful, please try again' with no indication of which field was wrong, and the user assumed the whole service was broken.
Now you don't have a retention problem, an onboarding problem, or an activation problem. You have a specific, cheap, high-leverage fix: surface the validation error at the field level and allow one-tap correction.
Five minutes of engineering, probably 4–7% of the activation funnel. None of that was visible from 'why did the user churn?'
What to do when you see it
- The feature someone asks for is usually the 'what'. The real job is a few 'whys' below the surface.
- Five is not a magic number. Sometimes three 'whys' gets you there, sometimes seven, sometimes the chain breaks.
- The skill isn't the count. It's refusing to stop at the first answer that sounds plausible.
- Done well, Five Whys turns 'a better version of the wrong thing' into 'a smaller, correct thing'.
Sources & further reading
- Toyota Production System: Beyond Large-Scale Production — Taiichi Ohno, 1988Ohno's own book, where he describes asking 'why' five times as the basis of Toyota's scientific approach to problem-solving.
- The Five Whys — The Lean Startup, Eric RiesEric Ries's adaptation of the Five Whys for startup root-cause analysis.