I have sat at the table where decisions are made, and I have sat in the audience where people line up to speak. I have been a city councilor, a mayor, and now a land-use attorney. As an elected official, I met with, and guided many developers through the public process. Some listen and are patient, others are defensive and entitled. The former get approvals. Public meetings are not singularly where you get final approval but rather a critical opportunity to hear concerns and gather input in order to improve the project and better understand community and board concerns. When developers walk into a meeting thinking it will be the first and last meeting it will not go well.
Community meetings are not a hurdle to clear. They are part of the project itself. When developers treat them as a slideshow or plain obligatory, trust disappears. When they do them right, projects move faster and with less damage, division, cost and delay.
The First Mistake Is Showing Up Too Late
Many developers wait until the design is nearly finished before meeting the neighborhood. The community sniffs that out immediately .Sometimes the developer is ignorant of the long history around the development site or the community. At that point, the room can feel ambushed. People see a plan that already looks locked in, and they react accordingly.Let’s face it the community is not looking to trust a developer so this is not hard to screw up.
From the City Hall side, we could always tell when a team waited too long. Worse, they thought it was a top down process. Neighbors showed up angry because this was the first time they had heard anything. The tone was set before the meeting even started.
The better approach is early and informal. Meet people when ideas are still flexible. Tell them what you are thinking and why. Ask what matters to them before you draw hard lines. Early conversations do not guarantee support, but they reduce shock and build credibility. As a politician the best campaigning was in off election years, in sports the best practices are long before the season and in permitting you have to show people you care before the permits are filed.
PowerPoint Does Not Equal Listening
Developers love slides. The more detail the more the project feels baked without community input. Neighbors love being heard. Those two things are not the same.
A long presentation that leaves ten minutes for questions tells people that their role is secondary. It signals that the meeting is about selling, not listening. Once people feel talked at, they stop engaging constructively. Most architects are uncomfortable with the external interactions and so are many of the other consultants. The land use attorney is the strategist and the coach. I spend a lot of time getting ahead of potential mistakes. Exaggerations or obvious avoidance of key facts are big mistakes. You will lose facts. As my Mom said “don’t be cute,” be honest and consistent. Test all your arguments internally before you say a word in public. Presentations should reference the community process and even individual neighbors and groups who gave direction, Make is granular and personal.
A better meeting flips the script. Keep the presentation short and clear. Use plain language. Leave real time for questions and comments. Take notes in front of the room so people see their input being captured. Listening is visible. People know when it is real.
Chose the best timing and location and Don’t be defensive
I remember getting a notice of a meeting about a construction project next to my house on Valentine’s night at 6: 30 pm. I made it clear that they could have come to my house and seen me since I was 50 feet away and that I was already upset at the choice of dates and time. Anxiety and distrust for developers is a given, so do not make it worse by scheduling a meeting mid summer, or at an inconvenient time. Remember you are not entitled to approvals so be patient and never seem inconvenienced. People are protecting their homes, their streets, and their sense of place.
When a developer responds defensively or worse, says “ this will improve your community”, tension escalates fast. Dismissing concerns or supplanting your own opinions are absolute no nos. Appreciate sincerely peoples time and input no matter how critical..
From behind the table, I learned that the best presenters stayed calm and respectful. They acknowledged fear even when they disagreed with it. They explained tradeoffs instead of denying impacts. Any threat of walking away if you don’t get approved is a sure death knell. If there is a threat of losing the project or a worse alternative let the residents come to that conclusion on their own. Threats will back fire. Let them know you will try as much as possible to address their concerns.
Respond to concerns without judgement
This is a big one. Neighbors often talk about height, traffic, or shadows. Sometimes those are real issues. Sometimes they are stand-ins for something deeper. You have to remember that residents don’t have time or coaching to plan their every word. Do not hold words against them. Some residents will miss the mark or not be constructive but that does not mean you should write them off.
Change is hard and anxieties could be about small, but important things, like parking or a specific shadow, or it could be all around concern about how new development will change their neighborhood. Listen carefully and do not judge.
Good community meetings create space for those broader conversations. You cannot solve every fear, but you can name it and explain how your project fits into a larger plan. That honesty goes a long way. The community meeting should be met with very detailed personal follow up with every speaker and attendee.
Exaggerating the economics will backfire
Taking financing risks is a real thing. Its ok to speak of challenges and risk but exaggerating cost will not go over well and will face challenges. In the heat of a meeting, it is tempting to exaggerate unknown risks, but just saying it’s hard to know what is possible is honest and true.
Also if you absolutely know you cannot do something do not say maybe. Yes is yes, maybe is maybe, and no is no. The community will rate your honesty and consistency.
The better approach is disciplined honesty. Say what you can do. Say what you cannot do. If something needs more study, say that. Credibility is built by underpromising and following through.
Humility and likability and tell the real story
Stay long after the meeting is over to get to know people. Break bread. Show you can take a beating and keep on showing up. The community process rarely ends after one meeting. If you get approved it will be like a marathon, with people who have become part of the process and hopefully friends. People would rather support people they like. Show your human. Be yourself
One thing I learned in public office is that inconsistency is a red flag. When a developer tells a different story at each meeting, people assume the worst.
Good teams keep their message consistent. They are honest about real challenges and the inside baseball of a deal. Sometimes there are third parties needed for a deal to work or other constraints. Be transparent. If you want the community as a partner, treat them like one. Changes are explained clearly. Commitments are repeated and documented. Consistency builds confidence even among skeptics.
Respect City Staff and the Process
Community meetings do not exist in a vacuum. City staff are often in the room, or at least watching closely.
Find a way to make the community the primary audience without alienating staff. This is a tough balance so it involves one on one check ins and circling back. This is a balance that can be a no win. If the project feels City driven the community will react poorly. If you do not involve city staff that can hurt you. In this situation trust is absolutely critical. City Staff know how invested I am in the community but always keep them close. It’s an ongoing effort to keep both audiences aligned. In fact it’s an artform. Also create a transparent community process web page and post all materials online. This is not a substitute for a one on one, but it keeps everyone up to speed. When the meeting is over, post the materials and video.
Respecting holidays and building relationships that are not about permitting
You should not only talk to staff or residents about your project. That is selfish, boring and counter productive. No one likes to feel like a relationship is one way. Find ways to talk to see and get to know neighbors. It’s ok to check in without pushing the project. Sometimes staff like to hear about the economic environment, the financing world or other industry updates. Permitting attorneys and developers that survive are not just around when they need something.
Why Doing This Right Saves Time
Some developers see community processes as a delay and the chaos of external politics unfair. Permitting is fluid and so are the feelings of the community. Roll with it.
Think of how you want to be treated on your next project. Clients that behave like its their last and only project usually fail, Teams that build trust face fewer appeals, fewer political obstacles, and fewer surprises. Boards feel more comfortable approving them. Staff feel supported. Neighbors may not love the project, but they accept the process.There will be nights that boards want more time for what seem like bad reasons. You can explain the reason for exigency but always let them off the hook. Tell the community more meetings are possible if needed. Take the pressure off.
From my seat behind the table and now beside it, I can say this clearly. Community meetings are not about winning the room. Projects get approved way before the actual hearings. It’s like election day. You have either already earned the votes or you haven’t.
If developers approach them with patience, humility, clarity, and honesty, they do not just get better meetings. They get better outcomes.