John Davies

Because communities differ, developers should begin with local listening rather than assume a strategy that worked elsewhere will work here.

In one post, Davies describes a progression from questions to conversations, relationships, and support. Another says early engagement gives developers time to address concerns and establish credibility before opposition shapes the discussion.

Read original · Original 2 · Original 3

It should help identify relevant stakeholders, local concerns, and messages grounded in verified information.

A post on renewable energy says developers should understand local opinion before deciding what to do next. In another, Davies says data center developers should not rely on a national campaign; local issues may include water use, energy demand, infrastructure, jobs, or tax revenue.

Read original · Original 2 · Original 3

A permit may allow a project to proceed, but trust depends on how developers address concerns and build relationships with people in the community.

A post puts the distinction plainly: a permit allows a data center to move forward, while community trust helps it succeed. A separate renewable-energy post says engagement should begin well before a public hearing and include honest communication about what is known and unknown.

Read original · Original 2

Responding to President Trump’s call for data centers to generate their own power and provide community dividends, Davies argues that financial incentives alone will not build lasting trust. The post says support has to be earned through listening and showing how a project fits the community’s future.

Read original

Residents should understand a project and be able to take part in the approval process in their own voices.

A post lists letters of support, participation in public meetings, and community members speaking as advocates in their own words. Another describes mapping local decisionmakers and potential allies for rural energy approvals.

Read original · Original 2 · Original 3

The proposed sequence is to listen first, learn what matters locally, and then choose whom to reach and what to say.

A renewable-energy post describes targeted ads as a one-to-one way to reach open-minded people before their views harden, and calls this a public-affairs tool rather than just a marketing tactic.

Read original · Original 2

Consistency across conversations can make that explanation clearer.

A post says the same project identity should carry from a neighbor meeting to a public hearing, grounded in research and clear messaging.

Read original

This is the clearest statement of the sequence John Davies works from.

• The argument is that research comes before a project enters a community, and that its job is to name the right stakeholders, surface local concerns, and produce messaging that can be turned into action.
• The closing line is the operating principle: understanding what a community thinks is what lets a developer decide what to do next.
• The post stays on strategy rather than method — it does not describe survey design or sample sizes — so it functions as a principle statement, not a how-to.

For brands planning a campaign

Budget and schedule listening as a gate before creative or outreach work. Ask any agency or internal team what decisions the research is meant to unlock, not just what it will report.

The post rejects reactive public affairs.

• Its reasoning is that every community differs, so assumptions carried from one place to another are unreliable, and the only dependable starting point is listening to local concerns and building relationships around them.
• The chain it describes — questions into conversations, conversations into relationships, relationships into support — is the clearest summary in the set of how the work is supposed to compound over time.

For brands planning a campaign

Treat early engagement as insurance, not overhead. A developer who can show a relationship history from before a filing is in a stronger position when a hearing or local vote does arrive.

The post is the most concrete description of deliverables in the set.

• It says support is built through early listening and consistent engagement, and then it lists what that produces: people who understand the project, submit letters of support, attend public meetings, and speak as advocates in their own words.
• That last phrase matters — the goal is residents making the case themselves, not the developer's talking points repeated back.
• The framing that follows, "build the support that shows up when it matters," ties the work to a specific moment of consequence rather than general goodwill.

For brands planning a campaign

When evaluating a public affairs plan, ask who the named local supporters are and whether they can speak without a script. Letter counts and hearing turnout are testable outputs; sentiment scores are not.

This short post draws the distinction that runs through the whole body of work: a permit is permission, not acceptance.

• Written about data centers, it argues that developers need to address local concerns and build relationships before opposition takes hold, and it points to research, targeted messaging, and grassroots outreach as the mechanisms.
• The three-beat close — start by listening, build trust, earn support — is deliberately sequential, and it is also a compact statement of the division of labor between research and outreach.
• It references a National Review interview and the agency's site for the fuller argument.

For brands planning a campaign

Plan for the period after approval, when construction, local hiring, and any expansion still depend on the same relationships. A campaign that ends at the permit leaves the harder phase unmanaged.

