TL;DR
The 5 Whys method traces a single causal chain by asking “why” repeatedly until you reach a root cause. A fishbone (Ishikawa) diagram maps multiple possible cause categories simultaneously. For simple, single-event incidents, the 5 Whys is faster and works well with small teams. For complex, multi-factor events, a fishbone diagram prevents tunnel vision. The strongest investigations use both: fishbone first to widen the search, then 5 Whys to drill into the most likely causes. OSHA expects root cause depth but does not mandate a specific method.
After a jobsite incident, near miss, or OSHA-reportable injury, someone has to figure out what actually went wrong. Not just what happened, but why it happened. That distinction is the entire point of root cause analysis, and it is where most investigations either succeed or fall apart.
Two tools dominate the conversation: the 5 Whys and the fishbone diagram. Both are free, low-tech, and field-ready. Neither requires specialized software. But they work differently, suit different situations, and fail in different ways. Picking the wrong one, or using either one poorly, leads to corrective actions that look good on paper and change nothing on the ground.
This guide breaks down both tools from a construction safety perspective, explains when to use each, and walks through how to combine them for serious investigations.
If your team needs help conducting a thorough post-incident analysis, ESR provides professional incident investigation support led by credentialed safety professionals (CSP, CHST, OSHA 500/501).
5 Whys vs. Fishbone Diagram: Quick Key Differences
The primary difference between the 5 Whys and a fishbone (Ishikawa) diagram lies in analysis depth versus breadth:
5 Whys Method: A linear root cause analysis tool that drills deep into a single causal chain by asking “Why?” repeatedly until reaching systemic failures. Best for simple, single-event incidents handled by 1 to 3 investigators.
Fishbone Diagram: A categorical visual mapping tool that evaluates multiple potential cause categories (People, Equipment, Methods, Environment, Materials, Management) simultaneously. Best for complex, multi-factor incidents involving cross-functional teams.
Combined Approach: For major incidents or OSHA-reportable events, safety teams should use both: start with a fishbone diagram to brainstorm all potential contributing factors, then apply the 5 Whys to drill down into the top priority causes.
What Is the 5 Whys?
The 5 Whys is a root cause analysis technique invented by Sakichi Toyoda and later formalized within the Toyota Production System. The concept is simple: start with the problem, ask “why” it happened, take that answer, and ask “why” again. Repeat until you reach a cause that is both fundamental and fixable. Five iterations is a rule of thumb, not a hard rule. Some investigations need three rounds, others need seven.
The method assumes a single dominant causal chain. You are following one thread from surface symptom to underlying system failure.
Construction Example: Fall from Scaffold
Problem: A worker fell from a scaffold and broke his wrist.
Why did the worker fall? He lost his balance while reaching for material on a higher platform.
Why was he reaching instead of repositioning the scaffold? No one told him to stop and adjust. He was working alone.
Why was he working alone at height? The crew was short-staffed that day, and the foreman assigned him solo to stay on schedule.
Why did the foreman override the two-person policy? There is no written policy requiring two workers on scaffold operations.
Why is there no written scaffold safety program? The company has never developed one, and no one has been assigned ownership of the safety program.
The root cause is not the worker losing his balance. It is the absence of a written safety program and a designated safety function. That is a system-level failure that can actually be fixed. If your investigation reveals gaps in written programs, it may be time to check whether your safety manual is OSHA-compliant.
Strengths of the 5 Whys
Fast. A competent investigator can run through it in 15 to 20 minutes.
Requires no special tools, templates, or software.
Forces the investigator past the surface cause.
Works well for near misses, first aid incidents, and single-event triggers.
Small teams (even one person) can use it effectively.
Weaknesses of the 5 Whys
The 5 Whys has real limitations, and some of the sharpest criticism comes from unexpected places. Teruyuki Minoura, former managing director of global purchasing for Toyota, criticized the technique as too basic to analyze root causes at the depth necessary to ensure problems are actually fixed. When a Toyota executive questions Toyota’s own tool, that should get your attention.
Practitioners on LinkedIn have pointed out a core structural problem: “An insufficient 5 Why method results in a linear analysis, wherein, one thing led to another which led to the next thing. The final answer after the last Why usually is not the root cause.”
Other well-documented weaknesses include:
Repeatability problem. Different investigators asking “why” about the same incident will arrive at different root causes. The method depends heavily on the knowledge and assumptions of whoever is asking.
Tunnel vision. Because the 5 Whys follows a single chain, it structurally cannot capture incidents with multiple independent contributing factors.
Stopping too early. Investigators tend to stop at the first answer that feels satisfying rather than pushing to a systemic cause.
Knowledge ceiling. The technique cannot go beyond what the investigator already knows or suspects.
A 2017 commentary in BMJ Quality & Safety by researcher Alan Card acknowledged the 5 Whys as a useful teaching tool but argued that its application to root cause analysis may be misguided because it tends to oversimplify complex problems.
The bottom line: the 5 Whys is generally recommended for low-severity incidents such as minor injuries, first aid cases, and minor equipment damage. For anything more complex, it needs help.
What Is a Fishbone (Ishikawa) Diagram?
The fishbone diagram was developed by Dr. Kaoru Ishikawa in the 1960s for quality management in Japanese manufacturing. It has since become a standard tool in occupational safety and health investigations worldwide.
The diagram gets its name from its shape. A horizontal arrow (the “spine”) points to the incident or problem (the “head”). Diagonal branches (“bones”) extend from the spine, each representing a major category of potential causes. Teams brainstorm causes within each category and map them visually, creating a comprehensive picture of everything that might have contributed to the event.
Construction-Specific Categories
The traditional manufacturing categories (the “6 Ms”: Man, Machine, Method, Material, Measurement, Milieu) don’t translate cleanly to a construction jobsite. More useful categories for construction safety investigations are:
People: Competency, fatigue, communication, crew experience, language barriers
Equipment: Condition, inspection status, compatibility, maintenance history
Methods: Work procedures, assembly sequence, inspection protocols, handover processes
Environment: Weather, floor condition, lighting, congestion, noise
Materials: Quality, compatibility, damage, storage conditions
Management: Supervision, planning, scheduling, procurement, training program adequacy
Construction Example: Struck-By Incident
A carpenter is struck by a steel beam during an overhead lift. The fishbone diagram might surface the following across categories:
People: Crane operator was on overtime (12th hour), spotter was reassigned to another task
Equipment: Rigging sling had visible wear, not flagged in last inspection
Methods: No lift plan was developed for this specific pick
Environment: Wind gusts exceeded 20 mph that afternoon, no weather hold protocol existed
Materials: Beam was longer than specified, requiring a different rigging configuration
Management: No competent person was designated on-site for crane operations; the supervisor safety training gap had not been addressed
This incident had at least six contributing factors across four categories. A 5 Whys analysis starting with any single branch would miss the others. The fishbone captures the full picture.
Strengths of the Fishbone Diagram
Visual format that is easy for cross-functional teams to understand and contribute to.
Covers multiple causal categories simultaneously, preventing tunnel vision.
Inclusive. Everyone from the foreman to the project manager can add observations.
Forces the team to consider categories they might otherwise overlook (materials, environment, management).
Weaknesses of the Fishbone Diagram
It generates hypotheses, not conclusions. A fishbone identifies possible causes. It does not prove which ones actually contributed. Every branch must be tested against photographs, inspection records, interviews, training records, and site procedures.
It can become cluttered. Large teams brainstorming freely can produce a diagram with dozens of entries, making it hard to prioritize.
No causal ranking. The diagram treats all potential causes equally. Without follow-up analysis, you don’t know which factors were dominant.
Not sufficient alone for serious incidents. Academic critics on ResearchGate have noted that the fishbone diagram is “poorly suited to represent the dynamic interactions between human, technical, and organisational factors.”
5 Whys vs. Fishbone Diagram: Side-by-Side Comparison
5 Whys vs. Fishbone Diagram: Comparison Matrix
Feature: Analysis Scope
5 Whys Method: Linear / Depth (Single causal chain)
Fishbone Diagram: Categorical / Breadth (Multi-factor map)
Feature: Primary Purpose
5 Whys Method: Root cause identification
Fishbone Diagram: Contributing factor brainstorming
Feature: Best Incident Complexity
5 Whys Method: Simple, single-event incidents
Fishbone Diagram: Complex, multi-variable incidents
Feature: Recommended Team Size
5 Whys Method: 1 to 3 investigators
Fishbone Diagram: 4 to 10 cross-functional team members
Feature: Time Required
5 Whys Method: 15 to 20 minutes
Fishbone Diagram: 30 to 60 minutes
Feature: Key Advantage
5 Whys Method: Speed, simplicity, and minimal prep
Fishbone Diagram: Prevents tunnel vision; covers multiple categories
Feature: Key Limitation
5 Whys Method: Misses secondary or parallel causes
Fishbone Diagram: Identifies possibilities without proving root cause
Feature: Regulatory & OSHA Suitability
5 Whys Method: Minor incidents, first aid, near misses
Fishbone Diagram: Severe incidents, recordables, complex jobsite events
The core structural difference: the 5 Whys assumes a chain. The fishbone assumes a spread. Picking the wrong shape for the incident in front of you is the most common way an investigation ends with a corrective action nobody believes in.
When to Use Each in a Safety Investigation
Use the 5 Whys When:
The incident has a clear, single-event trigger (one thing went wrong)
You are investigating a near miss or first aid case
Your team is small (one safety pro or a supervisor and two crew members)
You need results quickly, same day or next day
The cause category is fairly obvious, and you need to drill into it
Use a Fishbone Diagram When:
The incident involved multiple contributing factors
You are investigating an OSHA-recordable injury or a serious near miss
A cross-functional team is available (superintendent, foreman, safety, workers, equipment operators)
You suspect causes span more than one category (e.g., both equipment failure and inadequate training)
The incident is similar to previous events, suggesting the earlier investigation missed something
If a root cause points to a training deficiency, that finding should connect to your company’s OSHA-required training program.
Use Both Together When:
A fatality or serious injury has occurred
The incident is OSHA-reportable (hospitalization, amputation, loss of eye)
You are dealing with a repeat incident where previous corrective actions failed
OSHA is likely to inspect and review your investigation report
The event involves contractors, subcontractors, and the owner on the same site
Incident Selection Decision Matrix: Which Tool Should You Choose?
Selecting the right root cause analysis tool depends on the severity and complexity of the event:
Low Severity / Single Trigger (First aid cases, minor property damage, simple slips or trips on level ground)
Recommended Tool: 5 Whys
Action: Perform a quick 15-minute 5 Whys investigation with the supervisor and involved worker to identify the underlying administrative or training failure.
Moderate Severity / Multi-Factor Risk (OSHA-recordable injuries, major equipment damage, near misses with high injury potential)
Recommended Tool: Fishbone Diagram
Action: Hold a 45-minute structured brainstorming session with a team to evaluate People, Equipment, Methods, Environment, Materials, and Management.
High Severity / OSHA-Reportable (Fatalities, amputations, in-patient hospitalizations, repeat incidents)
Recommended Tool: Combined Workflow (Fishbone + 5 Whys)
Action: Map all possibilities using a fishbone diagram, vote on top candidate causes, and run a 5 Whys analysis on each selected branch.
How to Use Both Together: The Combined Workflow
The most effective safety investigations sequence both tools. The fishbone widens the search. The 5 Whys narrows it. Practitioners across safety forums and professional communities consistently recommend this combined approach for any event more serious than a minor first aid case.
Here is the step-by-step workflow:
Step 1: Define the Problem Statement (10 minutes)
Write a clear, specific statement of what happened. Not “worker got hurt” but “Carpenter sustained a laceration to the left forearm when a circular saw kicked back during a rip cut on the second floor of Building C at approximately 2:15 PM on June 12.”
A vague problem statement produces vague results.
Step 2: Build the Fishbone Diagram as a Group (30 to 45 minutes)
Gather the investigation team. Use the six construction categories (People, Equipment, Methods, Environment, Materials, Management). For each category, brainstorm every plausible contributing factor. Write them on the diagram without judging or filtering. The goal is completeness, not accuracy. Accuracy comes later.
Step 3: Vote on the Most Likely Causes (10 minutes)
Each team member gets three votes. Place them on the causes they believe were the strongest contributors based on evidence available. The top two or three causes become candidates for deeper investigation.
This voting step is critical. Without it, the fishbone just sits on a whiteboard looking thorough but producing nothing.
Step 4: Run a 5 Whys on Each Top Candidate (15 to 20 minutes each)
Take each high-priority cause from the fishbone and drill down with 5 Whys until you reach something systemic and fixable. If you started with “Rigging sling had visible wear,” you might end up at “No scheduled inspection program for rigging equipment” or “Inspection responsibility was never assigned to a specific person.”
Step 5: Assign Corrective Actions with Owners, Deadlines, and Verification Dates
Every root cause needs a corrective action. Every corrective action needs a person responsible, a deadline, and a date when someone will verify it was actually completed and working. Without this step, you have completed an academic exercise, not an investigation.
For organizations that need support building this process into a formal safety management system, outside guidance can accelerate the effort significantly.
Common Mistakes That Weaken Safety Investigations
Regardless of which tool you choose, these errors undermine the process.
Stopping at “Operator Error”
The single most common weakness in incident investigation reports is a stated cause of “operator error,” full stop, with nothing behind it. That is a description of what happened, not an explanation of why it happened.
OSHA’s incident investigation guidance specifically warns against concluding that an incident occurred because of “carelessness” or a “missed procedure step” without going further. Behind every instance of human error are equipment factors, training gaps, supervision failures, and system-level breakdowns that actually need fixing. Understanding the difference between blaming behavior and fixing systems is central to a mature behavior-based safety approach.
Using the 5 Whys Alone on Complex Incidents
If a struck-by incident involved operator fatigue, defective equipment, an absent spotter, high winds, and no lift plan, the 5 Whys will only chase one of those threads. The other four contributing factors go unexamined, and your corrective actions address a fraction of the problem.
Treating the Fishbone as Proof
A fishbone diagram is a brainstorming tool. It generates hypotheses. Every branch must be verified against physical evidence: photos, inspection logs, training records, equipment condition reports, witness statements. A fishbone full of unverified guesses is not an investigation. It is a wish list.
Different Investigators, Different Conclusions
Because the 5 Whys depends on the investigator’s existing knowledge, two investigators analyzing the same incident will often reach different root causes. This repeatability problem is well documented. The mitigation is straightforward: use a team, not a solo investigator, and always validate findings against physical evidence.
Failing to Connect Corrective Actions to System-Level Causes
A corrective action like “retrain the worker” is almost never sufficient. If the root cause is a missing written program, inadequate supervision, or a scheduling practice that puts fatigued workers in high-risk tasks, the corrective action must address that system failure. Retraining one person changes nothing if the system that created the hazard is still running.
OSHA Incident Investigation Compliance Guidelines
While OSHA does not mandate a single root cause analysis tool, federal standard guidelines expect employers to go beyond human error to uncover system-level breakdowns. Regulatory compliance considerations include:
29 CFR 1910.119(m) (PSM Standard): Mandates that incident investigations begin as promptly as possible, and no later than 48 hours following a reportable safety event.
Form 301 & Recordkeeping: Root cause findings directly inform corrective actions documented in OSHA Form 301 injury and illness incident reports.
Systemic Action vs. Behavior Blame: OSHA inspectors frequently reject investigation logs that stop at “worker carelessness” or “failure to follow procedure,” requiring evidence of corrected training, equipment maintenance, or management supervision gaps.
What OSHA Expects from Your Investigation
OSHA does not mandate a specific root cause analysis method. You can use 5 Whys, a fishbone diagram, fault tree analysis, or any combination. What OSHA does expect is depth.
OSHA’s fact sheet on root cause analysis states that “a root cause is a fundamental, underlying, system-related reason why an incident occurred that identifies one or more correctable system failures.” The agency urges employers to go beyond immediate causes to find the management, design, planning, organizational, or operational failures underneath.
For employers covered by the Process Safety Management (PSM) standard at 29 CFR 1910.119(m), incident investigation is a regulatory requirement. Employers must start an investigation as promptly as possible, and no later than 48 hours after the incident.
Even outside PSM-covered workplaces, OSHA inspectors will review your investigation reports after a serious event. If your report concludes with “worker error” and no systemic analysis, that report will not satisfy the inspector. And if an inspection leads to a citation, understanding how to respond becomes the immediate priority.
The context matters. In 2024, there were 5,070 fatal work injuries in the United States, with construction accounting for 1,034 of those deaths, the most of any private industry. Fatal falls, slips, and trips alone accounted for 844 fatalities. A worker died every 104 minutes from a work-related injury. These are not abstract numbers. They represent real failures of the systems that investigations are supposed to fix.
Key Takeaways
The 5 Whys and the fishbone diagram are not competing tools. They solve different problems and work best when combined.
Quick decision framework:
Minor incident, single cause, small team: 5 Whys alone
Multi-factor event, recordable injury, cross-functional team: Fishbone diagram, possibly followed by 5 Whys on top causes
Fatality, serious injury, OSHA-reportable, or repeat incident: Fishbone first for breadth, then 5 Whys for depth on priority branches, with full corrective action tracking
Both tools are free and require minimal training. The bottleneck is never the tool itself. It is investigator skill, team discipline, and organizational willingness to act on what the investigation finds.
If your team needs to build or strengthen its investigation capability, root cause analysis services from experienced safety professionals can close the gap between documenting an incident and actually preventing the next one.
Frequently Asked Questions
Does OSHA require a specific root cause analysis method?
No. OSHA requires employers to investigate incidents and identify root causes, but the agency does not mandate the 5 Whys, fishbone diagram, or any other specific technique. What matters is that the investigation reaches system-level causes and produces corrective actions that prevent recurrence.
Can I use the 5 Whys by myself, or do I need a team?
You can run a 5 Whys analysis solo, and many safety professionals do for minor incidents and near misses. However, a solo analysis is limited by your own knowledge and assumptions. For anything beyond a first aid case, involving at least one other person (ideally someone who was present during the event) improves accuracy.
How long does each method take?
A 5 Whys analysis typically takes 15 to 20 minutes. A fishbone diagram brainstorm takes 30 to 60 minutes with a group. When combined, expect a full investigation session of 60 to 90 minutes, not counting evidence gathering and corrective action assignment.
What if my 5 Whys analysis leads to more than one root cause?
That usually means the incident is more complex than a single causal chain can capture. This is exactly when you should switch to a fishbone diagram to map all contributing factors before drilling deeper. The 5 Whys can then be applied to multiple branches.
Is the fishbone diagram only for serious incidents?
Not necessarily. A fishbone works well anytime you suspect multiple factors contributed to an event, even a near miss. That said, for a simple trip-and-fall caused by a single housekeeping failure, a fishbone is overkill. Match the tool to the complexity.
What is the most common mistake in safety investigations?
Stopping at “operator error” or “worker carelessness” without investigating the system conditions that made the error possible. Training gaps, missing written programs, inadequate supervision, equipment deficiencies, and scheduling pressure are almost always present behind individual mistakes.
Should I document my investigation with one of these tools if OSHA inspects?
Yes. A documented investigation using any structured method demonstrates good faith and compliance with OSHA’s expectation that employers investigate incidents and address root causes. An undocumented investigation, or one that ends at a surface-level cause, will not satisfy an inspector reviewing your records.
Where can I learn more about building a complete investigation process?
Start with OSHA’s incident investigation guide for employers. For hands-on support building investigation skills into your safety program, ESR’s incident response services cover everything from initial response through root cause analysis and corrective action verification.