Ishikawa Fishbone Diagram Combined with 5 Whys for Root Cause Analysis

Learn how to pair an Ishikawa fishbone diagram with 5 Whys drill-down to find real root causes, sort them into the 6M categories and build a clear template.

9 min read0 views
— · 0 votes
Contents
  1. What the combined method does
  2. Build the fishbone before asking why
  3. Sort candidate causes into the 6M categories
  4. Run the 5 Whys on shortlisted causes
  5. Connect the two tools in one workflow
  6. A worked root cause example
  7. Keep the diagram accurate and useful
  8. Templates and formats for the diagram
  9. Questions About Fishbone and 5 Whys
  10. What is root cause analysis with 5 Whys and an Ishikawa fishbone?
  11. What are the fishbone diagram root cause analysis categories?
  12. How many whys should I ask before stopping?
  13. Can I use a fishbone diagram template in Word?
  14. Where does the 5 Whys drill-down fit on the diagram?
  15. Is a fishbone analysis enough on its own for root cause?

An Ishikawa fishbone diagram combined with 5 Whys gives you two passes at the same problem. The fishbone spreads possible causes across clear categories so nothing is missed, and the 5 Whys drill-down pushes each shortlisted cause toward the underlying reason. Together they turn a messy incident into a short list of causes you can act on.

  • Place the effect in the head of the fishbone, then add candidate causes on the bones before asking any why.
  • The 6M categories (people, methods, machines, materials, measurement, environment) keep the search broad and organized.
  • Run 5 Whys only on causes the team has evidence for, not on every branch of the diagram.
  • Stop the drill-down when a cause is something the team can change, not when you reach the fifth question.
  • Record the evidence for each cause so the diagram becomes a working record, not a guess sheet.

What the combined method does

The combined method uses a fishbone diagram to widen the search and 5 Whys to deepen it. The cause and effect diagram, also called an Ishikawa diagram, shows many possible causes of one problem at a glance. The 5 Whys drill-down then follows a single cause backward until the team reaches something it can change.

The fishbone answers the question of where to look, and 5 Whys answers the question of why it happened. A pure fishbone session often stops at symptoms, such as a scratched panel or a mislabeled container. A pure 5 Whys session can follow one wrong guess for too long without checking the rest of the process.

Using both keeps the analysis balanced and honest. The diagram records what the team considered, and the why chain records how far each line of thinking went. That record helps a detailing shop explain the fix to staff and to a customer without relying on memory.

Build the fishbone before asking why

Start the Ishikawa diagram with the problem written in the head of the fish, stated as an effect and not a blame. Write the effect in concrete terms, such as a coating failure or a missed handover, with where and when it showed up. A clear effect statement keeps the team from drifting into unrelated complaints.

Draw the spine and add the main bones for the cause categories your process needs. Each bone becomes a home for candidate causes the team can see, measure or has heard about. Add causes with a short phrase on a smaller branch, and leave space under each because the why chain will grow there.

Keep the first pass fast and judgment-free. The aim is a full picture of possible causes, not a debate about the right one. Moving straight to a single theory at this stage defeats the purpose of the cause and effect diagram.

Sort candidate causes into the 6M categories

The 6M categories give a fishbone diagram its structure: people, methods, machines, materials, measurement and environment. These headings work well for detailing because a vehicle finish, a chemical mix and a staff routine all interact. Use the 6M set as a prompt and drop any category that clearly does not apply to the job.

People covers training, attention and shift handover habits. Methods covers the written sequence of a wash, a polish or a coating step, plus whether staff follow it. Machines covers polishers, extractors, pressure washers and their condition, while materials covers chemicals, pads, cloths and water quality.

Measurement covers how the team checks results, such as light inspection or film thickness, and whether those checks agree. Environment covers lighting, temperature, dust, airflow and space around the vehicle. Naming the six categories once at the start of a session saves time and stops the diagram from leaning on one area.

  • People: training, attention, handover between staff
  • Methods: the written sequence of each process step
  • Machines: polishers, extractors, washers and their upkeep
  • Materials: chemicals, pads, cloths and water
  • Measurement: inspection method and how results are judged
  • Environment: lighting, dust, temperature and space

Run the 5 Whys on shortlisted causes

The 5 Whys drill-down works on one cause at a time, and it needs evidence rather than opinion. Pick the causes on the fishbone that the team can support with a photo, a record or an observation. Ask why that cause happened, write the answer, then ask why again about the answer.

The number five is a guide and not a rule. Stop when the answer describes a condition the team can control, such as a missing checklist or a worn pad that nobody inspects. If the chain wanders into company policy or budget, note it and hand that part to whoever owns the decision.

Write each why step as a short statement and keep the chain visible on its branch. A chain that loops back to an earlier answer shows the team is guessing. A chain that ends at a person's name alone is not a root cause, so ask what allowed the mistake to reach the vehicle untouched.