Drawn from a conversation with National Review, the post argues that data center developers cannot rely on a national campaign because what works in one location may not work in another.

• It then gets specific about what actually surfaces locally: water use, energy demand, local infrastructure, jobs, and tax revenue.
• The recommendation is to listen before a project is announced and to show how the project responds to what residents raised — the post distinguishes that from simply delivering a message, calling it taking action.
• The closing line, that every data center has to stand on its own in each community, is the practical consequence: no template carries over.

For brands planning a campaign

Build per-market messaging from local research rather than adapting one national narrative. For data centers specifically, prepare credible answers on water and power before they are asked, since those are the issues named here.

The post uses President Trump's call for data centers to generate their own power and provide community dividends as the setup, then makes a sharper point: incentives alone do not build lasting trust.

• The reasoning is that communities need to understand a project's broader value before financial benefits can resonate, and that economic upside becomes meaningful once people trust the project and see how it fits the community's future.
• The line "community support can't simply be bought" is the thesis, and "starts with people, not just dollars" is the application.
• The post does not dismiss incentives — it puts them downstream of trust.

For brands planning a campaign

Sequence benefit communication after listening and framing. Leading with tax revenue or payments before residents feel heard tends to read as a transaction and can harden opposition.

The post argues that online social media debates about renewable projects tend to deepen opposition rather than build support, and contrasts that with targeted digital advertising, which can reach people who are open-minded one-on-one before their opinions harden.

• The recommendation is not to run ads first: the post insists on listening to the community, identifying what people care about, and then putting the right message in front of the right people.
• The reframing at the end — advertising as a public affairs tool rather than just a marketing tactic — signals how the channel should be judged, on whether it moves a project decision rather than on reach or engagement.

For brands planning a campaign

Steer paid spend toward persuadable audiences identified through research, and measure it against project milestones. Public comment threads are not the audience; treating them as one usually amplifies the loudest opposition.

Posts on renewable energy and data centers say developers should not wait for opposition to start building relationships, because early listening gives time to address concerns and establish credibility before opponents shape the conversation.

Starts with listening, then targeted outreach and consistent engagement, with the aim of building relationships before a formal approval process begins.

For brands planning a campaign

For a developer that wants to improve community acceptance ahead of hearings, this is a front-end relationship-building approach rather than late-stage persuasion. A campaign brief should expect time and local work before any public meeting.

Examples: Source 1 · Source 2 · Source 3 · Source 4

Public opinion research should come before engagement: it identifies the people, issues, and local dynamics that can shape a project, then informs messaging and next steps.

For brands planning a campaign

Useful when a developer needs to tailor communication to each site instead of running one national message. Budget and timeline should include research before outreach begins.

Examples: Source 1 · Source 2 · Source 3

Targeted digital advertising can reach people who are open-minded about a project one-on-one before they form a strong opinion, but only after the developer has listened to the community and identified what people care about.

For brands planning a campaign

Offers a specific channel for reaching persuadable audiences before views harden. A brand should test whether the project has a large enough open-minded audience and whether the message can be delivered with the clear, verified information Davies emphasizes.

Examples: Source 1 · Source 2

For brands planning a campaign

Practical for projects that need visible local support at hearings. The approach depends on locating willing community members and giving them the information to participate credibly.

Examples: Source 1 · Source 2 · Source 3 · Source 4

A permit or approval may let a project move forward, but trust has to be earned, and financial incentives alone do not buy lasting support. Posts on data centers argue that communities need to understand a project's broader value before economic benefits resonate.

One reviewed post refers to President Trump's call for data centers to generate their own power and provide community dividends, which Davies uses to argue that tangible benefits matter but are not sufficient on their own.

For brands planning a campaign

A developer seeking durable acceptance should be ready to discuss local benefits and tradeoffs, not just approvals or payments. Davies's framing fits campaigns where trust is a stated goal.

Examples: Source 1 · Source 2 · Source 3

The work includes mapping decisionmakers, identifying potential allies, and organizing support through the approval path.

For brands planning a campaign

Relevant when a project depends on county or local approvals and needs a map of who influences the outcome. The post is specific to rural energy projects, so applicability should be checked for other project types.

