# Fishbone diagram

> A fishbone diagram maps the possible causes of one problem on branches, like fish bones. Teams also call it a cause-and-effect or Ishikawa diagram.

Source: https://incidentkit.ai/glossary/fishbone-diagram · Updated Oct 5, 2026

Also known as: Ishikawa diagram, cause and effect diagram, cause-and-effect diagram

## What it is

IHI defines a cause and effect diagram as a graphic tool to explore and show the possible causes of an effect.

Use the classic fishbone when causes fit groups like materials, methods, equipment, environment and people. Or use a process-type diagram to show causes at each step.

IHI lists three benefits. It shows a team that many causes add up to an effect. It shows how causes relate to the effect and to each other. And it helps find areas to improve.

## How to use it

1. Write the problem at the head, specific and measurable.
2. Draw branches for the groups that fit.
3. Brainstorm causes with the people who do the work.
4. Mark the likeliest causes. Check each against data before you accept it.

Example: late first-case starts at a surgery center. Branches might hold people (arrival times), methods (room turnover steps), equipment (instrument trays not ready) and materials (supply stock-outs).

Mix-up: a fishbone lists possible causes and does not prove them. Combine it with [five whys](https://incidentkit.ai/glossary/five-whys) and check records.

The VA's version works backward with 'caused by' and asks for at least two causes: an action and a condition. In IncidentKit, investigations record contributing factors.

## Frequently asked questions

### Why is it called a fishbone diagram?

The problem sits at the head of a long spine, and cause groups branch off like ribs, like a fish skeleton. It is also called an Ishikawa or cause and effect diagram.

### Which categories should a fishbone use?

IHI's classic version uses materials, methods, equipment, environment and people. Switch to a process-type diagram or change the groups when causes do not fit.

### Does a fishbone find the root cause?

No. It lays out possible causes. Check each one against records, observation and interviews. Confirmed causes lead to corrective actions.

## Sources

- [IHI: Cause and effect diagram (QI Essentials toolkit)](https://www.ihi.org/library/tools/cause-and-effect-diagram)
- [VHA National Center for Patient Safety: Root cause analysis (page and Guide to Performing a Root Cause Analysis, rev. 02/05/2021)](https://www.patientsafety.va.gov/professionals/onthejob/rca.asp)

## Related terms

- [Five whys](https://incidentkit.ai/glossary/five-whys)
- [Root cause analysis](https://incidentkit.ai/glossary/root-cause-analysis)
- [Fault tree analysis](https://incidentkit.ai/glossary/fault-tree-analysis)
- [Corrective and preventive action](https://incidentkit.ai/glossary/corrective-and-preventive-action)

## Related

- [Five whys vs fishbone vs fault tree: how to choose](https://incidentkit.ai/blog/five-whys-vs-fishbone-vs-fault-tree)
- [Root cause analysis and CAPA: methods and strong actions](https://incidentkit.ai/guides/root-cause-analysis-and-capa-guide)
- [Root Cause Analysis Worksheet (5 Whys Template)](https://incidentkit.ai/templates/root-cause-analysis-worksheet)
- [Incident investigations and root cause analysis](https://incidentkit.ai/product/investigations)
- [Root Cause Analysis: How to Run One That Leads to Action](https://incidentkit.ai/use-cases/root-cause-analysis)