Fishbone Diagram (Ishikawa)

A fishbone diagram (also called an Ishikawa diagram, after Kaoru Ishikawa who popularized it at Kawasaki in the 1960s, or a cause-and-effect diagram) is a visual tool that organizes possible causes of a problem into categories radiating from a central spine. The shape resembles a fish skeleton — problem statement at the head, categories as the major bones, sub-causes as the smaller bones. It's a foundational Lean Six Sigma tool used in the Analyze phase of DMAIC.

Use a fishbone when the problem likely has multiple categories of causes acting together — most quality, throughput, and customer-experience issues. Use 5 Whys when you're chasing a single causal chain to its root. In practice, they're complementary: the fishbone enumerates branches, and 5 Whys is the technique applied to each branch to push past surface explanations.

A fishbone enumerates possible causes; a Pareto chart ranks them by frequency or impact. They work in sequence: fishbone identifies candidates, Pareto narrows the field to the vital few. Most experienced black belts use both — fishbone in the Analyze phase to map the problem space, Pareto to decide which sub-cause gets the improvement budget.

Yes — that's why the 8P (services) and 4S (administrative) frameworks exist alongside the manufacturing 6M. The same diagnostic logic works for software incidents, marketing campaign underperformance, claims processing errors, loan operations delays, and patient flow problems. The frameworks change; the technique doesn't.

AI agents shift the fishbone from a brainstorm-driven artifact to an evidence-driven one. Instead of starting with categories and asking 'what could cause this,' agents query the event log for steps with anomalous timing, rework loops, and correlation with the defect. The resulting fishbone starts with statistically-supported candidates ranked by observed impact, and stays current as new data arrives. Humans still validate causes and design interventions — agents do the data work.