The Neuroscience of NIMBY: Why Community Opposition to Data Centers and Broadband Isn't Irrational

Part 2: Why Data Centers are Losing the Narrative 

When a broadband expansion project or data center siting gets announced in a community, the same pattern emerges almost without fail. Facebook groups triple in size within weeks. City council meetings overflow. Residents show up with printouts about electromagnetic fields, environmental damage, and energy costs. They don't want your environmental impact assessment. They want you to hear their concerns. 

Project leaders label these residents CAVE people—Citizens Against Virtually Everything. The label feels accurate. It feels like explaining everything: irrational opposition, activist manipulation, stubborn resistance to progress. You hear the term NIMBY—"Not In My Backyard"—thrown around as shorthand for local resistance to change. 

But both labels are hiding what's really happening. 

When Data Doesn't Land: Why Stat Attacks Fail 

Here's what developers, broadband companies, and infrastructure professionals keep getting wrong: they treat community opposition as a messaging problem that requires more information. So they hire a PR firm. They run ads. They hold info sessions. They bring printouts of environmental studies, job creation projections, tax revenue analyses, and compliance certifications. 

It's a stat attack. Here are all the facts about our company, our project, how good this is for the region. 

And nothing lands. 

Why? Because before people can process facts about your project, they need to know you understand what they care about. They need to feel heard. Until their nervous system settles, data is just noise. 

When people feel threatened by something happening in their community—loss of control, uncertainty about who bears the risk, skepticism about distant corporations' promises—their brain's threat-detection system activates. The brain shifts into survival mode. Reasoning, nuance, and data processing take a back seat. The parts of the brain responsible for deliberation and complex thinking go quiet. Your environmental study becomes background noise. Your job numbers sound like empty promises. You cannot think your way out of fear when your neural pathways are locked in threat response. 

You cannot logic someone into trust when their brain is in protection mode. 

This is the neuroscience of NIMBY. It's not about localism or resistance to change. It's about how brains respond to perceived threat. And stat attacks actually amplify the threat—they signal that you're trying to convince them rather than understand them. 

But here's what does work: showing you understand what they need, want, and deserve. 

Not telling them what benefits the project offers. Acknowledging what they need from any infrastructure project that comes to their community. What do they deserve from a developer? Transparency about impact. Genuine input into decisions. Verifiable benefits. Accountability when things go wrong. Respect for what they value about their community. 

When you start there—with what communities deserve—their nervous system begins to calibrate differently. You're not selling. You're acknowledging. That distinction opens doors that stat attacks slam shut. 

This is where most infrastructure projects fail. Not because the infrastructure isn't good. But because the engagement strategy treats opposition as something to overcome with better information rather than something to understand by listening first. 

The Power of Empathy in Conflict: How Brains Sync 

Here's something that happens in conflict settings that most project leaders don't understand: brains mirror each other. When you walk into a heated meeting with a PowerPoint deck of stats and a defensive posture, residents pick up on that instantly. Their threat detection amplifies. Everyone's brain is locked in protection mode. The room becomes an echo chamber of defensiveness and argument. 

Conversely, when you walk in genuinely curious about their perspective—when you're actually trying to understand what they need and what they fear—something different happens. People can sense authentic interest. Their nervous systems begin to calibrate to yours. The threat response softens. Space opens for actual conversation. 

This isn't manipulation. It's neuroscience. Empathy isn't just an emotion. It's a physiological state that gets transmitted between people. When you demonstrate real empathy—when you actually try to understand what the world looks like from someone else's perspective, what keeps them up at night about this project—their brain responds by lowering its defenses. 

This is why the first thing that happens in a room with a data center developer or broadband representative isn't about facts or benefits. It's about whether people believe you understand and respect what they need. Do you actually care about their experience? Do you understand what a responsible developer should do? Or are you here to convince them your stats prove they're wrong? 

People can tell the difference instantly. And so can their brains. 

The companies that move infrastructure forward aren't the ones with the best talking points or the most impressive data. They're the ones who walk into the room already understanding what communities deserve—and prepared to show how the project delivers on that. 

Opposition Isn't One Thing 

The acronym feels useful. NIMBY, CAVE people—they package opposition into dismissible categories. But they're also traps that keep you from understanding what you're actually facing. 

When you label people as NIMBY or CAVE, you stop asking important questions: What do they actually need from this process? What are they afraid will happen? What would a responsible developer look like to them? 

