Both the 5 Whys and the Fishbone (Ishikawa) diagram are root cause analysis tools, but they approach the problem from opposite directions. Understanding when to use each — and how to combine them — will make your problem-solving faster and more thorough.
Quick comparison
| Aspect | 5 Whys | Fishbone (Ishikawa) |
|---|---|---|
| Approach | Goes deep on one causal chain | Goes wide across many potential causes |
| Structure | Linear: symptom → cause → cause → root | Branching: categories → sub-causes → sub-sub-causes |
| Best for | Operational problems with a clear trigger | Complex problems with many potential causes |
| Time needed | 15–30 minutes | 45–90 minutes |
| Team size | 1–5 people | 3–8 people |
| Output | One root cause + corrective action | Map of all potential causes organized by category |
| Risk | May miss parallel causes | May stay at surface level without drilling deep |
| Origin | Toyota Production System (Sakichi Toyoda) | Kaoru Ishikawa, 1960s |
How each method works
5 Whys
Start with a specific symptom and ask "Why?" repeatedly. Each answer becomes the basis for the next question. You follow a single chain until you reach a systemic root cause.
- Problem: Server crashed
- Why? Memory was exhausted
- Why? A query loaded all records
- Why? No pagination was implemented
- Why? No performance review in code review
- Root: Missing performance checklist
Fishbone Diagram
Write the problem at the head of the "fish." Draw main bones for categories (People, Process, Technology, Environment, etc.). Brainstorm potential causes under each category.
- People: Training gap, understaffing
- Process: No code review, no alerts
- Technology: No auto-scaling, old DB
- Environment: Traffic spike, vendor issue
- Then investigate the most likely causes
Fishbone diagram structure
A Fishbone diagram organizes potential causes into categories. The six most common categories (the 6 M's from manufacturing) are: Man, Machine, Method, Material, Measurement, and Mother Nature (environment). In service industries, teams often use: People, Process, Technology, Policy, Environment, and Measurement.
When to use which method
🔵 Use 5 Whys when...
The problem has a specific trigger and a fairly linear causal chain. You need a quick answer. You are working alone or with a small team. You already have a hypothesis about the likely cause. Examples: a specific incident, a single process failure, a customer complaint about a particular feature.
🟢 Use Fishbone when...
The problem has many possible causes across different areas. You want the whole team to brainstorm. The root cause is not obvious. You need to see the big picture before drilling into details. Examples: recurring quality defects, systemic performance issues, cross-departmental problems.
🟣 Use both together when...
You need both breadth and depth. Start with a Fishbone to brainstorm all possible causes across categories. Then pick the 2-3 most likely causes from the Fishbone and run a 5 Whys on each one. This is the gold standard for thorough root cause analysis.
The combined workflow
The most effective teams use both methods in sequence. Here is a practical workflow that combines the strengths of each:
- Define the problem clearly. Write a specific, measurable problem statement. This is the "head" of your fishbone and the starting point for 5 Whys.
- Brainstorm with a Fishbone diagram (30-45 min). Gather 3-8 people. Draw the Fishbone. Fill in potential causes under each category. Do not judge or filter at this stage.
- Vote on the most likely causes (10 min). Each team member gets 3 votes. The top 2-3 causes become candidates for deeper investigation.
- Run a 5 Whys on each candidate (15-20 min each). Take each top candidate from the Fishbone and drill down with 5 Whys to find the systemic root cause.
- Define corrective actions. For each root cause found, assign an owner, deadline, and success metric.
- Verify in 2-4 weeks. Check whether the problem has recurred. If it has, revisit the Fishbone and investigate other branches.
Try both tools — free, no signup
Map all causes with the Fishbone Diagram, then drill down to the root cause with 5 Whys.
Example: Using both methods together
Problem: Customer support satisfaction score dropped from 4.2 to 3.1 out of 5 over the last quarter.
Step 1: Fishbone brainstorm
| Category | Potential causes |
|---|---|
| People | New hires not fully trained; senior agents left; low morale |
| Process | Ticket routing broken; no escalation path; SLA not enforced |
| Technology | CRM migration caused data loss; slow helpdesk tool; broken search |
| Measurement | Survey sent too late; wrong questions; sample bias |
After voting, the team identified "CRM migration caused data loss" and "New hires not fully trained" as top candidates.
Step 2: 5 Whys on top candidate
Investigating: CRM migration caused data loss
- Why did the CRM migration cause data loss? — Customer history from the old system was not fully imported.
- Why was it not imported? — The migration script skipped records with non-standard date formats.
- Why were there non-standard dates? — The old CRM allowed free-text date entry with no validation.
- Why was the script not tested against real data? — Testing used a sanitized sample dataset, not a production copy.
- Root cause: The migration testing plan did not include a validation step comparing record counts between old and new systems.
Corrective action: Run a record count comparison now to identify missing records. Update the migration playbook to require a pre/post record count check for all future migrations.
Common mistakes when choosing a method
- Using 5 Whys for complex multi-cause problems. If your 5 Whys keeps branching into multiple answers at each level, you need a Fishbone first.
- Using Fishbone without follow-up. A Fishbone lists possibilities but does not confirm root causes. Without drilling deeper (with 5 Whys or data analysis), you end up with a long list of guesses.
- Skipping the problem statement. Both methods fail if the starting problem is vague. Always start with a specific, measurable symptom.
- Stopping at "people" causes. Both methods should lead to process or system fixes. If your root cause is a person's name, reframe it as a process question.
Frequently asked questions
What is the difference between 5 Whys and Fishbone diagram?
The 5 Whys follows a single causal chain in depth, asking "why?" repeatedly until you reach one root cause. A Fishbone diagram maps many potential causes across categories simultaneously. The 5 Whys goes deep; the Fishbone goes wide. They serve different purposes and work best together.
Can I use 5 Whys and Fishbone together?
Yes, and this is the recommended approach for thorough analysis. Use the Fishbone first to brainstorm all possible causes. Then pick the most likely candidates and run a 5 Whys analysis on each to find the true root cause. This gives you both breadth and depth.
When should I use 5 Whys instead of Fishbone?
Use 5 Whys when the problem has a clear trigger, the causal chain is fairly linear, you need results quickly (15-30 min), or you have a small team. Use Fishbone when causes are unclear, you want team brainstorming, or the problem spans multiple areas.
Which method is better for incident postmortems?
For most incident postmortems, 5 Whys is preferred because incidents typically have a specific trigger and a linear chain. For recurring incidents with multiple contributing factors, combine both: Fishbone to map all contributors, then 5 Whys on each major branch.
What are the 6 categories in a Fishbone diagram?
The classic 6 M's from manufacturing: Man (People), Machine (Equipment), Method (Process), Material, Measurement, and Mother Nature (Environment). In service industries, common categories are: People, Process, Technology, Policy, Environment, and Measurement. Choose categories that fit your context.
📚 Recommended Reading
- The Lean Six Sigma Pocket Toolbook — George et al. — Covers both 5 Whys and Fishbone in one reference
- Thinking in Systems — Donella H. Meadows — For complex problems that need a systems perspective
Related resources
- Free Fishbone Diagram Maker — build Ishikawa diagrams with 6M, 6P, or custom categories
- Free 5 Whys Online Tool — interactive, guided analysis with PNG export
- Fishbone Diagram Examples: 7 Real Case Studies
- How to Create a Fishbone Diagram: Step-by-Step
- 5 Whys Examples: 10 Real-World Case Studies
- 7 Common 5 Whys Mistakes (And How to Avoid Them)