Fishbone vs. 5 Whys vs. A3: When to Use Each
- timothyferguson1
- Jun 13
- 4 min read
June 13, 2026
"Should we do a fishbone or a 5 Whys?" is one of the most common questions in root cause analysis — and it's the wrong question. Fishbone, 5 Whys, and A3 aren't rival methods you pick between. They're different stages of the same investigation, each doing a job the others can't. Used together, they take you from "something's wrong" to a fix that sticks.
Here's what each one is for, when to reach for it, and how they fit together.
Want the full process first? See our https://www.fsquaredconsultinggroup.com/post/root-cause-analysis-guide
The short answer
- Fishbone (Ishikawa) — to explore possibilities when you don't yet know the cause. It widens your thinking.
- 5 Whys — to drill a chosen cause down to its systemic root. It deepens your thinking.
- A3 — to document and standardize the whole story on one page. It communicates and sustains.
Fishbone goes wide. 5 Whys goes deep. A3 ties it together. Most real investigations use all three, in roughly that order.
Compared at a glance
| Fishbone (Ishikawa) | 5 Whys | A3 Report |
Purpose | Brainstorm possible causes | Drill to the root cause | Document & standardize |
Shape of thinking | Wide (many candidates) | Deep (one chain) | Whole story (one page) |
Best when | The cause is unknown | You have a strong candidate cause | You need to share & sustain the fix |
Output | Categorized cause map | A root cause + corrective actions | A one-page PDCA report |
Risk if used alone | Lots of ideas, no root | Tunnel vision on one path | Nothing to document yet |
RCA stage | Explore | Drill | Document |
When to use a fishbone diagram
Reach for a fishbone early — when you have a defined problem but don't yet know what's causing it. By sorting candidate causes into categories (commonly the 6 Ms: People, Process, Equipment, Materials, Environment, Management), it forces you to consider the whole problem space instead of fixating on the first plausible idea.
Use it when:
- The cause is genuinely unknown or contested.
- You want a team's full range of ideas on the table.
- The problem could have several contributing factors.
Its weakness alone: a fishbone produces possibilities, not proof. You still have to drill the most likely branches.
When to use 5 Whys
Reach for 5 Whys once you've got a strong candidate cause and need to reach its systemic root. You ask "why does that happen?" repeatedly — about five times — until the answer points to a process, standard, or design factor you can actually change.
Use it when:
- You've identified a likely cause (often from a fishbone) and need to go deeper.
- The problem runs in a fairly traceable chain of cause and effect.
- You need to land on something fixable, not just another symptom.
Its weakness alone: start 5 Whys without exploring first and you can tunnel down one path while the real cause sits on a branch you never considered. For complex issues, run it in branching or three-legged form (Occurrence / Detection / Systemic) so you don't fix the event but miss the escape point or the system.
Reach for an A3 to capture and communicate the whole investigation on a single page — problem, background, current state, root causes, plan, results, and reflections, following PDCA. It's how you get leadership alignment and make the fix part of the standard rather than a one-time heroics.
Use it when:
- You need to brief stakeholders or get a countermeasure approved.
- You want a durable record others can learn from.
- You're standardizing and sustaining a fix, not just finding it.
Its weakness alone: an A3 is a container — it's only as good as the analysis you put in it. Do the fishbone and 5 Whys first.
How they work together
A typical end-to-end investigation looks like this:
Define the problem precisely. https://www.fsquaredconsultinggroup.com/post/how-to-write-a-problem-statement
Explore with a fishbone — map every plausible cause.
Drill the strongest branch with 5 Whys — reach the systemic root and draft corrective actions.
Document it in an A3 — tell the story, assign actions, standardize the fix.
Each tool feeds the next: the fishbone narrows the field, the 5 Whys proves the root, and the A3 turns it into action others can follow.
Try the whole flow free: The F Squared RCA Suite connects all four steps — Problem Builder, fishbone, 5 Whys, and A3 — so your analysis carries from one to the next without re-typing. Try it free →
Or download the free RCA Starter Kit — printable templates for all of them plus a quick-start guide. https://www.fsquaredconsultinggroup.com/digitaltools
Frequently asked questions
Is a fishbone better than 5 Whys?
Neither is "better" — they do different jobs. A fishbone explores many possible causes; 5 Whys drills one cause to its root. Use the fishbone first to find candidates, then 5 Whys to dig.
Can you use 5 Whys and a fishbone together?
Yes — that's the ideal. Brainstorm causes on a fishbone, pick the most likely branch, then run a 5 Whys on it. Many teams write the chosen cause from the fishbone as the top of the 5 Whys.
Where does the A3 fit in?
The A3 is the documentation layer. After the fishbone and 5 Whys reveal the root cause and countermeasures, the A3 captures the whole story on one page for review and standardization.
Which should a beginner start with?
Start by defining the problem clearly, then use a fishbone — it's the most forgiving way to get a team's ideas out. Add 5 Whys and an A3 as the investigation matures.
Do I need all three for every problem?
No. Small, well-understood issues might just need a quick 5 Whys. Use the full sequence for recurring, costly, or high-risk problems where a lasting fix matters.
Comments