A truck can be ordered. A charger can be purchased. Neither decision means the site will be ready when the vehicle arrives.

The property must be suitable. Enough power must be available. The infrastructure needs to be designed, funded and delivered. The commercial responsibilities must be clear. The final solution must also work for the people operating the fleet every day.

Each part is manageable on its own. The challenge is making all the parts work together.

Strong individual decisions can still create a weak system

The heavy-duty charging ecosystem includes fleet operators, vehicle manufacturers, property owners, grid operators, energy companies, charging providers, technology platforms and investors. Each organisation has its own targets, risks and timelines.

The fleet operator needs certainty before committing to electric vehicles. The grid operator needs a clear view of future demand. The property owner needs to understand the long-term requirements of the site. The investor needs confidence in the commercial model. The delivery partners need an agreed scope.

Each party can make a sensible decision for itself and still create a poor result for the system as a whole.

The problem becomes clearer at scale

It is possible to solve many issues within one project. People know the site. The customer requirement is clear. A local team works through the problems and finds a way forward.

But doing this once is different from doing it across a portfolio. The next site may have a different landlord, grid operator, building design, lease structure or planning process. The vehicles may arrive at a different time. Power may be available immediately at one location and take years to secure at another.

If every site begins from zero, growth creates more complexity. More projects mean more individual decisions, more interfaces and more opportunities for delays. The lessons from one deployment are often lost before the next one begins.

Real scale means making each deployment easier, faster and more predictable than the last.

Projects deliver sites. Programmes connect them.

Individual projects will always be needed. They are how infrastructure gets designed, approved and built. A programme serves a different purpose. It begins with the wider outcome and works backwards.

Where will electric vehicles be needed? When will they arrive? Which locations are most important? How much power is required now, and how could that demand grow? Who should invest, own and operate the infrastructure?

A programme creates a common structure around those questions. It connects demand across multiple locations. It helps identify which sites should move first. It creates clearer signals for power and capital. It gives delivery teams standards they can repeat while still allowing for local differences.

The site is where everything comes together

Working at the intersection of logistics real estate and energy, I see how important the site is to this transition. It is where the vehicle meets the charger, but it is also where fleet operations, property, power, infrastructure and capital meet.

Markets, regulations, grid conditions and customer requirements vary. A programme must create enough consistency to scale while leaving enough flexibility to work locally. Finding that balance is part of the work.

Collaboration needs structure

Good collaboration needs a shared outcome, trust between the parties and coordination around the decisions that matter.

The shared goal gives everyone a common destination. Trust allows the parties to be open about demand, constraints, risks and uncertainty. Coordination turns that understanding into decisions, responsibilities and action.

Making the next deployment easier

The real test of a programme is not simply how many projects it contains. It is whether the programme reduces friction.

Are customer requirements understood earlier? Can sites be assessed consistently? Are power needs visible before vehicles are committed? Can commercial and technical decisions be repeated? Do partners understand their roles? Are lessons carried from one deployment to the next?

If the answer to these questions improves over time, the programme is beginning to scale.

The transition will still be delivered one site at a time. But it must be planned as something larger.

Adapted from the original essay.