Fishbone Diagram

Also known as: Ishikawa Diagram, Cause-and-Effect Diagram

tool · management · organizing-schema

Visual root-cause analysis grouping causes under categories like people, process, materials.

The Fishbone Diagram, developed by Kaoru Ishikawa at Kawasaki Shipyards in the 1960s and named for its visual resemblance to a fish skeleton, is a structured cause-and-effect analysis tool that organizes potential causes of a defined effect (the fish's head) into categorical 'bones' branching off the spine. The classic 6M categories for manufacturing are Man, Machine, Method, Material, Measurement, and Mother Nature (environment), with service-industry adaptations like 4P (Policies, Procedures, People, Plant) and 8P variants. The diagram supports systematic brainstorming by ensuring causes from multiple categories are considered, and is one of the seven basic tools of quality (alongside Pareto charts, control charts, histograms, scatter diagrams, check sheets, and stratification or flow charts). It is typically used in conjunction with Five Whys to drill down from category-level causes to root causes.

Originators

Kaoru Ishikawa high

Year / Decade

1960s development; 1968 (Guide to Quality Control) high

Primary sources

Ishikawa, K. (1968). Guide to Quality Control, Ishikawa, K. (1985). What Is Total Quality Control? The Japanese Way high

Core components

Effect (the problem) at the head
Major cause categories as primary bones
Sub-causes as secondary bones
6M categories (Man, Machine, Method, Material, Measurement, Mother Nature) for manufacturing
4P/8P variants for services
Pairs with Five Whys for drill-down
One of seven basic tools of quality

Primary use case

Root-cause analysis in quality improvement, manufacturing, healthcare incident review, and service operations; structured brainstorming for incident postmortems; teaching tool for systematic causal reasoning; component of A3 problem-solving and DMAIC analyze phase.

Common criticisms

Generates lists of potential causes without prioritizing or testing which are actually contributing
categorical structure can force-fit causes that don't naturally belong
tendency to populate all categories even when some are not relevant
doesn't address interactions between causes
static snapshot rather than dynamic system view
can substitute for empirical investigation
outcome quality depends heavily on team breadth and brainstorming rigor
works better for well-bounded operational problems than for systemic or organizational issues.

Lineage

Siblings: Five Whys, Pareto Analysis