A fishbone diagram — also called an Ishikawa diagram or cause-and-effect diagram — is one of the seven basic quality tools. It helps teams visually map all potential causes of a problem before jumping to conclusions. If the 5 Whys drills deep along one causal chain, the fishbone diagram goes wide, capturing every factor that could contribute to an effect.
This guide covers everything you need to run effective fishbone sessions: the theory behind the tool, which framework to use (6M, 6P, or custom), a worked example from manufacturing, common mistakes, and how to combine the fishbone with other root cause analysis methods.
What is a fishbone diagram?
A fishbone diagram is a structured brainstorming tool that organizes potential causes of a problem into categories. The diagram looks like a fish skeleton:
- Head (right): The problem or undesirable effect you are investigating.
- Spine: A horizontal line pointing to the head.
- Primary bones: Diagonal lines branching off the spine, each labeled with a category of causes (e.g., Machine, Method, Material).
- Secondary bones: Smaller branches off each primary bone, listing specific causes.
- Tertiary bones: Even smaller branches for sub-causes (optional, but powerful for complex problems).
The visual structure forces teams to consider multiple dimensions of a problem rather than fixating on the first idea that comes to mind. It was designed precisely for this purpose: to prevent premature conclusions.
Brief history: Kaoru Ishikawa and Toyota
The diagram was created by Kaoru Ishikawa, a Japanese professor of engineering at the University of Tokyo, in the early 1960s. Ishikawa was a pioneer of quality management in Japan and one of the key figures behind the Japanese quality revolution after World War II.
Ishikawa developed the diagram as a way to help factory workers — not just engineers — participate in quality improvement. He believed that quality was everyone’s responsibility, and the fishbone diagram gave non-experts a structured way to contribute their knowledge of the process.
Toyota adopted the fishbone as part of the Toyota Production System (TPS), using it alongside the 5 Whys method. Together, these tools form the backbone of lean problem-solving: the fishbone identifies what to investigate, and the 5 Whys reveals why it happens.
Today, the fishbone is a staple in Lean Six Sigma, healthcare patient safety (RCA2), aerospace quality (AS9100), automotive APQP, and agile retrospectives.
When to use a fishbone diagram
A fishbone diagram is most effective when:
- The problem has multiple potential causes and you need to explore all possibilities before narrowing down.
- A cross-functional team is involved — different perspectives reveal different cause categories.
- You want to prevent tunnel vision — the category structure forces you to look beyond the obvious.
- You need documentation — the diagram serves as a visual record of your brainstorming session.
- The causal chain is branching — unlike the 5 Whys (which follows a single path), the fishbone handles multiple branches simultaneously.
When NOT to use a fishbone:
- Simple problems with one obvious cause — just fix it.
- Emergencies requiring immediate action — do the fishbone in the post-incident review.
- Problems that need quantitative prioritization — use a Pareto chart first, then fishbone the top category.
Category frameworks: 6M, 6P, and custom
The categories you choose determine the structure of your diagram. There are three common frameworks:
6M (Manufacturing / Operations)
The original framework designed for factory environments:
| Category | What to investigate |
|---|---|
| Man (People) | Training, skills, fatigue, communication, staffing levels |
| Machine | Equipment condition, calibration, maintenance, capacity, age |
| Method | SOPs, work instructions, process design, sequence of steps |
| Material | Raw materials, components, suppliers, specifications, storage |
| Measurement | Gauges, inspection criteria, data accuracy, sampling methods |
| Mother Nature (Environment) | Temperature, humidity, lighting, contamination, noise |
6P (Service / IT / Healthcare)
Better suited for service processes, software, and knowledge work:
| Category | What to investigate |
|---|---|
| People | Skills, workload, communication, handoffs, decision-making |
| Process | Workflow design, bottlenecks, exceptions, automation gaps |
| Policy | Rules, regulations, compliance requirements, approval chains |
| Place | Physical or digital environment, infrastructure, accessibility |
| Procedure | Step-by-step instructions, documentation, checklists |
| Technology | Software, hardware, integrations, uptime, version control |
Custom categories
For domain-specific problems, create your own 3–8 categories. Examples:
- E-commerce: Website, Fulfillment, Payment, Customer Support, Marketing, Vendor
- Software incidents: Code, Infrastructure, Monitoring, Deployment, Dependencies, Configuration
- Healthcare: Patient, Staff, Equipment, Environment, Communication, Documentation
Not sure which to pick? See our fishbone template guide for a decision flowchart.
How to build a fishbone diagram (6 steps)
This is the condensed version. For a more detailed walkthrough with tips at each stage, see our step-by-step creation guide.
1 Define the problem
Write a clear, measurable problem statement. This becomes the "head" of the fish. Bad example: “Quality is bad.” Good example: “PCB solder defect rate increased from 0.8% to 3.2% over 6 weeks.”
2 Choose your category framework
Pick 6M, 6P, or custom. Draw the spine and label each primary bone with a category name. Use 4–8 categories — fewer is too shallow, more becomes unwieldy.
3 Brainstorm causes
Go category by category. Ask: “What factors under [category] could contribute to this problem?” Write every idea — no filtering yet. Aim for 3–7 causes per category.
4 Add sub-causes
For each cause, ask “Why does this happen?” to identify deeper factors. Branch these off the primary cause bone. This is where the fishbone starts revealing systemic issues.
5 Prioritize and validate
Use dot voting, data analysis, or a Pareto chart to identify the top 2–3 most likely root causes. Circle or highlight them on the diagram.
6 Investigate further
Run a 5 Whys analysis on each top candidate to drill to the true root cause. Then create a corrective action plan with owners and deadlines.
Try it now: Our free fishbone diagram maker guides you through all 6 steps and exports a clean PNG. No signup needed.
Worked example: Assembly line defect rate
Problem: “PCB solder defect rate increased from 0.8% to 3.2% over 6 weeks.”
Using the 6M framework, the team identified:
| Category | Causes identified |
|---|---|
| Man | 2 new operators (< 30 days), night shift fatigue, supervisor vacancy |
| Machine | Wave solder nozzle wear (last replaced 14 months ago), conveyor speed drift |
| Method | SOP not updated after product revision B, no pre-solder inspection step |
| Material | New solder paste supplier (switched 5 weeks ago), PCB moisture absorption |
| Measurement | AOI threshold set for old paste, sampling plan covers only 10% of boards |
| Mother Nature | Humidity spike (72% vs. spec max 60%) due to broken HVAC unit |
Top 3 candidates (by dot voting + data):
- New solder paste supplier — defect spike correlates with supplier change date.
- Wave solder nozzle wear — 14 months without replacement (PM spec: 6 months).
- Humidity spike — 72% humidity directly affects solder joint quality.
The team ran 5 Whys on each candidate and found that the nozzle wear + humidity combination accounted for 78% of the defect increase. The supplier change contributed the remaining 22%.
For more real-world examples across 7 industries, see our fishbone diagram examples collection.
7 common fishbone mistakes
- Vague problem statement. “Things are going wrong” gives the team nothing to anchor on. Be specific: what, where, when, how much.
- Skipping categories. If a category seems “not relevant,” investigate anyway. The most surprising root causes often come from unexpected categories.
- Listing solutions instead of causes. “Need better training” is a solution. “Operators not trained on revision B procedure” is a cause. Keep brainstorming focused on causes.
- Blaming people. “John is careless” ends the analysis. Instead: “Process lacks error-proofing for manual assembly step.” Always target the system, not individuals.
- Not going deep enough. A fishbone with only primary bones is a shallow brainstorm. Add sub-causes and sub-sub-causes to reveal systemic issues.
- No prioritization. A fishbone with 40 causes and no highlighting is a wall of text. Vote on the top 3 before leaving the room.
- Stopping at the diagram. The fishbone is a brainstorming tool, not a conclusion. You still need to validate candidates with data and drill deeper with 5 Whys.
Combining fishbone with 5 Whys and Pareto
The most effective RCA workflow uses three tools together:
1 Pareto chart — Prioritize where to focus
If you have data on defect types, failure modes, or complaint categories, build a Pareto chart first. The 80/20 rule identifies which categories deserve your fishbone session.
2 Fishbone diagram — Map all potential causes
Use the fishbone tool to brainstorm causes within the top Pareto category. This gives you width — a complete map of everything that could be contributing.
3 5 Whys — Drill to root cause
Take the top 2–3 fishbone candidates and run a 5 Whys analysis on each. This gives you depth — the systemic root cause that, if eliminated, prevents recurrence.
This Pareto → Fishbone → 5 Whys pipeline is the gold standard for structured root cause analysis. For a deeper comparison of when to use each tool, see our articles on 5 Whys vs. Fishbone and 5 Whys vs. Pareto.
Fishbone diagram tools and software
You can build a fishbone diagram on a whiteboard, in a spreadsheet, or with dedicated software. Here are the common options:
| Tool | Best for | Cost |
|---|---|---|
| 5xWhys Fishbone Maker | Quick online diagrams with PNG export | Free |
| Whiteboard / flip chart | In-person team workshops | Free |
| Excel / Google Sheets | Data-heavy analysis with tables | Free |
| Miro / Mural / FigJam | Remote team collaboration | Freemium |
| Lucidchart / draw.io | Polished diagrams for reports | Freemium |
| Minitab / JMP | Statistical integration (Six Sigma) | Paid |
For most teams, a whiteboard session followed by digital documentation (using our free online tool or a screenshot) is the most effective workflow.
Frequently asked questions
What is the difference between a fishbone diagram and an Ishikawa diagram?
They are the same tool. “Fishbone diagram” refers to the shape (it looks like a fish skeleton). “Ishikawa diagram” honors the creator, Professor Kaoru Ishikawa. “Cause-and-effect diagram” describes its function. All three names are used interchangeably in quality management literature.
How many causes should a fishbone diagram have?
A typical fishbone has 4–8 categories with 3–7 causes each, totaling 15–40 causes. This is enough to be thorough without becoming overwhelming. The key is not the number but the quality — every cause should be specific and testable, not vague or overlapping.
Can I use a fishbone diagram for positive effects (not just problems)?
Yes. Some teams use a “reverse fishbone” to identify factors that contribute to a desired outcome. For example, “What caused our best quarter of customer retention?” This helps you understand and replicate success, not just fix failures.
Should I use 6M or 6P?
Use 6M for manufacturing, production, and physical processes where materials and machines are central. Use 6P for service, IT, healthcare, and knowledge work where policies and technology dominate. If neither fits perfectly, create custom categories that match your domain. See our template guide for a decision flowchart.
How is a fishbone diagram different from a fault tree?
A fishbone organizes causes by category and is used for brainstorming (qualitative). A fault tree uses Boolean logic (AND/OR gates) and is used for quantitative failure probability analysis. Fishbone is faster and more accessible; fault tree is more rigorous for safety-critical systems. See our fishbone vs. fault tree comparison for details.
What do I do if the team disagrees on root causes?
Use structured voting (each person gets 3 dots to place on their top candidates) and follow up with data. If data is not available, run small experiments or observations to test the top hypotheses. The fishbone is a starting point for investigation, not a verdict — disagreement is healthy and means you are considering multiple angles.
How often should a team use fishbone diagrams?
Use a fishbone whenever you face a complex problem with multiple possible causes. Common triggers: recurring quality defects, safety incidents, customer complaint spikes, project delays, or any situation where the root cause is not immediately obvious. Many lean teams run fishbone sessions monthly as part of their continuous improvement cadence.
Does this tool store my data?
No. Our free fishbone diagram maker runs entirely in your browser. No data is sent to any server. You can export your diagram as a PNG image, but the tool itself does not store any information after you close the page.
Build your fishbone diagram now
Our free online fishbone tool guides you through category selection, cause brainstorming, and exports a clean PNG. No signup, works offline.