Fishbone Diagram
A fishbone diagram organizes possible causes of a problem into categories. It helps a team generate and compare hypotheses, which must then be checked against evidence.
THE IDEA
The Fishbone Diagram and Eight Ways of Understanding Why
'All the classifications man has ever devised are arbitrary, artificial, and false, but … reflection also shows that such classifications are useful, indispensable, and above all unavoidable since they accord with an innate aspect of our thinking'.
– Egon Friedell
A fishbone diagram, also called an Ishikawa or cause-and-effect diagram, places a problem at the head of a central spine and groups possible causes along branches. The supplied account calls its category set the 5 Ms but lists six: Man, Machine, Method, Material, Measurement, and Milieu. Categories can be adapted to the problem.
Use the diagram to generate hypotheses, then examine records, observations, or tests to determine which factors contributed. A populated diagram is not proof of a cause. The heading also mentions eight ways of understanding why, but those ways are not supplied here.
When to use it
Quality control teams investigating product defects in a factory.
Project managers diagnosing delays or budget overruns in a project.
Healthcare professionals analyzing patient safety incidents or clinical errors.
Service teams uncovering reasons for low customer satisfaction scores.
FROM THEORY TO EVERYDAY LIFE
In practice
Production Delay in a Manufacturing Plant
A team investigating production delays lists operator training, equipment condition, workflow, material shortages, and lighting on a fishbone diagram. Preventive maintenance emerges as a hypothesis. The team checks maintenance and downtime records before deciding whether it explains the delays.
High Customer Complaints in a Call Center
A service team maps out all potential reasons for high complaint rates: agent knowledge gaps, long hold times, unclear scripts, system errors, and lack of escalation paths. The visual layout helps prioritize training and process improvements.
A MOMENT TO REFLECT
Put it to work.
Think of a problem you recently encountered. Could you use a fishbone diagram to systematically explore its causes? What categories would you include?
When using the fishbone diagram, how do you ensure you are not missing important categories or jumping to conclusions too quickly?
What evidence would you seek to distinguish a plausible cause on the diagram from a factor that actually contributed to the problem?
CONTINUE THE CONVERSATION
Source texts
- Beyond the Five Whys Root Cause Analysis and Systems Thinking (James C. Paterson)