Root cause analysis (RCA) is the disciplined process of identifying the fundamental reason a problem occurred so that effective corrective and preventive actions can be developed. Without proper RCA, organizations end up treating symptoms — retraining workers, issuing reminders, posting new signs — while the same problems continue to recur.
Why Surface-Level Fixes Fail
Common Root Cause Analysis Methods
5 Whys
The simplest and most widely used RCA method. Start with the problem and ask “why?” repeatedly (typically five times) until you reach a systemic cause. Best suited for straightforward problems with a single causal chain.
Example: A worker slipped on a wet floor → Why? A pipe was leaking → Why? The gasket failed → Why? The gasket was past its replacement interval → Why? Preventive maintenance was not scheduled → Why? The equipment was not entered in the PM system. Root cause: Incomplete equipment inventory in the preventive maintenance program.
Fishbone (Ishikawa) Diagram
Organizes potential causes into categories — typically People, Process, Equipment, Materials, Environment, and Management — branching off a central “spine” that points to the problem. Effective for complex problems with multiple contributing factors.
Best for: Team brainstorming sessions, problems with multiple contributing causes, situations where you need to explore all potential factors before narrowing down.
Fault Tree Analysis (FTA)
A top-down, deductive approach that uses Boolean logic (AND/OR gates) to map all possible combinations of events that could lead to the undesired outcome. Particularly useful for safety-critical systems where multiple failures must coincide for an incident to occur.
Best for: Complex system failures, process safety events, situations where multiple barriers failed simultaneously.
Barrier Analysis
Examines the controls (barriers) that should have prevented the problem and asks why each one failed. Barriers can be physical (guards, interlocks), procedural (permits, checklists), or administrative (training, supervision). Pairs naturally with the hierarchy of controls.
Best for: Incident investigations where existing safeguards were in place but failed to prevent harm.
Change Analysis
Compares current conditions against a time when the problem did not exist and identifies what changed. Effective when a previously stable process begins producing nonconformities or incidents.
Best for: Problems that emerged after a change in personnel, equipment, materials, procedures, or environment.
Choosing the Right Method
RCA Best Practices for EHS Teams
- Start early — begin the investigation within 24 hours while evidence and memories are fresh
- Involve the right people — include workers who perform the task, supervisors, maintenance, and subject matter experts
- Focus on systems, not blame — asking “why did the system allow this?” rather than “who caused this?”
- Stop at actionable causes — continue asking “why” until you reach a cause that can be addressed with a realistic corrective action
- Document everything — capture the analysis, evidence reviewed, participants, and the logic connecting root cause to corrective action
- Test the logic — read the causal chain in reverse (“therefore”) to verify it makes logical sense
- Link to corrective and preventive actions — every identified root cause should generate at least one tracked action
Ecesis EHS Software Solutions
Task Tracking
Assign, prioritize, and track tasks with automated reminders and dashboards
Incident Management
Report, investigate, and resolve incidents with root cause analysis and CAPA
Inspections & Audits
Schedule inspections, document findings, and generate corrective actions
Compliance Obligations
Track regulatory requirements and link obligations to recurring tasks
Training Management
Manage training assignments, certifications, and competency tracking
Dashboards & Reporting
Real-time KPI dashboards with CAPA status, overdue tasks, and trends
