Skip to content

Stockertim Dictionary · Project management

Fishbone diagram

Also called Ishikawa diagram, cause-and-effect diagram, fishbone

In short

A cause-and-effect diagram with the problem at the head and possible causes grouped along bones by category, used to explore root causes.

  • Beginner
  • Process
  • Checked

In detail

A fishbone diagram helps a team think broadly about why a problem happens. The problem is written at the head of the fish, and a spine runs back from it. Major bones branch off the spine for categories of cause, often people, methods, equipment, materials, measurement and environment, and smaller bones carry the specific causes the team suggests under each.

The structure prevents a group from fixing on the first explanation offered. By working through every category, the team surfaces causes that might otherwise be missed, such as a measurement problem behind what looked like a training issue. The diagram also makes the discussion visible, so everyone can see and challenge the reasoning.

A fishbone shows possible causes, not proven ones. The next step is to test the most likely ones with data, for example by counting how often each cause appears in a sample of failures. Combined with Pareto analysis, this shows which causes deserve action first.

In practice

Improvement teams draw fishbones on whiteboards in workshops with frontline staff, then test the leading causes with data before choosing actions.

Watch out

  • A full diagram is a list of hypotheses until data confirms them.
  • Generic category headings can force causes into the wrong boxes; adapt them.

Learn it properly

Official sources

Facts last checked on 3 November 2026.

Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.

English