How to make a fishbone diagram

A fishbone diagram sorts the possible causes of one problem. Learn to pick categories, ask why, test what you find and draw one in FlowDraw.

Written by
FlowDraw Team
Published
Reading time
6 min read
A FlowDraw board with a fishbone diagram for Orders ship late: People, Process, Tools, Materials, Environment and Measurement bones with causes on each.

Orders ship late, and everyone has a theory. The warehouse blames the app, the app team blames training. A fishbone diagram puts every theory on one page, sorted, before anyone fixes the wrong thing. You can make one in about 30 minutes.

Quick Answer

A fishbone diagram sorts the possible causes of one problem. Write the problem at the head, draw a spine toward it, add one bone per category such as People or Process, list causes on each bone, and ask why until you reach something you can test.

What is a fishbone diagram?

It is a tool for groups: it collects what people suspect and shows where to look next. The name comes from its shape. The other common name, Ishikawa diagram, comes from Kaoru Ishikawa, the Japanese quality expert who made it popular.

A fishbone diagram for Orders ship late, with numbered pins on the head, the spine, a category box and a cause.
The four parts of a fishbone diagram
  1. Head: the problem, as one statement.
  2. Spine: the arrow leading to the head.
  3. Main bones: categories of cause, such as People or Process.
  4. Small bones: specific causes, such as “Short-staffed Mondays”.

Use one when a problem has many plausible causes and people disagree about them. If the causes form one clear chain, the “5 whys” template is quicker. If nobody can describe the process yet, draw it first as a flowchart.

How to make a fishbone diagram

State the problem as a fact

Agree what “Orders ship late” means first: which orders, how late and since when. If people picture different problems, you collect causes for different problems.

Only the head and the spine of the diagram: an arrow pointing at a red box that says Orders ship late.
Start with the head and the spine

Pick the bones

The example uses the classic 6 Ms from manufacturing, in plainer words. Four to six bones is usual, and a bone nobody can fill should go.

Six category boxes joined to the spine by slanted lines: People, Process, Tools, Materials, Environment and Measurement.
One bone per category
In the exampleClassic nameQuestion to ask
PeopleManWho does the work, and what do they know?
ProcessMethodWhat procedure do they follow?
ToolsMachineWhat equipment and software do they rely on?
MaterialsMaterialWhat goes into the work?
EnvironmentMother NatureWhat around the work affects it?
MeasurementMeasurementHow do we know what is happening?

These suit physical work. For service or software problems, rename them to fit.

Collect causes, quietly at first

Give everyone a few minutes to write causes alone, so the first loud theory does not set the direction. Then place each one on a bone.

The finished diagram with two causes on each of the six bones, the new causes dark and the rest faded.
Each cause gets its own short line

Write specific statements, so someone can go and check them:

Two panels. The left bone says Staffing and Training. The right bone says Short-staffed Mondays and Untrained new pickers.
The same bone, vague and specific

Ask why

For each cause, ask why it happens and add the answer as a smaller branch. Why are there untrained new pickers? Perhaps training stops during busy weeks. Keep going until you reach something you can act on or test.

Choose what to test

Agree on the few causes most likely to matter, then check them against data. Do late orders cluster on Mondays? Do they follow scanner outages? Here, “No on-time metric” and “Missed scans” come first, because without them you cannot test the rest.

Why the example is drawn this way

  • The head sits on the right, so the eye follows the arrow from causes to effect.
  • A real diagram is lopsided. A crowded bone shows where attention went, and an empty one may show what nobody has looked at.
  • Causes outside your control still belong. “Storm delays” is one. You can plan around it, and writing it down stops it becoming a catch-all excuse.

Drawing a fishbone diagram in FlowDraw

The template is free on every plan, and nothing in this diagram needs Pro.

The FlowDraw Templates page with Fishbone diagram as the one result.
Find it under Templates in the sidebar
  1. Open the template

    Search for “Fishbone diagram” under “Templates”, open the card, then choose “Use template”.

  2. Write your problem and bones

    Double-click the box at the head and type your problem. Do the same for each category box.

  3. Add a cause

    Each cause is a text box on a thin line. Shift-click both, press ⌘D (Ctrl+D on Windows) and drag the copy into place. A dashed guide appears when it lines up.

  4. Add a bone

    Copy a category box, press Esc, then L, and draw a line from the spine to the box. In “Line properties”, choose “Straight” and set the end to “None”. FlowDraw cannot rotate shapes, so slanted bones are always connectors.

  5. Work on it together

    Choose “Share” and add people. They can add causes alongside you, and you see their cursors. On Free, everyone you invite can edit. On Pro only one person can, so others press C and comment.

  6. Mark what to test

    FlowDraw has no voting or timers. Agree aloud and change the text with “Color” in “Text properties”, or each person presses Esc, then N, and drops a note beside their picks.

The fishbone template open in the FlowDraw editor, with the toolbar at the bottom and Share at the top right.
The template open in the editor

On a blank board, press L to draw the spine, R for the boxes and T for each cause, with Esc between them. “5 whys”, “Problem tree” and “Cause and effect” are free templates too.

Fishbone diagram mistakes to avoid

  • A vague head. “Quality is poor” invites everything. Name one problem you could measure.
  • Solutions dressed as causes. “Need a new scanner” is a fix. Write the fault: “Scanner outages”.
  • Stopping at labels. “Training” cannot be tested. Ask why again.
  • Filling every bone evenly. Identical counts usually mean people are padding.
  • Treating the picture as the answer. The favourite cause is still a guess until the data agrees.
  • Several problems in one head. “Orders ship late and arrive damaged” needs two diagrams.

FAQ

It helps a group list and sort the possible causes of one specific problem, so they can decide what to investigate. It gives you ideas to test, not proof of the cause.

Continue Reading

A FlowDraw board with a project timeline for Product launch 2027: six milestones on one rail, from Kickoff on Jan 11 to First review on Sep 13.

Guides·

How to make a project timeline

Learn how to make a project timeline: pick milestones, get honest dates, choose a scale and draw one in FlowDraw, and see when a Gantt chart fits better.

A FlowDraw board with a three-circle Venn diagram called Who owns what: Design, Engineering and Business overlap, with Product at the center.

Guides·

How to make a Venn diagram

How to make a Venn diagram: when overlapping circles help, how to sort items into regions, and how to build a two or three circle diagram in FlowDraw.

A FlowDraw board with a concept map of Photosynthesis: Light energy, Carbon dioxide and Water go in, Glucose and Oxygen come out, joined by labeled arrows.

Guides·

How to make a concept map

Learn how to make a concept map with focus questions, linking phrases and cross-links, how it differs from a mind map, and how to draw one in FlowDraw.

Ready to create your first diagram?

Turn your ideas, notes, or documents into a clear,
editable flowchart in seconds.

Get Started Free