Ask most organizations how they develop safety leaders, and the answer will center on hazard recognition. Supervisors learn to identify exposed edges, improper personal protective equipment, and equipment out of position. They are trained to document what they find and to correct what they document, and these are reasonable skills. The problem is that the industry has largely stopped there, treating hazard recognition as the destination rather than the beginning.
For risk managers and insurers, this distinction carries real consequences. A workforce of well-trained inspectors will find hazards that are already visible. What it will not produce is an organization where workers voluntarily surface the conditions that precede those hazards: the schedule pressure that shortened a planning conversation, the crew's quiet uncertainty about a new procedure, or the near miss that nobody mentioned because nobody asked. The difference between those two organizations is not a training gap; it is a leadership gap.
What the Compliance Model Produces
Most safety leader development programs share a common architecture: Supervisors are taught to recognize hazard categories, conduct structured walk-throughs, and meet observation requirements. Advancement follows demonstrated proficiency in these tasks. The underlying assumption is that safety performance is primarily a function of how thoroughly a leader can assess physical conditions and that the job, at its core, is a perceptual one.
What this model tends to produce, over time, is a particular kind of supervisor: technically competent, procedurally fluent, and deeply uncomfortable with ambiguity. When something goes wrong, the instinct is to locate the deviation, the skipped step, the removed guard, or the ignored procedure. This is a useful reflex in some circumstances. However, it becomes a liability when the more important question is not what rule was broken but what conditions made breaking it feel like the only reasonable option.
The deeper problem is that inspection-oriented training teaches supervisors to look outward for risk rather than inward at the dynamics of their own teams. A supervisor who has been developed primarily as an evaluator approaches the field as something to be assessed; a supervisor developed as a leader approaches it as something to be understood. Those are different orientations, and they produce different relationships with the workforce. Those relationships determine, more than any checklist, whether critical information reaches the people who need to act on it.
Consider a straightforward at-risk observation: A worker on a three-story building throws shingles over the edge rather than carrying them to the dumpster. A compliance-trained supervisor documents the behavior, issues a correction, and closes the record; the observation is complete. What the form does not ask, and what the supervisor has not been trained to pursue, is everything surrounding that decision. The single dumpster approved for the job was placed on the opposite side of the building. The schedule left no buffer for additional trips. Someone earlier in the day made the same call, and nothing was said.
Each of those conditions contributed to the moment, and none of them appear in the observation log. The hazard was visible; the system that produced it was not. Until those contributing factors are surfaced and addressed, the next worker in the same situation faces the same pressures and is likely to reach the same conclusion.
The Research Case for Cultural Leadership
The academic literature on high-reliability organizations offers a useful counterpoint to the compliance model. Harvard Business School professor Dr. Amy Edmondson's research on psychological safety, defined as the belief that one can raise concerns without fear of punishment or embarrassment, has consistently shown that team performance is shaped less by individual skill than by the environment that leaders create. In her foundational study of hospital nursing units, Dr. Edmondson found that teams reporting the highest number of errors were frequently the highest performing. The explanation was not that these teams made more mistakes; it was that they had built environments where mistakes could be acknowledged and corrected before they compounded.1
The implications for construction and other high-risk industries are direct: Hazards rarely appear without warning. They develop through a series of small adaptations, schedule adjustments, equipment substitutions, and informal work-arounds, all of which workers navigate every day. The crews closest to the work are the first to see these conditions. Whether that information reaches anyone in a position to act on it depends almost entirely on the environment their supervisor has created. A leader trained primarily in inspection techniques is not equipped to build that environment; a leader trained in how people communicate under pressure and how to respond when they share difficult information is.
Organizational psychologist Dr. Karl Weick's work on sense-making in high-stakes environments adds another dimension. In his research on high-reliability organizations, conducted with Kathleen Sutcliffe, Dr. Weick found that teams managing complex, dynamic risk effectively share a consistent disposition: They treat near misses and weak signals as meaningful data rather than noise, actively resisting the tendency to normalize what has not yet caused harm.2 This posture does not emerge naturally from compliance training; it has to be cultivated deliberately, through the way leaders frame conversations, respond to bad news, and model curiosity about how work actually unfolds.
What Culture-Focused Development Looks Like
An example of the contrast between compliance-focused and culture-focused leader development is most visible not in how supervisors respond to incidents but in how they run a pretask plan. For a compliance-trained leader, the pretask plan is primarily a document: The hazards are identified in advance, the controls are listed, and the crew signs to confirm they have been informed. If conditions change midshift—a material substitution, a scope addition, or an unexpected tie-in with another trade—the form has already been completed, and work continues.
A culture-focused leader treats the pretask plan as a live conversation rather than a completed artifact; the document is a starting point, not a conclusion. Before work begins, the question is not only what hazards have been identified but what conditions could change and what the crew will do when that happens. Workers are directly asked the following questions: What do you see that we have not planned for? If the scope shifts this afternoon, what decision will we need to make? Who makes it? This kind of planning acknowledges that field conditions are dynamic and that the crew's judgment is a resource to be activated before it is needed, not consulted after something has gone wrong.
The difference in outcomes is not accidental. When workers have been invited to anticipate change before the shift starts, they are more likely to pause and communicate when change actually arrives. The pretask plan has established a norm: Uncertainty is expected, and raising it is part of the job. Without that norm, the default response to an unexpected condition is improvisation in silence, an adaptation that may be entirely reasonable or quietly catastrophic and that the organization will have no way to distinguish until after the fact.
This is the practical difference between developing supervisors as planners and developing them as inspectors: Inspection discovers what is already wrong, and planning shapes the conditions under which workers decide what to do next. For organizations operating in complex, variable environments, the second capability is the more consequential one, and it is the one that current training models are least likely to build.
What this Approach Does Not Solve
Developing leaders around culture rather than compliance does not eliminate the need for technical safety knowledge. Supervisors still need to understand regulatory requirements, recognize high-energy hazards, and execute standard operating procedures. The argument here is not that inspection skills are irrelevant but that they are insufficient on their own. A leader who can identify every hazard on a jobsite but has not built the trust necessary for workers to approach them with concerns is operating with an incomplete picture of the risk.
Culture-focused development also does not produce immediate, linear results. Organizations that shift their approach should expect reporting to increase before outcomes improve visibly, which is a dynamic that can be difficult to explain to clients, executives, and underwriters accustomed to reading safety performance through lagging indicators. Managing this transition requires organizational patience and, critically, a shared understanding among risk managers and insurers that an increase in reported near misses can represent improving system health rather than declining performance.
Finally, no leadership development program changes a system that is structurally rewarding silence. If supervisors are still evaluated primarily on incident rates and observation scores, the incentives for managing the scoreboard rather than managing the risk remain in place; cultural development and measurement reform have to move together. One without the other tends to produce cynicism in the field rather than genuine change.
The Risk Management Implication
For risk managers and insurers, the quality of a safety program has historically been evaluated through the metrics it produces: incident rates, audit scores, and observation volumes. These remain relevant, but they describe what a system has done rather than what it is capable of doing. The more revealing question is whether the organization has built the conditions under which accurate information flows freely from the field to decision-makers.
That question points directly to leadership; the supervisor who conducts a thorough inspection and the supervisor who creates an environment where workers raise concerns without being asked are not performing the same function. Only one of them is reducing the organization's exposure to the risks it cannot yet see. Training programs that treat hazard recognition as the primary objective are developing the first type of leader, but the industry needs more of the second.
Organizations that invest in culture-focused leader development are not abandoning attention to detail; they are applying it to a harder problem, one that compliance training was never designed to solve. For those assessing risk from the outside, the presence of that investment may be a more reliable signal of organizational health than the numbers those organizations report.
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.
Footnotes
1 Amy C. Edmondson, "Psychological Safety and Learning Behavior in Work Teams," Administrative Science Quarterly, June 1999, pp. 350–383.
2 Karl E. Weick and Kathleen M. Sutcliffe, Managing the Unexpected: Sustained Performance in a Complex World, John Wiley and Sons, 3rd Edition, 2015.
Ask most organizations how they develop safety leaders, and the answer will center on hazard recognition. Supervisors learn to identify exposed edges, improper personal protective equipment, and equipment out of position. They are trained to document what they find and to correct what they document, and these are reasonable skills. The problem is that the industry has largely stopped there, treating hazard recognition as the destination rather than the beginning.
For risk managers and insurers, this distinction carries real consequences. A workforce of well-trained inspectors will find hazards that are already visible. What it will not produce is an organization where workers voluntarily surface the conditions that precede those hazards: the schedule pressure that shortened a planning conversation, the crew's quiet uncertainty about a new procedure, or the near miss that nobody mentioned because nobody asked. The difference between those two organizations is not a training gap; it is a leadership gap.
What the Compliance Model Produces
Most safety leader development programs share a common architecture: Supervisors are taught to recognize hazard categories, conduct structured walk-throughs, and meet observation requirements. Advancement follows demonstrated proficiency in these tasks. The underlying assumption is that safety performance is primarily a function of how thoroughly a leader can assess physical conditions and that the job, at its core, is a perceptual one.
What this model tends to produce, over time, is a particular kind of supervisor: technically competent, procedurally fluent, and deeply uncomfortable with ambiguity. When something goes wrong, the instinct is to locate the deviation, the skipped step, the removed guard, or the ignored procedure. This is a useful reflex in some circumstances. However, it becomes a liability when the more important question is not what rule was broken but what conditions made breaking it feel like the only reasonable option.
The deeper problem is that inspection-oriented training teaches supervisors to look outward for risk rather than inward at the dynamics of their own teams. A supervisor who has been developed primarily as an evaluator approaches the field as something to be assessed; a supervisor developed as a leader approaches it as something to be understood. Those are different orientations, and they produce different relationships with the workforce. Those relationships determine, more than any checklist, whether critical information reaches the people who need to act on it.
Consider a straightforward at-risk observation: A worker on a three-story building throws shingles over the edge rather than carrying them to the dumpster. A compliance-trained supervisor documents the behavior, issues a correction, and closes the record; the observation is complete. What the form does not ask, and what the supervisor has not been trained to pursue, is everything surrounding that decision. The single dumpster approved for the job was placed on the opposite side of the building. The schedule left no buffer for additional trips. Someone earlier in the day made the same call, and nothing was said.
Each of those conditions contributed to the moment, and none of them appear in the observation log. The hazard was visible; the system that produced it was not. Until those contributing factors are surfaced and addressed, the next worker in the same situation faces the same pressures and is likely to reach the same conclusion.
The Research Case for Cultural Leadership
The academic literature on high-reliability organizations offers a useful counterpoint to the compliance model. Harvard Business School professor Dr. Amy Edmondson's research on psychological safety, defined as the belief that one can raise concerns without fear of punishment or embarrassment, has consistently shown that team performance is shaped less by individual skill than by the environment that leaders create. In her foundational study of hospital nursing units, Dr. Edmondson found that teams reporting the highest number of errors were frequently the highest performing. The explanation was not that these teams made more mistakes; it was that they had built environments where mistakes could be acknowledged and corrected before they compounded. 1
The implications for construction and other high-risk industries are direct: Hazards rarely appear without warning. They develop through a series of small adaptations, schedule adjustments, equipment substitutions, and informal work-arounds, all of which workers navigate every day. The crews closest to the work are the first to see these conditions. Whether that information reaches anyone in a position to act on it depends almost entirely on the environment their supervisor has created. A leader trained primarily in inspection techniques is not equipped to build that environment; a leader trained in how people communicate under pressure and how to respond when they share difficult information is.
Organizational psychologist Dr. Karl Weick's work on sense-making in high-stakes environments adds another dimension. In his research on high-reliability organizations, conducted with Kathleen Sutcliffe, Dr. Weick found that teams managing complex, dynamic risk effectively share a consistent disposition: They treat near misses and weak signals as meaningful data rather than noise, actively resisting the tendency to normalize what has not yet caused harm. 2 This posture does not emerge naturally from compliance training; it has to be cultivated deliberately, through the way leaders frame conversations, respond to bad news, and model curiosity about how work actually unfolds.
What Culture-Focused Development Looks Like
An example of the contrast between compliance-focused and culture-focused leader development is most visible not in how supervisors respond to incidents but in how they run a pretask plan. For a compliance-trained leader, the pretask plan is primarily a document: The hazards are identified in advance, the controls are listed, and the crew signs to confirm they have been informed. If conditions change midshift—a material substitution, a scope addition, or an unexpected tie-in with another trade—the form has already been completed, and work continues.
A culture-focused leader treats the pretask plan as a live conversation rather than a completed artifact; the document is a starting point, not a conclusion. Before work begins, the question is not only what hazards have been identified but what conditions could change and what the crew will do when that happens. Workers are directly asked the following questions: What do you see that we have not planned for? If the scope shifts this afternoon, what decision will we need to make? Who makes it? This kind of planning acknowledges that field conditions are dynamic and that the crew's judgment is a resource to be activated before it is needed, not consulted after something has gone wrong.
The difference in outcomes is not accidental. When workers have been invited to anticipate change before the shift starts, they are more likely to pause and communicate when change actually arrives. The pretask plan has established a norm: Uncertainty is expected, and raising it is part of the job. Without that norm, the default response to an unexpected condition is improvisation in silence, an adaptation that may be entirely reasonable or quietly catastrophic and that the organization will have no way to distinguish until after the fact.
This is the practical difference between developing supervisors as planners and developing them as inspectors: Inspection discovers what is already wrong, and planning shapes the conditions under which workers decide what to do next. For organizations operating in complex, variable environments, the second capability is the more consequential one, and it is the one that current training models are least likely to build.
What this Approach Does Not Solve
Developing leaders around culture rather than compliance does not eliminate the need for technical safety knowledge. Supervisors still need to understand regulatory requirements, recognize high-energy hazards, and execute standard operating procedures. The argument here is not that inspection skills are irrelevant but that they are insufficient on their own. A leader who can identify every hazard on a jobsite but has not built the trust necessary for workers to approach them with concerns is operating with an incomplete picture of the risk.
Culture-focused development also does not produce immediate, linear results. Organizations that shift their approach should expect reporting to increase before outcomes improve visibly, which is a dynamic that can be difficult to explain to clients, executives, and underwriters accustomed to reading safety performance through lagging indicators. Managing this transition requires organizational patience and, critically, a shared understanding among risk managers and insurers that an increase in reported near misses can represent improving system health rather than declining performance.
Finally, no leadership development program changes a system that is structurally rewarding silence. If supervisors are still evaluated primarily on incident rates and observation scores, the incentives for managing the scoreboard rather than managing the risk remain in place; cultural development and measurement reform have to move together. One without the other tends to produce cynicism in the field rather than genuine change.
The Risk Management Implication
For risk managers and insurers, the quality of a safety program has historically been evaluated through the metrics it produces: incident rates, audit scores, and observation volumes. These remain relevant, but they describe what a system has done rather than what it is capable of doing. The more revealing question is whether the organization has built the conditions under which accurate information flows freely from the field to decision-makers.
That question points directly to leadership; the supervisor who conducts a thorough inspection and the supervisor who creates an environment where workers raise concerns without being asked are not performing the same function. Only one of them is reducing the organization's exposure to the risks it cannot yet see. Training programs that treat hazard recognition as the primary objective are developing the first type of leader, but the industry needs more of the second.
Organizations that invest in culture-focused leader development are not abandoning attention to detail; they are applying it to a harder problem, one that compliance training was never designed to solve. For those assessing risk from the outside, the presence of that investment may be a more reliable signal of organizational health than the numbers those organizations report.
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.