Ishikawa diagram
Definition
The formal name for a fishbone or cause-and-effect diagram, developed by quality management pioneer Kaoru Ishikawa in the 1960s to systematically identify and display the potential causes of a problem or quality defect.
Kaoru Ishikawa developed the diagram while working at the Kawasaki shipyards in the early 1960s as part of his broader work on total quality management. The diagram was first presented as part of the Japanese quality movement and became one of the seven basic quality control tools alongside control charts, Pareto charts, scatter plots, histograms, check sheets, and stratification.
Why it bears his name: Ishikawa was instrumental in adapting Western quality concepts (W. Edwards Deming, Joseph Juran) to Japanese manufacturing contexts and then developing original frameworks. The diagram is the most visually distinctive of his contributions — its fishbone shape makes it immediately recognizable.
Ishikawa diagram vs. fishbone diagram vs. cause-and-effect diagram: These three terms refer to the same tool. 'Fishbone diagram' is the most common colloquial usage; 'Ishikawa diagram' is preferred in formal quality management and academic contexts; 'cause-and-effect diagram' is the generic descriptor.
Applications beyond manufacturing: Originally developed for production quality analysis, Ishikawa diagrams are now used in healthcare (Joint Commission requirements), software engineering (post-mortems, RCA), project management, and business strategy. The categories shift based on domain — the 6Ms for manufacturing become 4Ps or custom categories in knowledge work.
The Ishikawa diagram is a whiteboard-native format. Snap it with BoardSnap to extract the cause branches and their sub-items as a structured summary.
Examples
- Toyota's early adoption of the Ishikawa diagram as a standard quality tool helped establish it as a global standard in the automotive industry.
- A hospital quality team uses the Ishikawa diagram to analyze a medication error, mapping causes across Staff, Supplies, Systems, Surroundings, and Procedures.
- A software architect draws an Ishikawa diagram on a whiteboard during an architecture review to map potential causes of a performance bottleneck.
- A business school professor uses the Ishikawa diagram in a case study class to teach students to distinguish root causes from symptoms.
Related terms
Snap a ishikawa diagram. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.