What is the 5 Whys technique?
The 5 Whys is a simple root cause analysis method: state the problem, ask why it happened, then ask why about that answer, and repeat until you reach a cause that, once removed, prevents the problem from coming back. It was developed by Sakichi Toyoda and became a core practice of the Toyota Production System and lean manufacturing.
The power of the 5 Whys is that it moves a team past symptoms ("the sensor failed") to process and system causes ("equipment changes bypass change control"). That is where corrective actions are the most effective.
5 Whys example
The tool opens with a packaging example. Problem: a customer received 200 cartons without lot number labels.
| Why? | Answer |
|---|---|
| 1 | The labeler skipped cartons during the run. |
| 2 | The carton-present sensor did not detect some cartons. |
| 3 | The sensor was misaligned after the conveyor belt was replaced. |
| 4 | The belt replacement work instruction has no sensor alignment check. |
| 5 | The new conveyor was installed without change control, so maintenance instructions were never reviewed. |
Replacing the sensor would fix today's symptom. Bringing equipment modifications under change control fixes the root cause.
The 3-legged 5 Whys
Many quality teams run three chains for the same problem, a practice often required by automotive and medical device customers:
- Occurrence: why did the problem happen?
- Detection: why did our controls not catch it before it reached the customer?
- Systemic: why did our management system (planning, FMEA, change control, training) allow it?
Click + Add chain to add each leg. Each chain gets its own root cause and countermeasure.
Rules for a good 5 Whys
- Base each answer on facts. Go to the gemba, check records and data. Do not guess.
- Don't stop at "human error". Ask why the process made the error possible or likely.
- Test the logic backwards. Read from the root cause up, joining answers with "therefore". If it doesn't hold, fix the chain.
- Branch when needed. If one why has two valid answers, start a new chain, or map causes first with a fishbone diagram.
- Stop at a cause you control. "Supplier quality" is too broad; "no incoming inspection for this critical dimension" is actionable.
From root cause to CAPA
Finding the root cause is half the job. The rest is implementing the countermeasure, verifying it worked and proving it to auditors. Cloudtheapp's eQMS turns the countermeasure into a CAPA, assigns actions with due dates and reminders, and closes the loop with effectiveness checks.
How to use this 5 Whys tool
- Define the problem. Write a factual problem statement: what happened, where, when and how big. Do not include a suspected cause.
- Ask the first why. Ask why the problem happened and record the answer, based on facts and evidence from the process.
- Keep asking why. Ask why about each answer. The tool shows the previous answer as a prompt. Press Enter to add the next why.
- Add a detection or systemic chain. Add a second chain for why the problem escaped detection, and a third for why the system allowed it.
- Confirm the root cause. Check that fixing the last answer would prevent recurrence. Read the chain backwards with "therefore" to test the logic.
- Define countermeasures. Add an action, owner and due date for each root cause, then export the analysis for your CAPA or 8D.
Frequently asked questions
What is the 5 Whys technique?
The 5 Whys is a root cause analysis technique where you ask "why?" repeatedly, each time about the previous answer, until you reach a cause that, if removed, would prevent the problem from recurring. It was developed by Sakichi Toyoda and made famous by the Toyota Production System.
Do you always have to ask exactly five whys?
No. Five is a rule of thumb. Stop when you reach a cause you can act on and that explains the problem, which may take three whys or seven. If you stop at a symptom or at "human error", keep asking.
What is a 3-legged 5 Whys?
A 3-legged (or 3x5) Whys analyzes three paths for the same problem: why it occurred, why it was not detected, and why the management system allowed it. This tool supports as many chains as you need, with presets for all three legs.
What are the limitations of the 5 Whys?
A single chain assumes one linear cause, and results depend on the knowledge of the people in the room. For complex problems, start with a fishbone diagram to map all potential causes and use 5 Whys to drill into the most likely branches, verifying each answer with evidence.
Can I use the 5 Whys in an 8D or CAPA?
Yes. The 5 Whys is commonly used in D4 (root cause) of an 8D report and in the investigation section of a CAPA. Export your analysis as a PDF or Excel file to attach it to the record.
Is this 5 Whys template free?
Yes. The tool is completely free, requires no sign-up and keeps your data in your own browser. You can export to PDF, PNG, Excel or CSV, or save a file to continue later.