Definition
Root cause analysis (RCA) is a structured process for identifying the underlying cause of a problem so that corrective action prevents recurrence — not just the next occurrence of the symptom. In a quality system, RCA is the investigative core of the corrective and preventive action (CAPA) process and is triggered by nonconformances (NCRs), customer complaints, audit findings, and internal quality events.
The discipline matters because surface-level fixes (rework, re-train, re-inspect) don't change the system that produced the failure. A proper RCA distinguishes occurrence causes (why the defect happened) from detection causes (why it wasn't caught), and treats both. For the documented follow-through after the investigation, use a structured corrective action plan template.
Common RCA methods
5 Whys
Iteratively asks "why" — typically five times — to drill from the visible symptom down to a process or system cause. Lightweight, fast, and effective for single-thread failures and lower-severity issues. Best paired with a reverse test: if removing the proposed cause would have prevented the defect, the cause is plausible.
Fishbone (Ishikawa) Diagram
A cause-and-effect brainstorming structure organized around the 6Ms: Man, Machine, Method, Material, Measurement, Environment. Useful early in an investigation when many candidate causes need to be surfaced and grouped. A fishbone is a brainstorming aid, not a conclusion — candidates must still be validated with data.
8D (Eight Disciplines)
A formal corrective-action methodology used heavily in automotive and other regulated industries. The eight disciplines run from forming a cross-functional team (D1) through interim containment (D3), root cause (D4), permanent corrective actions (D5), validation (D6), prevention via FMEA / control plan / SOP updates (D7), and team recognition (D8). 8D is the standard response format for many OEM customer complaints.
Other methods worth knowing
- Fault tree analysis (FTA) — top-down, deductive analysis for safety-critical failures.
- Pareto analysis — for prioritizing where to focus when many defects compete for attention.
- FMEA — preventive sibling of RCA; identifies failure modes before they occur.
- DOE (Design of Experiments) — used to confirm causes and screen factors when data alone is ambiguous.
When to use RCA
- A nonconformance (NCR) is opened — internal or supplier.
- A customer complaint or field failure is received.
- An audit finding (internal, customer, or registrar) requires corrective action.
- Process performance metrics drift outside control limits.
- A safety incident, near-miss, or environmental deviation is reported.
- A repeat defect emerges — usually a sign that previous corrective action wasn't effective.
Match the method to the severity. A quick 5 Whys may be enough for a low-impact, one-off issue. A customer-driven complaint in automotive almost always demands an 8D. Repeat or systemic problems usually need a fishbone to map the territory before a focused root cause investigation.
Industries that use RCA
- Automotive — IATF 16949 suppliers; 8D is the de facto response format for OEM complaints.
- Aerospace & defense — AS9100; corrective action and read-across are tightly enforced.
- Medical devices & pharma — FDA 21 CFR 820, ISO 13485; CAPA effectiveness verification is heavily audited.
- Energy, oil & gas, utilities — incident investigations and regulatory reporting (OSHA, EPA, sector regulators).
- Food & beverage — FSMA, BRCGS, SQF; deviations from HACCP critical control points trigger RCA.
- Manufacturing & electronics — ISO 9001 and customer-specific quality programs.
- Healthcare — sentinel-event investigations and patient-safety reviews.
- IT, software & SRE — post-incident reviews and blameless postmortems borrow directly from RCA.
Get started
The fastest way to put this into practice is to use a structured template. All four templates on this site are aligned with the workflows above and ship in Word and PDF.