Definition
Root cause analysis examines the event sequence, technical evidence, and organizational contributors. Its goal is an evidence-based explanation and an action that meaningfully reduces recurrence risk.
Key facts
- The first visible failure is not automatically the root cause.
- Facts, timeline, and operating conditions should come before hypotheses.
- Methods such as 5 Whys or fishbone diagrams structure analysis but do not replace evidence.
- Actions need an owner, due date, and effectiveness review.
What does Root cause analysis (RCA) reveal about failures?
A useful problem statement describes the deviation, location, timing, frequency, and impact. A broad statement or one that already assumes a cause sends the analysis in the wrong direction.
How do teams use Root cause analysis (RCA) in failure analysis?
Data, damaged components, photos, alarms, and interviews are connected in a timeline. Potential causes are tested against observations rather than selected only because they sound plausible.
What can make Root cause analysis (RCA) misleading?
Effective actions change technical or system conditions. Training and reminders may support them but are rarely enough when design, material, or process conditions enable the failure.