Root Cause Analysis: 5 Whys vs Fishbone vs 8D — When to Use Each
Choosing a Root Cause Analysis Method
Root cause analysis (RCA) is the process of finding the underlying reason a problem occurred — not just the symptom you can see, but the system failure that allowed it to happen. For UK manufacturing SMEs running an ISO 9001 quality management system, RCA is the engine behind every meaningful corrective action. Get it wrong and you fix the symptom; the problem comes back. Get it right and the non-conformance does not recur.
The difficulty is not that RCA methods are hard to learn — most quality managers know all three covered here. The difficulty is choosing the right method for the problem in front of you. A 5 Whys analysis on a complex multi-cause failure produces a single shallow answer that misses two of the three real causes. A full 8D investigation on a one-off operator slip wastes two days of cross-functional time. Matching the method to the problem is the skill.
This guide compares the three most common RCA methods used in UK manufacturing — 5 Whys, fishbone (Ishikawa) diagrams, and 8D — and explains when each one is the right tool.
Quick Comparison
| Method | Best for | Effort | Output | Team size |
|---|---|---|---|---|
| 5 Whys | Simple, single-cause problems with a clear linear chain | Low (15-30 min) | A short cause chain ending in a root cause | 1-3 people |
| Fishbone (Ishikawa) | Problems where multiple categories of cause might contribute | Medium (30-90 min) | A categorised map of possible causes | 3-6 people |
| 8D | Serious, recurring, or customer-reported problems needing formal closure | High (days to weeks) | A structured 8-discipline report with containment, root cause, and verified corrective action | Cross-functional team |
The 5 Whys: Fast and Linear
The 5 Whys method asks "why?" repeatedly until you reach a root cause you can act on. It is the fastest RCA method and the easiest to teach. A typical analysis:
- Problem: A batch of machined parts was rejected for an out-of-tolerance bore diameter.
- Why 1: The boring tool was worn beyond its limit. Why?
- Why 2: The tool was not replaced at its scheduled change interval. Why?
- Why 3: The operator was not aware a change was due. Why?
- Why 4: The tool-life counter was not visible on the machine HMI. Why?
- Why 5: The maintenance procedure did not require a tool-life display to be configured.
The root cause is the procedure gap — not the worn tool, and not the operator. The corrective action targets the procedure.
When 5 Whys works well:
- The problem has a single, linear chain of cause and effect
- The root cause is within the team's knowledge and does not need data collection
- You need a fast answer for a low-to-medium impact non-conformance
Where 5 Whys falls down:
- Multiple causes. If a failure has three contributing causes, 5 Whys follows only one branch and misses the other two.
- Stopping too early. Teams often stop at the first cause they can blame (usually "operator error") rather than continuing to the systemic cause.
- No evidence. 5 Whys is only as good as the team's assumptions. Without data, each "why" can be a guess.
Run a structured 5 Whys analysis with the free 5 Whys Template Generator — it captures the problem statement, each why, the root cause, and the corrective action in a downloadable record you can attach to an NCR.
The Fishbone Diagram: Mapping Many Possible Causes
A fishbone diagram (also called an Ishikawa diagram or cause-and-effect diagram) maps every plausible cause of a problem into categories. The classic manufacturing categories are the 6Ms: Machine, Method, Material, Manpower (People), Measurement, and Mother Nature (Environment).
Where 5 Whys follows one chain, a fishbone explores all branches at once. The team brainstorms possible causes under each category, then investigates the most likely ones with data.
When a fishbone works well:
- The problem could have several causes and you are not sure which one dominates
- You want a structured brainstorm that does not jump to a single conclusion
- A cross-functional team needs a shared visual to discuss
Where a fishbone falls down:
- It identifies possible causes, not the root cause. A fishbone is a hypothesis-generating tool. After building it, you still need data to confirm which branch is the actual cause.
- It can become a wish-list. Without discipline, teams add every conceivable cause and end up with a diagram too large to action.
Use the free Fishbone Diagram Maker to build a 6M cause-and-effect diagram and export it as a PDF for your quality records.
The two methods complement each other: a fishbone identifies the candidate causes, then a 5 Whys drills into the most likely branch to reach the actionable root cause.
The 8D: Formal, Cross-Functional, Auditable
8D (Eight Disciplines) is the most rigorous of the three. It originated in the automotive industry and is now the default RCA framework for serious or customer-reported problems across UK manufacturing. The eight disciplines are:
- D1 — Establish the team
- D2 — Describe the problem
- D3 — Implement interim containment action
- D4 — Identify and verify the root cause
- D5 — Choose and verify permanent corrective actions
- D6 — Implement and validate corrective actions
- D7 — Prevent recurrence (systemic)
- D8 — Recognise the team and close
8D embeds the other two methods inside it: D4 (root cause) typically uses a fishbone to map candidate causes and 5 Whys to drill into them. What 8D adds is structure, containment, and verification — the things a quick 5 Whys leaves out.
When 8D is the right method:
- A customer has raised a complaint or a Supplier Corrective Action Request (SCAR) and expects a formal response
- The non-conformance is high-impact, safety-related, or recurring
- An ISO 9001 surveillance audit or a major customer expects to see documented, verified corrective action
Where 8D is overkill:
- One-off, low-impact problems. Running a full 8D on a single mis-labelled box wastes cross-functional time. A 5 Whys and a containment note are enough.
Build a complete 8D report with the free 8D Report Builder — it structures all eight disciplines and exports a customer-ready PDF.
A Decision Rule for UK SME Quality Managers
The depth of investigation should match the impact of the problem. A practical rule used across UK manufacturing SMEs:
- Low impact, single occurrence → 5 Whys. Contain, find the root cause, action it, close.
- Uncertain or multiple causes → Fishbone first (to map candidates), then 5 Whys (to drill into the dominant branch).
- High impact, recurring, or customer-reported → 8D. The customer or auditor expects formal containment, verified root cause, and effectiveness verification.
This matching is itself an audit point. ISO 9001:2015 clause 10.2 requires corrective action that is "appropriate to the effects of the nonconformities encountered" — auditors check that your investigation depth is proportionate, neither rubber-stamping serious issues nor over-engineering trivial ones.
Where RCA Fits in the ISO 9001 Process
Root cause analysis is the heart of the corrective action loop. The full sequence:
- A non-conformance is detected and a non-conformance report (NCR) is raised
- If the issue is systemic or recurring, a corrective action is opened (see the CAPA guide)
- Root cause analysis — using the method matched to the problem — establishes the underlying cause
- Corrective action targets the root cause, not the symptom
- Where the root cause requires a design or process change, an Engineering Change Request (ECR) is raised
ISO 9001:2015 clause 10.2 does not prescribe which RCA method to use — it requires you to "determine the causes" of the non-conformance. The method is your choice; the rigour must be proportionate.
How ChangeRoute Fits
A pattern of NCRs against the same drawing or process is often the evidence base for a design change. ChangeRoute links the root cause analysis, the NCR, and the resulting Engineering Change Request into one traceable chain — exactly the NCR-to-CAPA-to-ECO trace UK certification bodies look for during surveillance audits.
If you run a UK manufacturing SME and want to spend less time managing quality investigations in spreadsheets and Word documents, join the waitlist for early access.
Sources
- ISO 9001:2015 — Quality management systems — Requirements (clause 10.2 Nonconformity and corrective action). Available from ISO and BSI (paywalled).
- ISO/TC 176 — the ISO Technical Committee responsible for ISO 9001: iso.org/committee/53882