Safety Performance Is Usually an Execution Issue
One of the most common misconceptions I've encountered throughout my career is the belief that safety performance can be primarily driven by safety programs, safety meetings, posters, slogans, or compliance campaigns.
Those things have value. They can reinforce expectations, increase awareness, and help maintain focus.
But on large, complex projects, they’re rarely successful if utilized as the primary drivers of safety performance.
More often than not, strong safety outcomes are a reflection of how effectively the project itself is being executed.
Projects with strong planning, clear accountability, effective coordination, disciplined/ effective oversight, and aligned leadership tend to perform well from both an execution and safety standpoint.
Projects struggling with those same fundamentals often experience safety challenges as well.
The reason is simple.
Many safety issues are not truly safety issues.
They're execution issues that happen to manifest themselves in a way that creates risk to people.
The Relationship Between Execution and Safety
Consider a few common examples.
A crew arrives at a work location only to discover another group is already occupying the area.
At first glance, it may appear to be a safety problem.
In reality, it’s usually a coordination problem.
Example: A critical work activity begins before prerequisite tasks have been completed.
Again, the resulting risk may be categorized as a safety issue.
The underlying cause is often a sequencing issue.
A field team proceeds with work despite unresolved questions regarding scope, responsibilities, or work boundaries.
The hazard may become visible in the field, but the root cause is frequently a communication or leadership issue.
The pattern repeats itself over and over.
When coordination breaks down, risk increases.
When sequencing is disrupted, risk increases.
When accountability becomes unclear, risk increases.
When leadership loses visibility into actual field conditions, risk increases.
Safety is often the first place where these weaknesses become visible.
Why Strong Projects Tend to Be Safer Projects
The best-performing projects I've observed generally share several characteristics:
Clear Accountability
Everyone understands their responsibilities.
Decisions are made at the appropriate level.
Issues are owned rather than ignored.
When accountability is clear, gaps are identified and addressed earlier.
Effective Coordination
Multiple organizations, contractors, departments, and stakeholders often operate simultaneously on large projects.
Strong coordination ensures that work activities support one another rather than conflict with one another.
Poor coordination creates uncertainty, and uncertainty creates risk.
Logical Sequencing
Complex projects depend on work occurring in the proper order.
When schedules become compressed, there is often pressure to bypass steps, overlap activities, or accept conditions that would normally be considered unacceptable.
Every deviation introduces additional risk.
Leadership Alignment
Conflicting priorities create confusion.
When leadership teams consistently communicate expectations and reinforce project priorities, organizations tend to perform more predictably.
When leaders send mixed signals, performance becomes inconsistent.
Consistent, Effective Oversight
Oversight is not about finding fault.
It is about maintaining visibility.
Effective oversight helps identify emerging issues while options still exist.
By the time a problem becomes obvious to everyone, corrective actions are usually more difficult, more expensive, and less effective.
The Phase Where Many Projects Become Vulnerable
Interestingly, some of the greatest safety challenges occur near the end of a project.
At that point, many organizations begin focusing on completion milestones, turnover dates, punch-list activities, reductions in force, and closeout objectives.
The project team may be fatigued.
Resources may be transitioning elsewhere.
Schedules may be compressed.
The sense of urgency increases.
Ironically, this is often when organizations are most tempted to relax the very disciplines that helped them succeed throughout the project.
Coordination becomes less rigorous.
Oversight becomes less frequent.
Leadership attention shifts to the next challenge.
Small deviations begin to accumulate.
The project appears close to the finish line, but risk is often increasing.
I've seen more than one project perform exceptionally well for months or years, only to experience significant events during the final stages because execution discipline began to erode.
Another indicator worth paying attention to is when safety performance begins to deteriorate without any obvious change in work scope or risk profile.
In many cases, the safety event itself is not the root problem. It's simply the first visible symptom of a larger execution issue that has been developing beneath the surface.
When that occurs, leaders should resist the temptation to focus solely on the event and instead ask what underlying project controls, coordination mechanisms, or leadership practices may be beginning to break down.
Final Thoughts
Good safety performance is rarely the result of luck.
It is usually the result of disciplined execution sustained over time.
Organizations that consistently perform well understand that safety cannot be separated from planning, coordination, accountability, leadership, and oversight.
These elements are interconnected.
When execution is strong, safety performance often follows.
When execution begins to deteriorate, safety performance is frequently one of the first indicators that something larger is occurring beneath the surface.
In many respects, safety is less a standalone function and more a visible reflection of how effectively an organization is managing the work itself.
The question leaders should continually ask is not simply, "How is our safety performance?"
It may be more valuable to ask:
"How well are we executing the project?"
Because in many cases, the answer to one question will explain the answer to the other.