The Cost of Leadership — and the Price of Getting It Wrong in Major Projects

In large-scale projects — data centers, industrial investments, and complex infrastructure — leadership is often discussed as a cultural or organizational topic. In reality, it is one of the most decisive economic variables in the entire project, because it determines how reliably work is planned, coordinated, and executed under pressure.

There is little ambiguity in the evidence. Poor leadership does not simply create inefficiency; it drives measurable losses. Deficiencies in leadership sit behind accidents, disruptions, and performance variability, and the pattern is consistent across high-risk industries: what leaders pay attention to becomes what the organization treats as real. Research on safety climate has repeatedly shown that leadership behavior shapes priorities at the frontline, and analyses of major failures keep pointing to the same underlying mechanism — systemic weaknesses in how work is led, interfaces are managed, and trade-offs are handled when schedules tighten.

In practical terms, poor leadership in major projects rarely looks dramatic. It shows up as small, repeated failures of coordination that quietly accumulate into delay, rework, degraded quality, and unsafe conditions. Interfaces remain vague, so contractors optimize locally and problems move downstream instead of being solved. Risks are discovered late because early signals are not surfaced, or because people have learned that raising concerns changes nothing. Supervisors spend their limited time enforcing documentation while the real work drifts away from the plan. Under production pressure, deviations become normal and "temporary" workarounds turn into the operating model. The cost is rarely visible in a single line item, but it embeds itself across the project lifecycle until it becomes unavoidable — lost time, strained relationships, and reduced margins.

Local rationality: why nobody comes to work intending to fail

Here is a critical insight: nobody comes to work intending to fail. Sidney Dekker's concept of local rationality explains why. People make decisions that are rational given the information they have, the pressures they face, and the goals they understand. When a supervisor cuts a corner, it is not because they want the project to fail; it is because from their vantage point, the trade-off between schedule pressure and the risk they perceive seems justified. When a contractor optimizes locally instead of coordinating across interfaces, it is because the interface expectations were never made clear. When people do not surface early signals, it is often because they have learned that speaking up does not change anything. The problem is not the people; it is that the system — and the leadership within it — has not made the right goals, trade-offs, and information visible.

This reframing changes everything. Instead of asking "why did they fail," the question becomes "what did the system not make clear." And that is a leadership problem that can be solved.

Safety I vs Safety II: why systems alone don't solve it

The inverse is equally important. When leadership functions effectively at the line level — where daily decisions are made and work is actually performed — the impact is immediate and measurable. This is also where many organizations misfire. They respond to safety challenges by adding systems, processes, and reporting requirements. Those tools have their place, but they do not solve the core issue in complex projects: HSE performance is not primarily a system design problem; it is a leadership execution problem.

This distinction matters more than it first appears. Erik Hollnagel's Safety I and Safety II framework offers clarity here. Safety I is reactive: it focuses on preventing failures, adding controls, and ensuring compliance. Safety I is necessary — but in complex projects, Safety I alone creates a false sense of security. It assumes that if you build enough barriers and require enough documentation, the system will be safe. What Safety I misses is that safety in real operations depends on how people adapt, prioritize, and coordinate when conditions change. That is Safety II: the capacity of the system to succeed under varying conditions, not just to avoid failure under ideal ones.

The problem is that many organizations treat Safety I as if it were sufficient. They add more procedures, more reporting, more audits. But in a major project where interfaces are complex, where schedules compress, and where people must make real-time decisions under incomplete information, Safety II is what actually determines whether the project stays on track or begins to drift. Safety II is built through leadership — through the quality of decisions made at the frontline, the clarity of handovers, the speed of escalation, and the willingness to surface problems early. And because people are rational within their own context, good leadership does not require changing people; it requires changing the context in which they make decisions.

What effective leadership looks like on site

Leadership execution becomes concrete through repeatable routines that control the work, not just the paperwork. On well-led sites, the day starts with a short alignment that makes change visible: what is different today, where the critical interfaces are, what the highest-risk step is, and who owns it. During the shift, leadership is present in a way that is operational rather than ceremonial: checking whether the plan is still valid, noticing drift early, and escalating before small issues become schedule-impacting events. At the end of the shift, learning is captured while it is still fresh, not as an investigation after harm, but as a practical adjustment to tomorrow's plan. This routine is not about control for its own sake; it is about making sure that the people doing the work have the clearest possible picture of what success looks like and what obstacles stand in the way.

Make production pressure discussable

A second concrete method is making production pressure discussable instead of hidden. In major projects, pressure is normal; the leadership difference is whether it becomes managed trade-offs or silent drift. When supervisors and managers explicitly name the moments where the team will be tempted to cut corners — and agree in advance how that temptation will be handled — work stays controllable. When that conversation never happens, the project pays for it later through variability: last-minute changes, unplanned exposure, and "surprises" that were visible to the people doing the work but never reached decision-makers in time. This is coaching in its most practical form: helping people see the trade-offs clearly so they can make better decisions.

Lead the interfaces

Equally decisive is how interfaces are led. Most project losses live between organizations, scopes, and handovers, and interface failure is often misdiagnosed as individual performance. Effective leadership makes handovers concrete by defining what "ready" means, clarifying ownership on both sides, and setting clear thresholds for when work must stop and escalate. When nobody owns the interface, the site compensates with improvisation, and the schedule eventually compensates with delay. Good interface leadership removes ambiguity, which is exactly what allows people to succeed.

Field presence as a reliability mechanism

Field presence is another method that separates effective leadership from compliance theatre. Presence is not walking around to catch mistakes; it is structured engagement that improves the quality of information in the system. Leaders who ask what is different today, what is hardest to do safely, and what obstacle is slowing safe execution create a climate where weak signals are surfaced early. That climate is not "soft"; it is a reliability mechanism. It reduces the time between signal and response, which is exactly what complex projects need. And it sends a clear message: your judgment matters, and we want to hear it before something goes wrong.

Coaching line management capability

Finally, developing line management capability through coaching is one of the highest-leverage interventions available. When supervisors are equipped to lead conversations rather than merely enforce rules, the dynamic shifts. Risk identification becomes earlier and more accurate, coordination improves across contractors, and deviations are treated as system signals rather than personal failures. People begin to understand not only what is required, but why it matters, which reduces friction and increases follow-through. Coaching works because it assumes competence and good intent — and then helps people see the full picture so they can make better decisions. The result is not only fewer incidents, but also better productivity and more stable delivery.

The economic implication

The economic implication is straightforward. Investing in leadership capability is not an overhead; it is a lever for performance. The cost of poor leadership is nonlinear, often escalating rapidly as complexity increases. Conversely, effective leadership stabilizes the system, reduces variability, and enables projects to deliver as intended.

For organizations operating in large and complex environments, the question is not whether leadership matters. The question is whether it is being developed and exercised where it has the greatest impact — at the frontline, every day. Because in the end, HSE is not defined by the sophistication of a management system, but by the quality of leadership that brings it to life.