What is a fishbone diagram?
A fishbone diagram, also called an Ishikawa diagram or cause-and-effect diagram, is a visual tool for identifying the possible causes of a problem. The problem (the effect) sits in the head of the fish. Major cause categories branch off the spine like bones, and individual causes and sub-causes hang off each bone.
It was popularized by Kaoru Ishikawa at Kawasaki in the 1960s and is one of the seven basic tools of quality. Its strength is that it makes a team look at every area that could contribute (people, equipment, methods, materials, measurement and environment) instead of jumping to the first explanation.
When to use a fishbone diagram
- At the start of a root cause investigation for a nonconformance, deviation, complaint or incident.
- In step D4 of an 8D report, the Analyze phase of DMAIC or the analysis box of an A3.
- When a team has many opinions about a problem and needs to structure them.
- When the obvious fix has already failed and you suspect several interacting causes.
A fishbone diagram lists potential causes. Pair it with 5 Whys to drill into a branch, or with an cause-and-effect matrix to prioritize which causes to verify first.
Fishbone categories: 6M, 8P and 4S
Categories give the brainstorm structure. Choose the set that matches your environment, then adapt it. This tool includes all of these as templates.
| Template | Typical use | Categories |
|---|---|---|
| 6M | Manufacturing, production, labs | Man (People), Machine, Method, Material, Measurement, Mother Nature (Environment) |
| 8P | Service and marketing | Product, Price, Place, Promotion, People, Process, Physical evidence, Productivity & quality |
| 4S | Service operations | Surroundings, Suppliers, Systems, Skills |
| Healthcare | Patient safety events | Patient, Staff, Equipment, Procedures, Environment, Communication |
| Software / IT | Incidents and outages | People, Process, Code, Infrastructure, Data, Third parties |
Fishbone diagram example
The tool opens with a worked example from pharmaceutical manufacturing: "Tablet weight out of specification on compression line 3." The team used the 6M categories and found potential causes such as worn feeder paddles (Machines), a new API supplier with variable particle size (Materials), an SOP that does not define the in-process check frequency (Methods) and an overdue balance calibration (Measurements).
Notice how the sub-causes are already a step deeper ("why is the feeder speed fluctuating? worn paddles"). The next step would be to collect data, for example particle size by lot against tablet weight, to confirm which causes really drive the problem.
Tips and common mistakes
- State the effect, not a cause. "Operators make errors" is a cause; "12 mislabeled cartons shipped in May" is an effect.
- Brainstorm first, judge later. Capture every idea before the team debates which ones are likely.
- Avoid blaming people. "Operator error" is rarely a root cause; ask why the system allowed the error.
- Go deep enough. A cause is useful when you can act on it or test it. Use sub-causes to keep asking why.
- Verify with data. Mark the causes to investigate and confirm them before writing corrective actions.
From fishbone diagram to CAPA
A diagram is only the start. Regulated organizations need to show that the root cause was verified, that corrective and preventive actions were implemented and that they were effective. In Cloudtheapp's eQMS, the investigation is recorded in the nonconformance or CAPA record, actions are assigned with due dates, and every change is captured in a 21 CFR Part 11 compliant audit trail.
How to use this Fishbone Diagram tool
- Write a precise problem statement. Describe the effect in the head of the fish: what is wrong, where, since when and how much. Avoid putting a cause or a solution in the statement.
- Choose your categories. Start from the 6M, 8P, 4S, healthcare or software template, then rename, add or remove categories to fit your process.
- Brainstorm causes on each bone. Add every potential cause the team can think of under the right category. Press Enter to add the next cause quickly.
- Drill down with sub-causes. For each cause ask "why does this happen?" and add the answers as sub-causes until you reach something actionable.
- Select causes to verify. Agree on the most likely causes, then collect data to confirm or rule them out before you define corrective actions.
- Export and share. Download the diagram as a PDF report, PNG or Excel file for your CAPA, 8D or A3 record.
Frequently asked questions
What is a fishbone diagram used for?
A fishbone (Ishikawa or cause-and-effect) diagram is used to brainstorm and organize all the possible causes of a problem into categories, so a team can see the full picture before deciding which causes to verify with data.
What are the 6Ms of a fishbone diagram?
The 6Ms are the classic manufacturing categories: Man (People), Machine, Method, Material, Measurement and Mother Nature (Environment). Service teams often use the 8Ps or 4Ss instead, and you can rename any category in this tool.
Is a fishbone diagram the same as an Ishikawa diagram?
Yes. Fishbone diagram, Ishikawa diagram and cause-and-effect diagram are names for the same tool, popularized by Kaoru Ishikawa in the 1960s. It is one of the seven basic quality tools.
Does a fishbone diagram identify the root cause?
Not on its own. A fishbone shows potential causes. You still need to verify the most likely ones with data, then confirm the root cause, for example by asking 5 Whys on a branch or by testing the cause against an Is/Is Not analysis.
Can I export my fishbone diagram?
Yes. Export a PDF report, a high-resolution PNG, an Excel workbook or a CSV of all causes, or save a .json file to reopen and keep editing later. Everything is free and nothing is uploaded to a server.
How many causes should a fishbone diagram have?
There is no fixed number. A good session typically produces 3 to 6 causes per category. If a branch is empty, ask whether that category really cannot contribute; if it is overcrowded, split it or drill deeper with sub-causes.