What I'd Tell Myself a Decade Ago About This Industry

Two weeks ago, I started this series intending to write about a handful of separate, somewhat disconnected topics: the grid connections crunch facing UK data centres, the detail of BS 7671's EV charging requirements, the discipline required around underground cable records, the skills shortage in specialist trades, the changing role of the humble car park. Distinct subjects, each worth fourteen-hundred words on its own.

Writing through them in sequence has made something obvious that wasn't obvious to me when I started: these aren't separate problems. They're the same problem, observed from different points in a project's life.

The thread running through every article

The grid connection queue, the duct route design, the cable pulling tension calculation, the as-built record, the EV charging circuit, the new battery storage chapter in BS 7671 — every single one of these is downstream of a single, deceptively simple question: did anyone think carefully about delivery before the decisions that determine delivery got locked in?

The 460% growth in the speculative connections queue exists because, for a long time, the system rewarded early applications over genuinely deliverable ones — a structural failure to distinguish intention from delivery capability at the point where it mattered most. The recurring pattern of duct banks getting poured before anyone properly checks whether the proposed cable route can actually be pulled within the cable's mechanical limits is the same failure, replayed at a different scale and a different stage of the same kind of project. The documentation gaps that make underground works genuinely dangerous, and the skills shortages that quietly threaten programme delivery on hyperscale projects, are both, in their own way, failures to plan for delivery realities early enough that planning could still influence the outcome cheaply.

What changes when you see it this way

This reframing matters because it changes where effort gets directed. If you treat grid connection strategy, cable route design, documentation discipline, and workforce planning as genuinely separate problems, you end up solving each one reactively, as it individually becomes urgent — usually later than would have been ideal, and usually at a point where the available solutions are more expensive than they needed to be.

If you recognise them as expressions of the same underlying discipline — closing the gap between plan and physical reality, as early and as cheaply as possible — you start asking a consistent question across every stage of a project, rather than a different question each time a different specialist problem surfaces. Can we actually build what we're designing? Can we actually deliver what we're committing to in this application? Can we actually prove, later, what we actually did?

The decade ahead

If I were advising myself a decade ago, knowing what the UK energy transition would demand of construction and infrastructure delivery by the mid-2020s, I think the single most useful thing I could say is this: the industry's best opportunities over the next decade will not go to whoever has the most ambitious plans.

They'll go to whoever consistently closes the gap between the plan and the physical reality of building it — fastest, most reliably, with the least rework, and with the clearest evidence afterward of exactly what was delivered. Ambition is increasingly cheap to produce. Genuinely reliable delivery, at the pace and scale this transition requires, remains scarce — which is precisely why it's valuable.

That's been the real subject of this entire series, even on the days I was ostensibly writing about queue reform, wiring regulations, or underground cable records. Every one of those topics, looked at closely enough, turns out to be about the same thing: the discipline of treating delivery as a first-class concern from the earliest possible moment, rather than a problem to be solved once the more exciting decisions have already been made.

A closing thought

This is the last article in the fourteen-day series, and it feels right to end without an engagement question, a call to action dressed as curiosity, or a prompt designed primarily to generate comments. The series has had plenty of those already, and they've genuinely improved the thinking here — several of the angles explored in the later articles came directly from conversations and challenges raised on earlier posts.

So instead, simply: thank you for following along, for the comments, the corrections, and the war stories shared along the way. If any of what's been covered over these two weeks is relevant to a project you're currently working on — grid strategy, cable routing, documentation, or simply working out where your specific challenge actually sits in this wider system — I'd genuinely welcome the conversation.