When Two Safety Systems Both Say They Have You Covered

A wireline hand on a night shift needs an answer in under thirty seconds, and neither of his two safety systems gives him one.

He's in the middle of the task. The permit references one management system for the lift plan and a separate one for the procedure that controls pressure. On this sequence, the two don't quite line up. One is silent on a step the other treats as mandatory. He doesn't stop to pull up both manuals and reconcile them. Nobody does, not at 2 a.m., not with the crew waiting. He does what he watched the senior hand do on the last job like this one, and the crew moves on. The moment disappears into the shift log as a normal night, because nothing went wrong this time.

The Shift You Might Not Have Noticed

Somewhere in the last decade, your operation likely added a second, third, or fourth layer of documented safety management on top of what already existed. Each one was added for a good reason. A new personnel safety initiative here, a framework for managing integrity there, each one built by a well-intentioned team trying to close a real gap. Individually, every page is defensible. Collectively, they've built something no field hand can hold in his head during a live task.

If you handed a supervisor a specific, ordinary compliance question right now and gave them nothing but current policy to answer it with, most operations couldn't say how long it would take to find the answer. When the search takes longer than the task itself, the system is telling you something the training records can't.

This Pattern Has a Name

Todd Conklin, who spent 25 years in the Human Performance program at Los Alamos National Laboratory, built his work around a line that has stuck with a generation of safety leaders: "Safety is not the absence of events, it's the presence of defenses." More paper isn't automatically more defense. A defense that a worker can't actually retrieve and apply in the two minutes he must make a call is just weight on a shelf that nobody has time to reach for.

Conklin's fourth principle of human performance puts responsibility exactly where it belongs. Individual behavior is a function of the organization's systems, processes, and culture, not a function of individual willpower or good intentions. When your wireline hand defaults to imitation instead of procedure, that's the system speaking through him.

Erik Hollnagel, the safety-science researcher who developed the Safety-I/Safety-II framework, gives this gap a name too. Work-as-imagined is the version of the job that lives in your policy manuals, the version your management systems assume is happening. Work-as-done is what happens on the rig floor, where people are constantly adapting to real conditions your paperwork didn't fully anticipate. The distance between those two versions of the job is information, not defiance, and right now your organization may not be collecting it.

What Actually Fixes This

This isn't solved by writing a fifth system to reconcile the first four. It isn't solved by another training module reminding field hands to "know the procedures." The volume and the overlap are a leadership design problem, and design problems get fixed by leadership, not by asking the workforce to absorb more.

Put it to the test this week. Pick one task your crews perform regularly, something ordinary, not exotic. Ask a supervisor to sit down with your current manuals, cold, and find the complete answer to what's required across every system that touches that task, then time how long it takes them. If your best people can't do it quickly, your newest hire on a night shift has no chance, and he's not going to try. He's going to do what he watched someone else do.

That's not a compliance failure on his part. That's your organization's answer to a question nobody's been asking out loud. Can a real person, under real conditions, carry what we've written down?

Across nearly three decades in this industry, I've found that paperwork is rarely wrong on any single page. The failure lives in what happens when you stack all those individually correct pages on top of each other and hand the result to someone who has thirty seconds to decide.