Back to Blog
Energy Ninja Chronicles
4 min read

Why Critical Infrastructure Is Getting Harder to Build

A framework for understanding why data centers, transmission lines, pipelines, and other critical infrastructure face growing approval challenges.

By Ralph Rodriguez

Every generation of critical infrastructure gets built the same way. One approval at a time, one community at a time, one hearing at a time.

That process was manageable when infrastructure was visible and local. A road. A water tower. A power plant everyone could see and understand.

It is not manageable anymore.

The Paradox

Society has never depended more heavily on infrastructure most people never think about.

Data centers process the searches, transactions, and AI queries that now sit underneath daily life. Transmission lines move power across regions that would otherwise sit in the dark. Pipelines fuel the plants that keep the grid stable. Fabs produce the chips inside everything from phones to cars. Water systems, telecom networks, and the plants generating the power for all of it operate quietly in the background, until they don't.

The paradox is this: the more society depends on infrastructure, the less visible that infrastructure becomes to the people who benefit from it. And the approval process hasn't caught up. Every one of these projects still has to be approved locally, community by community, by people who see the cost up close and the benefit from a distance, if they see it at all.

Why this is happening

The asymmetry is straightforward once you name it.

Costs are local. Noise, traffic, land use, water draw, visual impact. A community feels these directly and immediately.

Benefits are distributed. Grid reliability, economic growth, national competitiveness, lower prices somewhere downstream. A community rarely feels these directly, and when it does, the connection isn't obvious.

Local officials are asked to weigh both sides, often with incomplete visibility into the broader value of what they're approving. They see the substation. They don't see the grid it stabilizes. They see the truck traffic. They don't see the supply chain it supports.

This isn't a failure of process. It's a mismatch between where decisions get made and where impact gets felt.

Why data centers illustrate the problem

Data centers aren't a special case of this paradox. They're the clearest current example of it.

AI made the invisible visible. For decades, data centers sat quietly at the edge of most communities, drawing power and raising few questions. Load growth was slow enough that the grid absorbed it without much friction.

That changed fast. A single hyperscale campus can now request several hundred megawatts, more than some small cities consume. Utilities that spent years planning for flat or modest load growth are suddenly fielding requests that reshape their capital plans. Communities that never thought about where their electricity came from are now asked to approve substations, gas plants, and transmission upgrades to serve a facility most residents will never set foot in or fully understand.

The industry's early instinct was to respond with scale. More power, more capacity, more megawatts, faster. That instinct is understandable, but it treats the problem as a supply constraint instead of a trust constraint.

Local officials aren't asking whether AI infrastructure matters. They're asking who bears the cost of building it and who actually benefits. "We need more power" doesn't answer that question. It just restates the demand.

The next evolution

The developers who get projects approved going forward will be the ones who stop leading with capacity and start leading with value.

That means demonstrating:

𝗚𝗿𝗶𝗱 𝘃𝗮𝗹𝘂𝗲. How the project strengthens reliability for everyone on the system, not just the facility drawing power.

𝗙𝗹𝗲𝘅𝗶𝗯𝗶𝗹𝗶𝘁𝘆. Willingness to curtail, shift load, or self-generate during system stress instead of treating the grid as a bottomless resource.

𝗥𝗲𝗹𝗶𝗮𝗯𝗶𝗹𝗶𝘁𝘆. A credible plan for how the facility gets power when the grid is under strain, not just when conditions are ideal.

𝗘𝗰𝗼𝗻𝗼𝗺𝗶𝗰 𝘃𝗮𝗹𝘂𝗲. Jobs, tax base, and investment that a community can see and measure, not abstractions about regional GDP.

𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆 𝗽𝗮𝗿𝘁𝗻𝗲𝗿𝘀𝗵𝗶𝗽. Genuine engagement before the approval process starts, not a public comment period after the plan is already finished.

That's a far more sophisticated conversation than "we need more power." It's also the only conversation that actually moves projects forward now.

What actually gets approved

The challenge was never deciding whether we need this infrastructure. It's building a process that lets communities see both its local cost and its broader value, and the projects that earn approval will be the ones that treat that as the job, not an obstacle to it.

Originally published in Energy Ninja Chronicles (LinkedIn newsletter).