Every team has faced a problem that keeps coming back no matter how many quick fixes get tried. A fishbone diagram, also called a cause-and-effect or Ishikawa diagram, gives the team a way to slow down and look at the whole picture before anyone reaches for a solution.
Key Concept
A fishbone diagram places one clearly defined problem in the "head" of the fish and arranges possible causes along branches leading toward it. Its strength is breadth: it keeps a team from locking onto the first explanation someone happens to say out loud.
Practical Example
A neighborhood bakery notices that about one batch in five comes out with a pale, soft crust. Instead of arguing about whose fault it is, the team draws a fish. Under Machine they write "oven runs cool in the morning," under Material "new flour supplier," under Method "proofing shortened on busy days," under People "newer staff trained by video only," and under Environment "kitchen humidity rises in the afternoon."
Standard Procedure
- 1Write the problem as a specific, measurable statement in the head box on the right.
- 2Draw a long horizontal spine pointing to the head.
- 3Add the main category branches (the "bones") angled off the spine.
- 4Brainstorm with the team and attach each cause to the branch where it fits best.
- 5Ask "why" about each cause and add deeper sub-causes underneath.
- 6Mark the most likely causes so they can be checked with evidence.
Lesson Summary
- ✓The head holds the effect; the bones hold possible causes.
- ✓A good problem statement says what happened, how much, and where or when.
- ✓The diagram widens the team's thinking before it narrows it.