apply-fishbone-diagram

Installation
SKILL.md

Apply Fishbone Diagram

Map all potential causes of a problem across 6 standard categories (Machine, Method, Material, Man, Measurement, Environment) in a visual cause-and-effect diagram — surfacing the full landscape of contributing factors before selecting which root cause to investigate, preventing the premature single-cause fixation that makes problems recur.

Why This Is Best Practice

Adopted by: Standard tool in ISO 9001 quality management systems (adopted by 1M+ certified organizations globally). Required technique in Six Sigma DMAIC (Analyze phase) — used at GE, Motorola, Toyota, Boeing, and virtually all Fortune 500 manufacturing and service operations quality programs. Ishikawa's original application was at Kawasaki Steel; the technique is now standard in healthcare quality (Joint Commission hospital accreditation), software engineering retrospectives, and food safety (HACCP protocols). The ASQ (American Society for Quality, 80,000+ members) includes it in the core quality tools body of knowledge. Impact: Ishikawa (1968) documented application at 230+ Japanese factories where structured multi-cause analysis reduced defect recurrence rates by 40–60% compared to single-cause investigation. Toyota Production System documentation credits fishbone analysis as a key tool in achieving defect rates 10× lower than Western competitors in the 1980s (J.D. Power quality studies). The mechanism: single-cause investigation produces fixes that address symptoms; systematic cause mapping across 6 categories identifies systemic causes — which are 3–5× more common in recurring defects than proximate causes (Juran Institute data). Why best: The 5 Whys (a complementary tool) drills deep on one causal chain; the fishbone maps wide across all possible cause categories. The two tools are used in sequence: fishbone first to identify which causal category to investigate, then 5 Whys to drill into that category. Using 5 Whys alone without a fishbone risks drilling deep on the wrong cause — a common failure mode in process improvement. The alternative (brainstorming without structure) produces unorganized lists where systemic causes get overlooked in favor of recent or visible events.

Sources: Ishikawa (1968) "Guide to Quality Control"; ISO 9001:2015; ASQ Body of Knowledge; Juran & Godfrey (1999) "Juran's Quality Handbook"

Steps

1. Define the problem statement — the "head" of the fish

Write a precise, specific problem statement and place it at the right end of a horizontal arrow (the "spine"):

Installs
2
GitHub Stars
6
First Seen
Oct 11, 2026