What is it?
5 Whys helps you move beyond the immediate explanation for a problem and explore what allowed it to happen. By asking why the previous answer was true, you can trace a chain from the visible symptom towards something more useful to investigate.
What's it really for?
The number five is not sacred. It is simply long enough to discourage a shallow answer and short enough to fit on a page. The real discipline is refusing to stop at an explanation that merely relocates the blame.
You know when…
A defect reaches the customer and the explanation arrives before the investigation: somebody did not follow the procedure. The procedure is quietly updated, everyone is reminded to be more careful, and the same defect returns three months later wearing a different hat.
Have a go
- Start with one specific problem or event.
- Ask why it happened and record the answer.
- Ask why that answer was true, following evidence rather than opinion.
- Stop when the next answer points to something the system can change.
Why it works
The first explanation usually describes what happened nearest to the problem. That is useful, but rarely sufficient. Repeating the question encourages the team to move from event to condition, and from condition to the way the system was designed, managed or understood.
Look for…
Good chains move from symptoms towards conditions such as unclear standards, weak feedback, missing controls, competing priorities or poor process design. Notice when several chains arrive at the same underlying condition; that is often more useful than reaching exactly five answers.
Watch out…
Asked badly, 5 Whys can feel like an interrogation with stationery. Use it to understand the work, not to corner the person nearest to the problem. When an answer contains a name, a job title or the phrase “lack of attention”, there is probably another why worth asking.
Worth noticing…
A root cause is not the deepest sentence on the page. It is a condition worth changing because doing so makes recurrence less likely.
Try next…
Use a Fishbone Diagram when several possible cause paths need exploring. Use an A3 or PDCA cycle when the investigation is ready to become a managed improvement.