Somewhere right now, a program director is presenting a slide that says a project is green. It isn't. The interconnection queue slipped, a supplier went quiet two weeks ago, and the one engineer who can unblock it is committed to three other programs. The slide is green because the slide was built from last month's status calls.

That's the energy transition's quiet risk

The public conversation is about technology and capital: panels, batteries, transmission, rate cases. But talk to the people delivering these programs and you hear a different story. The engineering is largely understood. What's breaking is coordination at portfolio scale: thousands of interdependent projects, shared crews and scarce specialists, regulatory milestones that don't move, and status reporting that runs weeks behind reality.

Project management sounds like the unglamorous answer. It's also the honest one. When a wind program slips a year, the root cause is rarely a turbine. It's a dependency someone spotted too late. Oxford researcher Bent Flyvbjerg's long-running study of large infrastructure programs found that roughly nine in ten megaprojects go over budget, a pattern that has held steady across decades and sectors. In nearly every post-mortem, the signal existed in the data long before it surfaced in a meeting.

The shift: from reporting what happened to seeing what's coming

The organizations pulling ahead are changing the question their systems answer. Not "what happened last month" but "what's trending wrong right now." That means delivery data (projects, milestones, resources, supplier interactions) living in one place, current, where a program leader can interrogate it directly: which projects in this portfolio are trending late, where does resource contention bite next quarter, which dependencies put the Q3 energization date at risk.

When the data is live and unified, those become questions you ask in plain language and get answered in seconds, not requests that take an analyst a week. McKinsey's grid-planning research points at the scale of the prize: utilities that move to an integrated, systems-level planning approach can unlock up to 20% in capital efficiency and a 15% to 30% reduction in major outage events. And the effect compounds on the project side too: teams that see drift early consistently run with fewer surprises, up to 30% fewer project overruns in our customers' experience, because the window to act is still open when the signal arrives.

Why we hold this view

We work with energy and utility organizations running exactly these portfolios, and the pattern is unmistakable: the constraint on the transition isn't ambition or engineering talent. It's whether the delivery organization can see its own work clearly enough to steer it. Visibility is infrastructure now, as real as the steel in the ground.

That's why we built Cloud Coach's Delivery Intelligence layer to run natively on Agentforce, directly on the live project data already sitting in your Salesforce org. Project Copilot answers a program director's question about risk or resource contention in plain language, grounded in that day's data, not a compiled deck; Customer Signal Intelligence and AI Meeting Manager do the same for stakeholder and supplier communication. None of it requires exporting delivery data anywhere else.

The energy transition is a project management problem. The organizations that treat it that way will be the ones that hit their dates.

Sources Cited

Bent Flyvbjerg, Saïd Business School, University of Oxford, as cited in McKinsey & Company, "Megaprojects: The good, the bad, and the better." https://www.mckinsey.com/capabilities/operations/our-insights/megaprojects-the-good-the-bad-and-the-better

McKinsey & Company, "Grid planning under uncertainty: Investing for the energy transition," McKinsey analysis of integrated system planning outcomes. https://www.mckinsey.com/industries/electric-power-and-natural-gas/our-insights/grid-planning-under-uncertainty-investing-for-the-energy-transition