Business Growth
How to Make a Fishbone Diagram (Template, Example, and Steps)
How to make a fishbone diagram for a small business: what an Ishikawa or cause-and-effect diagram is, when to use one, the categories to use, the step-by-step method, a template, a worked example, common mistakes, and a Claude workflow for building your own.

Founder, AI Tools and Training Club · November 18, 2026 · 8 min read

The short version
- A fishbone diagram, also called an Ishikawa or cause-and-effect diagram, maps every possible cause of one problem, grouped into categories that branch off a central spine like the bones of a fish.
- To make one, write the problem at the head, draw four to six category bones, brainstorm causes under each, ask why to break big causes into smaller ones, then pick the two or three most likely causes and check them with real evidence.
- Use it when a problem has many possible causes and people disagree about which one matters. Then run a 5 Whys on the strongest branches to reach a root cause you can fix.
How do you make a fishbone diagram?
To make a fishbone diagram, write the problem as one specific sentence in a box on the right side of the page. Draw a horizontal line, the spine, running left from it. Add four to six diagonal bones off the spine, one for each category of cause, such as people, process, tools, inputs, measurement, and environment. Brainstorm possible causes and write each one on the bone it belongs to, adding smaller branches when a cause has causes of its own. Finally, mark the two or three causes the evidence points to most strongly, and investigate those first.
My strong opinion: the value of a fishbone diagram is not the drawing, it is the argument it prevents. When something goes wrong in a small business, everyone already has a favorite cause, usually the one that is not their fault. The fishbone forces every possible cause onto one page before anyone decides, so the team investigates the likely cause instead of the loudest one.
What is a fishbone diagram?
A fishbone diagram is a visual map of the possible causes of a single problem. The problem, or effect, sits at the head of the fish. The causes branch off the spine as bones, grouped into categories, with smaller bones for the causes behind each cause. It is also called an Ishikawa diagram, a cause-and-effect diagram, or a herringbone diagram. It was popularized in the 1960s by Kaoru Ishikawa, a Japanese quality management pioneer, and it is one of the seven basic tools of quality control.
The fishbone does not tell you the answer. It is a structured brainstorm. Its job is to make sure you have considered every reasonable cause before you commit time and money to fixing one of them.
| Fishbone diagram | 5 Whys | |
|---|---|---|
| Shape of the thinking | Wide: many possible causes at once | Deep: one chain of cause and effect |
| Best for | Problems with several plausible causes | Following one cause down to its root |
| Output | A map of candidate causes to investigate | One root cause to fix |
Fishbone diagram compared with the 5 Whys
When to use a fishbone diagram
- A problem has many possible causes. Falling repeat sales could be product, price, service, delivery, or a competitor. Map them all before you chase one.
- The team disagrees about the cause. Putting every view on one page turns an argument into a list of things to check.
- A quick fix has already failed. If the obvious fix did not work, the real cause is probably on a bone nobody looked at.
- You are about to spend money on a fix. A new tool, a new hire, or a new supplier is a big bet. Make sure the problem actually lives where you are about to spend.
- Not for simple problems with one obvious cause. If the cause is clear, go straight to a 5 Whys or just fix it.
Fishbone diagram categories
The bones are categories of cause. The classic manufacturing set is the 5 Ms: manpower, machine, material, method, and measurement, sometimes extended with more. Service businesses often use the 4 Ss: surroundings, suppliers, systems, and skills. You can use any set that fits your business, as long as the categories together cover everywhere a cause could hide.
| Category | What it covers | Example causes |
|---|---|---|
| People | Skills, training, workload, handoffs | New staff not trained on the process, one person covering two roles |
| Process | The steps, rules, and checklists | No checklist for a key step, two versions of the process in use |
| Tools | Software, equipment, automations | A broken integration, an outdated template, a slow system |
| Inputs | Materials, supplier work, information from clients | Late supplier deliveries, incomplete client briefs |
| Measurement | How you track and spot problems | No report for the number that slipped, data entered inconsistently |
| Environment | Market, season, location, outside events | Seasonal demand, a competitor's promotion, a price change |
A practical set of fishbone categories for a small business
How to make a fishbone diagram step by step
- Write a specific problem statement. What happened, when, and how big. "Refund requests doubled between August and October" beats "customers are unhappy." Put it in the head of the fish.
- Draw the spine and the category bones. Choose four to six categories that fit your business and label one bone for each.
- Brainstorm causes onto the bones. Get the people closest to the work in the room. Aim for quantity first and do not debate causes yet. Each cause goes on the bone it belongs to.
- Break big causes into smaller ones. For any cause that is still vague, ask why it happens and add the answers as smaller branches off that bone.
- Mark the likely causes. Have the group pick the two or three causes most likely to explain the problem, based on what they have seen, not on who is in the room.
- Check the likely causes with evidence. Pull the numbers, look at the records, or test the cause before you act on it. A cause that does not show up in the data comes off the shortlist.
- Find the root and fix it. Run a 5 Whys on each confirmed cause to reach something you can change, then give the fix an owner and a date to check the problem has stopped.
Fishbone diagram template
You can draw a fishbone on a whiteboard or a sheet of paper. If you want to keep it in a doc or spreadsheet, this table holds the same information and is easier to share.
| Field | What to write |
|---|---|
| Problem (the head) | What happened, when, and how big, in one sentence |
| Category bones | Four to six categories, for example people, process, tools, inputs, measurement, environment |
| Causes | Every possible cause, listed under its category |
| Sub-causes | The answers to why each vague cause happens |
| Likely causes | The two or three causes the team rates most likely |
| Evidence | What the data or records show for each likely cause |
| Fix, owner, and check date | One change per confirmed cause, one person, one date to confirm it worked |
Fishbone diagram template
Fishbone diagram example for a small business
Here is an illustrative example for a made-up online coffee subscription business. Problem statement: subscription cancellations in the first 60 days rose sharply over the last quarter.
| Category | Possible causes from the brainstorm |
|---|---|
| People | New packer started last quarter, customer emails answered more slowly |
| Process | Grind preference not checked before the first box ships, no welcome email explaining how to change the roast |
| Tools | Checkout no longer asks for grind preference after a site update |
| Inputs | New green bean supplier, a few late roast batches |
| Measurement | Cancellation reasons not recorded, only the total count |
| Environment | A competitor launched a cheaper starter offer |
Illustrative fishbone causes for early subscription cancellations
The team rated three causes most likely: the new supplier, the competitor's offer, and the checkout change. Checking the evidence ruled two out quickly. Reviews of the new beans were no worse than before, and the rise in cancellations started several weeks before the competitor's offer launched. The checkout change held up: since the update, every new subscriber had been sent whole beans by default, and a manual review of cancellation emails showed many mentioned having no grinder. A 5 Whys on that branch led to the root cause: nobody owns testing checkout after a site update. The fix was to restore the grind question and add a short checkout test to the update checklist.
Fishbone diagram mistakes to avoid
- A vague problem statement. "Sales are down" produces a diagram of everything. Name the number, the period, and the size.
- Debating causes during the brainstorm. Get every cause on the page first. Judging too early means quieter people stop contributing.
- Treating the diagram as the answer. Every cause on the fishbone is a guess until the evidence confirms it.
- Too many categories. More than six or seven bones and the diagram becomes hard to read. Merge categories that overlap.
- Blaming people. A cause like "careless staff" belongs one level deeper: what in the process made the mistake easy to make?
- Stopping at the diagram. A fishbone without a fix, an owner, and a check date is just a picture of the problem.
How the fishbone diagram fits with other strategy frameworks
- To dig from a likely cause to the root cause: run How to Do a 5 Whys Analysis (Template, Example, and Steps) on each confirmed branch.
- To measure how far you are from where you want to be first: start with How to Do a Gap Analysis (Template, Example, and Steps), then use a fishbone on the biggest gap.
- When the problem is lost deals: pair it with How to Do a Win-Loss Analysis (Questions, Template, and Steps).
- When the causes keep pointing at how the business is organized: step up to How to Use the McKinsey 7S Framework (Template, Example, and Steps).
How to make a fishbone diagram with Claude
Claude is a good brainstorming partner for a fishbone because it fills in the bones you forgot to think about. It does not know your business, so the evidence still has to come from you. Open the Claude desktop app and work through it in passes.
- Describe the problem and ask Claude to rewrite it as one specific problem statement, then to ask you what would make it more precise.
- Ask it to suggest four to six fishbone categories that fit your type of business, and to explain what each one covers.
- Give it the causes your team already came up with and ask it to sort them onto the bones, then to suggest causes for any bone that is thin or empty.
- Paste in the relevant data, such as order logs, support tickets, or cancellation reasons, and ask which causes the data supports, which it contradicts, and what you would need to check the rest.
- Ask it to draw the finished diagram as a simple text layout or a diagram you can paste into a doc, then decide which causes to act on yourself. Claude widens the search, but the judgment about your business stays with you.
Frequently asked questions
What is a fishbone diagram used for?
A fishbone diagram is used to map all the possible causes of one problem in a single view, grouped into categories, so a team can decide which causes to investigate before choosing a fix.
Why is it called an Ishikawa diagram?
It is named after Kaoru Ishikawa, the Japanese quality management pioneer who popularized it in the 1960s. It is called a fishbone diagram because its shape looks like the skeleton of a fish.
What are the categories in a fishbone diagram?
The classic set is the 5 Ms: manpower, machine, material, method, and measurement. Service businesses often use surroundings, suppliers, systems, and skills. A small business can use people, process, tools, inputs, measurement, and environment.
What is the difference between a fishbone diagram and the 5 Whys?
A fishbone diagram goes wide and maps many possible causes at once. The 5 Whys goes deep and follows one cause down to its root. Use the fishbone first to find the likely causes, then run a 5 Whys on each.
How many causes should a fishbone diagram have?
There is no fixed number. Aim to capture every reasonable cause during the brainstorm, then narrow to the two or three most likely ones to check with evidence.
Can I make a fishbone diagram in Word, Excel, or Google Docs?
Yes. You can draw one with shapes and lines in most document and slide tools, or keep the same information in a simple table with columns for category, cause, and sub-cause.