What Is Fishbone Diagram?

Definition

A fishbone diagram, also called an Ishikawa or cause and effect diagram, is a visual tool that groups the possible causes of a problem into categories so a team can explore them systematically.

Fishbone Diagram in Simple Terms

The problem is written at the head of the fish. Each bone is a category of possible causes, and the team adds specific causes to each bone during a brainstorm. The diagram was developed by Kaoru Ishikawa and is one of the basic quality tools used in root cause analysis.

The 6M Categories

  • Man (people): training, skill, fatigue.
  • Machine: equipment condition, settings, wear.
  • Method: procedures, work instructions, sequence.
  • Material: raw material, supplier, batch variation.
  • Measurement: gauges, calibration, inspection method.
  • Mother Nature (environment): temperature, humidity, dust.

Teams can use other categories when they fit the problem better.

Example

A moulding plant sees short shots on a housing. The fishbone lists low barrel temperature (machine), a new resin lot with higher moisture (material), skipped dryer checks (method) and a cold, damp night shift (environment). Testing the moisture and dryer causes first confirms that undried resin was the root cause.

Common Mistakes

  • Treating every idea on the diagram as a proven cause. A fishbone lists possible causes; data must confirm them.
  • Writing vague causes such as "poor quality".
  • Stopping at the diagram without following up with 5 Whys or tests.

The fishbone is often used in D4 of an 8D. OperaHive quality inspection software helps teams record nonconformances and follow corrective actions.

FAQ

Frequently Asked Questions

Still unsure? Ask our team.

Why is it called a fishbone diagram?

The finished diagram looks like a fish skeleton, with the problem as the head and the cause categories as the bones.

What are the 6Ms of a fishbone diagram?

Man, Machine, Method, Material, Measurement and Mother Nature (environment).

What is a fishbone diagram?

A fishbone diagram is a cause and effect chart used to brainstorm and group the possible causes of a problem. The problem sits at the head and the causes branch off a central spine in categories.

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, named after Kaoru Ishikawa, who popularised it in Japanese quality control.

How do you make a fishbone diagram?

Write the problem statement at the head, draw the spine, add category branches such as the 6Ms, then brainstorm causes under each branch with the team. Finally, select the most likely causes for data checks.

When should you use a fishbone diagram?

Use it when a problem has many possible causes and the team needs to structure brainstorming, for example during 8D, CAPA or a customer complaint investigation. It is less useful when the cause is already known.

What is the difference between a fishbone diagram and 5 Whys?

A fishbone diagram spreads out to list many possible causes across categories. The 5 Whys drills down one cause chain to its root. Teams often use the fishbone first, then apply 5 Whys to the strongest causes.

What is a fishbone diagram example in manufacturing?

For a problem such as burrs on machined parts, causes might include worn tooling (machine), wrong feed rate (method), soft material batch (material), untrained operator (man), no deburr check (measurement) and coolant temperature (environment).

Does a fishbone diagram find the root cause?

No, it only lists potential causes. Each likely cause must be tested with data, trials or observation to confirm which one is the true root cause.

Is there a fishbone diagram template?

A standard template has a problem box on the right, a horizontal spine and six angled branches labelled with the 6M categories. Many quality and CAPA tools include a digital fishbone so the analysis stays linked to the investigation record.

Put Fishbone Diagram Into Practice

Book a demo and see how OperaHive handles this on your own parts, processes and documents.