News
Jul 24, 2026
8 min read

Five Whys vs Fishbone vs Fault Tree Analysis for Construction Incidents

Choosing the right root cause analysis method improves construction incident investigations. This guide compares Five Whys, Fishbone Analysis, and Fault Tree Analysis, explaining when to use each method, their strengths and limitations, how they support evidence-based investigations, and how to develop effective corrective actions.

Five Whys is best for exploring a relatively simple causal chain, Fishbone Analysis helps teams organise multiple contributing factors, and Fault Tree Analysis is suited to complex events involving interconnected technical or operational failures.

Construction incidents rarely result from one unsafe act. Supervisors may identify the immediate event but miss planning, equipment, communication or management failures. Choosing the wrong analysis method can produce weak corrective actions. Understanding root cause analysis in construction means selecting the tool that matches the incident complexity.

Why Does Root Cause Analysis Matter in Construction?

Incident analysis showing immediate to root causes.

Root cause analysis in construction requires understanding four distinct causal levels:

Immediate Cause: What happened directly (e.g., scaffold moved unexpectedly)

Contributing Factor: What increased the likelihood or severity (e.g., load imbalance, floor unevenness)

Underlying Cause: The organisational or system weakness (e.g., inspection procedure not followed)

Root Cause: A fundamental failure that must be addressed to prevent recurrence (e.g., inspection and handover process not adequately defined)

Investigations should support learning, not worker blame. "The worker failed to follow the procedure" is not normally a complete analysis. Investigators should ask why the behaviour, condition or decision was possible.

OSHA's guidance supports looking beyond surface-level events to equipment, procedures, training and safety-program deficiencies. Professionals responsible for investigations can strengthen these skills through the Incident Investigation / Root Cause Analysis course.

Five Whys vs Fishbone vs Fault Tree: Quick Comparison

Five Whys, Fishbone, and Fault Tree analysis infographic.

Method

Best Suited To

Main Strength

Main Limitation

Five Whys

Simple or moderately complex events

Fast causal questioning

Can oversimplify multi-causal incidents

Fishbone Analysis

Incidents involving several categories of causes

Broad team-based exploration

Generates possible causes that still require verification

Fault Tree Analysis

Serious or technically complex events

Maps logical combinations and failure pathways

Requires more expertise, evidence and time

Use the simplest method capable of explaining the incident without excluding important causal pathways.

AHRQ describes Five Whys and Fishbone as root cause analysis tools, while NASA describes Fault Tree Analysis as a top-down method for identifying process hazards.

What Is the Five Whys Method?

How Five Whys Works

Five Whys is a questioning technique that repeatedly asks why an event occurred until the investigation reaches a controllable system or organisational cause. Remember that five is a guide, not a mandatory number.

Use the scaffold example to demonstrate:

Why did the worker fall? The scaffold moved.

Why did it move? One or more wheels were not effectively secured.

Why was this not identified? The pre-use inspection was incomplete.

Why was the inspection incomplete? Responsibilities were unclear during a shift change.

Why were responsibilities unclear? The site's scaffold inspection and handover process was not adequately defined.

This final answer points to a controllable organisational failure—the process itself requires redesign.

When to Use It

Five Whys is suitable for:

  • Minor incidents and near misses
  • Repeated operational problems
  • Events with a reasonably clear causal chain
  • Situations requiring rapid analysis with limited resources

Limitations

Five Whys can:

  • Follow only one causal path, missing parallel failures
  • Depend heavily on the investigator's assumptions and knowledge
  • Stop too early at "carelessness" or "lack of training" without questioning system causes
  • Miss design, environmental or simultaneous failures
  • Underestimate complexity in multi-contractor or multi-department incidents

What Is Fishbone Analysis?

Fishbone Analysis is a cause-and-effect method that organises possible contributing factors into categories before evidence is used to confirm or reject them. Alternative names include Fishbone diagram, Ishikawa diagram and Cause-and-effect diagram.

Use construction-specific categories rather than generic manufacturing categories:

  • People: competency, fatigue, communication
  • Equipment: scaffold wheels, brakes, components
  • Methods: assembly, inspection, handover
  • Environment: floor condition, congestion, lighting
  • Materials: incompatible or damaged components
  • Management: supervision, planning, procurement, scheduling

For the scaffold event, the team might identify several credible factors instead of one linear explanation. A wheel brake may be defective (equipment), the pre-use inspection may have been rushed (method), the inspector may lack competency (people), and site supervision may be inadequate (management). Fishbone organises these possibilities visually.

Best Applications

Fishbone Analysis works best when:

  • Several people or contractors were involved
  • Causes may span departments or disciplines
  • The incident involves organisational and workplace factors
  • The team needs a structured brainstorming method
  • Multiple potential explanations exist
Root cause analysis comparing possible causes with verified evidence.

Important Warning

A Fishbone diagram identifies possible causes; it does not prove them. Every branch must be tested against photographs, inspection records, interviews, training records, equipment condition and site procedures. AHRQ describes the method as a visual way to organise suspected causes, while HSE guidance stresses the need to investigate underlying and organisational factors.

What Is Fault Tree Analysis?

Fault Tree Analysis is a top-down method that begins with an unwanted event and works backwards through the combinations of failures that could produce it.

Key definitions:

Top Event: The unwanted outcome (e.g., Worker falls from mobile scaffold)

Basic Events: Individual failures or conditions

OR Gate: Any listed event could produce the outcome

AND Gate: Several events must occur together

Possible scaffold pathways:

  • Scaffold movement OR loss of balance OR platform failure
  • Scaffold movement caused by unlocked wheels AND horizontal force
  • Loss of balance caused by overreaching AND inadequate platform positioning
  • Severity increased by missing or ineffective fall-prevention controls

