When a problem keeps coming back, the usual reaction is to fix the first cause someone mentions in a meeting. A few weeks later, the problem is back. The fishbone diagram exists to stop that cycle. It forces a team to lay out every possible cause in an organised way before deciding what to fix.
This guide explains what a fishbone diagram is, how to build one step by step, which categories to use for different industries, and how to move from a diagram full of ideas to a root cause you can prove with data.
Quick Answer
A fishbone diagram, also called an Ishikawa or cause-and-effect diagram, is a root cause analysis tool used in the Analyze phase of Six Sigma. The problem is written at the "head", and possible causes are grouped along "bones" under categories such as People, Methods, Machines, Materials, Measurement and Environment. Teams then dig deeper with "why" questions and verify the most likely causes with data before fixing them.
In this guide
- What a fishbone diagram is
- When to use it in DMAIC
- Which categories to use (6M, 4P, 4S)
- How to make a fishbone diagram in 7 steps
- Worked example: rising rejection on a machining line
- Examples from IT, healthcare and banking
- Common mistakes
- Fishbone vs 5 Whys vs Pareto
- FAQs
What Is a Fishbone Diagram?
A fishbone diagram is a visual map of all the possible causes of one specific problem. It gets its name from its shape: the problem sits at the head of the fish, a horizontal line forms the spine, and the main cause categories branch off as bones. Smaller sub-causes branch off each bone.
The tool was popularised by Japanese quality expert Kaoru Ishikawa, which is why it is also called an Ishikawa diagram. You will also see it called a cause-and-effect diagram. All three names mean the same tool.
Its value is not the drawing. It is what the drawing makes a team do:
- Look beyond the obvious cause
- Consider every area, not just the one closest to the person speaking
- Separate symptoms from causes
- Agree on which causes to test with data
When to Use a Fishbone Diagram in Six Sigma
The fishbone diagram belongs in the Analyze phase of DMAIC. By then, you have defined the problem and measured how big it is. Now you need to know why it happens.
Use it when:
- The cause is not obvious, or people disagree about it
- Several departments or factors could be involved
- Earlier fixes have not worked
- You need a structured way to run a team brainstorming session
Skip it when the cause is already proven, or the problem is so simple that one round of asking "why" settles it. The fishbone is one of several Analyze-phase tools; see the top tools used in the Analyze phase for the others.
Which Categories Should You Use?
Categories are the main bones of the fish. Using a standard set makes sure you do not forget whole areas. Pick the set that suits your industry, and rename or add categories if your process needs it.
| Set | Categories | Best for |
|---|---|---|
| 6M | Man (People), Machine, Method, Material, Measurement, Mother Nature (Environment) | Manufacturing, production, labs |
| 4P | Policies, Procedures, People, Plant (facilities and equipment) | Administrative and service processes |
| 4S | Surroundings, Suppliers, Systems, Skills | Service industries such as BPO, retail and hospitality |
| Custom | For example: People, Process, Technology, Data, Vendors, Customers | IT services and software support |
How to Make a Fishbone Diagram: 7 Steps
Step 1: Write a specific problem statement
The head of the fish needs a problem, not a topic. "Quality issues" is a topic. "Rejection rate on Line 2 rose from 2% to 6% between July and September" is a problem. Include what, where, when and how much. Use the data you collected in the Measure phase.
Step 2: Draw the spine and choose categories
Draw a horizontal arrow pointing to the problem. Add one bone for each category from the table above. A whiteboard, flip chart or simple Excel sheet is enough.
Step 3: Bring the right people
Invite the people who actually do the work, not only managers. Operators, agents, nurses or developers usually know causes that never appear in reports. Five to eight people is a good size.
Step 4: Brainstorm causes under each category
Go one category at a time. Ask, "What in this area could cause the problem?" Write every idea on the bone. Do not debate or judge ideas at this stage. Sticky notes work well because they let people add ideas quietly.
Step 5: Dig deeper with "why"
For each cause, ask why it happens and add the answers as smaller branches. Stop when you reach something the team can act on. This is where the fishbone and the 5 Whys technique work together.
Step 6: Shortlist the likely root causes
Ask the team to vote, or circle the three to five causes that appear most often or seem most likely to explain the size of the problem. These are still hypotheses, not facts.
Step 7: Verify with data before fixing anything
This is the step most teams skip, and it is the one that makes the difference. Collect data to confirm or reject each shortlisted cause. A Pareto chart shows which causes account for most defects; stratifying data by shift, machine or supplier shows where the problem is concentrated. Only then move to the Improve phase.
Worked Example: Rising Rejection on a Machining Line
This is an illustrative example to show the method. An auto component plant sees the rejection rate for machined shafts on Line 2 rise from 2% to 6% over one quarter, mostly for diameter out of tolerance. The team uses a 6M fishbone.
What the team did next: They had twelve possible causes. Voting shortlisted four: new night-shift operators, a new bar-stock supplier, spindle bearing wear, and an uncalibrated gauge. Then they tested each one:
| Shortlisted cause | How it was tested | Result |
|---|---|---|
| Night-shift operators | Compared rejection by shift | Similar on all shifts, so rejected |
| New supplier | Compared rejection by material batch | No clear difference, so rejected |
| Spindle bearing wear | Vibration check and rejection trend since last service | Rejection climbed steadily after service was overdue, so confirmed |
| Uncalibrated gauge | Gauge study with three inspectors | Measurement error too large, so confirmed |
Without the data step, the team would probably have retrained the night shift and changed supplier, spending time and money on two causes that were not driving the problem. Instead they replaced the bearing, added it to the preventive maintenance plan, recalibrated the gauge, and put a control chart on shaft diameter to catch any drift early.
The gauge finding is a reminder to check your measurement system before trusting any data. Our guide to measurement system analysis (MSA) explains how.
Fishbone Diagram Examples Outside Manufacturing
IT service desk: too many repeat tickets
- People: new agents close tickets before the user confirms the fix
- Process: no knowledge article for common issues; tickets closed to meet the SLA timer
- Technology: monitoring tool raises duplicate alerts
- Data: ticket categories too broad to spot patterns
Hospital: patient discharge takes too long
- People: discharge summary waits for the consultant's evening round
- Procedures: insurance approval requested only after the discharge decision
- Plant: pharmacy is far from the ward
- Policies: final bill needs sign-off from two departments
More healthcare cases are covered in Lean Six Sigma in healthcare.
Bank: loan processing errors
- Skills: staff unfamiliar with the new document checklist
- Systems: manual re-entry between two software systems
- Suppliers: property valuation reports arrive in different formats
- Surroundings: month-end volume spikes
For more complete project stories, see our Six Sigma project examples and case studies.
Common Fishbone Diagram Mistakes
- A vague problem statement. "Poor quality" leads to a vague diagram. Be specific and use numbers.
- Writing solutions instead of causes. "Need more training" is a solution. "Operators unsure of setup steps" is a cause.
- Blaming people. "Careless operator" stops the analysis. Ask why the process allows the mistake.
- Stopping at the first level. Keep asking why until you reach something actionable.
- Treating votes as proof. The diagram produces hypotheses. Data confirms them.
- Mixing up root and contributing causes. Our post on root cause vs contributing cause explains the difference.
Fishbone vs 5 Whys vs Pareto Chart
These three tools are often used together. Each one answers a different question.
| Tool | Question it answers | Best used when |
|---|---|---|
| Fishbone diagram | What are all the possible causes? | Many factors could be involved and you need breadth |
| 5 Whys | Why does this one cause happen? | You need depth on a single cause |
| Pareto chart | Which causes matter most? | You have data and need to prioritise |
A practical sequence: build the fishbone to see the full picture, use 5 Whys on the shortlisted causes, then use Pareto and other data to confirm which ones to fix. For complex or high-risk problems, see advanced root cause analysis techniques and FMEA.
Tools for Drawing a Fishbone Diagram
You do not need special software. A whiteboard and sticky notes work best for live team sessions. For digital versions, Excel and PowerPoint shapes, Minitab's cause-and-effect diagram, and online whiteboards such as Miro or Lucidchart all work well. Choose whatever your team can edit together easily.
Learn root cause analysis on real projects
Our Lean Six Sigma Green Belt programme covers the fishbone diagram, 5 Whys, Pareto analysis and hypothesis testing, with project guidance from experienced trainers.
New to Six Sigma? Start with the Yellow Belt course, or read our Green Belt certification guide for India.
Frequently Asked Questions
Why is it called a fishbone diagram?
Because of its shape. The problem sits at the head, a horizontal line forms the spine, and cause categories branch off like the bones of a fish.
Is a fishbone diagram the same as an Ishikawa diagram?
Yes. Fishbone diagram, Ishikawa diagram and cause-and-effect diagram are three names for the same tool. The Ishikawa name comes from Kaoru Ishikawa, who popularised it.
What are the 6Ms of a fishbone diagram?
The 6Ms are Man (People), Machine, Method, Material, Measurement and Mother Nature (Environment). They are the standard categories used for manufacturing problems.
In which DMAIC phase is the fishbone diagram used?
Mainly in the Analyze phase, to list and organise possible root causes. Teams sometimes use it briefly in the Define phase to understand the scope of a problem.
Can a fishbone diagram be used outside manufacturing?
Yes. IT services, banks, hospitals, BPOs and government offices use it widely. They usually swap the 6Ms for categories like Policies, Procedures, People and Systems.
Does a fishbone diagram find the root cause on its own?
No. It lists and organises possible causes. You still need data, such as a Pareto chart or a comparison by shift or batch, to confirm which causes are real before you fix them.
Leave a Comment