There are five root cause analysis tools that every quality professional should know. Each one solves a slightly different problem. Choose the wrong tool and you’ll spend hours on a process that produces the wrong kind of answer. This guide explains all five, shows when to use each, and gives you a decision framework you can apply immediately.
Quick comparison: all five RCA tools at a glance
| Method | Type | Speed | Team size | Best for | Free tool |
|---|---|---|---|---|---|
| 5 Whys | Reactive | 15–30 min | 1–4 | Simple to medium problems with a clear trigger | Yes → |
| Fishbone | Reactive | 30–60 min | 4–10 | Complex problems with many possible causes | Yes → |
| Fault Tree | Reactive | Hours–days | 2–5 experts | Safety-critical failures, quantitative analysis | No |
| FMEA | Proactive | Days–weeks | Cross-functional | Preventing failures before they happen | Coming soon |
| Pareto | Prioritization | 30–60 min | 1–3 | Ranking which problems to tackle first | Coming soon |
Notice that four of the five tools are reactive — you use them after something goes wrong. FMEA is the exception: it is a proactive tool designed to prevent failures before they occur. Pareto is neither reactive nor proactive in the pure sense — it is a prioritization tool that helps you decide where to focus your other RCA efforts.
1. The 5 Whys method
5 Whys
Invented by Sakichi Toyoda · Used in: Lean, Six Sigma, Agile, DevOps
Ask “Why did this happen?” five times in sequence. Each answer becomes the input to the next question. The chain ends when you reach a cause you can actually fix — the root cause.
The method is deliberately simple. No charts, no formulas, no software required. The Toyota Production System made it famous, and it has spread to virtually every industry that cares about quality. For most everyday problems, 5 Whys is all you need.
Strengths
- No training required
- Done in 15–30 minutes
- Works with small or solo teams
- Produces a clear, actionable root cause
- Naturally resists blame (focuses on process)
Limitations
- Struggles with multi-branch causes
- Depends on team knowledge
- Can stop too early (symptom, not root)
- No quantitative risk assessment
- Biased by whoever asks the questions
Best used when: you have a well-defined problem with a clear trigger event, your team has domain knowledge about the process, and you need an answer in under an hour. It works exceptionally well in Agile retrospectives, Lean stand-ups, and DevOps incident postmortems.
Not ideal when: the problem has many simultaneous causes from different departments, you need to quantify risk, or the failure involves safety-critical systems.
2. Fishbone diagram (Ishikawa / cause-and-effect)
Fishbone Diagram
Invented by Kaoru Ishikawa (1960s) · Also called: Ishikawa diagram, cause-and-effect diagram
Draw the problem at the “head” of a fish skeleton. Branch out to major cause categories (6M, 6P, or custom). Each branch lists possible causes within that category. Sub-causes branch off the main causes. The result is a visual map of every potential contributor to the problem.
Where 5 Whys goes deep on one path, the Fishbone goes wide across many paths simultaneously. It is a brainstorming tool first — it does not identify the root cause, it identifies all candidate causes worth investigating. You then use data or a 5 Whys drill to confirm which one is actually responsible.
Strengths
- Surfaces causes you might miss alone
- Great for cross-functional team sessions
- Visual — easy to present and share
- Prevents premature conclusions
- Works for both simple and complex problems
Limitations
- Lists possibilities, not confirmed causes
- Can produce long, unfocused diagrams
- Requires follow-up analysis (5 Whys, data)
- Dominant voices can skew the session
- Harder to do solo or asynchronously
Best used when: the root cause is not obvious, multiple departments may be contributing, you want team buy-in, or you want to make sure you have not missed anything before drilling deeper. See 5 Whys vs. Fishbone: the full comparison for a detailed side-by-side.
Classic combination: use Fishbone to brainstorm all candidate causes, then run a 5 Whys on the top one or two. This gives you both breadth and depth, and is the approach recommended by ASQ (American Society for Quality).
3. Fault Tree Analysis (FTA)
Fault Tree Analysis
Developed at Bell Labs (1962), adopted by NASA, aerospace, nuclear · Formal engineering method
Start with the top-level undesired event (e.g., “engine failure”). Work downward using Boolean logic: AND gates (all sub-events must occur together) and OR gates (any one sub-event is sufficient to cause the event above). Keep branching until you reach basic events — equipment failures, human errors, or external conditions that cannot be broken down further.
The result is a logical tree diagram that models every possible combination of failures that can lead to the top event. Analysts can then calculate the probability of the top event if they have failure-rate data for each basic event. This is what makes FTA distinct from 5 Whys and Fishbone: it can be quantitative.
Strengths
- Rigorous — captures all failure combinations
- Quantitative when failure data is available
- Industry standard for safety-critical systems
- Identifies “cut sets” (minimal failure combinations)
- Can model both hardware and human failure
Limitations
- Complex — requires formal training
- Time-intensive (hours to weeks)
- Needs specialized software
- Overkill for most operational problems
- Requires reliable failure rate data
Best used when: the failure involves a safety-critical or high-reliability system (aerospace, automotive, medical devices, chemical plants, nuclear), you need to demonstrate compliance with safety standards (IEC 61508, MIL-STD-882), or you need to quantify the probability of a catastrophic event.
Industries that routinely use FTA: aerospace (Boeing, Airbus), automotive (ISO 26262 compliance), pharmaceutical (FDA validation), nuclear power, and medical device manufacturing (ISO 14971).
Not ideal for: everyday quality problems, software bugs, service issues, or any situation where speed matters more than rigor. If you work in manufacturing or healthcare operations rather than system safety engineering, you likely do not need FTA. The Fishbone vs. Fault Tree comparison covers the differences in detail. See also our complete Fault Tree Analysis guide with AND/OR gate examples and minimal cut set analysis.
4. Failure Mode and Effects Analysis (FMEA)
FMEA
Developed by the US military (1949) · Used in: automotive (AIAG), aerospace (SAE), medical devices (ISO 14971)
FMEA is a proactive method. Before launching a product or process, identify every possible way it could fail (failure modes), what would happen if each failure occurred (effects), and how likely and detectable each failure is. Score each failure mode on three dimensions: Severity (S), Occurrence (O), and Detection (D). Multiply to get the Risk Priority Number: RPN = S × O × D. High-RPN items get corrective actions before launch. See our complete FMEA guide for rating scales, full worksheet examples, and DFMEA vs PFMEA.
Unlike every other tool in this list, FMEA is not used after something goes wrong. It is used during the design phase to prevent failures from happening at all. This makes it a fundamentally different kind of tool — not a root cause analysis tool in the traditional sense, but a risk management tool that belongs in the same toolkit.
Strengths
- Prevents failures before they occur
- Produces a quantified risk register (RPN)
- Structured — covers all failure modes
- Required for ISO/TS 16949, IATF 16949, ISO 14971
- Forces cross-functional collaboration
Limitations
- Time-intensive (days to weeks)
- Requires significant process knowledge
- RPN scores can be misleading without calibration
- Does not help after a failure has occurred
- Maintenance-heavy — must be kept current
Our free FMEA / RPN Calculator is coming soon to tools/fmea/.
Best used when: you are designing a new product or process, changing an existing one, or need to demonstrate regulatory compliance. FMEA is mandatory in automotive supply chains (IATF 16949), medical device development (ISO 14971), and many aerospace programs.
FMEA types:
- Design FMEA (DFMEA) — examines potential failures in a product design before prototyping
- Process FMEA (PFMEA) — examines potential failures in a manufacturing or service process before launch
- System FMEA — examines failures at the system level, including interfaces between components
5. Pareto Analysis (80/20 rule)
Pareto Analysis
Based on Vilfredo Pareto’s 1906 observation · Popularized by Joseph Juran for quality management
Collect data on all defects, complaints, or problems over a period of time. Count the frequency of each type. Sort from most frequent to least. Plot as a bar chart with a cumulative percentage line. In most real-world datasets, roughly 80% of the problems come from 20% of the causes. Pareto Analysis makes this visible so you can prioritize where to start your root cause investigation.
Pareto does not find the root cause — that is the job of 5 Whys or Fishbone. What Pareto does is answer a prior question: which problem should we investigate first? Without this step, teams often spend time on noisy, low-impact issues while ignoring the few causes that account for most of the damage.
Strengths
- Focuses limited resources on highest impact
- Data-driven — removes opinion and politics
- Fast to build from existing data
- Easy to communicate to management
- Works for defects, costs, complaints, delays
Limitations
- Requires historical data to be meaningful
- Does not explain why the top issue occurs
- 80/20 split is not universal (can be 70/30)
- Frequency-based — misses high-severity rare events
- Only as good as the data you collect
Try our free Pareto Chart Maker → — enter your defect counts, get an 80/20 chart with vital few callout and PNG export.
Best used when: you have multiple recurring problems and need to decide which to tackle first, you want to show management or a client where to invest improvement effort, or you are working in a DMAIC (Six Sigma) project at the Measure or Analyze phase.
A note on severity vs. frequency: Pareto ranks by frequency by default, but you can also weight by cost, customer impact, or safety risk. A defect that happens rarely but causes catastrophic consequences should rank higher than its raw count suggests. Adjust your Pareto accordingly.
How to choose the right RCA tool
Use these three questions to narrow your choice quickly:
Decision guide
No / planning phase → FMEA
No / multiple problems → start with Pareto to prioritize
| If the problem is… | Use this tool | Why |
|---|---|---|
| Simple, single trigger, clear causal chain | 5 Whys | Fast, no setup, actionable root cause in <30 min |
| Complex, causes unclear, many departments involved | Fishbone then 5 Whys | Fishbone maps the space; 5 Whys drills the winner |
| Safety-critical system failure, needs probability | Fault Tree | Boolean logic, quantitative, meets safety standards |
| Pre-launch risk review, regulatory requirement | FMEA | Proactive, produces RPN risk register |
| Multiple recurring problems, need to prioritize | Pareto first | Identifies the 20% of causes driving 80% of impact |
Using multiple tools together
The best RCA practitioners do not pick just one tool — they sequence them. Here are three battle-tested combinations:
Combination 1: The Lean Six Sigma sequence (DMAIC)
Pareto → Fishbone → 5 Whys. Define the scope with Pareto (which defect costs the most?), brainstorm all causes with a Fishbone in a team session, then drill the most likely candidate with 5 Whys. This is the classic approach in DMAIC Analyze phase and takes 1–3 hours total.
Combination 2: The cross-tool handoff (5 Whys + Fishbone)
Fishbone → 5 Whys → corrective action. Use the Fishbone Diagram Maker to map all possible causes. Click the most likely one to pre-fill the 5 Whys tool for deeper investigation. Both tools on this site support this handoff natively.
Combination 3: The safety engineering approach
FMEA (design) → FTA (system) → 5 Whys (incident). Use FMEA during design to rank and mitigate risks. Use FTA for the most critical failure modes to model all combinations. After any incident that does occur, run 5 Whys on the specific failure path to update both the FMEA and FTA. Common in automotive and medical device industries.
Start your analysis now — free
Both tools below are free, require no signup, and export to PNG. The Fishbone tool pre-fills the 5 Whys tool automatically when you identify a cause worth drilling.
Frequently asked questions
What is the most commonly used root cause analysis tool?
The 5 Whys is the most widely used RCA tool because it requires no special training, no software, and can be done in under 30 minutes. It is the default method in Lean, Six Sigma, and Agile environments. For more complex problems, the Fishbone diagram is the second most popular choice.
What is the difference between 5 Whys and Fault Tree Analysis?
5 Whys is a conversational, qualitative method that traces one causal chain. Fault Tree Analysis (FTA) uses Boolean logic (AND/OR gates) to model all possible combinations of failures leading to a top-level event. FTA is common in aerospace, nuclear, and chemical industries where safety is critical. 5 Whys is faster and accessible to any team; FTA requires engineering expertise and can take days or weeks.
When should I use FMEA instead of 5 Whys?
Use FMEA when you want to prevent failures before they happen — during product design, process design, or system changes. 5 Whys is reactive: you use it after a failure occurs. FMEA is proactive: you use it to identify and rank potential failure modes before they cause problems. If something has already gone wrong, start with 5 Whys. If you are designing a new process and want to anticipate what could go wrong, use FMEA.
Can I use multiple RCA tools on the same problem?
Yes, and this is often the best approach. A common combination is: (1) Pareto Analysis to identify which problem to work on first, (2) Fishbone diagram to brainstorm all possible causes, (3) 5 Whys to drill into the most likely cause. Each tool answers a different question, so combining them gives a more complete picture.
What is the simplest root cause analysis method?
The 5 Whys is the simplest RCA method. It requires no templates, no software, no statistical knowledge, and no special training. Anyone can run a 5 Whys session with a whiteboard and a team in 15 to 30 minutes. The Fishbone diagram is slightly more structured but still simple — you just need sticky notes or a whiteboard.
What is the difference between FMEA and Fishbone diagram?
A Fishbone diagram is used reactively to explore causes of a problem that already occurred. FMEA is used proactively to anticipate and prevent potential failures before they occur. Fishbone maps causes visually across categories; FMEA produces a risk register with Severity, Occurrence, and Detection scores (RPN). Fishbone is qualitative; FMEA is quantitative. Use Fishbone for diagnosis; use FMEA for risk management.
How do Pareto Analysis and 5 Whys work together?
Pareto Analysis (80/20 rule) helps you decide which problem to investigate first by showing which issues cause the most impact. Once you have identified the top problem using Pareto, use 5 Whys to find its root cause. This is a classic Lean Six Sigma sequence: Pareto narrows the focus, 5 Whys finds the fix.
📚 Recommended Reading
- The Lean Six Sigma Pocket Toolbook — George et al. — Covers all five tools with worked examples in a single pocket reference
- Root Cause Analysis Handbook — ABS Group — Deep dive into Fishbone, FTA, and barrier analysis with real case studies
- Beyond the Five Whys — James C. Paterson — Extends 5 Whys with systems thinking for GRC and audit professionals
Related resources
- Root Cause Analysis: A Complete Guide (2026) — the full RCA process from problem statement to corrective action
- 5 Whys vs. Fishbone Diagram: When to Use Which — detailed comparison of the two most popular tools
- Fishbone vs. Fault Tree Analysis — when visual brainstorming meets formal logic
- 7 Common 5 Whys Mistakes (And How to Avoid Them)
- 5 Whys for Incident Investigation: Safety Guide (2026)
- PDCA Cycle: The Complete Guide with Examples — how Plan-Do-Check-Act wraps around RCA tools like 5 Whys and Fishbone
- RCA Examples by Industry — manufacturing, healthcare, software, customer service