Maintaining Momentum in Critical Infrastructure Delivery

Project managers can’t treat all environments the same. In complex environments, tension exists between stable objectives and organisations’ ability to deliver using traditional methodologies. Operating assumptions such as strong logistics, adequate technical capacity, and stable regulatory environments do not hold in conflict and post-conflict areas, which alter or destroy supply lines, incite human capital flight, and give large skilled contractors reason to question working in areas that still suffer from unrest.

Where Traditional Approaches Can Fall Short

This is particularly salient because infrastructure projects pursued in complex environments often involve critical installations such as hospitals and power grids, where success cannot wait for improved conditions. These infrastructures’ purposes and requirements are generally fixed, making scope quite rigid and delivery schedules challenging, as delays may put lives in danger. The need to deliver the project may also strike a tenuous balance with security risks that would normally halt infrastructure projects.

So how do we maintain delivery momentum when the infrastructure is too important to wait for better conditions? 

Project resilience becomes especially important as delays from security issues or a lack of HR continuity become more acute. The additional constraints of these environments mean that time spent on superfluous bureaucracy, meetings, and lengthy decision-making processes translates into lost opportunities and slower progress in the field. Finally, adaptability becomes paramount, as thorough planning and inflexible delivery often lead to paralysis in these circumstances. 

These points are not always considered. Those pursuing large construction projects in complex environments often use traditional project management methodologies. This makes sense, as requirements are well-defined and unlikely to change; the project has clear objectives, deliverables, and an endpoint; and it often has multiple dependencies, including regulatory and compliance requirements. However, delivery methods must adapt to maintain momentum under environmental stressors.

• What remains stable: core requirements.

• What can change: sequencing, methods, resources and decision processes.

Using Hybrid Approaches Under Constraint

This does not mean that we should throw away what we know about project management. Many of the necessary tools already exist across established project management approaches, but they need to be selected and adapted to the operating context. The framework below brings together several principles from existing project management methodologies, keeping what is useful and shedding what is not for critical infrastructure projects in complex environments.

Cross-cutting elements

01 Strategic narrative, team and culture

Maintain a shared understanding of why the project matters, what success looks like and how individual work contributes to the overall outcome. This point becomes more salient as pressures build and project delivery success comes into question. Teams must be able to explain the project’s core objective and raise delivery issues without fear of blame. Build a culture where problems surface early, commitments are meaningful, and teams can adapt without losing direction. If the strategic narrative is known and accepted, approval processes become less numerous as direction is known and shared.

What this looks like:

• Be able to explain the project and its importance in one to two sentences. Use this as the central logic for your endeavour.

• Fixation on problem-solving and progress, not on averting mistakes or punitive measures

• Use of the strategic narrative to encourage individual autonomy and ownership

02 Efficient, flexible decision-making and governance

Establish clear decision rights, short escalation routes and proportionate controls. Make decisions at the lowest competent level, with rapid escalation when safety, scope, cost, or strategic objectives are threatened. A decision rights matrix can help remove unnecessary blockers.

What this looks like:

• Clear agendas and objectives for decision-making meetings

• Clearly identified decision-making rights that push decision-making as close as possible to the point of action

• Processes and procedures designed for the work, not the other way round

Framework principles

01 Stable core requirements

Retain the strengths of traditional project management for large-scale infrastructure: clear core requirements and explicit project boundaries. This means that unnecessary scope can be reassessed; however, adaptation should not become an excuse to renegotiate the project’s core requirements. 

What this looks like:

• Examination of differentiated project management techniques during the feasibility study (adaptive vs traditional)

• A means of communicating core requirements, why delays may occur and how they may be offset in lay terms

• Acceleration of work through a focus on core requirements and clear plan adaptation procedures to allow for efficiency improvements

02 Continuity of direction and process

Build project resilience through stable responsibilities, retained institutional knowledge, and continuity of human resources. The aim is to deliver despite adverse contextual conditions; this can conflict with efficiency, especially where human resource redundancy may be the only way to ensure leadership continuity.

What this looks like:

• Instilling the project with HR continuity arrangements, such as tandem positions and access to surge capacity

• End-to-end project supervision in the hands of one person or group of persons close enough to the works to be intimately familiar with them and the stakeholders surrounding the project

• Proper recording and reporting of decision-making, incidents and successes vs. failures

03 Minimise internal friction

Maintain only the controls necessary for quality, technical specifications, safety, finance, and regulatory compliance. Reduce unnecessary reporting, duplicated validation, avoidable approval layers and long communication lines.

There are twin objectives: 1) ensure that the implementation teams can spend the majority of their time dealing with implementation issues; 2) reduce the time between recognising a problem and taking an appropriate decision.

What this looks like:

• A team culture where unnecessary tasks can be named as such

• Clear links between processes, procedures and their intended effects

• Success metrics that promote project advancement, not siloed departmental self-importance

04 Adaptive execution

Adjust sequencing, methods, resources and short-term plans as conditions evolve. The delivery pathway should change through structured review, feedback and delegated authority. When technically safe, operationally viable and consistent with agreed requirements, consider phased delivery to bring core deliverables into function as fast as possible.

What this looks like:

• A feasibility study that looks broadly across not just the technical details of the works but the security setting, local skills, local supplies and constraints internal to the organisation

• Establish milestones, trigger points, decision owners and contingency options in advance.

• Ensure there are dates on deliverables as well as decision points if dates are not met (if we do not achieve objective X by date Y, we will review the course of action on date Z to choose between options A, B and C for future action)

Conclusion

This framework visualises a mindset for tackling infrastructure projects in unstable contexts. It is specifically adapted to critical infrastructure where the infrastructure’s essential purpose and technical requirements are relatively fixed, though the route to delivery can and should be flexible. The key takeaway is that the project methodology needs to align with the project’s core requirements and contextual reality. This may vary significantly from project to project; however, the above principles can help maintain forward momentum when security, regulatory, supply, and HR pressures threaten to bring your project to a standstill.

Keep core requirements stable, preserve the people, knowledge, and authority needed to keep delivery moving, remove unnecessary friction, and adapt the execution plan as conditions change.

Disclaimer: The views and opinions expressed in articles published on this website are those of the author and are provided for general information and discussion. They do not necessarily reflect the views of any current or former employer, client, partner organisation, or affiliated institution.