Examples: Source 1

It should help people understand the project, why it matters locally, and where it stands. The strongest project brands are built on research and clear messaging and stay consistent from neighbor meetings to public hearings.

For brands planning a campaign

Useful for developers who need a single, coherent story across many local conversations. The brand is treated as a communication tool, not just visual identity.

Examples: Source 1

Community meetings are opportunities to answer questions and understand concerns, but Davies says the key is ensuring those conversations lead to action.

For brands planning a campaign

A developer should plan for what happens after a meeting, including how concerns are answered and how supporters are moved into action. The approach requires staff capacity for sustained engagement.

Examples: Source 1

The exact relationship is not stated: the material does not identify John as owner, employee, or contract client.

View example

The posts present a media interview or citation, not a sponsorship or commercial partnership.

View example

Mata describes renewable sites developed specifically to power data centers and AI infrastructure, and argues that shared data and process discipline is what lets projects scale; Davies covers the community side of the same projects.

Mata's posts are about technology, data governance, and delivery inside a developer, including interconnection risk and the infrastructure stack.

• Davies stays on local opinion, trust, and whether residents show up for a project.
• Follow Mata for how projects get built at scale; follow Davies for whether a community accepts one.

Read original · Original 2

Ben P. uses official statistics and research to argue that decarbonisation is a sound economic bet and says the positive story has to be communicated to the public and to leaders who still need convincing; Davies argues that local trust has to be earned before a project can proceed.

Ben P. works at national scale: sector turnover, employment, competitiveness, and the geopolitics of clean technology.

• Davies works site by site, on listening, messaging, and hearing turnout.
• Read Ben P. for the broader economic argument and Davies for how to carry it into one community.

Read original · Original 2

The reviewed posts make the economic case for decarbonisation rather than the engagement case: they cite Office for National Statistics figures putting UK low-carbon and renewable energy turnover at an estimated £77.0 billion in 2024, up £8.1 billion on 2023, with employment in low carbon services rising 20.5 per cent, and they use Ember research on Chinese exports of solar, batteries and electric vehicles to argue that fossil fuels are a volatile part of the energy mix.

• The stated audience is policymakers, boards and executives who still need convincing.
• If the developer's real blocker is a council vote, a planning committee or a hostile local meeting, Ben P. does not answer it; if the blocker is a board that has not yet approved the project or a government that has not yet set supportive policy, this material speaks directly to that room.

The tradeoff is method.

• These posts argue from third-party datasets and comment on national trends; they describe no community research design, no local listening process, no supporter activation, and no route from a public meeting to letters of support or hearing testimony.
• A developer switching to this alternative gains a persuasive macro-economic narrative and loses the site-level execution plan the brief actually asks for.
• The framing is also UK-specific, and the posts read as commentary on published statistics rather than as a described service, so the reader would need to establish separately what work is on offer.

Examples: Source 1 · Source 2

The reviewed posts describe moderating an Infraday Mountain States panel on connecting the infrastructure stack across GIS, BIM, municipal operations and enterprise data and AI in renewable energy, and they draw the conclusion that the technology is rarely the constraint while data and process governance is.

• A second post describes renewable energy data, AI and analytics work recognised by a CIO 100 award for a third consecutive year, including GridSim AI, which turns interconnection risk into a runnable data product used before capital is committed.
• Choose this alternative when the audience is technical or enterprise, when the decision turns on siting, interconnection queues, or how a developer's own data is governed, or when the buyer wants evidence of large-scale development operations rather than communications.

The tradeoff is scope.

• Nothing in the reviewed material addresses public acceptance: no community listening, no project-level messaging, no grassroots outreach, no engagement with opponents or local officials.
• The vantage point is also that of a large corporate developer building renewable sites largely to power data centres and AI infrastructure, which is the situation the community-engagement brief is trying to avoid duplicating, and the posts name AES and its customers rather than describing an engagement service a brand could commission.
• A developer who follows this alternative gets a route into internal data and delivery problems and still has to solve the trust problem elsewhere.

Examples: Source 1 · Source 2