InsightFab
Knowledge Base/Fishbone Diagram: Making Root Cause Analysis More Than Just a Brainstorming Session
DMAIC7 min read

Fishbone Diagram: Making Root Cause Analysis More Than Just a Brainstorming Session

Everyone knows how to draw a Fishbone Diagram (Ishikawa Diagram), but truly effective root cause analysis requires a methodology. This article teaches you how to systematically find the true root causes using the 6M framework, rather than just listing a series of guesses.

Scenario

At the monthly QC meeting, a product defect issue was discussed for an hour. Everyone proposed over twenty possible causes, but ultimately, no conclusions were reached, and the meeting minutes stated "continue to observe." The same problem reappeared next month.

The problem isn't the fishbone diagram; it's how it's used.

What is a Fishbone Diagram?

A Fishbone Diagram, also known as an Ishikawa Diagram or Cause and Effect Diagram.

Structure:

  • Fish Head (right side): Problem/Effect
  • Fish Bones (main branches): Cause Categories
  • Small Bones: Specific Causes

The 6M Framework

The most commonly used classification method is 6M, which covers all possible sources of causes in manufacturing:

Man

Operator skill, training, fatigue, shift changes

Machine

Equipment precision, wear and tear, calibration, maintenance status

Method

Unclear SOPs, operating sequence, parameter settings

Material

Raw material specifications, supplier batch variations, storage conditions

Measurement

Gage precision, calibration, operator reading differences

Mother Nature / Environment

Temperature, humidity, vibration, dust

5 Keys to Effective Use

1. Define the Problem Specifically

Bad: "Product quality is poor"

Good: "Line A, from March 15-20, had B component weld strength below the lower specification limit, at a proportion of 8.3%."

2. Conduct On-Site Investigation Before the Meeting

First, go to the site to observe the problem, collect preliminary data, and then use the fishbone diagram to organize the information. Do not guess blindly in the meeting room.

3. For Each Cause, Ask "Why"

"Operator skill is insufficient" → Why? → "No standardized training procedures" → Why? → "SOP hasn't been updated in three years"

This is the root cause, not just a surface phenomenon.

4. Use Data for Screening, Not Voting

After brainstorming, do not use "what everyone thinks is most important" to screen causes. Use data: perform correlation analysis, hypothesis testing, Pareto analysis.

5. Select Only 3-5 Key Causes in the End

It's impossible to solve all 30 causes on a fishbone diagram. Use the Pareto principle to identify the Vital Few that have the greatest impact.

Fishbone Diagram vs. 5 Whys

ToolSuitable ScenariosLimitations
Fishbone DiagramComplex causes, multi-directional explorationRequires subsequent data validation
5 WhysClear cause chain, single pathMay stop at surface causes

In practice, combine both: Use Fishbone Diagram to find all possible causes → Use Pareto to screen → Apply 5 Whys to key causes for root tracing.

Golden Quote

"A fishbone diagram is a map, not the answer. After drawing the map, you still need to walk the path to know which way leads to success."

Want to try it yourself?

Every tool mentioned in this article is available on InsightFab — just upload a CSV to analyze.

Go to Tools