Safety auditors now become the safety police. I haven’t talked to a safety professional who hasn’t bristled at the notion that, at least part of their job is to serve as the safety police. Sad but true. One would think that the front line supervisor should be playing the role of rule enforcer. After all, it is probably in their job description and they are the folks most likely to be present when front line workers violate rules, or at least present enough to learn that it happened because of equipment damage, a disrupted process, or their own spidey-senses (supervisors know).

Acting safely can be punishing! Safety is punishing because it creates a Response Cost. A famous behavioral dude named Tom Glibert made a strong point in his Behavioral Engineering Model: Behavior is costly.

How much do you know about your workforce’s minor injuries? What is your reporting culture around minor injuries? What percentage of minor injuries do you know about? Some of these minor injuries are above the waterline. This could be the case if a worker suffers a cut and seeks first aid and it gets recorded or a manager witnesses the minor injury. You can also see some of the iceberg right below the waterline, although it may be distorted. Here we may learn about a minor injury sometime after the fact or learn about one through the grapevine.

Labels are Easy. It’s quite easy to give ourselves a label, isn’t it? We look at our behavior, see the outcome of it, and we give ourselves a label. In fact, labeling is quite popular in modern business where management training often involves some personality test like the Colors or the MBTI (Myers Briggs Type Inventory) where we learn everyone’s label in hopes of better collaboration. We are taught to describe ourselves

Now listen carefully: your system is perfectly designed to get the results you received… because your system is perfectly designed to produce the behaviors you shaped. You built it, folks. You and your engineers, and your managers, and your industry egg-heads, and your consultants, and people you’ll never know who built parts of your system long ago. All of you constructed the systems, processes and environment that put the worker in a position to take the risk.

It is conventional wisdom. Don’t do things that can get you hurt. After all, who wants to get hurt? Who wants their life changed because of something that happened at work? I think we can all agree that getting hurt at work really sucks for all involved.

Have you heard the old adage: You can’t manage what you can’t measure? Frankly, if you cannot measure something, you’re merely guessing. There is too much at stake in safety to guess. Your job, in fact everyone’s job, indeed the job of ALL your safety management systems and processes is to measure behavior. Because it takes discipline, measurement is the hardest management practice to execute, yet the most essential. And that discipline is practiced through observation.

Our attitudes don’t always translate into behaviors. That’s the bottom line. Similarly, attitudes of workers, supervisors and leaders don’t always translate to the critical safety behaviors needed at work. Similarly, values and intentions also don’t always translate to actions either.

Fear is the Devil of safety programs, while trust is the safety program Saint. It’s true that management actions can reduce fear, but as any leader trying to change a culture knows, you need those small wins to reinforce the trust your workforce can demonstrate when they open up and start to report.

Fortunately, getting your feelings hurt is NOT a recordable incident. True, no OSHA or other government reporting need be done, no incident investigations must ensue, and I’m not sure it even qualifies as a near miss. Instead, I’d argue it is the opposite of an incident.

To maintain the most optimized processes, we need to foster a safety culture that fosters “attentive human beings” who are on the alert for something out of the ordinary that may result in an injury or process event.