Root Cause Analysis Toolkit: 5-Why, Fishbone, Fault Tree

Four root cause analysis methods side by side: 5 Why, fishbone, Is/Is-Not and fault tree analysis, when to use each and how to verify the cause.

16 min read 5 sections Guide 12 of 20, Lean Master Practitioner Updated

WHY 1WHY 2WHY 3WHY 4ROOT
5 WhysAsk why until the answer is something you can fix

New to this topic?

Read these first to get the most out of this guide:

4
RCA Methods
5
Why’s (Minimum)
6M
Fishbone Categories
3
Root Cause Tests

Method 1: 5-Why Analysis

The simplest and most frequently used RCA method. Start with the problem, then ask “Why?” repeatedly until you reach a root cause that is actionable.

SafetyHazard tape lays across the aisle and the walkway lines mark the safe pathThe Safety guide
5-Why Example CNC Tool Breakage
LevelQuestionAnswer
ProblemWhat happened?Drill bit broke during wing rib machining
Why 1Why did the drill bit break?Excessive heat buildup during drilling
Why 2Why was there excessive heat?Coolant was not reaching the cutting zone
Why 3Why was coolant not reaching the zone?The coolant nozzle was clogged with chip debris
Why 4Why was the nozzle clogged?The chip guard was removed during a repair and never reinstalled
Why 5Why was the chip guard not reinstalled?There is no post-repair checklist to verify all guards are in place before returning the machine to production

Root cause: No post-repair verification checklist. Countermeasure: Create a maintenance return-to-service checklist that includes all guards, covers, and safety devices. Verify with a sign-off before the machine resumes production.

5-Why Pitfalls

Stopping too early: “Why did the drill break? Because the operator used the wrong speed.” That is Why 1, not a root cause. Keep going. Blame trail: If every Why leads to “because the operator didn’t…” you are finding human error, not system failure. The system should prevent the error. Single path: Problems often have multiple contributing causes. Branch your 5-Why when “Why?” has more than one valid answer.

Method 2: Ishikawa (Fishbone) Diagram

The fishbone diagram organizes potential causes into categories, ensuring you consider all dimensions of the problem. The standard manufacturing categories are the 6M’s:

PEOPLETOOLSMETHODPARTSGAUGESHOP
Fishbone diagramCauses in six families, traced back to the one effectThe Fishbone diagram guide
CategoryWhat to ExamineExample Causes for Sealant Rework
Man (People)Training, skill, experience, fatigue, technique variationNo standard work for bead application; 3 operators use 3 different techniques
MachineEquipment condition, calibration, maintenance, toolingSealant gun nozzle worn, dispensing inconsistent bead width
MaterialRaw material quality, shelf life, lot variationSealant batch from vendor B has higher viscosity than vendor A
MethodProcess design, work instructions, sequenceWork instruction says “apply sealant” but does not specify bead width or technique
MeasurementGage capability, inspection method, criteria clarityFillet radius acceptance criteria is ambiguous (“adequate” vs. “0.125 ± 0.020 in”)
Mother Nature (Environment)Temperature, humidity, lighting, contaminationShop temperature below 65°F causes sealant to thicken and resist flow

The fishbone is a brainstorming tool: list every possible cause under each M, then use data to narrow down to the actual root cause(s). It prevents the team from fixating on the first cause that comes to mind.

Method 3: Is/Is-Not Analysis

Is/Is-Not is powerful when you can observe the problem selectively: it happens sometimes but not always, in some locations but not others, with some operators but not all. The method systematically maps the boundaries of the problem to narrow the cause.

ISIS NOT
Is / is notTwo columns side by side: where the problem is, and where it could be but is not
Is/Is-Not Example Fastener Torque Failures
DimensionIS (problem occurs)IS NOT (problem does not occur)Distinction
WhatHi-Lok fasteners in Zone 3Hi-Lok fasteners in Zones 1, 2, 4Zone 3 only
WhereAft fuselage sectionForward fuselage, wingAft section only
WhenNight shiftDay shiftNight shift only
WhoAll night shift operatorsDay shift operatorsNot person-specific

Hypothesis from distinctions: Zone 3 on aft fuselage, night shift only. Investigation reveals: the night shift torque wrench for Zone 3 was out of calibration (last calibrated 6 months ago). Day shift uses a different wrench that is current. The root cause is not operator error. It is a calibration management gap.

Method 4: Fault Tree Analysis (FTA)

FTA works top-down: start with the undesired event (“top event”) and decompose it into all possible cause combinations using AND/OR logic gates. It is the most rigorous RCA method and is used for safety-critical analysis in aerospace (required by many AS9100 and MIL-STD processes).

TOP EVENTORANDOR
Fault treeThe top failure splits through AND and OR gates down to the basic events that cause it
GateSymbolMeaning
OR gate⋀The output event occurs if ANY input event occurs (either/or)
AND gate⋂The output event occurs only if ALL input events occur simultaneously

