What is a fishbone diagram?
A fishbone diagram — also called a cause-and-effect diagram or Ishikawa diagram — is a structured visualisation tool for identifying the root causes of a problem or defect. The diagram is shaped like a fish skeleton: the problem or effect is written at the "head" (the right end of the main horizontal arrow), and the major cause categories branch off the spine as diagonal ribs. Specific causes within each category appear as sub-branches off the ribs.
The diagram was developed by quality management pioneer Kaoru Ishikawa at Kawasaki in the 1960s and is now a cornerstone of lean manufacturing, Six Sigma, quality control, and structured problem solving across industries from healthcare to software engineering. The visual structure forces teams to think systematically about all possible cause categories rather than jumping to the most obvious explanation.
The 6Ms framework for fishbone analysis
| Category (M) | What it covers | Example causes |
|---|---|---|
| Machine | Equipment, tools, technology, software | Equipment calibration drift, software version mismatch, tool wear |
| Method | Processes, procedures, workflows, standards | Undefined approval steps, inconsistent testing procedure, missing checklist |
| Material | Raw materials, components, consumables, data inputs | Supplier quality variation, out-of-spec raw material, corrupted data feed |
| Man (People) | Human factors: skills, training, fatigue, communication | Insufficient onboarding, shift handover miscommunication, operator error under pressure |
| Measurement | How outcomes are measured, data accuracy, instrument calibration | Sensor miscalibration, wrong KPI definition, sampling bias in reporting |
| Milieu / Environment | Physical or digital environment, external conditions | Temperature variation on the production floor, network latency spikes, regulatory change |
In service and software contexts, the 6Ms are often adapted. Common alternatives include Management (decision-making, prioritisation), Money (budget constraints, cost pressures), and Market (customer behaviour, competitive pressure). Use the 6Ms as a starting framework and replace categories that don't fit your context.
How to run a fishbone analysis session
- Define the problem precisely. Write it at the head of the diagram as a specific, measurable statement. "Product defect rate increased 15% in Q3" is better than "quality problem".
- Select your cause categories. Start with the 6Ms or an adapted set. Write each category on a rib branching off the spine.
- Brainstorm causes in each category. For each rib, ask "what in this category could have caused the problem?" Add each cause as a sub-branch. If a cause has a sub-cause, add it as a branch of the branch.
- Look for causes that appear in multiple categories. Causes that show up under more than one category are strong root cause candidates — they are systemic, not isolated.
- Validate with data. The diagram identifies candidate root causes; data confirms which are real. Follow up each high-priority cause with measurement or investigation before acting.
- Prioritise and assign corrective actions. Select the two or three root causes most supported by data and assign owners and timelines for corrective action.
Example prompt for fishbone diagram generation
Fishbone diagram. Problem at the head: "Customer complaints about late deliveries increased 40% in Q4". 6Ms cause categories. Machine: warehouse management system outage (3 days in November), barcode scanner failures in picking zone. Method: no escalation path for delayed orders, manual re-routing process for carrier exceptions. Material: supplier delays on SKUs 1120 and 1345, packaging stockout causing repack delays. Man: 20% temporary staff with incomplete training, shift supervisor vacancy not filled. Measurement: on-time delivery metric calculated at dispatch, not actual delivery — masking true performance. Environment: record rainfall disrupted last-mile carrier in two regions.
Fishbone diagram vs mind map: which to use
A fishbone diagram is structured and problem-focused. It has a fixed shape, a defined starting point (the problem), and standard cause categories. It is designed to work backward from an effect to its causes. Use it when you are investigating a specific problem and want a systematic, auditable analysis.
A mind map is freeform and topic-focused. It starts from a central concept and expands outward in any direction, with branches representing subtopics, associations, or ideas. Use it for brainstorming, note-taking, and knowledge organisation. If you are investigating a problem, use a fishbone diagram. If you are exploring a topic, use a mind map.
Fishbone diagram best practices
- Write the problem at the head as a specific, measurable statement — not a vague description. Precision at the head forces precision in the branches.
- Use a team to generate causes, not one person. The diagram's value comes from diverse perspectives surfacing causes that any single analyst would miss.
- Add sub-branches when a cause has its own cause. Asking "why does this cause exist?" one more level down often reveals the true root cause beneath the surface symptom.
- Look for causes that appear under multiple categories — they are systemic and usually the highest-priority targets for corrective action.
- Don't skip the data validation step. A fishbone diagram is a hypothesis generator, not a conclusion. Validate candidate causes with measurement before assigning corrective actions.
- Export to PDF for quality management documentation — it is print-ready and audit-suitable, with all cause labels clearly readable at any zoom level.
Frequently asked questions
- What is a fishbone diagram?
- A fishbone diagram — also called a cause-and-effect diagram or Ishikawa diagram — is a structured tool for identifying the root causes of a problem. The problem is written at the "head" of the fish shape, and major cause categories branch off the spine as ribs. Specific causes appear as sub-branches. Developed by Kaoru Ishikawa in the 1960s, it is widely used in lean manufacturing, Six Sigma, healthcare quality, and IT incident analysis.
- What are the 6Ms categories in a fishbone diagram?
- The 6Ms are the standard cause categories in manufacturing fishbone diagrams: Machine (equipment and tools), Method (processes and procedures), Material (raw materials and inputs), Man (people, skills, training), Measurement (how outcomes are measured and calibrated), and Milieu/Mother Nature (environmental conditions). In service or software contexts these are often adapted — common replacements include Management, Money, and Market.
- When should I use a fishbone diagram?
- Use a fishbone diagram when investigating the root causes of a recurring problem, quality defect, process failure, or unexpected outcome — especially when multiple possible causes are hard to untangle or when a team needs to brainstorm causes in a structured way. They are valuable in manufacturing quality control, IT post-mortems, customer complaint analysis, healthcare adverse event reviews, and product defect investigations.
- How is a fishbone diagram different from a mind map?
- A fishbone diagram is structured and problem-focused: fixed fish-skeleton shape, defined starting point (the problem at the head), and standard cause categories. It is designed for root cause analysis — working backward from an effect. A mind map is freeform and topic-focused: it starts from a central concept and expands in any direction. Use a fishbone diagram to investigate a problem; use a mind map to explore a topic or brainstorm ideas.
- What industries use fishbone diagrams?
- Fishbone diagrams are used in manufacturing (lean and Six Sigma quality control), healthcare (patient safety incident analysis using the 4Ps: Place, Procedure, People, Policies), software engineering (post-incident retrospectives), food and beverage (quality and contamination investigations), financial services (operational error and fraud root cause analysis), and construction (defect investigation and delay analysis).
- Can I export my fishbone diagram?
- Yes. flow-chart.io exports fishbone diagrams as SVG (scalable vector, for Confluence, Notion, or quality management docs), PNG at 2× and 4× resolution (for slides and reports), PDF (print-ready for audit files and improvement reviews), and JSON (re-importable scene graph for future editing). All exports come from the editable scene graph — not screen captures — so they stay sharp at any size.