A warehouse manager reads the weekly report and sees that too many outbound orders left the dock after the promised time. Everyone has a theory: the drivers, the pickers, the software, the weather. A fishbone diagram stops the theories turning into an argument, because it makes the team write every theory on one page, sort it by category, and then go and test the likely ones. Here is how to run one properly, from the blank board to the follow-up.

The diagram goes by three names: fishbone, Ishikawa and cause-and-effect diagram. All three are the same picture, a spine that ends in the problem with branches of possible causes leading into it. Kaoru Ishikawa, a Japanese quality-control specialist, popularised it in the 1960s, and the Wikipedia entry on the Ishikawa diagram gives the history. Below you will find the steps, the two category sets people use, one worked example you can copy, how to pair it with 5 Whys and a Pareto chart, and the ways teams misuse it.
Is a fishbone diagram a Six Sigma tool, and what is it for?
Yes, it is one of the standard quality tools used in Six Sigma projects, though it is older than Six Sigma and is used in healthcare, software, logistics and manufacturing alike. Its job is narrow and useful: it organises a brainstorm about why a problem happens, so that a group does not fixate on the first cause somebody names.