Fishbone diagram: how it gets used on the floor, not in the classroom
It exists to organize hypotheses before you spend money testing them. It does not exist to guess elegantly.
A fishbone diagram, also called an Ishikawa or cause and effect diagram, is a tool that sorts every possible cause of a problem into categories so a team can review them in order instead of jumping to the first explanation. Kaoru Ishikawa created it, and it is used as the step before root cause analysis.
The 6Ms, which is how manufacturing uses it
- Method
- how the operation is defined: instruction, sequence, parameters.
- Machine
- equipment, tooling, maintenance, condition at the moment of the defect.
- Material
- input, lot, supplier, storage, shelf life.
- Manpower
- training, certification, shift, turnover.
- Measurement
- instrument, calibration, acceptance criteria, who measures.
- Mother nature
- temperature, humidity, cleanliness, noise, lighting.
- 01 Define the effect with a number Not "welding defects". Instead: "12% rejection for cold welds on line 3, second shift, since May 14". An effect without a date and a figure cannot be closed.
- 02 Fill it in with the team, not just with engineering The operator at that station sees things the report never captures. If they are not in the room, half the causes never get written down.
- 03 Mark which entries are hypotheses and which are facts This is the step almost everyone skips. A cause that is written down is not a cause that is proven.
- 04 Prioritize by available evidence, not by intuition Attack first the branches where data already exists to confirm or kill them fast.
- 05 Move to the 5 whys only on the branch that survives The fishbone opens the fan. The 5 whys close it. Doing it backwards is what produces twelve point action plans that fix nothing.
- Filling it in between two people in an office and calling it team analysis.
- Writing causes so general they cannot be tested: "lack of training", "operator carelessness".
- Treating the diagram as the conclusion. A fishbone does not give you root cause, it organizes the candidates.
- Filing it away. If the diagram does not end in a plan with an owner and a date, it was an expensive meeting.
In the workshop we run it on a real problem from your plant with your own data. By the end of the session every branch is marked as proven, ruled out, or waiting on data, and that last column becomes next week’s measurement list.
This lives inside Problem solving and continuous improvement
What is the difference between a fishbone diagram and the 5 whys?
The fishbone opens up: it gathers every possible cause and sorts it by category. The 5 whys close in: they take one cause and drive down to its origin. Use them in that order, open first and close after.
How many causes should a good diagram have?
There is no number. There is a test: if no branch surprised you, the team was incomplete or nobody felt free to speak.
Can it be used outside manufacturing?
Yes. The 6Ms are the plant version. Service operations often use 4Ps or their own categories, and it works the same as long as the effect is defined with a number.
What is holding your operation back today?
Tell me the concrete problem. I will tell you whether it is mine to solve or someone else’s, and what I would do first.