There’s a specific kind of investigation finding that no amount of retraining can fix, and it’s more common than most safety programmes account for: the job itself was never engineered with a safer way to do it. Tripod Beta classifies this as a Design Basic Risk Factor, and it’s worth understanding in detail, because misclassifying it as a training or compliance issue guarantees the next person assigned the same task walks into the same gap.
This article continues a series built around one real investigation, with equipment, task, and setting fictionalised for confidentiality. The case involved a technician who fell from a support ledge while tightening a mounting bolt on a pump coupling at a processing plant.
What the Investigation Found
Two specific findings landed under the Design BRF category.
There was no other suitable rigging method available for installing this component at that location — the manual method being used, which required a technician to physically position himself at height to reach both sides of the assembly, was effectively the only option available.
There was no alternative mechanical aid — such as a powered hoist or lifting device — available for this task, which meant the only way to accomplish it was the manual approach that ultimately required the climb.
Why This Isn’t a People Problem
Retrain every technician on that crew, and the next one assigned the same job will hit the exact same physical constraint. He’ll need to reach both sides of the same component, from the same limited access, with the same absence of a mechanical alternative — because none of what caused the fall was a knowledge gap. He knew how to do the task. The task itself had no safer version available to do.
This is the specific value of the Design category within Tripod Beta’s Basic Risk Factor framework: it correctly routes a finding away from the training department and toward engineering and procurement, where the actual fix has to happen. A Design finding says the job was set up, at a physical and engineering level, in a way that made a safer outcome structurally unlikely — not merely possible to get wrong.
How a Design Finding Differs From Other BRF Categories
It’s worth distinguishing Design clearly from adjacent categories that can look similar on the surface. A Maintenance Management finding would describe equipment that was designed adequately but degraded over time without proper upkeep. A Hardware finding describes a physical tool or component that failed or was inadequate for its specific function. Design describes the underlying engineering or planning decision — the fact that, from the outset, no safer method or tool was specified or made available for the task as scoped.
This distinction matters practically because each implies a different corrective action, and conflating them produces the wrong one. Adding a maintenance schedule doesn’t fix a design that never had a safer option built in. Providing better hardware doesn’t help if the design itself never called for that hardware to exist on this job.
Why Design Findings Are Often the Hardest to Surface
Design-level gaps tend to survive in an organisation precisely because they don’t announce themselves through an obvious failure. The manual method worked, in the sense that the job got done, for however long it had been done that way before this incident. Nobody was actively resisting a safer approach — there usually wasn’t a safer approach on offer to resist. This is why Design findings frequently only surface during a formal incident investigation rather than a routine audit: an audit typically checks whether the specified method is being followed, not whether the specified method itself was ever engineered with a genuinely safer alternative in mind.
What a Genuine Fix Looks Like
A recommendation addressing a Design BRF finding has to land at the engineering or procurement level, and it has to be specific enough to verify — not “review rigging options” as an open-ended item, but a defined evaluation of mechanical lifting alternatives for this task type, with a decision point and an owner. Anything short of that risks becoming exactly the kind of vague, unverifiable recommendation that Tripod Beta’s SMART criteria are designed to prevent.
The Practical Question
For any task at your site currently performed manually because “that’s how it’s always been done,” ask whether anyone has actually evaluated a mechanical or engineering alternative — or whether the manual method persists simply because no one has been asked to look for one.
Want your investigation team correctly distinguishing Design findings from training gaps, so recommendations land with the right owner? Cikgu Barrier’s Tripod Beta Incident Investigation programme covers the full Basic Risk Factor framework and how to build SMART recommendations at the right level. Available in-house and as a public workshop across Malaysia.