What is it, and why use it?
5 Whys is an evidence-led investigation that asks why a specific problem happened and follows each plausible explanation toward an actionable system condition. Five is a prompt, not a required number of levels.
It helps a team move beyond the visible symptom without stopping at blame or the first convenient explanation.
Explore the 5 Whys features and local-file workflowWhen to use it
Use it for a clearly bounded problem where people can inspect the process and test explanations.
When another tool fits better
Use Fishbone to generate a broad set of hypotheses, or Root Cause Analysis Builder when several branches and validation records need to be coordinated.
Before you start
- An observable problem statement rather than a person to blame.
- Records or observations that can support or contradict an explanation.
- People with direct knowledge of the work.
Use fictional or approved non-sensitive information. Do not include patient details or proprietary records in practice worksheets.
Step-by-step in CI Tools
Enter the Problem statement and start the Primary investigation.
At each Why, write a possible cause and the evidence for it. Leave unsupported claims as hypotheses.
Add a branch when another explanation deserves investigation; do not force independent causes into a single chain.
Record the proposed root cause, validation and countermeasure in the investigation fields. Test the countermeasure on a small scale.
Use a related Action Plan to assign follow-up and retain the reasoning in your editable file.
Evidence matters more than the number of whys
For each link, name what was observed, what would contradict it and how you will check. Keep facts separate from recollection or assumptions. Do not use this worksheet as an individual performance judgment.
Completed worked examples
Demonstrations only: all organizations, observations, targets and results below are fictional. They are not clinical instructions or universal performance standards.
Healthcare operations — fictional
Missing referral attachment
Starting information: A fictional intake team repeatedly requests a missing attachment.
| Why 1 | The sender used a form without an attachment prompt |
|---|---|
| Why 2 | Two form versions were still available on the internal page |
| Validation / response | Observed submissions used the older version; remove the obsolete entry and test new submissions |
What the result means: The form-version explanation is supported by this fictional observation. It does not establish that every missing attachment has the same cause.
General business — fictional
Late stock replenishment
Starting information: A fictional shop runs out of packaging before the weekly delivery.
| Why 1 | The reorder was not raised when stock reached the threshold |
|---|---|
| Why 2 | The threshold was visible only in a spreadsheet that was not reviewed daily |
| Countermeasure | Assign a daily stock check and test whether orders trigger on time |
What the result means: Check demand and supplier reliability too. A different branch may explain the same symptom without contradicting this chain.
Practise in a separate worksheet
Open the tool’s built-in synthetic sample as a new editable worksheet. It may differ from the worked demonstrations above. It never replaces an existing worksheet. Save any work you want to retain to your computer.
Open built-in practice worksheetYou’ll be asked to log in if needed. No worksheet is created just by reading this page.
Common mistakes and how to avoid them
- Stopping at “human error”: investigate conditions that made the error possible.
- Treating a chain as proof: validate each link with evidence.
- Forcing exactly five answers: stop when the explanation is testable and useful, or branch when necessary.
Interpret the result
Read the chain backwards: if the proposed condition changed, why should the next event be less likely? Track contradictory evidence and test the proposed response. A plausible narrative alone is not a validated cause.
Record the assumptions and unanswered questions alongside the result. Use the relevant local review process before making operational decisions.
Credible further learning
These independent educational resources explain the methods. They do not endorse CI Tools Suite. Some external resources have their own access requirements.
- ASQ: Cause analysis tools (external resource)
- IHI: Quality Improvement Essentials Toolkit (external resource)
Resource links reviewed 29 October 2026. Our interface instructions and fictional examples are original CI Tools learning material.
Put the method into practice
Start a new worksheet, use the guide beside your work and keep an editable .citools copy on your computer.
Try This ToolChoose another tool