Why Kenwood's Beauty Conflicts with Data Centers

Infrastructure development can be a double-edged sword — it can either benefit communities or threaten cherished landscapes. Kenwood exemplifies the latter scenario, where a beloved, irreplaceable landscape is eyed for development in the name of progress.

Kenwood is worth paying attention to — not just because of what's at stake there, but because this exact conflict is playing out across the country as data center demand accelerates and developable land grows scarcer.

The Kenwood Campus Dilemma

Kenwood's campus isn't just aesthetically pleasing in the way that any well-maintained property might be. By all accounts, it's the kind of place that carries genuine civic meaning — the sort of landscape that, once altered, doesn't come back. That's precisely what makes it such a flashpoint when a developer arrives with plans for a power-hungry data center.

The central tension here isn't really about data centers — it's about who gets to decide what a piece of land is worth, and by what measure.

The proposal follows a familiar playbook: a developer identifies a large parcel with existing infrastructure, proximity to power grid connections, and enough land to build out significant computing capacity. From a pure site-selection standpoint, many campus-style properties check those boxes. From a community standpoint, those same properties often represent something that took generations to create and can't be replicated with a rezoning approval.

Be appropriately skeptical when a developer frames this kind of proposal as inevitable progress. The economics of data center development are real, but so is the leverage communities have before permits are signed.

The Environmental Costs of Data Centers

Here's the number that usually gets buried in the press release: a single hyperscale data center can consume anywhere from 20 to 100+ megawatts of power continuously. For context, 100 MW is enough electricity to power roughly 80,000 average American homes. That load doesn't fluctuate much — data centers run 24/7, which means the grid impact is constant, not occasional.

Water consumption is the quieter problem. Many data centers rely on evaporative cooling systems that consume millions of gallons of water annually. A facility processing significant compute loads might use 3 to 5 million gallons per day in peak cooling conditions. Situating that kind of infrastructure near a scenic, ecologically sensitive area introduces real stress on local water tables and watershed systems that weren't designed to accommodate industrial-scale demand.

The environmental footprint of a data center isn't just about carbon — it's about what happens to the land, the water, and the surrounding ecosystem for decades after the ribbon-cutting.

Local ecosystems near campus environments are often more intact than those near traditional industrial zones — precisely because the land was treated with care. Introducing heavy electrical infrastructure, cooling towers, backup generator systems, and high-security perimeter fencing doesn't just change what a place looks like. It changes what lives there, what grows there, and how stormwater and groundwater move through the landscape.

Economic Benefits vs. Aesthetic Values

Developers will lead with jobs. That's the standard framing, and the numbers aren't fictional — a mid-size data center might create 200 to 500 construction jobs over 18 to 24 months, and perhaps 50 to 150 permanent positions once operational. Those are real livelihoods, and dismissing them entirely would be bad faith.

But the math deserves scrutiny. Data centers are among the most capital-intensive, job-light industries per dollar invested. A $500 million facility might employ fewer full-time staff than a regional distribution center a fraction of the cost. The tax revenue is more compelling — data centers generate significant property tax income — but that benefit has to be weighed against what's lost when a scenic community landmark disappears.

The longer-term economic case for preservation is harder to quantify but no less real. Property values near protected, beautiful landscapes tend to be stable or appreciating. Tourism, local business activity, and quality-of-life metrics that attract skilled workers to a region all correlate with the presence of well-maintained natural and civic spaces. You can't easily put a dollar figure on what Kenwood represents to the surrounding community, but you can be certain that losing it has a cost.

This is where the short-term/long-term tension becomes sharpest. A data center generates immediate, measurable tax revenue. The slow erosion of a community's character generates nothing measurable until the damage is done and the people who could have left have.

Community Perspectives on Infrastructure Development

Public meetings around proposals like this tend to follow a predictable arc. Early sessions are dominated by developer presentations — polished renderings, economic impact studies commissioned by the applicant, assurances about design standards and landscaping buffers. Residents show up, voice concerns, and are told their worries have been addressed.

Then the technical details emerge. The noise from cooling systems. The truck traffic during construction. The visual intrusion that "architectural screening" doesn't actually screen. The questions about whether promised jobs will go to local residents or imported technical staff. The realization that "community benefit agreements" are often vague and unenforceable.

What experienced observers of these processes know is that community opposition is most effective early — before site plans are finalized, before political relationships are built, before the developer has sunk enough capital to make withdrawal painful. Once a $300 million investment is underway, the political calculus changes dramatically. Local officials who might have raised objections become invested in the project's success.

The residents who show up to the first public meeting matter more than those who show up to the last one. By the final hearing, the real decisions have usually already been made.

For landowners and adjacent property holders, this moment also carries financial implications. Infrastructure development proposals — even contested ones — can shift land values in the surrounding area in ways that aren't always predictable. Understanding the full scope of what's being proposed, and engaging legal and planning counsel early, is not overcaution. It's basic due diligence.

Finding a Balance That Actually Works

The reflexive answer to conflicts like Kenwood is "compromise" — some version of a smaller footprint, more screening, community benefit payments, and everyone declares a partial victory. Sometimes that's the right outcome. Often it's a way of approving something that should have been rejected while giving all parties political cover.

The more honest path forward requires developers to do harder work upfront: genuine site selection that prioritizes locations where data center development creates value without destroying it. There are brownfield sites, former industrial parcels, and underutilized commercial zones in most metropolitan areas that can accommodate the power and connectivity requirements of modern data centers without touching landscapes that communities have fought to protect.

For communities navigating these proposals, the strategic priority is simple: slow down and examine everything. Demand independent environmental impact assessments, not just the developer's studies. Ask for binding commitments, not letters of intent. Understand the rezoning implications before the first shovel breaks ground.

Data centers in scenic areas aren't inherently wrong — but they're almost never the only option. The question worth asking every developer who arrives with renderings and economic impact projections is: why here, specifically? What makes this site irreplaceable for your purposes? Because if the honest answer is "it's available and the price was right," that's not a reason to sacrifice something that took a century to build.

Infrastructure development doesn't have to be a zero-sum contest between economic growth and the places people love. But getting to that better outcome requires communities, planners, and yes, developers themselves, to hold a higher standard than "technically permitted." Kenwood is a test case. How it resolves will tell us something real about whether that higher standard is still achievable.

Explore more about infrastructure development and community impact on our marketplace.

[INTERNAL LINK: Kenwood Campus Dilemma]

[INTERNAL LINK: Environmental Costs of Data Centers]

[INTERNAL LINK: Community Perspectives on Infrastructure Development]