Build an Ishikawa / fishbone diagram online to map the root causes of a problem. Start with the 6 Ms, rename categories, add causes and sub-causes, then export your diagram — all in your browser.
Watch: Root Cause Analysis: The Fishbone Diagram Method
A problem has many possible causes and your team needs to organise them before chasing fixes. Enter the lab to see a worked cause-and-effect diagram.
Write the problem you want to investigate in the box — this becomes the fish's head. Keep it specific and measurable (e.g. 'late deliveries' or 'high scrap rate') so the team stays focused.
The diagram starts with 6 standard category labels (Man, Machine, Method, Material, Measurement, Mother Nature) — you can rename any of them. Add your team's brainstormed causes under each one, and break down big causes into smaller ones for more depth.
The diagram updates live as you type. Download it as SVG or PNG (or print it) for your report, then verify the likely causes with follow-up investigation before you act.
The fishbone (Ishikawa) diagram is the classic cause-and-effect tool for structured root-cause brainstorming. It groups the possible causes of a problem into categories — the 6 Ms — so a team explores the whole problem space before jumping to conclusions.
The fishbone (or Ishikawa) diagram is a visual cause-and-effect tool. The problem you are investigating sits at the head of the fish, a horizontal spine runs back from it, and angled bones branch off for each category of cause. Under each bone the team lists specific causes, with sub-causes for extra detail. It turns a messy brainstorm into a structured map that makes sure no type of cause is overlooked.
Start by writing a clear, specific problem statement. Add category bones — the default 6 Ms (Man, Machine, Method, Material, Measurement, Mother Nature) work for most processes, but you can rename them. For each category ask "what here could cause the problem?" and add the causes; drill into big ones with sub-causes. The result is a tree of candidate causes, grouped so the team can prioritise where to investigate.
A logistics team is getting complaints about late deliveries. Instead of guessing, they run a team brainstorm and map all possible causes under six headings: People, Process, Equipment, Material, Measurement, and Environment.
Under 'Process' they spot three causes nobody had connected before: handoff delays between picking and packing, a manual booking step only one person can do, and no buffer time in the schedule.
What to do with this: Fix the bottleneck first — cross-train two more people on booking and add 20 minutes of buffer. A fishbone turns a vague complaint into a concrete action list.
Teams often fix the first cause that comes to mind and the problem returns. The fishbone forces a broad, structured search across every category before action, so effort is spent on the real drivers rather than symptoms — saving time, cost, and repeat firefighting.
The fishbone belongs in the Analyse phase of DMAIC, where you move from "what is happening" to "why". It is a team activity — gather the people who know the process, brainstorm against each bone, then take the strongest candidates forward for verification with data.
Cause-and-effect analysis is a core Lean Six Sigma tool, usually paired with the 5 Whys and a Pareto chart. Together they take you from a broad list of possible causes to a short list of verified root causes ready for corrective action and control.
Once the diagram is complete, have the team vote on the most likely causes. Verify them with data rather than opinion, and run a 5 Whys on each to reach the underlying root cause. Use a Pareto chart to confirm which causes account for most of the problem. Then assign each confirmed root cause an owner, a corrective action, and a due date in an action log, and monitor the problem with a run chart or control chart to confirm the fix holds.
Combine the fishbone diagram with the 5 Whys, Pareto analysis, and a DMAIC project structure to find and fix root causes for good.
A fishbone diagram — also called an Ishikawa or cause-and-effect diagram — is a structured brainstorming tool that maps the potential causes of a problem. The problem (the effect) sits at the head of the fish, a horizontal spine runs back from it, and angled bones branch off for each category of cause. Under each category you list specific causes, and you can add sub-causes for extra detail. It helps a team see the whole problem space at a glance and avoid jumping to the first obvious explanation.
The 6 Ms are the classic manufacturing categories used to organise causes on a fishbone diagram: Man (people), Machine (equipment), Method (process), Material (inputs), Measurement (inspection and data), and Mother Nature (environment). They act as prompts so the team considers every type of cause rather than focusing on one area. You can rename them to suit your context — service teams often use the 4 Ps (People, Process, Policies, Plant) or the 8 Ms instead.
A fishbone diagram is a breadth-first tool: it spreads out many possible causes across categories so nothing is overlooked. The 5 Whys is a depth-first tool: it drills down one chain of cause-and-effect by repeatedly asking 'why?' until it reaches a root cause. They work best together — use the fishbone to surface and group candidate causes, then take the most likely ones and run a 5 Whys on each to find the true root cause before you act.
A fishbone lists possible causes, not proven ones. Once you have the diagram, prioritise the most likely causes (use team voting or a Pareto chart of data), verify them with evidence rather than opinion, and run a 5 Whys to reach the root cause. Then assign each confirmed root cause an owner, a corrective action, and a due date in an action log, and monitor the problem with a run chart or control chart to confirm the fix worked.
A fishbone diagram surfaces candidate causes. Structured training shows you how to verify them, find the true root cause, and put lasting fixes in place.
More calculators for statistics, quality, and improvement.
Want to find and fix root causes inside a structured improvement project? The Yellow Belt covers cause-and-effect analysis, the 5 Whys, Pareto, and the core problem-solving toolkit.
View Black Belt →