Root Cause Analysis Tool Selection — When to Use 5Why, Fishbone Diagram, FTA, and Pareto, and How to Combine Them

1. Too Many Root Cause Analysis Tools, Making Selection Difficult

When a problem arises on the shop floor, some people use 5Why, others draw fishbone diagrams, and still others want to apply FTA (Fault Tree Analysis)—a 2-hour meeting, and the walls are covered with paper, yet the root cause remains unclear, whether it is "human" or "system".

Root cause analysis is not a tool competition, but rather using appropriate methods for problems of suitable complexity. This article provides a selection decision tree, combined usage methods, and output standards to help quality engineers and team leaders reduce meetings, clarify causes, and implement corrective actions.

2. Quick Overview of Common Tools

3. Selection Decision Tree (Text Version)

Problem has occurred
  ├─ Is it related to recent changes? → Yes → Change analysis + timeline
  └─ No → Can defects/phenomena be categorized and statistically analyzed?
         ├─ Yes → Pareto/stratification → Top1 phenomenon into 5Why or fishbone
         └─ No → Is it related to safety/regulations/multiple system failures?
                ├─ Yes → FTA or fishbone + verification
                └─ No → Is the team ≥4 people and the cause unknown?
                       ├─ Yes → Fishbone brainstorm → Vote for Top3 → 5Why verification
                       └─ No → 5Why (at least 3 layers, to actionable system cause)

Stopping Rule: Stop 5Why at the level where process/equipment/standards can be changed, not at "human error."

4. Recommended Combined Approaches

4.1 Quick Line Events (<4h)

Pareto to identify defect patterns → 5Why × 3 → Temporary containment + whether to escalate to 8D

4.2 Cross-departmental Repeated Issues

Fishbone (5M1E) → Consolidate repeated branches → 5Why for Top2 branches → Countermeasure matrix

4.3 Customer Complaints / Safety

IS/IS NOT to define → FTA or fishbone → Experimental verification of hypotheses → 8D D4

4.4 Chronic Waste (Non-defect)

Value stream + cycle time → Changeover/waiting/rework stratification → Lean tools, no need to force FTA

5. Output Quality Standards

Regardless of the tool used, D4/root cause section must meet the following criteria:

1. Verifiable: Can be confirmed or negated through data or experiments
2. Actionable: Countermeasures correspond to processes, standards, and poka-yoke, not just "training"
3. Clear primary cause or combination of primary causes: Avoid listing "five causes" without prioritization
4. Distinguish root cause from trigger: Root cause is long-standing, trigger is when it is exposed

6. Common Pitfalls in 5Why

• Each layer lacks evidence (only guesses)
• Multiple Why questions mixed in the same layer
• Stopping at the second layer (human) without questioning the system
• Contradictory conclusions with fishbone without explanation

Tip: After each layer's answer, ask "How can we prove it?"

7. Common Pitfalls in Fishbone Diagrams

• Omission of categories (often missing Measurement/Management)
• Unclear verbs on branches (e.g., "poor management")
• No voting to focus on top branches, leading to scattered countermeasures

8. Interface with 8D, QRQC, and FMEA

• QRQC Rapid Response: Default to shallow 5Why; after escalating to 8D, D4 can switch to fishbone/FTA
• FMEA Update: If root cause involves failure modes, update RPN
• LL Library: Verified 5Why chains can be templated

9. Training and Certification Recommendations

• Team Leaders: 5Why + Pareto (1 day)
• Quality Engineers: Fishbone + IS/IS NOT + Change Analysis (2 days)
• Safety/Reliability: FTA Introduction (specialized)
• Internal Root Cause Review Meetings: Randomly select 8D D4, score using the checklist in this article

10. Checklist (for Review)

11. Quick Reference for Manufacturing Scenarios

12. Meeting Time Boxes

• QRQC Rapid Response: Root cause tool ≤30min to set hypotheses, containment first, then deep dive
• 8D D4 Workshop: Fishbone 60min + 5Why verification 90min, two separate meetings are better than a 4-hour marathon

13. MBB's Role in D4 Adjudication

MBB does not participate in guessing causes but reviews: whether the tool is appropriate, whether data supports, whether verified, and whether countermeasures target the root cause. Commonly uses the "So what?" three-question technique to push the team to the system level.

14. Digital Tools Considerations

FMEA software, 8D systems, and mind mapping tools cannot replace methodology. Online fishbone diagrams must export meeting conclusions and be version-controlled; prohibit unmoderated free editing to avoid excessive branching.

15. Appendix: 5Why Record Form Fields

Problem description / Why1 + evidence / Why2 + evidence / … / Root cause / Countermeasure / Verifier / Date

16. Appendix: Minimum Viable Fishbone Diagram Process

1. Clearly write the Problem in one sentence (30min)
2. Post 5M1E branches without criticism (40min)
3. Each person has 3 votes for top branches (10min)
4. 5Why for Top2 branches (60min)
5. Countermeasure matrix output (20min)

17. Connection with High-Reading "Fishbone Diagram Depth Interpretation"

The Quality Think Tank's QC Seven Tools · Fishbone (408 reads) has already covered drawing techniques; this article supplements when to use, and division of labor with 5Why/8D—it is recommended to train tools first, then selection.

18. Anti-pattern List (Review Rejection Items)

• Starting 5Why without data
• Fishbone branches only write "poor personnel quality"
• Using FTA for known single-point operational errors
• D4 conclusions have no logical link to containment measures
• Countermeasures are only retraining without system changes

19. Series Map (5.2)

This article, along with the 8D × QRQC joint article, 5Why high-reading article, and fishbone in-depth article, forms the "Four-Tool Problem Solving Kit"—covering fast, deep, tools, and joint mechanisms.

20. One-Page Wall Version (Tool Selection)

Repeated? Pareto → 5Why
Unknown cause by multiple people? Fishbone → 5Why
After change? Change analysis
Safety/multiple paths? FTA
Single customer issue? IS/IS NOT → 5Why

Select the right root cause tool, and 8D will not get stuck at D4 for two weeks; select the wrong one, and the fishbone diagram will only become wallpaper in the meeting room.

For complex problems, use the fishbone diagram; for vague phenomena, start with stratification; for single-line processes, use 5Why—don't use all three without completing any.

Knowledge code: 5.2.3

Version: v20260702

Author: Quality Think Tank Quality Think Tank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously improve their quality capabilities.