Connect the two tools in one workflow

A root cause analysis workflow that joins both tools runs in one session with two clear stages. The first stage fills the fishbone with candidates across the 6M categories, and the second stage drills into the shortlist. A short break between the stages lets the team step back and choose the strongest branches.

After the drill-down, mark every cause that survived on the original diagram. That link shows which category carried the real root cause and which categories only looked busy. The pattern often reveals a weak point in the root cause analysis steps, such as a check that exists on paper but never happens in the bay.

Close the session with actions written against the deepest cause in each chain. Give each action an owner and a check that shows it worked, since a fix nobody verifies can fade. Store the finished diagram with the incident record so a repeat problem can be compared against it.

StageToolOutput
1. Define the effectEffect statementOne clear problem in the fish head
2. List candidatesIshikawa fishboneCauses sorted into the 6M categories
3. Select branchesTeam reviewShortlist with evidence for each cause
4. Drill down5 WhysA cause the team can act on
5. Act and verifyAction listOwner, fix and proof it worked

A worked root cause example

A fishbone diagram root cause analysis example makes the method easier to copy. Suppose a car leaves the bay with polish residue packed around a trim edge. The effect goes in the fish head as residue found at final inspection after a machine polish.

On the fishbone, the methods bone gets a step missing for a residue check after polishing. The machines bone gets a polisher with a torn backing plate, and the materials bone gets a pad used past its shape. The environment bone gets poor inspection lighting at the trim line, and the measurement bone gets a final check done by feel rather than sight.

The team has photos of the torn plate, so that branch goes to 5 Whys. Why did the plate tear? It was stored loose in a drawer. Why was it stored loose? No marked storage point existed for backing plates. The fix lands on storage and inspection, and the diagram shows the other branches still need checks of their own.

Keep the diagram accurate and useful

Accuracy in a fishbone diagram depends on evidence written next to each cause. Add a short note of how the team knows a cause is possible, such as a photo, a batch record or a direct observation. Causes with no supporting note stay on the diagram only as open questions.

Words matter when the diagram leaves the room. Write causes as neutral statements about the process and avoid naming a person as the cause of an effect. A label like 'pad stored loose' survives a staff change, while a name does not and invites defensiveness.

Review the diagram after the actions are in place and mark which causes were confirmed. An old diagram with confirmed and rejected branches becomes a useful reference for the next incident. Keep the layout consistent so a reader can compare two diagrams side by side.

Templates and formats for the diagram

A fishbone diagram root cause analysis template needs little more than a head, a spine and six labeled bones. A whiteboard or paper sheet works for a live session, and a simple table can hold the same content for a record. The layout matters less than the discipline of filling every category.

A fishbone diagram Word template suits teams that file reports in a document system. Build the bones from lines or shapes, leave a text box under each bone, and place the effect in the head. Add a small column for the why chain beside each bone so the drill-down stays attached to its cause.

Whatever format you use, keep the effect statement at the top and the evidence notes next to each cause. A template should prompt the 6M categories so a session cannot skip machines or measurement. Review the template after a few uses and remove any field that never gets filled.

Questions About Fishbone and 5 Whys

What is root cause analysis with 5 Whys and an Ishikawa fishbone?

Root cause analysis with 5 Whys and an Ishikawa fishbone is a two-stage method for finding why a problem happened. The fishbone diagram lists possible causes across clear categories, and the 5 Whys drill-down follows the strongest causes toward a fixable root. Using both widens the search and then deepens it.

What are the fishbone diagram root cause analysis categories?

The fishbone diagram root cause analysis categories in the 6M set are people, methods, machines, materials, measurement and environment. These headings prompt the team to check several parts of the process instead of one. A team can rename a category to fit its work, but it should keep the six areas covered.

How many whys should I ask before stopping?

Ask as many whys as it takes to reach a cause the team can change, and treat five as a guide. Stopping at a fixed number can leave the chain at a symptom. Stopping when the answer names a person alone also leaves the real gap hidden.

Can I use a fishbone diagram template in Word?

Yes, a fishbone diagram template in Word works well for teams that file reports as documents. Draw the spine and six bones with shapes, place the effect in the head, and add a text box for evidence on each branch. The template should list the 6M categories so no area is skipped.

Where does the 5 Whys drill-down fit on the diagram?

The 5 Whys drill-down fits on the branch of a cause the team can support with evidence. Write each why step under that cause so the chain stays attached to its bone. A chain that floats away from the diagram is hard to check later.

Is a fishbone analysis enough on its own for root cause?

A fishbone analysis alone often stops at possible causes and does not prove any of them. The diagram organizes the search, while a drill-down method tests a cause in depth. Pairing the fishbone with 5 Whys gives the team both breadth and depth.

Latest articles