A governance-level breakdown of exposure, identity friction, and approval resilience

I’m writing this after recently returning from a trip to Atlanta, which has more than 100 data centers, which are attracting a lot of attention at the moment. I figured I’d write a post on how I’d approach tackling the push back from the community, given my years of volunteering for local government and serving two terms as a city council member. 

Executive overview

Across the country, data center proposals are encountering resistance during local approval.

In many cases, the fundamentals are strong:

• Significant capital investment
• Large property tax contribution
• Minimal traffic impact
• No additional school enrollment

Yet hearings extend. Votes delay. Projects stall. During six years on a city council, I learned that projects rarely falter because the numbers fail. They falter because exposure accumulates faster than resilience. Data centers are not uniquely controversial. They function as a governance stress test — revealing how visible tradeoffs, identity friction, and late-stage exposure shape modern infrastructure approvals. Understanding that dynamic changes how cities and developers should approach approval strategy.

It’s also what my work in decision viability — helping institutional leaders map exposure before it concentrates — is built around.

The approval environment has shifted

Local infrastructure decisions now unfold in a high-visibility, high-amplification environment.

• Information circulates instantly.
• Community groups organize quickly.
• Narratives form before staff reports are fully digested.
• Perceived tradeoffs harden early.

This does not make communities irrational. It changes how visible costs and benefits are weighted. 

The central question increasingly becomes: Will this decision remain stable once it leaves the chamber?

That question determines durability.

The vote moment: where exposure concentrates

Inside a council chamber, exposure does not distribute evenly; it concentrates.

An elected official evaluates staff recommendation, fiscal impact, and legal compliance. They also evaluate backlash durability, media amplification, electoral accountability, and institutional cohesion. I came to think of this as the vote moment — the point at which a technically sound proposal must withstand reputational pressure.

If resilience has not been built before that moment, hesitation rises.

A lesson from my first night on the dais

My first meeting as a council member, a developer made a controversial proposal — apartments — that reverberated for months in a city that defined by low density. The chamber was full as agitated residents lined the walls. A few brought printed petitions. Others rehearsed remarks in the hallway. Every council member understood the economics.

Downtown districts require proximity density to thrive. Without nearby residents, retail weakens, vehicle traffic increases, and long-term vibrancy erodes.

The math was clear; what was missing was preparation.

No effort had been made to explain what stagnation would cost. No groundwork had connected modest density to long-term identity. No acknowledgment had been made of visible tradeoffs. As speaker after speaker warned of “losing our character,” the vote shifted from economics to survivability. The proposal may have made fiscal sense. It had not built resilience.

The narrative layers at play that night were palpable:

• The developer looked through the lens of “What’s best for his bank account and the city?” — in that order.
• The council looked at it through the lens of “what’s survivable and best for the city?” —  in that order.

The developer was smart enough to know that by not doing the legwork to educate the community and then — and only then — coming back to the council when there was buy-in from the community, he robbed city leaders of the permission structure to move forward in everyone’s best interest. He certainly knew that an affirmative vote would effectively end each council member’s political career, which meant getting a yes was a near impossibility. The council, I feel — this was never discussed as a group, of course — took offense to this proverbial gun being placed to their heads and voted with their political futures in mind.

That lesson is repeating itself in data center debates across the country.

Why data centers face structural approval challenges

Data centers reveal recurring approval friction patterns with unusual clarity.

1. Visible resource intensity

Data centers require substantial electricity and water, and, for their size, yield few jobs. Plus, there is the noise component, as many residents who live near data centers complaining of the persistent low-frequency hum giving of by generators and cooling systems. Even when utilities confirm capacity and infrastructure upgrades are funded by the project, consumption remains highly visible. Residents respond first to perceived scarcity. Technical reassurance does not automatically rebalance perception.

2. Symbolic employment imbalance

A large physical footprint paired with relatively modest on-site employment creates intuitive imbalance. “A lot of land, not many jobs.” In public hearings, that perception often carries more emotional weight than long-term tax projections.

3. External beneficiary narrative

Data centers frequently serve national or global platforms. Benefits can feel abstract. Costs feel local. The governing dynamic is not misinformation — it is that the tradeoffs are highly visible and unevenly distributed.

How friction compounds

These three dynamics rarely operate in isolation.

• Resource visibility becomes symbolic shorthand.
• Employment imbalance becomes moral shorthand.
• External beneficiaries become political shorthand.

Over time, shorthand hardens. By the time a project reaches formal hearing, opposition arguments often feel settled — even if staff analysis is still unfolding. When shorthand solidifies early, late-stage persuasion operates in a compressed lane.

Resilience must precede persuasion.

When the weighting misfired

A few years after the apartment vote, we evaluated another large commercial development that would materially strengthen the city’s tax base. Staff supported it. Many members of the community reached out to me about the need to support it. Financial modeling supported it. Long-term planning supported it. In the weeks before the vote, a few vocal residents raised objections about the overall fit of the project, given its location. Engineering analysis indicated the strain was manageable. What had not been addressed early was perception and narrative. 

Residents aligned against the project could only see the negatives of the development, even though the latter was quite minuscule. 

At the public hearing, charts and projections competed with lived anxiety. The constraint had not been feasibility. It had been insufficient early mapping of exposure. The delay, tension, and reputational strain that followed were entirely avoidable. Data center debates today often follow that same trajectory.

Why economic arguments underperform under intensity

When resistance rises, the instinct is to add more data: expanded fiscal modeling, additional utility reports, comparative case studies. Those are necessary. They rarely shift how visible tradeoffs are weighted. If identity friction and symbolic imbalance are not acknowledged early, they solidify. By the time a hearing becomes adversarial, persuasion operates within a narrowed window. Approval durability — the capacity of a project to move forward without destabilizing the officials who approved it — depends on groundwork laid before that stage. Resilience is what makes durability possible.

Approval resilience: the governing variable

Engineering strength and fiscal modeling remain foundational. What increasingly determines outcome durability, however, is approval resilience — the capacity of a decision to withstand amplification once scrutiny intensifies.

Resilient approvals typically include:

• Early acknowledgment of visible tradeoffs
• Clear articulation of long-term necessity
• Alignment with community identity
• Credible institutional validation
• Exposure reduction for decision-makers

When these elements are built upstream, the vote moment stabilizes. When they are underdeveloped, risk concentrates late.

A resilience audit before the dais

Before a project reaches formal approval, developers and city officials should be able to answer four questions with specificity — and answer them with more than talking points.

1. Where will visible tradeoffs concentrate?
2. Which identity concerns are most likely to mobilize?
3. What narrative shorthand could solidify early?
4. If amplification occurs, who absorbs the exposure?

If those answers are vague, resilience remains underdeveloped. When they are concrete, the vote moment stabilizes.

The governing shift

Infrastructure approvals increasingly hinge on how decisions behave under pressure. Technical sufficiency remains necessary. Durability now depends on whether exposure has been mapped, tradeoffs surfaced, and resilience built before amplification begins. Data centers make this shift visible. Other infrastructure categories are not far behind. 

Leaders who understand that weighting can design approvals that stabilize rather than strain. Those who misdiagnose the constraint will continue to encounter late-stage fragility — even when the math works.

If you’re navigating a contested infrastructure approval or advising on one, I’d be glad to talk through where exposure may be accumulating. You can reach me at ronell@ronellsmith.com