“Human error” appears in a large share of Malaysian workplace incident reports as the final finding. It is fast to write, simple to close out, and rarely requires anyone above the person on shift to answer for anything. It is also, in the overwhelming majority of cases, not where the real explanation lives.
Why “Human Error” Isn’t an Explanation
Nobody arrives at work planning to make a mistake that harms themselves or a colleague. Every action a person takes in the moments before an incident made sense to them at that time, given what they knew, what they had been trained on, what they were being asked to deliver, and what the situation in front of them actually looked like. Stating that “the operator made an error” describes what happened. It explains nothing about why a competent, experienced person did the specific thing they did.
An investigation’s real job is to answer that second question — why the action made sense to the person at the time — and that answer almost always sits above the individual: in how the task was designed, how the training was scoped, how supervision was resourced, or how the surrounding system was built and maintained.
Tripod Beta’s Structural Answer
Tripod Beta, the investigation methodology behind this framing, treats the human action or inaction at the point of failure — the Immediate Cause — as the starting point of an investigation, never its conclusion. Every Immediate Cause traces back to one or more Preconditions: the situational, physical, or mental context that made that action likely. Each Precondition, in turn, traces back to one or more Underlying Causes — failures in the management system that allowed that precondition to exist. Underlying Causes are categorised across eleven Basic Risk Factors, none of which are “the person wasn’t careful enough.”
This structure exists because “be more careful” has never once fixed a systemic gap. It closes a file. It does not change the conditions that produced the incident, which means the same conditions remain in place for the next person who encounters them.
The Convenience of Stopping Early
Simplified investigation tools — basic incident report forms, five-whys worksheets used without rigour, root-cause templates built around a single linear chain — are efficient and familiar. They are also, by design, shallow. They typically stop at the first plausible explanation that closes the regulatory file, which in most cases is the action of the person present at the point of failure.
This isn’t necessarily dishonesty on the part of the people conducting the investigation. It’s a structural bias built into the tools themselves: a form designed to capture “what happened and what will we do about it” will keep producing the same category of answer regardless of how many times it’s used, because it was never designed to ask what happened above the person.
What a Deeper Investigation Actually Requires
Moving past “human error” as a conclusion doesn’t require blaming management instead of the worker. It requires treating the worker’s action as a data point that points toward a system question, rather than as the answer itself. What training did this person actually receive for this specific situation? What did the procedure assume about conditions that no longer held? What did supervision have the capacity to catch, given how many other things they were also responsible for at that moment? What did the equipment or system allow, structurally, regardless of who was operating it?
Each of these questions can be answered factually, without speculation, and each one moves the investigation further from “the person failed” and closer to “the system permitted this.”
A Pattern Worth Watching in Your Own Records
If your organisation’s corrective action register shows “retraining conducted” or “verbal warning issued” as the recurring fix across multiple incidents, on the same task or the same line, over multiple years — that pattern is itself a finding. It shows the investigation method has consistently produced the same shallow conclusion. It does not show that the underlying system is sound.
The Real Question
The question worth asking after your next incident report isn’t whether the investigation was thorough. It’s whether the methodology used is even capable of finding a management system failure — especially one created by decisions your own organisation made. If the framework stops at the operator level by design, the answer is no, regardless of how many hours the investigation took.
Want to build an investigation capability that goes past “human error” as a conclusion? Cikgu Barrier’s Tripod Beta Incident Investigation program teaches HSE teams and investigation leads the full causation chain — from Immediate Cause through Precondition to Underlying Cause — so the same recurring finding stops being the end of the investigation and starts being the beginning of one. Malaysia’s only accredited Tripod Beta training, delivered by a certified Tripod Trainer.