Thought Leadership

Engineering for Complexity: How the UK’s next decade of mega programs can create lasting social value

Why integrated leadership, early planning, faster consenting and community outcomes will define the success of the next generation of major infrastructure
Environmental Water
James LeVesconte
Project Management Director and Program Manager
Highway

The U.K. is entering a defining decade for infrastructure, both in ambition and the sheer density of delivery risk. As of 2024, the government’s Major Projects Portfolio comprised 227 projects with a combined whole-life cost of $1.1 trillion (£834 billion). The national pipeline is broader still. The last National Infrastructure and Construction Pipeline report listed 660 projects and $217 billion (£164 billion) of planned public and private investment. The Planning Inspectorate said it delivered 17 recommendations on national infrastructure applications and provided advice on roughly 80 potential projects in 2024/25. From Sizewell C and Eastern Green Link through to the Strategic Resource Options, there’s widespread growth opportunities across sectors, but they come with higher complexity. 

These programs will be built under public scrutiny, over timelines long enough to outlast leadership teams, procurement cycles and, sometimes, public patience. The winners will be the teams that collaboratively convert complexity into results using the right delivery model, and critically, do it in a way communities can easily see and feel the social value outcomes. 

My own career has moved from flood and coastal risk management into resourcing for London-based programs like Tideway and Heathrow, then onto major program leadership — including several years on the operational leadership team of Lower Thames Crossing. My biggest lesson from all that work, repeated across sectors, is simple: there's no silver bullet or technological solution to handle this rising complexity. It starts as a people-and-leadership question, and then culture and innovation take over.  

Start where complexity lives: the interfaces 

Large programs unravel in the handoffs between design packages, the overlooked logistics constraint, the “someone else owns that” interface. The most common failure pattern I've seen in major programs comes from disciplines operating in silos. Teams progresses their own pieces individually, and don’t speak to other groups early enough to improve decision-making. When that happens, costs escalate, tensions harden and the program becomes a contest between workstreams and rival companies rather than a collective push toward outcomes. 

The answer here is partly about choosing the right delivery model and procurement strategy. It’s also about forming an integrated leadership team early, with experienced, industry-leading talent, chartered around real objectives, constraints and opportunities — and given clear decision rights. It's like team sports: you can field the best players but still underperform if the team lacks shared purpose and discipline, alongside the right incentive. On a major program, the leadership team is responsible for building a shared, multi-company culture with the right behaviors and collaboration to break that complexity down into smaller parts which the most-suited team members can tackle.  

For clients, the pain point is direct: interface risk becomes schedule risk. Avoid siloed working from day one, or pay for it later in redesign, claims and lost time. 

Treat consent as the first construction milestone 

In the U.K., consent is a material part of delivery. The trap is familiar. During examination and public scrutiny, it can be tempting to make commitments that sound reasonable in the room but become operational constraints later. Once locked in, they’re difficult — sometimes impossible — to unwind without reputational damage or significant cost and schedule impacts.  

Then comes the second trap: treating the primary consent as the finish line. During the development or pre-primary consent stage, securing consent quickly and cost-effectively is often seen as the goal. This can result in missed risks and opportunities within the long-term program mission. Sometimes, there are benefits in going slower or investing more during the earlier stages which allows a project or program to accelerate the ultimate completion date or save whole life costs. 

Securing the primary consent should be celebrated. In reality, major programs often then face a long tail of secondary consents and planning applications that can multiply into the hundreds — and quietly become the critical path. On a recent large-scale transportation program in the U.K., there were over 8,000 separate permissions required during the first phase alone, many of which were managed concurrently or in rapid succession. If your team isn't integrated or is missing one central source of truth, this can dictate the schedule.  

The practical move is to integrate consenting and constructability early so that the public commitments match delivery reality. It's also critical to embed the consents function inside the delivery “control room.” That reduces late-stage surprises and keeps the program moving when scrutiny is highest. 

Make social value a delivery discipline  

Social value is often described as an outcome. On long, high-scrutiny programs, it's also a method. 

Communities don’t experience these projects as “nationally significant.” They experience them as traffic, noise, disruption and uncertainty over several years. This is why sequencing matters. If visible benefits arrive early, such as local access improvements, environmental enhancements or amenities that communities can use while construction continues, the program earns credibility and time. 

It also changes who must be in the room. Social value can't sit adjacent to the “real” work. In a recent major water resilience scheme, we explicitly challenged ourselves to ensure that social value leadership must sit at the core alongside master planning and technical leadership, and it must be locally grounded. Otherwise, large international delivery teams risk telling communities what they need rather than shaping outcomes with them. It goes beyond being a trust issue; it's a risk issue. 

Build a single source of truth and protect continuity for a decade 

When dozens of organizations converge, data becomes a governance issue. If each party brings its own systems and standards, the gaps between tools become gaps in accountability. I’ve seen this go wrong in mobilization: one organization brings a scheduling tool, another brings a document management system, another brings its own client platform — and everyone assumes they will connect.  

Then reality arrives. They don’t talk to each other, and the program pays for it in friction and duplicated effort, while accountability is blurred. That’s why a common data environment and a single source of truth are more than technology ambitions; they’re risk controls. On complex programs with multiple commercial entities and stakeholder ecosystems, the “truth” must be designed, governed and maintained. If it isn’t, the program drifts into competing versions of what's happening.  

This is also where lessons travel well across borders. On a recent program in the U.S. where a complex water reservoir was delivered under tight constraints, the work reinforced a principle I come back to in every major program: you can't manage risk you can't see. Instrumentation and monitoring alongside disciplined information management were the backbone of assurance, decision-making and long-term performance. That mindset translates directly to the U.K.’s next wave of major water resilience programs. Build the data spine early, and the program gains the ability to move faster with confidence.  

Continuity is the second half of the equation. These programs don’t have a static org chart; they move from early engagement into detailed design, then major construction, then commissioning and long-term operations. The only way to sustain momentum is to keep a stable thread of decision-making and institutional memory as specialist capabilities rotate in and out.  

And finally, keep curiosity as a delivery posture. On long-life assets, the unknowns matter: future technologies, shifting policy, new methods and collaborations with local universities and innovative suppliers. The teams that ask what could exist in six years, and what can be built now to keep options open, are the teams that turn ambition into durable results.  

The U.K.’s next decade of major programs will define growth, resilience and public trust. The winners will be the teams that engineer for complexity with integrated leadership, consent discipline, social value that shows up early and data that binds the delivery machine together.