Root cause analysis for quality management
The main root cause analysis methods — what each is good for, where each falls short, and how to choose the right one for the problem.
Root cause analysis (RCA) is how corrective action moves from firefighting to prevention. No single method fits every problem: 5 Whys suits simple, linear issues; fishbone diagrams organize many possible causes; FMEA anticipates failure before it happens; Pareto focuses effort; fault tree analysis suits complex, safety-critical systems. This guide helps you match method to problem.
- Corrective actions treat symptoms, not causes
- The same problems keep recurring
- You need to choose an appropriate RCA method
- You want analysis that leads to real prevention
5 Whys
Repeatedly asking why traces a problem back to its underlying cause. Fast and accessible, but it can oversimplify complex issues.
- Best for straightforward, single-cause problems
- Quick to run with the people who know the process
- Risk: stopping too early or following one biased path
Fishbone (Ishikawa) diagrams
A fishbone organizes potential causes into categories, useful when a problem could have many contributing factors.
- Best when causes span people, process, materials, and more
- Great for team brainstorming and shared understanding
- Needs evidence to confirm which causes actually matter
FMEA and fault tree analysis
FMEA anticipates how a process or product could fail and prioritizes prevention; fault tree analysis models how combinations of failures lead to an event.
- FMEA: proactive, ranks failure modes by severity and likelihood
- Fault tree: suits complex, safety-critical systems
- Both require discipline and cross-functional input
Pareto analysis
Pareto analysis identifies the vital few causes responsible for most of the problems, so effort goes where it has most impact.
- Best when you have data on frequency or cost
- Directs limited resources to the biggest drivers
- Pairs well with a deeper method on the top causes
- Using 5 Whys for genuinely complex, multi-cause problems
- Brainstorming causes without confirming them with evidence
- Stopping at a symptom that feels like a cause
- Producing analysis that never turns into corrective action
From root cause to owned action
Whatever method you use, Cogliva helps you turn findings into owned corrective actions connected to objectives and review, and spot recurring patterns over time. Cogliva supports analysis and follow-through; it does not replace human investigation and judgment.
Keep exploring
Related guides
Product & method
Frequently asked questions
What is root cause analysis?
Root cause analysis is a structured approach to finding the underlying cause of a problem so it can be prevented, rather than just treating the symptom. It underpins effective corrective action in a quality management system.
Which root cause analysis method should we use?
Match the method to the problem: 5 Whys for simple issues, fishbone for many possible causes, FMEA to anticipate failures, Pareto to focus on the biggest drivers, and fault tree analysis for complex, safety-critical systems.
Does ISO 9001 require a specific RCA method?
No. ISO 9001 requires you to determine the causes of nonconformities and act to prevent recurrence, but it does not prescribe a method. Choose the technique that fits the problem and your capability.
Find causes, prevent recurrence
Choose the right method, confirm with evidence, and turn findings into action.