FTA is more complex than 5-Why or fishbone and is typically used for high-consequence failures (safety incidents, field failures, MRB-level quality escapes). For daily shop floor problem solving, 5-Why and fishbone are sufficient.

Choosing the Right Method

A3The whole problem, story left to right, on one sheetThe A3 guide
SituationBest MethodWhy
Simple problem, daily use5-WhyFast (5 to 10 min), no special tools needed, good for daily standup
Complex problem, multiple possible causesFishboneStructured brainstorming, ensures no category is overlooked
Problem occurs selectivelyIs/Is-NotSystematically narrows the field using boundary conditions
Safety-critical, high-consequenceFault TreeExhaustive, logic-based, identifies all possible cause combinations
A3 Section 55-Why + FishboneFishbone to brainstorm, 5-Why to dig into the top candidates

The Bottom Line

Root cause analysis is the engine behind every lean improvement. 5-Why gets you to actionable causes quickly. Fishbone ensures you consider all dimensions (6M’s). Is/Is-Not narrows the field when the problem occurs selectively. Fault Tree provides exhaustive analysis for safety-critical failures. Use the three root cause tests (remove cause → problem stops? cause present → problem always? logical chain clear?) to verify you have found the real root cause, not a symptom. Next: Statistical Process Control, using data to detect problems before they become defects.

Frequently asked questions

What is root cause analysis?

Root cause analysis (RCA) is the systematic process of identifying the fundamental reason a problem exists, not just the symptom or proximate cause, but the deepest cause that, if eliminated, would prevent the problem from recurring. A symptom is 'Station 7 rework rate is 18%.' A proximate cause is 'the sealant bead is too thin.' A root cause is 'no standard work exists for sealant application, so each operator uses a different technique.'

How do you know when you have found the root cause?

Three tests: (1) If you remove this cause, does the problem stop? (2) If this cause is present, does the problem always occur? (3) Can you explain the logical chain from this cause to the observed symptom? If you cannot pass all three tests, you are at a symptom, not a root cause. Keep digging.

Which RCA method should I use?

5-Why for simple, single-cause problems (quick, good for daily use). Fishbone for complex problems with multiple potential cause categories (structured brainstorming). Is/Is-Not for problems where you need to narrow the field (the defect happens on Shift 1 but not Shift 2. Why?). Fault Tree for safety-critical or high-consequence failures requiring exhaustive analysis.

Share this guide: LinkedIn X Follow SymplProcess on LinkedIn

Take this to a room

The running order

For investigators. They should leave able to pick between four methods and to apply the three root cause tests.

7 beats · 12 min
  1. 1

    Four methods, four situations

    Using the same method for everything is why some investigations take a week and produce nothing.

    • 5-Why: fast, single-cause, recent problems.
    • Fishbone: many possible causes, unclear direction.
    • Is/Is-Not: the problem occurs selectively: some shifts, some machines, some parts.
    • Fault tree: safety-critical, combinations of failures.

    Ask the room What method did we use last time, and was it the right one?

  2. 2

    Three 5-Why pitfalls

    It is the easiest method to run and the easiest to run badly.

    • Stopping too early: the operator used the wrong speed is Why 1, not a root cause.
    • The blame trail: if every why ends in because the operator did not, you are finding human error, not system failure.
    • Single path: branch when a why has more than one valid answer.
  3. 3

    Fishbone covers the dimensions you were not going to check

    Six M's, and their value is that they force breadth.

    • Man, machine, material, method, measurement, environment.
    • Left to ourselves we investigate the two categories we already suspect.
    • The empty branches are often where the answer was.
  4. 4

    Is/Is-Not narrows a selective problem

    When something happens on one shift and not another, the contrast is the data.

    • What is affected, and what equally could have been but was not?
    • Where, when, and to what extent, and the matching is-not for each.
    • The difference between the two columns contains the cause.

    Ask the room Does our problem happen everywhere, or selectively?

  5. 5

    Fault trees for safety-critical work

    Exhaustive, top-down, and worth the effort only when the consequence justifies it.

    • Start from the undesired event and work down through AND and OR gates.
    • It finds combinations of failures that no single-cause method would reach.
    • Slow and expensive. Correct for the events where that is the right trade.
  6. 6

    Three tests for a root cause

    Apply all three before you accept an answer. They take a minute.

    • Remove the cause: does the problem stop?
    • When the cause is present, does the problem always occur?
    • Is the logical chain from cause to effect clear, without a leap?

    Ask the room Would our last root cause pass those three?

  7. 7

    The engine behind everything else

    Every improvement tool on this site depends on the root cause being right.

    • Wrong root cause means the countermeasure is decoration.
    • And the problem returns, which erodes belief in the whole system.
    • Verify before you act, and verify again after.

    Ask the room Which recurring problem here has never had a verified root cause?