Imagine coming home from work to find dinner already made. You eat, the
conversation is easy, and as you and your spouse clear the table, they ask if it tasted
good. You look up and say, "Well, that's what you were supposed to do." It's very easy
to understand that the likelihood of them ever doing something like that again just hit
zero.
Now move that same exchange onto a jobsite: A worker ties off before working
at height, without being told and without a supervisor watching. Or a crew member stops
a task and reports a near-miss instead of letting it go unnoticed. A supervisor who says
nothing because that behavior is simply the job is making the same mistake as the spouse
at the dinner table. It just draws less attention because nobody is standing there
waiting to be thanked.
A System Built to Correct, Not Recognize
This is not a training gap or a lapse in supervisor courtesy; it's
just baked into how most organizations design safety systems. Audits, corrective
actions, and incident write-ups consume most of a safety program's structure and
budget. Recognition, if it exists at all, tends to live at the edges, reserved for
the rare and exceptional, rather than built into the daily operations of the
program.
Ask a leadership team why, and a common answer surfaces quickly:
"We don't want to reward someone for doing what they were already supposed to do."
It's a fair instinct on its face; it's also the wrong frame.
Reward Does Not Equal Reinforcement
Reward and reinforcement are not the same thing, though most
leaders use them interchangeably. A reward implies exceeding some baseline: a bonus
for finishing early or a plaque for zero incidents in a quarter. Reinforcement means
increasing the likelihood that a behavior repeats, regardless of whether it exceeded
expectations. That distinction is the difference between a safety program that only
notices the exceptional and one that shapes daily behavior.
Recognition, in this sense, is not reward; it's reinforcement.
Three Tiers, Not Just One Program
Once recognition is understood that way, the structure that it
needs changes. A single program, no matter how well designed, cannot reinforce
behavior at every level where it needs to happen. What organizations actually need
is not more budget for one recognition effort but three separate tiers of
recognition, each doing a different job at a different altitude of the
organization.
Ground-, Mid-, and High-Level Recognition
A foreman who watches a worker tie off before climbing, without being asked, has a choice in that instant. Say something, or let it pass as expected behavior.
Ground-level recognition is that choice made correctly: immediate,
unbudgeted, and over almost as soon as it happens. It costs nothing but requires the
foreman to actually notice, which is a habit built through expectation, not training
modules.
A gift card handed out at a Friday toolbox talk, tied to a
specific near-miss report from earlier that week, is mid-level recognition at work.
This tier lives with the supervisor or the site, runs on a monthly or milestone
rhythm, and carries a modest, real budget. The point is not the size of the gesture;
it's that the gesture is tied to something specific enough that the worker remembers
what it was for.
Then there is the annual banquet—a name called from a stage, a
plaque, and applause from people who were not on-site the day that the behavior
happened. High-level recognition carries the highest visibility and the highest
cost, and for that reason, it's almost always the tier that survives budget
conversations. It's also the tier furthest removed from the moment it is meant to
reinforce.
Why the Top Tier Alone Isn't Enough
The mistake that organizations make is treating the high tier as
sufficient on its own. Reinforcement that arrives once a year, disconnected from the
specific behavior it is meant to recognize, does very little to shape what happens
on a Tuesday afternoon on a jobsite three states away. Sidney Dekker's research into
incident reporting found something similar: Workers do not stop reporting because
they fear punishment; they stop reporting when they lose the conviction that the
organization will do anything meaningful with what they report.
Recognition follows the same logic: A worker who never hears
anything about a behavior, positive or otherwise, learns the same lesson as one who
reports and hears nothing back—the system is not paying attention. Sustaining all
three tiers takes more coordination than sustaining one. Ground-level recognition
depends on supervisors who are trained to notice and comfortable saying something in
the moment, which is a cultural investment, not a financial one. Mid- and high-level
recognition depends on someone owning the cadence so it doesn't quietly become an
annual afterthought.
What Risk Managers and Insurers Should Ask
For risk managers and insurers evaluating a contractor's safety
program, the presence of a recognition program is not the useful signal; the useful
signal is whether that program operates at more than one altitude.
A contractor with a polished annual awards banquet and nothing
else is recognizing the exceptions while ignoring the daily behavior that the
program depends on. Ask whether supervisors are equipped and expected to recognize
behavior in the moment, not just whether an award exists at the top of the org
chart.
Back at the Dinner Table
Back at the dinner table with your spouse, the fix was never
complicated. The moment called for a simple acknowledgment, not a monetary reward or
a grand expansive gesture. Self-sustaining safety systems work the same way: The
recognition that matters most usually costs the least and happens closest to where
the behavior occurred.
Opinions expressed in Expert Commentary articles are those of the author and are not necessarily held by the author's employer or IRMI. Expert Commentary articles and other IRMI Online content do not purport to provide legal, accounting, or other professional advice or opinion. If such advice is needed, consult with your attorney, accountant, or other qualified adviser.
Imagine coming home from work to find dinner already made. You eat, the conversation is easy, and as you and your spouse clear the table, they ask if it tasted good. You look up and say, "Well, that's what you were supposed to do." It's very easy to understand that the likelihood of them ever doing something like that again just hit zero.
Now move that same exchange onto a jobsite: A worker ties off before working at height, without being told and without a supervisor watching. Or a crew member stops a task and reports a near-miss instead of letting it go unnoticed. A supervisor who says nothing because that behavior is simply the job is making the same mistake as the spouse at the dinner table. It just draws less attention because nobody is standing there waiting to be thanked.
A System Built to Correct, Not Recognize
This is not a training gap or a lapse in supervisor courtesy; it's just baked into how most organizations design safety systems. Audits, corrective actions, and incident write-ups consume most of a safety program's structure and budget. Recognition, if it exists at all, tends to live at the edges, reserved for the rare and exceptional, rather than built into the daily operations of the program.
Ask a leadership team why, and a common answer surfaces quickly: "We don't want to reward someone for doing what they were already supposed to do." It's a fair instinct on its face; it's also the wrong frame.
Reward Does Not Equal Reinforcement
Reward and reinforcement are not the same thing, though most leaders use them interchangeably. A reward implies exceeding some baseline: a bonus for finishing early or a plaque for zero incidents in a quarter. Reinforcement means increasing the likelihood that a behavior repeats, regardless of whether it exceeded expectations. That distinction is the difference between a safety program that only notices the exceptional and one that shapes daily behavior.
Recognition, in this sense, is not reward; it's reinforcement.
Three Tiers, Not Just One Program
Once recognition is understood that way, the structure that it needs changes. A single program, no matter how well designed, cannot reinforce behavior at every level where it needs to happen. What organizations actually need is not more budget for one recognition effort but three separate tiers of recognition, each doing a different job at a different altitude of the organization.
Ground-, Mid-, and High-Level Recognition
A foreman who watches a worker tie off before climbing, without being asked, has a choice in that instant. Say something, or let it pass as expected behavior.
Ground-level recognition is that choice made correctly: immediate, unbudgeted, and over almost as soon as it happens. It costs nothing but requires the foreman to actually notice, which is a habit built through expectation, not training modules.
A gift card handed out at a Friday toolbox talk, tied to a specific near-miss report from earlier that week, is mid-level recognition at work. This tier lives with the supervisor or the site, runs on a monthly or milestone rhythm, and carries a modest, real budget. The point is not the size of the gesture; it's that the gesture is tied to something specific enough that the worker remembers what it was for.
Then there is the annual banquet—a name called from a stage, a plaque, and applause from people who were not on-site the day that the behavior happened. High-level recognition carries the highest visibility and the highest cost, and for that reason, it's almost always the tier that survives budget conversations. It's also the tier furthest removed from the moment it is meant to reinforce.
Why the Top Tier Alone Isn't Enough
The mistake that organizations make is treating the high tier as sufficient on its own. Reinforcement that arrives once a year, disconnected from the specific behavior it is meant to recognize, does very little to shape what happens on a Tuesday afternoon on a jobsite three states away. Sidney Dekker's research into incident reporting found something similar: Workers do not stop reporting because they fear punishment; they stop reporting when they lose the conviction that the organization will do anything meaningful with what they report.
Recognition follows the same logic: A worker who never hears anything about a behavior, positive or otherwise, learns the same lesson as one who reports and hears nothing back—the system is not paying attention. Sustaining all three tiers takes more coordination than sustaining one. Ground-level recognition depends on supervisors who are trained to notice and comfortable saying something in the moment, which is a cultural investment, not a financial one. Mid- and high-level recognition depends on someone owning the cadence so it doesn't quietly become an annual afterthought.
What Risk Managers and Insurers Should Ask
For risk managers and insurers evaluating a contractor's safety program, the presence of a recognition program is not the useful signal; the useful signal is whether that program operates at more than one altitude.
A contractor with a polished annual awards banquet and nothing else is recognizing the exceptions while ignoring the daily behavior that the program depends on. Ask whether supervisors are equipped and expected to recognize behavior in the moment, not just whether an award exists at the top of the org chart.
Back at the Dinner Table
Back at the dinner table with your spouse, the fix was never complicated. The moment called for a simple acknowledgment, not a monetary reward or a grand expansive gesture. Self-sustaining safety systems work the same way: The recognition that matters most usually costs the least and happens closest to where the behavior occurred.
Opinions expressed in Expert Commentary articles are those of the author and are not necessarily held by the author's employer or IRMI. Expert Commentary articles and other IRMI Online content do not purport to provide legal, accounting, or other professional advice or opinion. If such advice is needed, consult with your attorney, accountant, or other qualified adviser.