Fishbone diagram
Definition
A cause-and-effect diagram shaped like a fish skeleton: the problem or effect sits at the head, and branches extending from the spine represent categories of possible causes — typically People, Process, Equipment, Environment, Materials, and Management.
The fishbone diagram — also called the Ishikawa diagram after its creator Kaoru Ishikawa, or a cause-and-effect diagram — is one of the seven basic quality tools. It was developed in the 1960s for manufacturing process analysis and has since spread to software engineering, healthcare, and business operations.
Structure: Draw a horizontal arrow pointing right — that's the spine. The problem statement goes at the arrowhead (the fish's head). Draw angled branches off the spine — typically four to six. Label each branch with a cause category. Then add sub-branches for specific causes within each category.
Classic cause categories (the 6Ms for manufacturing):
- Man / People
- Machine / Equipment
- Method / Process
- Material
- Measurement
- Mother Nature / Environment
Software engineering variant (4Ps or similar):
- People
- Process
- Product (technology/tools)
- Policy
When to use it: When the Five Whys is producing a single linear chain but you suspect multiple contributing causes across different domains. The fishbone makes multi-factor analysis visible simultaneously.
On a whiteboard: This is a native whiteboard format — it's hard to draw well in a spreadsheet but natural on a large wall. Teams often add sticky notes to the branches rather than writing directly, so causes can be moved and regrouped. Snap the completed diagram with BoardSnap to get a structured cause map before the meeting ends.
Examples
- A software team draws a fishbone diagram after a production incident, identifying contributing causes across People (missing runbook), Process (no mandatory review), and Technology (no circuit breaker).
- A product manager uses a fishbone diagram in a strategy session to map why customer retention is below target.
- A quality engineer draws a fishbone on a large whiteboard in a factory floor meeting, then uses sticky notes so causes can be rearranged as the discussion evolves.
- A consultant facilitates a fishbone session with a client using a whiteboard, then snaps it with BoardSnap to include in the debrief deck.
Snap a fishbone diagram. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.