Fishbone Diagram

Thinking Tools4.1 Root Causes and the Case for Going BackAlso known as Ishikawa Diagram, Cause-and-Effect Diagram

Developed by Kaoru Ishikawa (Guide to Quality Control, 1968).

Lays out the possible causes of a defect or failure on branches by category, such as method, machine, material, and people, so no family of causes is skipped.

Why invoices go out eleven days late, with the causes laid out by category

The effect sits at the head; each category branch holds the causes the team named, and the causes behind them. Select a cause to read what the team knew about it, then mark the two you would test with data first. Illustrative.

0 of 2 marked1 of 2 marked2 of 2 marked

Select a cause to read what the team knew about it.Effect: invoices go out 11 days late. Measured: invoices leave an average of eleven days after a job closes, against a target of two. About $1.4M of cash is waiting at any time.Method. How the work is done: the steps between a closed job and a sent invoice.Billing waits for the paper job sheet. Sheets ride back with the technician. In a quick look at ten late invoices, seven had waited on a sheet.Invoices are cut only on Fridays. A weekly run adds three days on average and up to six. On its own it cannot explain eleven.Machine. The tools and systems: here, the field app and the billing system.Field app does not pass the sign-off. The app records the customer's signature, but billing never sees it, so the clerk waits for paper anyway.Material. The inputs billing works from.Job sheets arrive without a PO number. A sheet without the customer's purchase order number cannot be billed.The PO field is optional in the app. Technicians skip it when the customer's contact is not on site. Each miss costs a phone call.Supplier parts costs arrive late. Only jobs with special-order parts wait for the supplier's bill: about one in twenty.People. Who does the work, and how it is staffed.Technicians hand in sheets on Fridays. Most technicians drop a week of sheets at the office at once, which feeds the Friday run.One clerk covers three regions. When she is out, nothing is billed. Her vacation weeks show as spikes, but the delay is high in normal weeks too.Measurement. What is counted and reported.Nobody tracks days to invoice. The team reports invoices sent per week. No report shows how old a job was when it was billed, so the delay grew unseen.Environment. The setting the work happens in.Month-end close takes the billing desk. For three days a month the desk helps finance close the books. It adds a little, once a month.Two customers require their own portals. Their invoices go through the customers' websites, one log-in each, held by the one clerk.

An example

A facilities maintenance company was billing its commercial customers an average of eleven days after each job closed, against a target of two, and about $1.4 million of cash sat waiting at any time. The first explanation in the room was the billing clerk, who covers three regions alone.

The operations manager drew the effect at the head of a whiteboard and six branches behind it: method, machine, material, people, measurement, and environment. The group had to name at least one cause on every branch before anyone argued. The people branch filled fastest. The method and machine branches turned out to hold the bigger causes: billing waited for paper job sheets that rode back with the technicians, the field app captured the customer's signature but never passed it to billing, and invoices were cut only on Fridays.

The team marked two causes to test. A sample of sixty late invoices showed that forty-one had waited on a paper sheet. Sending the app's sign-off straight to billing and running invoices daily cut the average to three days within a quarter.

Why it works

The diagram forces breadth before depth. A group investigating a failure usually seizes the first plausible cause, often the one that names a person, and stops looking. Fixed categories make the group fill every branch, so causes in tools, inputs, measurement, and the setting get a hearing even when nobody in the room thinks of them first.

Putting every candidate in one picture does two more things. It shows when causes on different branches are the same thing seen twice, and it turns an argument about the answer into a shared list of possibilities. The last move matters most. The diagram proves nothing on its own; it is a map of hypotheses, and the likeliest two or three are tested with data before anything is fixed.

The thinking behind it

Kaoru Ishikawa Kaoru Ishikawa, an engineering professor at the University of Tokyo and a leader of the Japanese quality movement, popularized the cause-and-effect diagram from the 1960s, and it now carries his name as well as the fishbone label. He used it in quality work at Kawasaki and set it out in his Guide to Quality Control (1968). He is also known for quality circles, small groups of workers who study and fix problems in their own work. The basic idea of a cause-and-effect diagram is older than his books; he made it a standard tool.

How to run it

  1. Write the effect as a measured fact. Invoices go out eleven days after the job closes gives the group a number to explain; billing is slow invites opinions.
  2. Choose categories that fit the work. Method, machine, material, people, measurement, and environment suit operations; a service team may swap in policies or systems, so long as the set covers the work.
  3. Fill every branch before going deep. Ask for at least two causes per category, so the quiet branches get a hearing before the loud ones.
  4. Ask why of each cause. Add the causes behind it on smaller branches until the next answer would be outside the team's reach.
  5. Note how each cause could be tested. A sample, a log, or a timing study written beside each leaf turns the drawing into a test plan.
  6. Test two or three before fixing anything. Pick the likeliest and the cheapest to check, and let the data choose the fix.
  7. Strike what the data rules out. Keep the corrected diagram, since the same effect tends to come back.

Where it goes wrong

The drawing becomes the answer. A full whiteboard looks like analysis, and the team fixes the cause it liked best. Spot it when no cause has a test written beside it, and do not act until two causes have been checked against data.

The people branch fills first and fullest, often with names, and the session turns into blame. For each people cause, ask what in the method or the system lets it happen; that is usually where the fix is.

Branches get padded to look complete. A category with nothing real in it can stay short, and weak causes added for symmetry only dilute the test list.

When to use something else

  • Five Whys. When the problem is small and one chain of causes is enough, so a full diagram would be ceremony.
  • Pareto Principle. When the causes are already logged and counted, and the job is to rank them by how much of the problem each explains.
  • Causal Loop Diagram. When the causes feed one another in loops, which a branching diagram cannot show.

Where it sits in SOLVE eX

Go to the source

  • Guide to Quality Control, JUSE, 1968

Back to the catalog