Insights

Fishbone diagram: template, example and how to use it

What an Ishikawa diagram is, how to set up the 6Ms, a template you can copy and a hypothetical worked example from a finance team.

By Christopher Fagan, Managing Partner, PEF Consulting Partners

£13bnlargest programme delivered
19 yrssenior systems delivery
5 continentsdelivered across
£25msaving on a single programme

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

Fishbone diagram is the common name for a cause and effect diagram, a visual tool that sets out the possible causes of a problem under a handful of headings so a team can see and test them in one place. The problem sits at the head of the fish and the causes branch off the spine like bones.

It is one of the simplest tools in quality management and one of the most misused. Drawn well, with the right people in the room, it stops a group fixing on the first explanation offered. Drawn badly, it becomes a wall of sticky notes that confirms what everyone already thought.

Ishikawa diagram, cause and effect diagram, fishbone: one tool

The three names describe the same thing. Ishikawa diagram credits the man who popularised it, cause and effect diagram describes what it does, and fishbone describes what it looks like.

The anatomy is always the same. The effect, meaning the problem you are investigating, goes in a box at the right hand end of a horizontal line, the spine. Diagonal lines, the major bones, run off the spine for each category of cause. Individual causes hang off the major bones and sub causes hang off those, so the further you move from the spine, the more specific the cause becomes.

Where the Ishikawa diagram comes from

The diagram is named after Kaoru Ishikawa, the Japanese quality engineer who popularised it in the 1960s as part of the quality control movement in Japanese industry. He saw it as a tool for front line teams, particularly the quality circles he championed, rather than for specialists.

It became one of the so called seven basic tools of quality, alongside the check sheet, the histogram, the Pareto chart and the control chart, among others. Ishikawa’s Guide to Quality Control, published in English in 1976, set these tools out as a practical kit for working teams, and that is still the right way to think about the fishbone: a working tool, not a deliverable.

The 6Ms and other ways to set up the categories

The classic manufacturing categories are the 6Ms:

  • Manpower: the people doing the work, their skills, training, workload and supervision. Many teams now simply call this people.
  • Machine: equipment, tools and systems.
  • Method: the process, procedures and rules being followed.
  • Material: inputs and components and, in office work, the information arriving from elsewhere.
  • Measurement: how performance is measured, inspected and reported, including whether the measure itself is wrong.
  • Mother nature: the environment, from temperature and layout to seasonal volumes and regulation.

Office, service and technology problems often fit better under headings such as people, process, systems, data, suppliers and policy. There is no prize for using a standard set. Choose four to six categories that suit the problem, and add one if the session keeps producing causes that have nowhere to go.

How to draw a fishbone diagram, step by step

  1. Agree the effect. Write a specific, measurable problem statement in the head, such as “Month end close takes nine working days against a target of five”. A vague effect produces vague causes.
  2. Choose the categories. Start with the 6Ms or a set that suits the problem, and draw them as the major bones.
  3. Get the right people in the room. Include the people who do the work, the people downstream who feel the problem, and someone who owns the systems. Senior people should listen more than they talk.
  4. Brainstorm causes. Go category by category. For each cause, ask why it happens and add the answers as smaller bones. Capture everything first and judge later.
  5. Tidy it up. Merge duplicates, move causes to the right category, and reword anything that is really a solution in disguise, such as “no automation”.
  6. Mark the likely causes. Note which causes have evidence behind them, which are opinion, and which could be checked quickly with data.
  7. Test before acting. Use data, observation or a small trial to confirm the few causes that matter, then take those into a fuller root cause analysis and an action plan.

If the process itself is poorly understood, map it before you draw the fish. A SIPOC diagram of suppliers, inputs, process, outputs and customers takes an hour or so and makes the brainstorm far sharper.

Fishbone diagram template

The fish is easiest to draw on a whiteboard, but the record is easier to keep as a table. Copy the template below, write the effect at the top, and replace the typical causes with the ones your team raises. Mark each one as confirmed, ruled out or still to test.

Effect. State the effect precisely: what is going wrong, where, since when and by how much. Keep causes out of it.

CategoryPrompt questionsTypical candidate causesEvidence and status
PeopleDo people have the skills, time, authority and information they need?Training gaps, reliance on one person, unclear roles, conflicting prioritiesConfirmed, ruled out or to test
Machine (systems and tools)Do the systems and tools work as intended?Manual workarounds, outages, slow batch jobs, poor integrationConfirmed, ruled out or to test
Method (process)Is the process defined, followed and current?Missing steps, handoffs, queues, rework, approvals that waitConfirmed, ruled out or to test
Material (inputs and data)Do inputs arrive on time, complete and correct?Late or incomplete inputs, poor master data, supplier errorsConfirmed, ruled out or to test
MeasurementAre we measuring the right thing in the right way?Inconsistent definitions, reports that double count, no baselineConfirmed, ruled out or to test
Mother nature (environment)Do timing, volume, location or regulation play a part?Seasonal peaks, quarter end pressure, site layout, rule changesConfirmed, ruled out or to test

Keep the rejected causes on the record with the reason they were ruled out. If the problem returns, the next team starts from evidence rather than from scratch.

Fishbone diagram example: a slow month end close

This example is hypothetical. The group, its figures and its systems are invented to show the tool in use.

A mid sized group with several trading companies takes nine working days to close its books each month, against a target of five. The finance director has been told the problem is the ERP system. Before committing to an expensive fix, she asks the finance team, the systems team and two budget holders to spend a morning on a fishbone, with the effect written as “Month end close takes nine working days against a target of five, and has done for six months”.

