8.3 Root Cause Analysis Methodologies: 5 Whys, Fishbone (Ishikawa), and Fault Tree

8.3 Root Cause Analysis Methodologies: 5 Whys, Fishbone (Ishikawa), and Fault Tree

When a catastrophic incident or near-miss occurs on a construction project, the visible physical failure is merely the tip of the iceberg. Identifying that an electrical cord shorted out, a worker slipped, or a crane tipped over describes what happened, but fails to explain why it happened. Root Cause Analysis (RCA) is a structured, systematic problem-solving process designed to drill past superficial symptoms to uncover the fundamental management, design, procedural, and organizational failures that allowed the hazard to exist.

Without rigorous RCA, corrective actions focus exclusively on symptoms (such as telling workers to "be more careful" or replacing a single damaged tool), leaving the underlying systemic defect intact to cause future injuries.

---

1. The Causal Hierarchy: Direct, Contributing, and Root Causes

A comprehensive safety investigation organizes causal factors into three distinct operational layers:

┌─────────────────────────────────────────────────────────────┐
│                     THE CAUSAL HIERARCHY                    │
├─────────────────────────────────────────────────────────────┤
│  1. DIRECT / IMMEDIATE CAUSE (The Symptom)                  │
│     • Substandard act or condition immediately preceding    │
│       the energy release (e.g., missing guardrail).         │
├─────────────────────────────────────────────────────────────┤
│                             ▲                               │
│                             │                               │
├─────────────────────────────────────────────────────────────┤
│  2. CONTRIBUTING / INDIRECT CAUSE (The Precondition)        │
│     • Environmental, supervisory, or task conditions that   │
│       set the stage (e.g., poor lighting, schedule rush).   │
├─────────────────────────────────────────────────────────────┤
│                             ▲                               │
│                             │                               │
├─────────────────────────────────────────────────────────────┤
│  3. ROOT / SYSTEMIC CAUSE (The Source)                      │
│     • Flaws in safety management systems, engineering       │
│       design, procurement, policies, or safety culture.     │
└─────────────────────────────────────────────────────────────┘

---

2. The 5 Whys Methodology in Construction RCA

Originally developed by Sakichi Toyoda for the Toyota Production System, the 5 Whys is an iterative interrogative technique used to explore the cause-and-effect relationships underlying a particular problem. By repeatedly asking "Why?" (typically five times), investigators drill down through successive symptomatic layers to identify root causes.

┌─────────────────────────────────────────────────────────────┐
│          PRACTICAL 5 WHYS CONSTRUCTION WALKTHROUGH          │
├─────────────────────────────────────────────────────────────┤
│  PROBLEM STATEMENT: A masonry laborer fell 14 feet from a   │
│  supported scaffold deck, fracturing both legs.             │
├─────────────────────────────────────────────────────────────┤
│  WHY 1: Why did the worker fall from the scaffold?          │
│  ➔ Because the end-frame guardrail was missing.             │
├─────────────────────────────────────────────────────────────┤
│  WHY 2: Why was the end-frame guardrail missing?            │
│  ➔ Because the crew removed it to load pallets of cinder    │
│     blocks with a telehandler and did not reinstall it.     │
├─────────────────────────────────────────────────────────────┤
│  WHY 3: Why was the guardrail removed instead of using a   │
│         designated scaffold loading gate?                   │
│  ➔ Because the scaffold was erected without loading gates.  │
├─────────────────────────────────────────────────────────────┤
│  WHY 4: Why was the scaffold erected without loading gates? │
│  ➔ Because the Competent Person scaffold builder was not    │
│     provided the site-specific loading plan prior to setup. │
├─────────────────────────────────────────────────────────────┤
│  WHY 5: Why was the plan not provided to the builder?       │
│  ➔ ROOT CAUSE: The project lacks an integrated Subcontractor│
│     Pre-Task Planning & Scaffold Permitting System to review│
│     scaffold engineering drawings before material loading.  │
└─────────────────────────────────────────────────────────────┘

Rules for Effective 5 Whys Execution

• Base Answers on Facts, Not Speculation: Every "Why" answer must be supported by physical evidence, witness statements, or documentation.
• Avoid Single-Track Tunnel Vision: Real-world incidents often have multiple parallel causal chains. If a question has more than one plausible answer, branch the analysis into a multi-legged 5 Whys tree.
• Stop at Actionable Systemic Roots: Stop when you reach an organizational system, policy, or engineering control that management has the authority to rectify.

---

3. The Fishbone (Ishikawa / 6 Ms) Cause-and-Effect Diagram

Developed by Dr. Kaoru Ishikawa, the Fishbone Diagram provides a visual, structured framework to brainstorm and categorize all potential causal factors contributing to a safety event. In construction and heavy industry, causal branches are organized using the 6 Ms Framework (or its operational equivalent, PEEM: People, Equipment, Environment, Methods):

┌─────────────────────────────────────────────────────────────────────────┐
│                         ISHIKAWA 6 Ms FISHBONE                          │
│                                                                         │
│   MANPOWER (People)         MACHINERY (Equipment)       METHODS         │
│       \                         \                         \             │
│        \ Inadequate Training     \ Hydraulic Seal Leak     \ No JHA     │
│         \ Fatigue / 12hr Shift    \ Outrigger Sensor Bad    \ Rush Sched│
│          ───────────────────────────┬─────────────────────────          │
│                                     │                          INCIDENT │
│                                     │                         ════════> │
│          ───────────────────────────┴─────────────────────────          │
│         / Low SBC Soil            / Non-Rated Slings        / Uncalib.  │
│        / Heavy Rain / Mud        / Missing Safety Latches  / Gauge      │
│       /                         /                         /             │
│   MILIEU (Environment)       MATERIALS                 MEASUREMENT      │
└─────────────────────────────────────────────────────────────────────────┘

