Your team commissioned the water study. The energy modeling is solid. The economic impact numbers are real. You bring it all to the community meeting, and it changes nobody's mind. If anything, some residents seem more convinced you're hiding something. If you've lived this, you're not imagining it, and your data probably isn't the problem.
Presenting accurate information rarely resolves opposition to a data center on its own. That's not a failure of your studies or a sign the community is irrational. It's a predictable result of how people process contested, high-stakes information, combined with the timing of its arrival. Understanding the mechanism is genuinely useful because it points to what works. This blog explains the why. For what to do, we'll point you to the specific guides along the way.
Most engagement strategies rest on an information-deficit model: the belief that opposition stems from a lack of facts and that supplying them will close the gap. It's an intuitive assumption. It's also wrong often enough to be dangerous, because when the facts don't land, teams tend to conclude they just need more facts, more studies, a better slide deck, and they double down on the one approach that isn't working.
Opposition to a data center is rarely a simple information gap. It's a mix of genuine trade-offs the community is weighing, questions your data doesn't actually answer, and a level of trust in you that was set before you presented anything. Facts operate on only the first of those, and only once the third is in place.
Decades of cognitive research explain why information alone moves people so little on charged topics. The core finding is that people don't evaluate new information neutrally when it touches identity, group belonging, or a sense of what's happening to their community. One overview of the research notes that people form opinions based on emotions such as fear and anger rather than on facts alone, and that a challenge to someone's worldview can feel like an attack, prompting them to harden their position rather than reconsider it.
The American Psychological Association describes a related asymmetry: it takes substantially more evidence to make someone accept a conclusion they'd rather not believe than one they already lean toward. Psychologists call the underlying pattern motivated reasoning. When accepting a fact would mean accepting an unwelcome outcome, the mind unconsciously works to find reasons to reject it.
Two things about this matter for a data center development project team. First, it isn't a defect specific to opponents. A developer under deadline pressure has its own reasons to read an ambiguous water constraint optimistically, and a local official who wants to expand the tax base has reasons to minimize residents' concerns. Second, it means your studies are not self-evidently convincing to someone who doesn't already trust you. The same page of data reads as reassurance to one person and as spin to another, and the difference is trust, not comprehension.
Even sound information struggles against the clock. By the time a data center reaches a public meeting or hearing, most attendees have already formed a view through local news, social media, neighbours, and, above all, the framing of the first thing they heard about the project. The meeting becomes the place where formed opinions are expressed, not where they are shaped.
That first impression does a lot of work. When a community's first real information about a project is a rezoning notice or a permit filing, the process can read as a decision already made behind closed doors, which primes distrust, no matter how good the later data is. This is why the sequence of engagement often matters more than its content. Presenting excellent facts in an environment that has already decided you can't be trusted is close to the hardest position to argue from.
The practical implication is that the highest-leverage moment occurs early, before opinion sets in, while the project is still open to change. We cover how to approach that window in our guide to building community support before a project goes public.
None of this means data is pointless. Accurate information is necessary. It's not sufficient, and it only does its job once a few other conditions are met. Here's what the evidence shows helps facts land, with a detailed guide for each.
Information is weighed against the credibility of its source. That credibility is built through earlier, lower-stakes contact, not manufactured at the podium. A team that the community has already met and seen respond honestly to hard questions gets a very different hearing than a name on a filing.
Facts persuade when they answer the question actually being asked. Water use is the most common concern communities raise about data centers, and a generic sustainability statement does nothing to address a specific worry. Meeting the real concern with relevant, honest information, including where the answer involves a genuine trade-off, is what makes the data usable.
We go into the water question specifically, focusing on how to address water-use concerns in data center engagements →
A fact carries more weight when it's verifiable and when past commitments have been kept. "We'll cap water draw at this level" lands differently coming from a developer with a documented history of honoring commitments than from one whose past promises can't be traced. A clear record of what was committed and what was delivered is what converts a claim into something a community can actually rely on.
That's the focus of our blog: how to track community commitments during a data center project →
If your accurate information isn't convincing anyone, the answer usually isn't more information. It's the conditions around it: whether trust exists yet, whether you're addressing the concerns people actually have, whether your claims can be verified, and whether any of this is happening early enough to matter. Facts are one input into a process that runs on trust and timing. Get those right, and your data finally gets a fair hearing. Get them wrong, and no volume of studies will substitute.
For the wider picture of why community response has become the leading risk to data center schedules, see our overview of community opposition and data center development →
Jambo is a Stakeholder Relationship Management (SRM) software used by teams running engagement on infrastructure and energy projects, including data centers. It doesn't change how people process information, nothing does that for you, but it supports the conditions that let facts land: a full history of who a team has talked to and what was said, so engagement can start early and stay consistent; a view of which concerns are being raised and where, so responses address the real issue rather than a generic one; and a dated record of commitments made and delivered so that claims can be checked. That record supports accountability in both directions, helping a project team show it followed through and giving communities and regulators something concrete to hold it to.
For teams handling sensitive landowner or community information, the security specifics tend to come up in IT and procurement reviews. For US customers, Jambo stores data in the US, processes AI in the US through Jambo Secure AI, never trains on customer data, runs on AWS US hosting, and holds ISO 27001:2022 and ISO 27017:2015 certifications.