Not all opposition is the same. Some residents are genuinely concerned about environmental impact on water resources or air quality. Some worry about how infrastructure changes affect their neighborhood character. Some are uncertain about whether job creation promises will materialize or who gets hired. Some are skeptical that community benefits agreements will be honored after the developer leaves. These are legitimate concerns grounded in real experience and data—and in what they rightfully expect a developer to deliver. 

Some opposition is performative—activists showing up to organize around a cause. Some opposition is ideological—people who approach all new infrastructure with caution. And some people have different values about growth, change, and development than project developers do. 

The threat response affects all of these groups differently. A person concerned about water impact is in threat mode because of a real need (clean water) that feels endangered. An activist is in threat mode because they're mobilized around a principle. Someone who values their neighborhood character is in threat mode around loss of what they care about. The brain activation is similar. The underlying needs and values are different. 

This is where understanding what communities deserve becomes strategic. When you can articulate what a responsible developer should do—transparency, genuine input, verifiable benefits, accountability—and show how your project delivers on that, you're not fighting opposition. You're meeting need. You're acknowledging what they deserve. 

The companies winning in this environment don't come armed with better stats. They come with genuine understanding of what communities need and deserve. They distinguish between concerns that can be addressed and resistance grounded in different values. They listen before announcing. They reshape projects based on what they learn. They structure partnerships that deliver on commitments. 

That takes more time upfront. It saves far more downstream—in timeline delays, in legal challenges, in reputation damage, in the ability to move the next project forward without starting from zero on community trust. 

Infrastructure at Scale: Data Centers and Broadband in the Real World 

The infrastructure being built right now—data centers powering AI, broadband expansion reaching rural communities, fiber networks enabling connectivity—is facing opposition at scale. And for good reason: communities are experiencing rapid change with minimal say in how it affects them, and little assurance that developers actually care about what they need. 

Most data center operations consume enormous amounts of water and electricity. Broadband infrastructure changes neighborhoods during installation and operation. Fiber networks require sustained community collaboration through construction and beyond. Communities rightly want to know: will this respect what we care about? Will we have real input? Will you stick around to ensure benefits happen? These aren't abstract concerns. They're real impacts on real communities, and real questions about what a developer owes them. 

The opposition you're seeing signals something important: communities are saying, "We deserve to understand what this means for us, we deserve to have real input, and we deserve to know you'll be accountable." 

When a broadband company or data center operator treats that as NIMBY to be overcome with better data, opposition entrenches. But when they treat it as legitimate—when they demonstrate through their actions that they understand what communities deserve and are committed to delivering on it—opposition often transforms into partnership. 

That difference compounds project by project, region by region. 

How Infrastructure Moves Forward: Five Phases of Real Partnership 

At Harry, we work with broadband companies, data center operators, and infrastructure developers navigating these exact conflicts. We've learned that the companies moving projects forward aren't the ones with the most impressive stats. They're the ones who understand what communities need and deserve—and structure their engagement to deliver on that from day one. 

Here's the framework we recommend: 

Phase 1: Listen for What Communities Need (Before You Announce) 

Before you go public, understand what the community actually cares about and what they deserve from infrastructure development. Not through a survey that gives you tick-boxes. Through real conversations with community leaders, local officials, business owners, and residents. What do they value about their community? What infrastructure impacts worry them? What would a responsible developer need to do to earn trust? 

This requires genuine empathy and curiosity. It means setting aside your agenda long enough to actually understand theirs. It means listening for what they need and deserve, not for ammunition to counter their concerns. This intelligence reshapes everything that comes next. It tells you where you need to address legitimate impacts. It shows you where you have actual community allies. Most importantly, it reveals what real partnership looks like in this community—not what you think should matter, but what actually does. 

Phase 2: Lead with What You Understand They Deserve (From Day One) 

When you announce, don't lead with stats about your company or project. Lead with acknowledgment of what communities deserve: transparency about impacts, genuine voice in decisions, verifiable community benefits, accountability for delivery. Then show how your project is structured to deliver on that. 

This demonstrates respect. You're not hiding impacts behind a wall of data. You're not overselling certainty you don't have. You're saying: we know what you deserve, and here's how we're going to make sure you get it. Communities are more likely to trust you when you acknowledge what they need than when you overwhelm them with why your project is beneficial. 

Phase 3: Give Them Structured Voice in What Happens (Feedback That Matters) 

