Beyond the Podium

5 Surprising Lessons from the Frontlines of the Data Center Wars

6 min read

An unused lectern in front of a round table where eight figures sit working together.

The scene is a recurring nightmare for infrastructure developers and local officials: a packed high school gymnasium, an exhausted planning commission, and a line of residents at a podium, many visibly vibrating with anger. As data centers—massive, power-hungry, and often misunderstood—proliferate, these “contested infrastructure” hearings have become the primary battleground for the future of our digital economy.

Traditional public engagement follows a predictable, failing script. The developer presents technical data, the public expresses fear and resentment, and the project eventually descends into a cycle of litigation and burned political capital. This model treats social license as a “communications” problem to be solved with better slide decks. It isn’t. Social license is a structural achievement based on control, voice, and enforceable accountability. To build in an age of saturated distrust, we need to move beyond the podium and adopt a new manual for legitimacy.

Based on the CommonWatts Method, here are five counter-intuitive findings from the frontlines of the data center wars.

1. More Facts Often Make the Fight Worse

The most common mistake project sponsors make is assuming the public simply needs to be “educated.” The data suggests that in high-stakes disputes, the “information deficit model” is a myth. Research by Dan Kahan on “Cultural Cognition” reveals a startling trend: polarization on high-stakes risks is often greatest among the most scientifically literate and numerate participants.

In identity-loaded disputes—what I call “a values dispute wearing a technical costume”—people do not use their reasoning capacity to find the truth. They use it to protect their standing within their social group. When a developer drops a 500-page noise study into a room that feels its rural identity is under threat, the most “numerated” residents will find the most sophisticated ways to pick the data apart. In these moments, “educating” the public is perceived as condescending and actually accelerates escalation.

“Don’t educate—facilitate. Gather information, seek answers to the unknowns, and help connect the dots so good decisions can be made.”

Analysis: The “messenger” matters more than the “message.” Reasoning capacity is deployed in service of identity, not against it. Facts only gain traction if they are delivered by a shared-values messenger after concerns have been understood rather than “corrected.” The structural version of this is joint fact-finding: when both sides pick the expert and frame the question together, the answer arrives without a side attached to it. It is slower than commissioning your own study, and it is the only version that survives cross-examination in a gymnasium.

2. The “Loudest” Voices Are Rarely the Most Trusted

Decision-makers often fall into the trap of treating the volume of public comment as a representative sample of public opinion. However, the work of Einstein, Glick, and Palmer proves that public comment is structurally skewed. Their analysis of zoning meeting minutes found significant demographic gaps between those at the microphone and the broader voting public:

  • Age 50+: 75.0% of commenters vs. 52.6% of voters.
  • Homeowners: 73.4% of commenters vs. 45.6% of voters.
  • Women: 43.3% of commenters vs. 51.3% of voters.
  • Opposition: Roughly a 4:1 ratio of comments opposed to projects.

Counting “support vs. opposition” at a hearing is a quantitative fallacy and a trap for officials. While the loudest voices signal the intensity of organized groups, they are rarely the “chosen” voices of a community. In every town, there are individuals—the extension office agent, the volunteer fire chief, or the retired engineer—whom residents actually trust to tell them the truth. Finding these chosen, shared-values messengers is a more vital exercise than counting hands in a crowded room.

3. Stop Negotiating Probability; Start Negotiating Consequences

Siting battles often stall because the community and the developer disagree on whether a harm will occur. Will the cooling fans be too loud? Will the backup generators impact the aquifer?

Arguing about the probability of these events is unresolvable because it requires the community to trust the developer’s models. The strategic alternative is the “Contingent Commitment.” This “if X, then Y” approach bypasses the need for “sincerity” or “belief” entirely. Instead of asking the community to believe the noise won’t exceed 55 dBA, the developer writes a contract:

  • If measured noise exceeds the limit, then operations must be reduced within 30 days.
  • If a monitored well shows contamination, then the developer pays for immediate filtration.

Reflection: This creates a “sue us if we’re wrong” reality. It moves the conversation from a battle of experts to a negotiation of enforceable terms. As the manual notes, verification buys the time in which trust can accumulate.

“Verification buys the time in which trust can accumulate. Trust is granted on perceived shared values, not credentials.”

4. Neutrality is Not Passivity—It’s an “Equalizer”

Facilitators often aim for a “scrupulously even-handed” process, but in practice, this creates an Equity Inversion. When a developer arrives with outside counsel and acoustic engineers, and the residents have no technical staff, a “balanced” process produces a lopsided result for the developer.

True neutrality requires acting as an “Equalizer.” This means building the technical capacity of the residents—providing developer-funded, community-controlled technical reviews and plain-language materials. Building resident capacity is a precondition for neutrality, not a violation of it.

Strategic Reflection: To remain truly neutral, the mediator must maintain “walk-away capacity.” If a facilitator’s revenue is structurally dependent on a single developer or a “yes” vote, they are captured. A concentration limit on revenue and the ability to decline engagements are the only safeguards that keep “The Equalizer” honest.

In practice that means terms you publish rather than assert. At CommonWatts, fees are fixed and disclosed to every party before the first meeting, never contingent on approval, denial, or the size of any benefit package, with a hard ceiling on how much of a year’s revenue any single client can represent. That’s the least interesting page in the whole method—right up until the moment somebody in the third row asks whose side you’re on, and you can answer by handing them the page.

5. The “Window of Fate” Closes in Weeks, Not Months

The political fate of a project is determined in a window only two to eight weeks long, triggered by the first moment of public awareness. Most institutions use the “Decide-Announce-Defend” (DAD) model: they decide on a site, announce it as a finished deal, and then spend months defending it.

This model fails because the announcement itself is the injury. It tells the community they have no voice. By the time the first permit is filed, the opposition frame is usually locked in. The alternative is the “Engage-Deliberate-Decide” model, which invites the community to shape the “where” and the “how” before the options are fixed.

“The announcement itself is the injury. It tells the community it had no voice.”

Analysis: When developers are secretive out of a desire for “certainty,” they are actually manufacturing a betrayal of autonomy. If you are brought in after the window has closed, you must be honest: the trajectory is likely set, and the process is now about mitigating damage rather than building consensus.

Conclusion: From Support to Legitimacy

The goal of high-stakes engagement is not to manufacture “support.” That is a promise no one can keep. The goal is to produce a “defensible decision” and a community that can live with it.

This is the essence of Tom Tyler’s Four Elements of Procedural Justice:

  • Voice: People get to state their case before the decision.
  • Neutrality: Decisions are made by transparent, consistent rules.
  • Respect: People are treated with dignity, affirming their standing.
  • Trustworthy Motives: Explanations are honest and demonstrate that concerns were considered.

We must design our processes as though we are not trusted and behave as though we intend to be. Trust is a structural achievement, not a branding exercise. As we face a decade of massive infrastructure expansion, we must ask ourselves: How will we build the power, land, and fiber of the future in a climate of saturated distrust?

More insights