Root Cause Analysis
Also known as: Cause-and-Effect Analysis, Fishbone Analysis, Ishikawa Diagram, Kök Neden Analizi
Root Cause Analysis (RCA) is a structured, systematic method for identifying the fundamental causes of defects, failures, or undesirable outcomes rather than treating surface-level symptoms. Popularised by Japanese quality engineer Kaoru Ishikawa in the 1960s–1980s, and formally codified in his 1986 Guide to Quality Control, RCA combines the Ishikawa (fishbone) diagram with the iterative 5 Whys questioning technique to trace causal chains back to their origin.
Key highlights
- Provides a visual, structured framework that aligns cross-functional teams around a shared causal picture
- Combines qualitative brainstorming (fishbone) with iterative questioning (5 Whys), making it accessible without statistical software
- Drives permanent corrective actions by targeting systemic causes rather than symptoms
- Widely recognised across ISO, Six Sigma, and lean methodologies, facilitating communication with auditors and partners
Intuition
This section is available to Pro members. Upgrade to Pro
How it works
This section is available to Pro members. Upgrade to Pro
When to use it
RCA is most valuable when a recurring defect, incident, or quality failure demands a permanent fix rather than a quick patch. It suits manufacturing, healthcare, software, and service operations contexts. The method assumes team members have sufficient process knowledge to propose and evaluate causes. It is less suited to novel, highly complex systems where causal chains are deeply non-linear; in such cases Fault Tree Analysis or systems-thinking approaches may be preferable. RCA works best when conducted close in time to the event while evidence is fresh.
Strengths & limitations
- Provides a visual, structured framework that aligns cross-functional teams around a shared causal picture
- Combines qualitative brainstorming (fishbone) with iterative questioning (5 Whys), making it accessible without statistical software
- Drives permanent corrective actions by targeting systemic causes rather than symptoms
- Widely recognised across ISO, Six Sigma, and lean methodologies, facilitating communication with auditors and partners
- Highly dependent on participants' process knowledge; gaps in expertise lead to missing cause branches
- The 5 Whys can follow different causal chains depending on who asks, potentially yielding inconsistent root causes across sessions
- Does not quantify the relative contribution of each cause, making prioritisation subjective
- Ill-suited to problems with multiple interacting, non-linear causes that defy simple chain-of-causation logic
Common pitfalls
This section is available to Pro members. Upgrade to Pro
Applications
This section is available to Pro members. Upgrade to Pro
Frequently asked
How is Root Cause Analysis different from a simple brainstorming session?
Brainstorming generates ideas without structure or causal discipline. RCA imposes a directional causal framework — the fishbone diagram ensures all major domains are examined, and the 5 Whys ensures the team drills down to underlying rather than surface causes. The result is a traceable causal chain validated against evidence, not merely a list of possibilities.
Must teams always ask exactly five 'whys'?
No. Five is a practical heuristic introduced by Taiichi Ohno, not a strict rule. Some problems require three iterations; complex technical failures may require seven or more. The criterion is reaching a cause that is actionable and whose removal would prevent recurrence, regardless of the iteration count.
Can Root Cause Analysis be used alongside Six Sigma DMAIC?
Yes, and it frequently is. Within the DMAIC framework, RCA tools are deployed in the Analyze phase to identify the vital few root causes before solutions are designed in the Improve phase. The fishbone diagram and 5 Whys complement statistical tools such as regression and hypothesis testing by generating the hypotheses that quantitative analysis then evaluates.
Sources
- 1.Ishikawa, K. (1986). Guide to Quality Control (2nd ed.). Asian Productivity Organization.ISBN 978-92-833-1036-7
You have read it. What now?
Cite this page
ScholarGate. (2026, June 2). Root Cause Analysis. ScholarGate. https://scholargate.app/quality-management/root-cause-analysis