Developers are very good at planning.
Before a major project ever breaks ground, enormous amounts of time and money go into engineering, financing, land acquisition, environmental studies, power, water, traffic, legal review and permitting. Teams model scenarios, identify risks and establish timelines. Nobody would seriously propose building a billion dollar project without blueprints, schedules and contingency plans.
Yet when it comes to community opposition and the public approval process, I continue to see developers operating without a playbook.
That is becoming increasingly dangerous.
After 30 years working in public affairs and NIMBY battles, I have watched opposition become more sophisticated, faster and better organized. This is particularly evident today with data centers, renewable energy, energy infrastructure and large industrial development. A project that might have generated a few concerned neighbors ten years ago can now generate a Facebook group, online petition, packed public hearing, organized coalition and political controversy within weeks.
The mistake developers make is assuming they can respond to those events as they happen. They cannot. By the time the opposition has organized, defined the project publicly and put elected officials on the defensive, the developer is already playing from behind. That is why one of the central principles of my NIMBY War Room approach is simple: developers need to stop treating public affairs as a communications function and start treating it as an operating discipline.
That requires a playbook.
Over the past year, I have worked with development teams to build exactly these kinds of playbooks. The objective is not to create another corporate document that gets presented at a meeting and then disappears onto a shared drive. A useful playbook captures what an organization has learned and turns those lessons into repeatable actions.
Think about how development companies typically operate. One project manager may have successfully navigated a difficult county approval. Another may have learned painful lessons from a hostile public hearing. A communications executive may understand how to respond to misinformation. A development executive may know which early warning signs indicate that opposition is beginning to organize.
One lesson I have learned repeatedly is that developers tend to define the beginning of the public approval process too late. They may view the first planning commission meeting, zoning application or public hearing as the beginning. Politically, the campaign may have started months earlier.
Neighbors are talking. Local officials are hearing rumors. Reporters are asking questions. Social media posts are circulating. Someone discovers a land transaction. An opposition group forms. A petition appears online. The project is being defined whether the developer participates in that conversation or not.
A good playbook forces the organization to think earlier. That begins with strategic siting and opposition risk. What is the political environment? Who are the decision makers? What issues have created controversy previously? What organizations influence local opinion? What concerns are likely to emerge? Who are the credible third parties in the community? What elections are approaching? What does the local media environment look like?
These are not communications questions. They are development questions because the answers can directly affect whether a project gets approved.
I have seen this firsthand on major development campaigns where technically strong projects suddenly found themselves facing organized opposition. Once that happens, random activity is not a strategy.
Holding a community meeting is not a strategy. Launching a website is not a strategy. Hiring a lobbyist is not a strategy. Sending mail is not a strategy. Meeting with elected officials is not a strategy. Each may be valuable, but only when connected to an overall approval strategy.
The playbook provides that structure. Who needs to hear from us first? What information do they need? Which concerns must be addressed before they become allegations? Which stakeholders should be engaged privately? When should broader public education begin? Who are the potential supporters? How do we give those supporters the information and confidence to speak publicly? What happens 90 days before a hearing? Thirty days before? Seven days before?
That is where public affairs becomes operational. On one major project, our strategy required us to simultaneously protect the approval pathway, build community support, counter misinformation, segment stakeholders and prepare for a series of public hearings. Each hearing was treated as a campaign milestone. Messaging, community education, supporter identification, elected official outreach and opposition intelligence all had to work together.
Without a playbook, those activities easily become disconnected. With one, they become a campaign.
Not every NIMBY problem is created by the opposition. Some are self inflicted.
Development organizations can be highly compartmentalized. Development is doing one thing. Legal is focused on another. Communications is brought in later. Community engagement may operate separately. Consultants receive different instructions from different executives. Then controversy erupts and everyone suddenly meets on a conference call.
That is not a War Room.
A real NIMBY War Room establishes clear lanes before the crisis. Who is the internal quarterback? Who owns political intelligence? Who communicates with elected officials? Who engages neighbors? Who approves public messaging? Who monitors opposition? Who prepares speakers for hearings? Who decides when an issue requires escalation?
The middle of a controversy is a terrible time to answer those questions. A playbook answers them beforehand.
My CASE framework stands for Credibility, Advocacy, Solutions and Education. The order matters.
Developers frequently want to begin with advocacy. They want people to support the project.
Communities usually want something else first. They want to know whether they can trust you.
That means acknowledging legitimate concerns, providing factual information, answering difficult questions and demonstrating that community engagement is more than checking a box on an application. Only after credibility begins to develop can meaningful advocacy follow.
The playbook should therefore include more than crisis response. It should establish standards for transparency, community education, stakeholder engagement, third party advocacy, media relations, digital communications and hearing preparation.
It should also anticipate the predictable allegations. Every industry has them. Data centers face questions about electricity, water, noise, taxes and land use. Renewable energy projects encounter concerns about property rights, farmland, environmental impacts and decommissioning. Industrial projects face questions about traffic, safety and quality of life.
You should know those questions before the opposition asks them. Better yet, you should answer them before the opposition weaponizes them.
Perhaps the most important thing I have learned from developing these systems is that a good playbook should never really be finished. It should be a living document.
Every project produces intelligence. Every difficult hearing teaches something. Every opposition campaign reveals new tactics. Every successful approval demonstrates something worth repeating. Those lessons should go back into the playbook.
That creates something far more valuable than a communications plan. It creates organizational muscle memory.
The companies that become best at navigating NIMBY opposition will not necessarily be the companies with the biggest communications departments, the largest lobbying budgets or the most expensive consultants. They will be the companies that learn faster, prepare earlier and execute more consistently.
America needs infrastructure. We need energy. We need data centers. We need manufacturing, housing, logistics and the infrastructure required to support economic growth. But needing something does not guarantee that a community will approve it. Developers still have to earn the social and political permission to build.
That brings me to the question I believe every developer and executive team should be asking themselves:
Consider what is actually at stake. A major development can represent hundreds of millions or even billions of dollars in investment. Years can be spent securing land, engineering a site, negotiating agreements, arranging financing and navigating regulatory requirements. Yet one of the greatest threats to that investment can come from something many developers still treat as secondary: organized community and political opposition.
A playbook cannot guarantee an approval. Nothing can. What it can do is make sure your organization is not improvising when the stakes are highest. It can help you identify opposition risk earlier, establish internal responsibilities, build credibility in the community, prepare for predictable attacks and give your team a common strategy from siting through the final vote.
The better question, then, may not be whether your company can afford to build a playbook.
If you do not have a confident answer to that question, it is probably worth a conversation. Not because every developer needs the same playbook, but because every developer should understand what its own playbook needs to accomplish before the next battle begins.
About the Author
Patrick Slevin is a nationally recognized NIMBY strategist, author and founder of the NIMBY War Room. He advises developers and infrastructure companies on navigating community opposition, political risk and public approvals.