What is a fishbone diagram — and how to draw one that finds real causes.
Short answer
A fishbone diagram (also called an Ishikawa diagram or cause-and-effect diagram) is a structured visualization for root cause analysis. The problem is the fish's head on the right; the main bones are categories of potential causes (People, Process, Machine, Material, Measurement, Environment — the 6Ms in manufacturing; or People, Process, Technology, Environment in software). Sub-bones are specific causes within each category. It's drawn on a whiteboard in 20–40 minutes.
The fishbone diagram was developed by Kaoru Ishikawa, a Japanese quality management expert, in the 1960s at Kawasaki shipyards. It's now used across manufacturing, software engineering, healthcare, and service industries for structured cause analysis.
The structure. Draw a horizontal arrow pointing right — the fish's spine. At the arrowhead, write the problem (the effect). Diagonal bones extend from the spine, each representing a category of potential causes. Sub-bones branch off each main bone, representing specific contributing factors within that category.
Standard cause categories.
For manufacturing (the 6Ms): Machine, Method, Material, Man (People), Measurement, Mother Nature (Environment).
For software/services (the 4Ps or 4Ss): People, Process, Technology (Systems), Environment. Some teams add Policy and Procedures as additional bones depending on the domain.
The categories are starting points — use the ones that fit your context. A product team investigating a low retention rate might use: Product design, Onboarding process, Customer support, Marketing message, Technical reliability.
How to run a fishbone session.
- Write the problem clearly at the fish's head. Be specific: "Free-to-paid conversion rate dropped from 12% to 6% in April" is better than "conversion is low."
- Draw the main bones — one per category.
- In silence, each participant writes sticky notes of potential causes and places them on the appropriate bone.
- Cluster and discuss. For each sub-bone, ask: "Is there evidence this contributed to the problem, or is it speculative?"
- For the most likely causes, apply Five Whys to drill deeper.
Fishbone vs. Five Whys. Fishbone is better when you want to ensure comprehensive coverage across cause categories before drilling down. Five Whys is better when you have a hypothesis about the cause and want to trace it to a systemic root quickly. Many post-mortems use fishbone for broad cause identification, then Five Whys on the most significant branches.
Common mistake. Treating the fishbone as the final analysis rather than a starting point. Sub-bones that aren't backed by data are hypotheses — they need to be tested, not accepted as causes.
Draw the fishbone on a whiteboard. Snap it with BoardSnap and the AI reads the spine, bones, and sub-bone content and produces a structured cause-and-effect summary organized by category.
Frequently asked
Who invented the fishbone diagram?
Kaoru Ishikawa, a Japanese organizational theorist and quality management expert, developed the fishbone diagram in 1968 at Kawasaki shipyards. It's also called the Ishikawa diagram in his honor. It became one of the seven basic tools of quality control and was widely adopted in the total quality management (TQM) movement of the 1980s.
When should you use a fishbone diagram instead of Five Whys?
Use a fishbone when you suspect multiple independent cause categories are contributing to a problem and you want structured coverage before drilling. Use Five Whys when you have a specific causal thread to trace to a root. For complex incidents, use both: fishbone to map the landscape, then Five Whys on the top branches.
What's the difference between a fishbone diagram and a mind map?
A fishbone diagram is a cause-analysis tool — it starts from a specific problem and works backward to causes. A mind map is an idea-organization tool — it starts from a central concept and works outward to related ideas. Both are visual and use branching structures, but they serve different purposes: cause analysis vs. idea exploration.
See it work in ten seconds.
BoardSnap is free on the App Store. Snap a board — get a summary and action plan.