5-Whys vs Fishbone vs TapRoot: The Right Root Cause Method for Each Investigation

Pick the wrong root cause analysis (RCA) technique and your "corrective action" fixes a symptom instead of a cause. Six months later the same incident happens, with a different name.

This guide compares the three most-used RCA methods — 5-Whys, Fishbone (Ishikawa), and TapRoot — and tells you exactly when to use each.

Why RCA Matters

Per the Bureau of Labor Statistics, 60-70% of corrective actions fail to prevent recurrence of similar incidents. The number one reason: shallow root cause analysis. The investigator stopped at "operator didn't follow procedure" instead of asking why the procedure was unfollowable, why training was inadequate, or why supervision was absent.

Strong RCA gets you to the systemic cause. Weak RCA gets you to the human to blame.

Method 1: 5-Whys

What it is

A structured questioning technique where you ask "why?" iteratively until you hit a systemic cause, typically 5 levels deep.

Example

Incident: Worker slipped on wet floor in warehouse.

1. Why? Floor was wet.
2. Why? A pipe was leaking overhead.
3. Why? The pipe joint failed.
4. Why? Joint hadn't been inspected in 18 months.
5. Why? No PM schedule existed for warehouse plumbing.

Root cause: Missing preventive maintenance program for utility infrastructure. Corrective action: Establish PM schedule for all warehouse utilities, with monthly inspections.

When to use 5-Whys

• Single-cause incidents with a clear linear chain
• Fast investigations (less than 1 hour)
• Frontline-led investigations where complexity should be low
• Near-miss reviews

When NOT to use 5-Whys

• Complex incidents with multiple contributing factors
• Process-safety events (use TapRoot or HAZOP review)
• Anything involving cultural/organizational factors

Common mistakes

1. Stopping at 3 whys (too shallow)
2. Going past 5 into speculation (too deep)
3. Single linear chain when multiple causes existed
4. Blaming the operator at why #2 ("wasn't paying attention") and stopping

Method 2: Fishbone (Ishikawa) Diagram

What it is

A visual brainstorming tool that organizes potential causes into categories (commonly: People, Process, Equipment, Environment, Materials, Management). The fish "head" is the problem; the "bones" are categories of causes.

Example

Incident: Recurring quality defects in welds.

People: Welder turnover, inconsistent training across shifts Process: WPS not consistently followed, no in-process inspection Equipment: Aging welding machines, no calibration program Environment: Drafty work area Materials: Inconsistent filler metal supplier Management: No quality KPI by welder, no feedback loop

The diagram exposes six contributing factor families, not a single root cause. You then prioritize which to address first.

When to use Fishbone

• Recurring problems (where 5-Whys keeps finding the same surface cause)
• Quality issues with multiple contributing factors
• Cross-functional problems (production, quality, safety, maintenance)
• Brainstorming sessions with 4-10 participants

When NOT to use Fishbone

• Simple, single-cause incidents (overkill)
• Time-pressured investigations under 30 minutes
• Solo investigations (loses the brainstorming benefit)

Common mistakes

1. Treating the fishbone diagram as the answer (it's a brainstorm, not a conclusion)
2. Skipping prioritization after building the diagram
3. Not validating brainstormed causes with data

Method 3: TapRoot

What it is

A structured, expert-driven RCA system with a defined methodology, tree-based root cause maps, and corrective action library. Originally developed for the nuclear industry, now widely used in oil & gas, chemicals, and aviation.

Example workflow

1. Snapchart: Build a chronological event sequence with conditions
2. Causal factors identified at each event/condition that, if absent or different, would have prevented the outcome
3. Root Cause Tree: For each causal factor, walk the standardized tree (Equipment Difficulty → Auditing → SPAC Not Used) to identify root causes
4. Generic causes identified (e.g., "Procedures Not Used Right" → "Wrong Procedure")
5. Corrective actions drawn from the linked corrective action library

When to use TapRoot

• High-severity events: fatalities, major equipment damage, environmental releases
• Process safety incidents under OSHA PSM or ISO 45001 management of change scope
• Events with regulatory or legal scrutiny
• Industries where defensibility of the RCA matters (energy, aviation, chemicals)

When NOT to use TapRoot

• Minor incidents (massively over-engineered)
• Anyone untrained (TapRoot requires formal certification to use well)
• Time-pressured investigations under 8 hours

Common mistakes

1. Using TapRoot for low-severity events (overkill creates documentation theater)
2. Untrained users misclassifying causal factors
3. Treating the corrective action library as a menu instead of customizing to context

Choosing the Right Method (Decision Matrix)

How EHS Software Supports RCA

Modern incident management platforms embed RCA workflows:

• 5-Whys digital templates with mandatory depth enforcement
• Fishbone diagram builders with category libraries by industry
• TapRoot integration (paid add-on for some platforms)
• Auto-link RCA findings to corrective actions
• Track corrective action close-out and effectiveness verification
• Trend analysis: which root causes recur across incidents?

Spreadsheet-based RCA loses traceability. Software-based RCA enables trend analysis — finding the root causes that show up repeatedly across your operation, which is where the highest-value interventions live.

RCA Anti-Patterns to Avoid

1. "Operator error" as root cause. Almost always wrong. Operator error is a symptom — ask why the system allowed it.
2. Single-shot corrective action. "We'll add it to the toolbox talk" rarely changes behavior. Stack 2-3 controls.
3. No effectiveness verification. A corrective action without verification at 30/90/180 days is a wish.
4. Investigating only what you can fix cheaply. RCA should expose systemic causes — even when the fix is hard.

FAQs

Which method is best for OSHA-required investigations?

OSHA doesn't mandate a specific RCA technique, but it requires documented investigation depth. 5-Whys is the floor for recordables; TapRoot or equivalent for serious injury/fatality events.

Can I combine methods?

Yes. A common pattern: Fishbone for brainstorming all contributing factors, then 5-Whys on each branch to drill down. Use whatever combination produces the most actionable findings.

How long should an RCA take?

• 5-Whys: 30-90 minutes
• Fishbone: 90-180 minutes (with cross-functional team)
• TapRoot: 8-40 hours, depending on event severity

Do I need formal RCA training?

For 5-Whys and Fishbone, internal training is sufficient. For TapRoot, formal certification ($1,500-$3,000/person) is effectively required to use it well.

How do I know my corrective actions are working?

Verify effectiveness at 30, 90, and 180 days post-implementation. Look at incident recurrence, leading indicators (observation findings, near misses) in the same area, and worker feedback. Software with built-in CA effectiveness tracking makes this routine.

---

Looking for incident management software with built-in RCA? Take our Get Matched quiz — we'll suggest 3 platforms based on your industry and incident severity profile.