Every investigation eventually arrives at a moment where someone in the room says some version of: “he should have been more careful.” It’s the most natural response to seeing a chain of failures laid out plainly, and it’s almost always where a genuinely useful investigation stops being useful.
This article continues a series built around one real investigation, with the equipment, task, and setting fictionalised to protect confidentiality — the causation chain itself is exactly as investigated. The previous article covered six barriers that failed on the same day, culminating in a technician’s fall from a support ledge while tightening a mounting bolt on a pump coupling.
What a Precondition Actually Is
In Tripod Beta methodology, once the immediate failures are mapped, the next layer is Preconditions — the situational and psychological context that made each failure feel normal, acceptable, or even sensible to the person at the time. This is not a softer version of blame. It’s a specific, defined analytical layer, and it exists because “the person made a mistake” describes a fact without explaining anything an organisation can act on.
A precondition can be internal — what someone believed, perceived, or assumed in the moment — or external, a physical or situational condition they were working within. Either way, the test is the same: does this statement explain why the action felt reasonable to that person at that time? If it does, it belongs here. If it instead describes a failure in a management process — a missing training programme, an absent review step — it belongs at a deeper layer entirely, one this series will get to shortly.
What Surfaced in This Case
Several preconditions emerged from the investigation.
The job had been labelled “light work” from the outset — a framing that shaped how much caution was applied to it, including the decision to let one technician work alone at ground level rather than allocate a second person to a task considered minor.
He was working solo in a noisy, hot environment, focused entirely on the task in front of him and not on his surroundings — a state that narrows attention in exactly the way that makes an unplanned step backward more dangerous than it would otherwise be.
His physical reach didn’t actually allow him to access the far side of the coupling properly, and he proceeded anyway — because reaching that side by hand was described, by the people who trained him, as normal practice for this kind of task.
Climbing onto a support ledge to save time was similarly described as standard practice for this type of job, not a shortcut he invented on the spot.
The method statement in the workpack only referred readers to the general equipment manual — it never broke the specific task down into steps, which meant nobody had flagged, in writing, that a platform or a second person might be required for this particular configuration.
Why This Layer Changes the Finding
None of this excuses the outcome. What it does is relocate the actual finding. “He climbed onto the ledge because he was careless” is not supported by the evidence — he climbed onto the ledge because doing so was normalised practice, endorsed implicitly by how the task had always been done, in an environment that made careful self-monitoring harder than it should have been. That’s a different finding, and it points at a different fix: not a disciplinary conversation, but a normalized-practice problem that almost certainly exists for the next technician assigned the same task.
This is also the layer where an investigation’s credibility is most exposed. A report that jumps from “worker fell” straight to “retrain the operator” has skipped an entire layer of analysis — and any recommendation built on that gap is addressing a symptom the investigation never actually diagnosed.
The Layer Beneath This One
Preconditions explain why an action felt reasonable. They don’t explain why the organisation allowed those conditions to exist in the first place — why “light work” gets applied to tasks that require judgment, why a method statement can pass review without task-specific detail, why normalized practices go unchallenged for years. That’s the Underlying Cause layer, categorised in Tripod Beta by Basic Risk Factor, and it’s where the next several articles in this series are headed.
The Practical Question
For any recent near-miss or minor incident at your site, ask the people involved not what they did wrong, but what made their action feel reasonable at the time. If the honest answer traces back to a label, a normalized shortcut, or a document that never got specific enough — that’s the actual finding. “Be more careful” was never going to fix any of it.
Want your investigation team trained to find the actual explanation, not just the convenient one? Cikgu Barrier’s Tripod Beta Incident Investigation programme teaches the full Precondition and Underlying Cause framework, so findings point at fixable systems, not blameable individuals. Available in-house and as a public workshop across Malaysia.