January 6, 2026 | Ken Reed

Don’t Bother Finding Root Causes in Investigations

finding root causes in investigations

This came up again in a recent LinkedIn post. I saw a risk and safety consultant discuss why finding root causes in investigations is a waste of time. This comes up every so often, and I always try to understand where they’re coming from when they say things like that. It doesn’t make sense to me that anyone would think stopping an investigation at a high-level causal factor (failed safeguard) gives you enough depth to avoid a repeat incident.

I try to read what is presented and get a feel for the specific take of the people who feel this way. In this case, the consultant felt that:

  • We can just look at the situation and “understand what happened.” We only have to find a failed defense.
  • All we have to do is compare what happened to what should have happened. We’re all smart enough to do this without any real guidance.
  • There is a single “root cause”, and therefore putting a label on it is a waste of time. This was at least implied multiple times.
  • People can look at a situation and just “know” what safeguard was missing. All we really have to do is identify the missing or failed barrier and fix it.
  • Root causes are ambiguous, and defining a nebulous root cause takes too much time.
  • Human performance-based root causes are not necessary. “Just” identify the defenses and fix or strengthen them.

This type of thinking is not common, but it does come up every now and then. It normally stems from a misunderstanding of root causes.

  • If you are “wasting time” trying to look through your investigation to find root causes, then you are not using a structured approach. You are trying to apply a definition to the information you’ve collected, then arguing among yourselves about what the root cause is.
    • A structured system gets you there automatically. No ambiguity; just follow the process, and you arrive at root causes.
  • There is almost never a single root cause. Again, you may find only a single root cause when you are staring at your data and applying ambiguous definitions. Without a structured methodology, you’ll never know what you don’t know.
  • Without proper guidance, you are depending on the investigator to “just know” what they should be looking for. It can be easy to identify a failed safeguard. However, did we find all the failed safeguards? Was the failed one the right one in the first place? Why did that safeguard fail in the first place? Most of this will be missed without a structured approach.
  • In most cases, applying corrective actions directly to a failed safeguard results in blame-oriented corrective action. That’s why you must identify human performance-based root causes and apply corrective actions to those root causes.

A structured method of identifying human performance-based root causes is critical to finding all the problems, removing blame and bias from your investigations, and avoiding repeat failures and incidents. If you stop at the failed defense (causal factor) level, you miss a huge opportunity to put effective corrective actions in place.

Go Beyond Failed Safeguards with TapRooT® Root Cause Analysis

Learn how to move from identifying what happened to understanding why. Join our 5-Day TapRooT® Advanced Root Cause Analysis Team Leader Training to practice a structured investigation process, identify human performance-based root causes, and develop effective corrective actions that help prevent repeat incidents.

Categories
Root Cause Analysis
-->
Show Comments

Leave a Reply

Your email address will not be published. Required fields are marked *