CategoryCandidate causes raisedWhat the evidence showed
PeopleOne group accountant prepares all consolidation journals; budget holders slow to approve accrualsConfirmed: the group accountant’s tasks sit on the critical path for three days
MachineTwo ledgers since an acquisition; consolidation done in spreadsheets; slow overnight jobsConfirmed: spreadsheet consolidation adds two days. Overnight jobs ruled out
MethodIntercompany balances reconciled only after period end; accruals rebuilt from scratch each monthConfirmed: intercompany mismatches take two to three days to clear
MaterialSupplier invoices arrive late; purchase orders raised after the invoicePartly confirmed: affects accruals but adds less than a day
MeasurementNo tracking of close tasks; management pack reworked because KPI definitions differ between companiesConfirmed: rework adds a day after the ledgers close
Mother natureQuarter end audit requests; holiday coverRuled out as a regular cause; affects some months only

The session changes the conversation. The ERP system is part of the picture, because running two ledgers forces a manual consolidation, but most of the lost days come from how the work is organised: intercompany left until the end, one person on the critical path, and a management pack rebuilt every month because definitions differ. Those can be fixed in weeks, without a new system.

The team agrees three actions, each with an owner and a date: reconcile intercompany balances weekly during the month, split the consolidation journals between two people with a written procedure, and agree one set of KPI definitions for the pack. A month end close checklist gives them a task list to track progress against, and the ledger question moves into the longer term plan with a proper business case.

Notice what the fishbone did and did not do. It proved nothing on its own. It made sure every plausible cause was on the table, and gave the team a structure for checking each one against evidence before any money was spent.

When a cause and effect diagram helps, and when it does not

Use one when a problem has several plausible causes and the people involved disagree, when you need a cross functional group to look at the same problem together, or when an investigation risks fixing on a favourite theory. It works well at the start of a root cause investigation, in a project review that needs to explain slippage, and in continuous improvement work.

It helps less when the cause is already obvious, or when the problem is a single technical fault that needs an engineer rather than a workshop. Where a failure involves complex combinations of events, fault tree analysis is a better fit. It is also a poor tool for choosing between options: it explains problems, it does not pick solutions.

Common mistakes

  • A vague effect. “Poor performance” produces a diagram full of everything. A measurable effect focuses the room.
  • Solutions written as causes. “No automation” or “not enough staff” assume the answer. Write down what is actually happening instead, such as “journals keyed by hand from three spreadsheets”.
  • Labels instead of causes. “Communication” and “culture” are categories, not causes. Keep asking why until the cause is specific enough to test.
  • The wrong people. A diagram drawn by managers alone reflects management’s view. The people doing the work usually know where the problems are.
  • Treating the diagram as the answer. Every cause on it is a candidate until evidence confirms it.
  • Stopping at the picture. A fishbone without owners, dates and follow up is just wallpaper.

From diagram to action

A fishbone is the start of the work, not the end of it. The causes you confirm need owners, the risks it surfaces belong in a RAID log, and what you learn should go into a lessons learned template so the next team does not start from nothing.

On a struggling project the same tool works at a larger scale. In a project recovery, mapping why milestones are slipping under headings such as people, process, suppliers, technology, governance and data is usually quicker and more honest than reading the status reports. Where the same causes keep appearing across several teams, the answer is broader operational excellence work rather than another workshop, and in a finance function that often means looking at the wider finance transformation agenda.

PEF takes no reseller fees or commissions from any software vendor, so we have no reason to steer the technology bone towards a new system. Our Managing Partner, Christopher Fagan, has run systems and transformation delivery for 19 years, and our consultants test the causes with your team and stay to put the fixes in, rather than leaving a diagram on the wall.

Common questions

What is a fishbone diagram?

A fishbone diagram, also called an Ishikawa or cause and effect diagram, is a visual tool for setting out the possible causes of a problem. The problem is written at the head, major categories of cause branch off a central spine, and individual causes hang off each category. It helps a team see every candidate cause before deciding which ones to test.

What are the 6Ms in a fishbone diagram?

The 6Ms are the classic categories used in manufacturing: manpower (people), machine, method, material, measurement and mother nature, meaning the environment. They act as prompts so a team considers every kind of cause, not just the obvious one. Service and office teams often adapt them to headings such as people, process, systems, data, suppliers and policy.

How do you make a fishbone diagram?

Write a specific, measurable problem in the head of the fish. Draw a spine and add four to six category bones, such as the 6Ms. With the people who do the work, brainstorm causes under each category and ask why each one happens to add sub causes. Then mark which causes have evidence behind them and test the likeliest before acting.

Who invented the fishbone diagram?

The fishbone diagram is credited to Kaoru Ishikawa, the Japanese quality engineer, which is why it is also called an Ishikawa diagram. He popularised it in the 1960s through the Japanese quality control movement, and it became one of the seven basic tools of quality taught to front line teams and quality circles.

What is the difference between a fishbone diagram and the 5 whys?

A fishbone diagram goes wide: it captures many possible causes across several categories at once. The 5 whys goes deep: it follows one chain of cause and effect down to a root cause. They work well together. Use the fishbone to surface candidates, data to narrow them, and then the 5 whys to drill into the few that matter.

Related reading: Root cause analysis: methods and template, SIPOC diagrams explained, Lessons learned template and Operational excellence consulting.

Need an honest view of what is causing the problem?

We run cause and effect sessions with your team, test the findings against data and stay to put the fixes in. Tell us about the problem and we will suggest a sensible first step.

Book a confidential conversation

Sources: Kaoru Ishikawa, Guide to Quality Control, 1976 (English edition); Nancy R. Tague, The Quality Toolbox, second edition, ASQ Quality Press, 2005

PEF TRACK RECORD£13bnLargestprogramme led5Continentsdelivered across19 yrsSystems delivery£25mLargestsingle saving
CF

Written by Christopher Fagan

Managing Partner, PEF Consulting Partners

Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.