Detailed Breakdown of the 6 Ms in Construction Investigations

1. Manpower / People: Human factors, training qualifications, experience level, physical/mental fatigue, situational awareness, communication barriers, supervision oversight.
2. Machinery / Equipment: Mechanical integrity, maintenance history, safety devices (LMIs, GFCIs, emergency e-stops), equipment capacity ratings, proper machine selection for the task.
3. Methods / Procedures: Site-Specific Safety Plans (SSSPs), standard operating procedures (SOPs), Job Hazard Analyses (JHAs), permitting workflows, pre-task briefings, contractor coordination.
4. Materials: Material specifications, structural integrity, packaging, chemical hazard data (SDSs), rigging hardware ratings, defective structural components.
5. Measurement / Inspection: Calibration of testing instruments (4-gas atmospheric monitors, torque wrenches), pre-shift equipment inspection logs, soil compaction testing, surveyor grade stakes.
6. Milieu / Environment: Weather conditions (wind, rain, extreme cold/heat), ambient lighting, ground bearing capacity, noise levels, congested workspace, overhead power lines.

---

4. Fault Tree Analysis (FTA) & Causal Factor Charting

For complex incidents involving interactions between mechanical failures, computerized control systems, and human actions, advanced safety engineering tools provide rigorous logic modeling.

Fault Tree Analysis (FTA)

FTA is a top-down, deductive failure analysis method that uses Boolean logic gates to break down an undesired "Top Event" (e.g., Crane Boom Structural Collapse) into its constituent sub-system failures:

┌─────────────────────────────────────────────────────────────┐
│               FAULT TREE ANALYSIS LOGIC GATES               │
├──────────────────────────────┬──────────────────────────────┤
│  AND GATE (Both Required)    │  OR GATE (Any Single One)    │
│                              │                              │
│             ┌───┐            │             ┌───┐            │
│             │AND│            │             │ OR│            │
│             └───┘            │             └───┘            │
│             /   \            │             /   \            │
│       Event A   Event B      │       Event A   Event B      │
│                              │                              │
│  OUTPUT OCCURS ONLY IF BOTH  │  OUTPUT OCCURS IF EITHER     │
│  EVENT A AND EVENT B OCCUR!  │  EVENT A OR EVENT B OCCURS!  │
└──────────────────────────────┴──────────────────────────────┘

• AND Gate: Represents a condition where the top event occurs only if all input events happen simultaneously (e.g., Boom collapses only if Crane is Overloaded AND LMI Computer Overload Cutout Fails).
• OR Gate: Represents a condition where the top event occurs if any single input event happens (e.g., Trench collapses if Soil Shears Due to Rain OR Excavator Surcharge Surcharges Trench Lip OR Vibration from Road Traffic Liquefies Soil).

Causal Factor Charting

Causal Factor Charting maps out the incident chronologically along a horizontal timeline using distinct geometric shapes: Events (rectangles showing actions in sequence) connected by directional arrows, with Conditions (ovals showing environmental or systemic states) feeding into each event. This visual sequence clearly illustrates where defensive barriers failed or were missing.

---

Practical Field Scenario: Structural Steel Erection Collapse RCA

During steel erection on an 8-story building, a 45-foot steel beam weighing 6,500 lbs slipped from a 2-choker wire rope rigging assembly at a height of 60 feet, crushing a mobile generator below. No personnel were injured.

• Direct Cause: Rigging choker hitch was applied at an angle of choke less than 120 degrees without derating capacity, causing the wire rope to slide along the steel flange.
• Contributing Causes:
  • High crosswinds ($28\text{ mph}$) caused the suspended beam to oscillate.
  • Ironworkers were using synthetic web slings on sharp steel edges without softeners or corner protectors.
  • Crew was rushing to complete the bay before a weekend concrete pour.
• Fishbone & 5 Whys Root Causes:
  • Methods: The steel erection subcontractor lacked a written Critical Lift Plan for loads hoisted over $5,000\text{ lbs}$.
  • Manpower: The designated "Rigger" on site had never completed a Qualified Rigger training program under 29 CFR 1926.1404 / 1926.1425.
  • Management System: General contractor had no qualification verification process in place to verify subcontractor rigger credentials before issuing site work badges.

---

Common Exam Traps & Pitfalls

• Trap 1: Confusing Direct Causes with Root Causes. If an answer choice states "The worker did not wear a hard hat," that is an immediate substandard act/condition, not a root cause. Root causes address why the safety management system permitted the condition.
• Trap 2: Misinterpreting Fault Tree AND vs. OR Gates. An AND gate requires every single input condition to occur for the top event to happen; an OR gate triggers the top event if any one input occurs.
• Trap 3: Assuming 5 Whys is Always Exactly Five Steps. "5 Whys" is a naming convention; some analyses reach the root cause in 3 questions, while complex systems may require 7 or 8 iterations.
• Trap 4: Treating the Fishbone Diagram as a Linear Timeline. Fishbone diagrams are category-based brainstorming tools (6 Ms), whereas Causal Factor Charting is chronological.