From March issue, NZ Manufacturer magazine

 

Stephanie Pretorius, Managing Principal, Argon & Co

 Infrastructure projects operate under relentless pressure: tightening margins, rising complexity, public scrutiny, and near-zero tolerance for delay.

Yet many delivery environments still default to recovery — catch-up programmes, overtime, task-force escalation — only after performance has already deteriorated.

In manufacturing, results improve when the production system is stabilised. Once flow is predictable, investment in capability, automation, and quality at source delivers compounding return. Stability creates ROI. Construction rarely affords itself that discipline.

Each project is framed as unique, variability is normalised, and management attention focuses on reacting to disruption rather than designing it out.

But the underlying principle does not change. Stability precedes return. In infrastructure delivery, prevention — of defects, rework, design ambiguity, coordination failure, and flow breakdown — is the equivalent of investing in a stable production line.

It is a deliberate decision to engineer reliability into planning, commercial strategy, stakeholder alignment, and daily management before work intensifies.

The most reliable infrastructure projects take a different path. They do not wait for delay to surface. They design systems that prevent instability from taking hold.

Prevention is not a support activity. It is the strategy.

Why recovery fails as a performance model

Most delays are not caused by a single failure or a lack of effort. They are the predictable outcome of how work is planned, coordinated, and managed across the system.

Common causes include:

• Unreliable handoffs between teams and contractors
• Late decisions and unresolved constraints
• Recurring problems across projects not addressed as delivery risk
• Overloaded schedules with no capacity for variation
• Poor visibility of emerging performance risks
• Escalation that happens too late—or not at all

By the time these issues show up on a critical path report, the cost has already been incurred. Recovery actions may stabilise the short term, but they rarely improve the system that created the delay.

Implementing an efficiency strategy—Not just cost control

An effective prevention strategy starts with efficiency, not cost cutting.

Efficiency in infrastructure delivery means:

• Reducing waiting, rework, and interruptions
• Improving flow across interfaces and packages
• Ensuring work is ready before it is released
• Designing plans that absorb variation rather than amplify it

This requires deliberate choices upstream—simplifying workflows, clarifying responsibilities, and aligning plans across disciplines. The goal is not to push teams harder, but to remove friction from the system so progress becomes predictable.

Addressing delay preventatively—Where it actually starts

Delays rarely start in the field. They start in planning, decision-making, and coordination.

Preventative action focuses on:

• Early identification and removal of constraints
• Clear definition of “ready” work
• Establishing process that create reliable promises between teams
• Delivery risk assessment based on prior project experience

When these elements are in place, risk of delays are mitigated and workflow protected.

Daily management: Effective leadership action

Prevention only works if information is acted on quickly. Daily management routines create the mechanism for this by:

• Making performance visible at the point of work (team KPI’s)
• Encouraging early escalation without blame
• Connecting frontline reality to leadership decisions
• Enabling fast, coordinated responses to emerging risk

This is not about more meetings. It is about structured, focused conversations that keep the system stable and responsive.

Connecting leadership from top to bottom

One of the most common failure points in infrastructure delivery is the gap between leadership levels. Horizontal silos disconnect strategic intent from operational reality.

Prevention requires structured design of leadership communication to align levels:

• Transparency and escalation for alignment on status
• Clear performance signalling between levels
• Blame free culture that encourages openness

When leaders of all levels are on the same page, performance improves without adding pressure.

From enduring problems to designed performance

Infrastructure delivery does not need more heroics. It needs better systems introduced from the start of the project to support optimal performance.

Projects that prioritise prevention consistently experience fewer disruptions, lower rework, more reliable outcomes, and reduced pressure on people. Most importantly, they improve rather than endure problems. Performance is no longer recovered—it is designed.

The choice is clear. We can continue managing the consequences of poor systems—or we can design performance into the way work is done.

Prevention is not passive. It is the most active strategy available.