Best Applications

Fault Tree Analysis works best for:

  • Fatal or high-potential incidents
  • Complex machinery and lifting operations
  • Electrical isolation failures
  • Structural collapse
  • Process-safety events
  • Multiple safeguards that failed simultaneously

Limitations

  • More time-consuming than simpler methods
  • Requires specialist knowledge to construct logically
  • Can become unnecessarily complex
  • Depends on reliable evidence and correctly defined logic

NASA describes FTA as a top-down approach used to identify process hazards and analyse complex safety and reliability pathways.

One Construction Incident Analysed Three Ways

Five Whys Result

Likely conclusion: The scaffold inspection and shift-handover process failed to ensure that wheel security was verified.

This produces a focused, actionable chain but may miss parallel factors. It answers the "why" chain efficiently but does not explore whether other failures contributed simultaneously.

Fishbone Result

Potential findings:

  • Poor floor condition
  • Incorrect scaffold placement
  • Damaged brake mechanism
  • Incomplete inspection
  • Rushed work sequence
  • Weak contractor coordination
  • Insufficient supervision

Fishbone creates a broader view but requires evidence validation. It surfaces possibilities that Five Whys might overlook but still needs investigation to confirm which factors actually contributed.

Fault Tree Result

Possible outcome: The fall required one of several initiation pathways, while the resulting injury severity depended on whether preventive and protective barriers were available and effective.

Fault Tree maps the logical combinations of failures and how multiple safeguards (fall-arrest systems, training, competent supervision) either prevented or failed to prevent harm.

The Main Lesson

The three methods do not necessarily compete. They examine the same event at different levels of depth and complexity. A simple incident might need only Five Whys, while a fatality might benefit from all three applied in sequence.

Which Root Cause Analysis Tool Should You Choose?

Comparison of Five Whys, Fishbone, and Fault Tree analysis methods.

Choose Five Whys When:

  • The incident is relatively simple
  • Evidence suggests one dominant causal chain
  • A rapid initial analysis is needed

Choose Fishbone Analysis When:

  • Several categories of contributing factors are possible
  • A multidisciplinary team is involved
  • The investigation needs structured brainstorming

Choose Fault Tree Analysis When:

  • The event is high severity or high potential
  • Technical systems and safeguards interacted
  • Several failures may have combined logically

Important note: Incident severity alone should not determine the method; causal complexity, uncertainty and available evidence also matter. A serious incident with a clear single cause may need only Five Whys. A minor incident with multiple contributing factors may warrant Fishbone.

Can You Combine Five Whys, Fishbone and Fault Tree Analysis?

Yes. A layered approach often produces stronger analysis:

  1. Begin with a Fishbone diagram to identify possible causal categories
  2. Apply Five Whys to the strongest evidence-backed branches
  3. Use Fault Tree Analysis when several pathways or safeguard failures must be mapped
  4. Validate every conclusion against evidence
  5. Emphasise that combining tools should add clarity, not unnecessary paperwork. Use multiple methods only if the incident complexity justifies it.

Turn Root Causes into Effective Corrective Actions

Safety infographic showing corrective actions from worker focus to stronger system controls.

A strong investigation should lead to:

  • A clearly defined corrective action
  • A named action owner
  • A completion deadline
  • Verification of implementation
  • Effectiveness monitoring
  • Communication of lessons learned

Contrast weak and strong actions:

Weak: Remind workers to be careful

Better: Introduce a documented scaffold handover and inspection process

Stronger: Improve planning, inspection, supervision and physical controls together

Link actions to the hierarchy of controls where appropriate. HSE presents investigation as a process for learning what went wrong and taking action to prevent recurrence.

Five Whys provides speed, Fishbone provides breadth and Fault Tree Analysis provides logical depth. Effective root cause analysis in construction depends less on choosing the most sophisticated tool and more on selecting and applying the right method objectively to the evidence.

Build the skills to investigate incidents beyond the obvious cause. The Incident Investigation / Root Cause Analysis course helps safety professionals examine evidence, identify contributing factors and develop corrective actions that support stronger workplace safety performance.

Frequently Asked Questions

01 What is the difference between Five Whys, Fishbone and Fault Tree Analysis? +

Five Whys explores a simple causal chain, Fishbone Analysis identifies multiple contributing factors, and Fault Tree Analysis maps complex combinations of failures and safety-system breakdowns.

02 When should construction teams use Five Whys? +

Five Whys is best for simple or moderately complex incidents where evidence suggests a clear causal chain and a rapid analysis is required.

03 When is Fishbone Analysis useful in construction investigations? +

Fishbone Analysis is useful when incidents involve multiple possible causes, different teams, contractors, or organisational factors such as people, equipment, methods, environment and management.

04 When should Fault Tree Analysis be used? +

Fault Tree Analysis is suitable for high-severity or technically complex incidents involving multiple failures, such as machinery failures, lifting incidents, electrical isolation failures or structural events.

05 Can Five Whys, Fishbone and Fault Tree Analysis be used together? +

Yes. A layered approach can combine Fishbone to identify possible causes, Five Whys to explore evidence-supported causes, and Fault Tree Analysis to map complex failure pathways.

06 Why should construction investigations focus on root causes instead of worker blame? +

Root cause analysis identifies system weaknesses in equipment, procedures, training, planning and management instead of stopping at individual actions or unsafe behaviour.

07 What makes corrective actions effective after a root cause analysis? +

Effective corrective actions require clear actions, responsible owners, deadlines, implementation verification, effectiveness monitoring and communication of lessons learned.