Root Cause Analysis Malaysia — What Most Incident Investigations Fail to Find
Most incident investigation reports produced in Malaysia reach the same three conclusions: procedure not followed, inadequate supervision, lack of training. These findings appear in reports across industries, across company sizes, and across incident types. They are almost always accurate. And they are almost always incomplete — which is why the same incidents keep happening at the same sites, year after year.
Effective root cause analysis in Malaysia does not stop at what went wrong at the task level. It traces why the management system that should have prevented those conditions failed to do so. The difference between these two levels of investigation is the difference between closing a file and actually reducing risk.
The Three Standard Findings — and Why They Are Not Root Causes
The three findings that end most incident investigations are not root causes. They are descriptions of conditions that existed at the time of the incident. Calling them root causes closes the investigation prematurely and leaves the actual cause intact.
“Procedure not followed.” This tells you what happened — a worker deviated from the documented procedure. It does not tell you why the deviation was rational from the worker’s perspective, why the system allowed it to occur without detection, whether the procedure accurately described the real task, or whether this deviation had been occurring for months before the incident. Without answers to these questions, your corrective action will be a retraining memo. The next deviation is already underway.
“Inadequate supervision.” This tells you that a barrier failed — supervision did not catch the unsafe condition. It does not tell you whether supervision was designed as a barrier for this specific hazard scenario, whether the supervisor’s workload made effective oversight impossible, whether there was a documented standard for what “adequate” supervision looked like for this task, or whether this supervisory gap was known and accepted. Without these answers, your corrective action will target the individual supervisor rather than the system that produced the gap.
“Lack of training.” This tells you that a worker did not have the competency required for the task. It does not tell you who was accountable for ensuring that competency existed before the task was assigned, what management system should have produced that training and why it failed, whether the gap was visible to anyone before the incident, or whether training was ever actually designed for this specific risk scenario. Without these answers, you will add a training record to a file and call it resolved.
The Three Levels of Root Cause Analysis
A complete root cause analysis in Malaysia — or anywhere — works through three levels. Most investigations reach level one. Few reach level three.
Level 1 — The Event. What happened? Which barrier failed, and what was the substandard act or condition that preceded the failure? This is the level most investigations describe well. The incident sequence is reconstructed, the immediate cause is identified, and the direct contributing factors are listed.
Level 2 — The Preconditions. What measurable, undesirable state existed before the event — and why? This is where investigations begin to identify the conditions the worker was operating under: the competency gap that existed before the task, the time pressure that made the shortcut attractive, the degraded equipment state that was known but not corrected. These preconditions did not appear on the day of the incident. They were produced by something deeper.
Level 3 — The Management System Failure. What system should have prevented the precondition from developing — and what caused that system to fail? This is the level that identifies the organisational weakness that produced the incident. It is also the level where corrective actions actually change something durable, because management systems can be redesigned, monitored, and held accountable in ways that individual behaviour cannot.
This three-level structure is the foundation of methodologies like Tripod Beta incident investigation, which traces the causation chain from the failed barrier through preconditions and underlying causes to the Basic Risk Factor — the category of management system failure at the root.
Why Investigations Stop Early — and the Cost of That Decision
Investigations stop at level one for understandable reasons. Time pressure is real. The regulatory requirement for an investigation report has a deadline. The worker who didn’t follow the procedure is visible and present. The management system failure is diffuse, systemic, and takes longer to trace.
But stopping early is not a neutral decision. It is a decision to leave the cause in place. Every investigation that closes with “procedure not followed” without asking why the bypass was rational and undetected is an investigation that sets up the next incident. The file is closed. The risk is not reduced.
As we explored in our analysis of why the 5 Whys method stops too early, the most common investigation tools in Malaysia are designed for speed and simplicity — not for system-level depth. They find the first plausible answer to each “why” and stop there. A proper root cause analysis requires a methodology that is specifically designed to trace to the management level, not just the task level.
What a Complete Root Cause Analysis Changes
When root cause analysis in Malaysia reaches the management system level, the corrective actions look different. Instead of “retrain the worker,” the action is “redesign the competency management system so that no worker can be assigned this task without verified competency.” Instead of “remind supervisors of their responsibilities,” the action is “define the specific oversight standard for this hazard category and build verification into the management review process.”
These corrective actions are harder to implement. They take longer. They require management commitment, not just a signature on a training form. But they change the system that produced the incident — which means the incident does not repeat.
DOSH Malaysia increasingly requires organisations to demonstrate that their incident investigations have identified systemic causes and implemented durable corrective actions. A report that closes with “procedure not followed — worker retrained” does not satisfy this standard, and experienced DOSH inspectors will probe further.
Frequently Asked Questions
What is root cause analysis and how is it applied in Malaysia?
Root cause analysis (RCA) is the process of tracing an incident beyond its immediate causes to identify the underlying management system failures that produced it. In Malaysia, RCA is required as part of DOSH incident investigation requirements. Common methods include 5 Whys, Fishbone (Ishikawa), and Tripod Beta. Of these, Tripod Beta is specifically designed to reach the management system level — making it the most complete approach for organisations seeking durable prevention.
Why do incident investigations keep finding the same root causes?
Investigations find the same causes repeatedly because they are identifying symptoms rather than root causes. “Procedure not followed” and “lack of training” are level-one findings — they describe the conditions at the time of the incident. The management system failures that produced those conditions are not being identified or corrected. When the system remains unchanged, it produces the same conditions — and eventually the same incident.
Build an Investigation Process That Actually Prevents Repeat Incidents
If your organisation’s investigations consistently close with procedure, supervision, or training findings — without reaching the management system level — your next incident is already being produced by the same conditions your last report failed to address.
Cikgu Barrier’s Incident Investigation Basics program trains your team to conduct investigations that reach the system level — using 5W/4P analysis, Fishbone methodology, and the management system tracing framework that prevents repeat incidents. For teams ready to go deeper, our Tripod Beta Incident Investigation program provides accredited methodology training for complete causation chain analysis. Contact us to discuss your investigation capability.