Five Whys is a questioning technique that follows possible causal links behind a problem. The number five is a guide to enquiry, not a required count or proof of depth. Each answer should be supported by evidence and may open several branches rather than a single neat chain.
The Corrective Action and Continual Improvement in Quality Management places this topic in its wider QMS context. Use the technique for a manageable problem whose mechanism can be examined. Complex interacting failures may require additional analysis and specialist investigation.
Define the decision and its boundary
Clarify the purpose of five whys analysis with the person who uses its result. Ask what information would make the output useful and which omissions would force that person to repeat the work. This discussion often reveals a different priority from the one suggested by the document title. Keep the final description concrete enough to guide a decision during an ordinary working day.
End questioning when the explanation is specific enough to support a feasible, testable response and the evidence supports the links. Continuing to ask why can eventually produce statements about broad organisational purpose that are too remote to act on. Stopping after exactly five questions can leave an important mechanism unexplained. Depth should follow the investigation, with a documented reason for the chosen response boundary.
Put the method into practice
Pilot the proposed method for five whys analysis using work of different complexity. Include at least one relevant change or exception rather than demonstrating only a straightforward success. Observe where staff hesitate, duplicate information or seek approval outside the described route. Revise those points before wider use, and explain which local choices remain available to the responsible person.
-
Start with an observable failure rather than a judgement about a person.
-
Ask why the condition occurred and record evidence for each answer.
-
Branch where causes differ and test the proposed chain against actual cases.
Worked example
A fictional office misses a review deadline. Why? The reviewer did not receive the file. Why? The notification used an outdated role address. Why? Role-address changes were outside the access-change checklist.
The team verifies the routing history and checks other role changes. It amends the relevant checklist and tests notification delivery rather than stopping at an absent individual.
Use the scenario to ask how five whys analysis would operate under your own conditions. The fictional organisation can make a decision because it has access to particular information and authority. A real team may need an additional enquiry or a temporary restriction. Adapt the reasoning rather than copying the outcome, and record why any important difference changes the chosen approach.
Useful evidence and records
Design the record for five whys analysis around continuity. Another competent person should be able to understand what was decided, what evidence supported it and what remains to be done. Avoid long copied passages when a controlled reference would be clearer. Equally, a bare link without context may become meaningless after a system change, so retain a useful description of the evidence.
| Record element | What it should establish |
|---|---|
| Starting event | Evidence of the missed review |
| Causal link | Observation supporting each answer |
| Alternative branch | Other credible explanations |
| Test | How the chain was challenged |
Check the result and avoid a common mistake
Leading questions can manufacture a chain that supports a preferred solution. Ask what evidence would disprove each answer and avoid stopping at blame or vague culture labels.
Have a colleague trace the chain backwards. Each proposed cause should plausibly create the next condition, with records or observations supporting the connection.
Judge five whys analysis against a stated purpose rather than a convenient activity count. Completing meetings, records or training may support the result but does not demonstrate it. Identify what changed for the next process or recipient. If a benefit is claimed, explain the comparison and account for material changes in workload or complexity before attributing the difference to the new arrangement.
Connect the next decision
When the evidence from five whys analysis changes, update the operating decision as well as the record. Explain the reason to affected staff and check whether documents, permissions or commitments need adjustment. A revised assessment has little practical value if people continue using the earlier arrangement. Preserve enough history to show why the change was reasonable when it was made.
Use Fishbone Diagram for Quality Problems when the work moves to the adjacent decision. The related guide to cause-and-effect diagrams explains the wider process dependency. The handover should identify what has been accepted, what remains open and who will review the next evidence. Keep the original decision traceable when later information changes the conclusion.
What if the fifth answer is uncertain?
Do not present it as a finding merely because the exercise has reached five questions. Record the uncertainty and decide which evidence could resolve it. The team may need to branch the enquiry, inspect additional cases or use a different analysis method before approving a cause-based response.