Root Cause Analysis Tools

Root Cause Analysis Tools

Quick Answer: After gap analysis sizes the shortfall, root cause analysis (RCA) finds underlying process conditions that create the gap. Core Green Belt tools include cause-and-effect (fishbone/Ishikawa) diagrams, 5 Whys, relational matrices, fault tree analysis (FTA), and related problem-solving methods. Tools organize thinking; data and process knowledge still confirm which causes are real.

From Gap to Cause

A quantified performance gap is a symptom of distance from target. Improve actions that only fight symptoms (reinspect, rework, overtime) leave the gap ready to reopen. RCA asks: Which process factors, if changed and controlled, would permanently shrink the gap?

BoK IV.C.2 (Analyze) expects you to select and apply these tools—not only name them.

Cause-and-Effect (Fishbone / Ishikawa) Diagrams

The fishbone places the effect (problem Y or gap statement) at the head and major cause categories as bones. Manufacturing often uses the 6Ms:

Service teams may use 4Ps (Policies, Procedures, People, Plant/technology) or custom categories. Facilitated build:

1. Write a crisp effect (“median complex-claim lead time 7.4 days above target”).
2. Label categories and brainstorm candidate causes without early judgment.
3. Cluster and deepen (ask why under each bone).
4. Prioritize 3–7 high-likelihood, high-impact candidates for data checks (multi-vari, Pareto, tests, later DOE).

Exam trap: A full fishbone is not proof. It is a structured hypothesis generator.

5 Whys — Worked Example

5 Whys drills from the observed problem toward a deeper controllable cause by asking “why?” until further why adds little process insight (often near five times—not a magic count).

Problem: Monthly on-time delivery (OTD) is 87% vs 95% target (gap = 8 points).

1. Why is OTD at 87%? → About 42% of late orders miss the ship window because pick/pack finishes after the carrier cutoff.
2. Why does pick/pack finish after cutoff? → Average pick wave release is 95 minutes later than the schedule requires.
3. Why is release 95 minutes late? → The WMS holds every wave until inventory accuracy checks complete for all SKUs in the wave.
4. Why do accuracy checks delay every wave? → Cycle-count exceptions are cleared only by two day-shift specialists; exceptions queue overnight.
5. Why only that way? → No standard work allows trained leads to clear low-risk exceptions, and exception codes were never stratified by risk.

Root-cause statement (controllable process condition): Low-risk inventory exceptions lack stratified standard work and multi-shift clearance authority, so waves release late and OTD misses target.

Not a root cause: “People don’t care” (blame without process control). Still required: Validate with data (exception volume by code, release-time distribution, OTD by exception type) before large Improve spend.

Good practice: Stay on one causal chain; prefer system causes over person-blaming; stop at a redesignable control point; attach evidence when possible. If a why step jumps to a broad abstraction (“culture”), branch back to a specific process mechanism you can measure.

Relational Matrices

A relational matrix (cause-and-effect matrix / L-matrix style) rates how strongly candidate causes or process inputs relate to effects or CTQs:

• Rows: candidate X’s or steps
• Columns: critical Y’s or requirements
• Cells: relationship scores (e.g., 0, 1, 3, 9)
• Optional weights for Y importance

Purpose: Prioritize which X–Y links deserve measurement when brainstorming produced too many bones. Ranking improves when scores rest on data or expert multi-voting—not pure politics.

Fault Tree Analysis (FTA)

FTA starts from a top event (the failure of interest) and decomposes it with logic gates:

• OR: Any one input can produce the output (parallel failure paths).
• AND: All inputs must occur together (redundant protections fail together).

FTA suits safety, reliability, and multi-path problems. Green Belts often use qualitative trees more than full probabilistic models. Contrast: fishbone is category brainstorming; FTA is logical structure of how basic events combine into the top failure.

Other Problem-Solving Tools

Use the lightest tool that frames the next data question—do not run every tool on every project.

Combining Tools and Exam Focus

1. Quantify the gap.
2. Map the process and stratify where the gap appears.
3. Fishbone/affinity to generate candidates.
4. 5 Whys on the top chains to reach controllable causes.
5. Relational matrix if many X’s compete.
6. FTA when combination logic matters.
7. Confirm with data before Improve.

Pitfalls: stopping at the first convenient why; treating the longest fishbone as truth; person-only causes; team consensus without validation; misusing OR/AND or over-applying FTA.

Expect items that distinguish fishbone vs. 5 Whys vs. FTA, choose the next why step, treat diagrams as hypotheses, read matrix priority, and phrase root causes as controllable process conditions tied to the gap.

Bottom line: Gap analysis tells you how far; RCA tools help you find why—then data proves it before Improve capital is spent. A Green Belt who can size the gap, structure candidates, drill to a controllable cause, and demand confirmation is doing Analyze at the BoK level the exam expects.