Design processes where community feedback actually shapes the project, not just informs it. This might mean adjusting siting based on community input about impact. It might mean scaling the project differently. It might mean stronger benefit agreements tied to what they actually said they needed. It means showing—explicitly—how specific feedback changed what you're building. 

This is where you prove you respect what they deserve. It's not enough to listen. People need to see that what they said actually mattered. When people see their input shape real project changes, their relationship to the infrastructure shifts. They move from opposition to ownership. 

Phase 4: Build Agreements with Real Accountability (Commitments They Can Track) 

Community benefit agreements only work if they're measurable and monitored. Job creation targets with actual hiring commitments and verification. Tax revenue projections with tracking mechanisms. Environmental monitoring with public reporting. Community fund management with transparent accounting and clear timelines. 

When communities can track whether you're delivering on commitments, trust compounds over time. When they can't, it erodes. This is where empathy shows up as follow-through. You've said they deserve accountability. Now prove it by making it measurable and transparent. 

Phase 5: Stay in Relationship (Beyond Permitting) 

Your relationship with the community doesn't end when shovels hit the ground. It's actually just beginning. How you operate during construction and after—whether you honor commitments, how you handle problems, whether you stay in communication—determines your reputation for the next project and the region's willingness to support broadband or data center infrastructure. 

The broadband and data center infrastructure being built right now will be followed by more. Communities remember who demonstrated they understood what communities deserve. They remember who delivered. They remember who treated opposition as a signal to improve the project, not a problem to overcome. 

Moving Brains from Threat to Thinking 

This framework works because it's grounded in how brains actually function. When communities feel understood—when they believe you grasp what they need and what they deserve—something shifts. The threat response quiets. The reasoning centers activate. They can actually think about trade-offs, weigh whether the project delivers on what they deserve, and engage with complexity. 

Empathy is the pathway that makes this shift possible. When you demonstrate genuine understanding of someone's perspective and their needs—when they feel you've actually tried to understand what matters to them—their nervous system begins to trust. Data can land. Conversation becomes possible. 

When communities feel dismissed or when you lead with stat attacks instead of acknowledgment, their threat detection stays activated. Opposition hardens. Their brain literally isn't available for nuance. All the data in the world won't move them because they haven't felt understood. 

This isn't soft skills. This is how people work. Understanding what communities need and deserve—and structuring your entire engagement around that—is what gives you a structural advantage: the ability to move communities from defensive to thinking mode, and often from opposition to partnership. 

The opposition you're seeing in CAVE people or NIMBY responses isn't irrational. It's protective. Your job isn't to overcome it with better marketing. Your job is to create conditions where it quiets naturally—through genuine listening to what they need, transparency about impacts, actual partnership on decisions, and accountable follow-through. 

Why This Matters for Your Projects

If you're developing broadband expansion, siting a data center, or building critical infrastructure, the opposition you're facing isn't something to message away with better stats. It's a signal about what communities need to feel safe enough to support the project—and what they deserve from a developer. 

Communities that feel understood and respected often become advocates. Communities that feel dismissed or stat-attacked become entrenched opponents. The difference in timeline, cost, and reputation is substantial. 

The framework isn't complicated. Listen first to what communities need and deserve. Lead with acknowledgment of that, not promotion of your project. Let feedback reshape what you build. Structure verifiable commitments. Stay in relationship. But it requires a fundamental mindset shift—from treating NIMBY as a problem to overcome with better data to treating it as a signal to understand and address. 

That shift is what moves infrastructure forward efficiently. Not by eliminating community voice. By integrating it. Not by overwhelming them with stats. By understanding what they need. 

Understanding how communities respond to infrastructure projects—why they enter threat mode, what they actually need and deserve, and what moves them from defensiveness to genuine partnership—is the key to building the broadband networks and data center infrastructure we need with communities that actively support them. 

About Harry 

Harry is a strategic communications and influence platform helping infrastructure companies, broadband providers, and developers navigate community engagement and stakeholder communication. We work with clients to understand what communities need and deserve—and structure engagement to deliver on that. If you're facing community resistance to a data center, broadband expansion, or infrastructure project, we can help you move the conversation forward grounded in empathy, understanding, and what communities actually deserve. 

Want to learn more? Reach out to discuss how understanding and respecting what communities need can accelerate your infrastructure projects. 

Stacie McDonald is Vice President of Strategic Communications at Harry. Reach her at stacie@harry.marketing