Four separate cases, four separate facilities, and one recurring pattern: the same investigation process, applied to four different situations, produced four different outcomes depending entirely on whether it was scoped to satisfy a requirement or scoped to actually prevent recurrence.
Four Cases, One Pattern
A bearing failure investigation satisfied a client’s vendor audit requirement twice, on the same underlying defect, because the fix identified in the first report never left the single asset it was written about — a Maintenance Management BRF that diagnosed correctly and stopped there. A HIRARC passed its supplier audit three years in a row while quietly drifting away from what was actually happening on the floor, because its review procedure was triggered by the calendar rather than by actual process change — a Procedures BRF hiding inside the paperwork itself. A Bowtie diagram was accurate on the day it was drawn for a client audit and wrong by the time it mattered, because neither of two subsequent process changes triggered a review of the barriers that depended on them. And one investigation did the opposite of all three: its finding was used past the single incident it was written about, audited across the rest of the operation, and kept preventing a repeat two years later.
Same Process, Different Scope
What separates the fourth case from the first three isn’t the quality of the original technical finding — in every case, the investigation correctly identified what had gone wrong. What separates them is whether the investigation was scoped to stop the moment its triggering requirement was satisfied, or scoped to keep going until the underlying gap was actually closed across the operation, not just documented for the one incident that surfaced it.
Why This Distinction Rarely Shows Up in Investigation Metrics
Most investigation tracking measures whether a report was filed on time, whether it satisfied its audit or notification requirement, and whether a corrective action was logged. None of these measures capture whether the corrective action was ever verified as implemented beyond the single asset, whether the review procedure that produced a stale HIRARC was ever redesigned, or whether a Bowtie diagram’s barriers were re-tested after a process change. An organisation can have a perfect on-time filing record and still be repeating the same failures, because the metric that gets tracked isn’t the one that predicts recurrence.
The Governance-Stage Opportunity
HIRARC and OSH Obligations for Management sit upstream of an incident — at the risk-assessment and governance stage, before anything has gone wrong. Tripod Beta and Bowtie Analysis sit downstream, tracing what happened after an incident or near-miss back to its systemic cause. The pattern across all four cases this week applies at both stages: whether the document or process in question gets treated as something to maintain and act on, or as an artefact to produce and file.
What Malaysian Companies Can Do Differently
None of the four gaps identified in these cases required additional headcount or a significant new system to close. The bearing failure gap needed a maintenance system that propagated findings to the full asset register. The HIRARC gap needed a review trigger tied to process change rather than the calendar. The Bowtie gap needed barrier reviews triggered by engineering sign-off on process changes. And the fourth case’s success came from a single additional step — auditing beyond the one asset — that any investigation process can build in as standard practice.
The Real Cost of Treating Investigation as Compliance-Only
Every one of the compliance-only outcomes in these four cases eventually cost more than the productivity-driven approach would have — in downtime, in rework, in a repeat client audit finding, or in a second incident that a wider audit would have caught the first time. That cost is real, but it’s rarely visible at the point the original investigation is filed and closed, which is exactly why it’s easy for an investigation process to drift toward compliance-only scoping without anyone deciding that on purpose.
Building Investigation Capability, Not Just Investigation Compliance
The gap between these two outcomes is a training and process design question, not an individual competency question. Teams that are taught to scope investigations toward prevention — checking for repeat exposure, redesigning review triggers, extending verification independence, auditing findings beyond the single incident — produce the fourth outcome by default, not by exception.
Starting Without a Full Programme Redesign
None of this requires an organisation to overhaul its investigation programme before seeing a benefit. A facility can start with a single change — adding one explicit “check beyond this asset” step to its existing investigation template, or adding one process-change trigger to its HIRARC review procedure — and test whether that single change catches a gap the current process would have missed. The four cases this week each trace back to one missing step, not a wholesale process failure. That’s a useful starting point for any HSE team deciding where to focus first, rather than treating “compliance vs. productivity” as an all-or-nothing programme decision.
Which of this week’s four outcomes is closest to how investigations get treated in your organisation? Cikgu Barrier’s public and in-house programs — HIRARC, OSH Obligations for Management, Incident Investigation Basics, Bowtie Analysis, and Tripod Beta — teach Malaysian HSE teams to close the gap between an investigation that satisfies a requirement and one that actually changes the operation. Register your interest in upcoming dates — no cost, no commitment.