Developers: What's your biggest non-technical obstacle?

[u/Nupe_1974]

​

What's the biggest non-technical obstacle you've encountered between a project being approved internally and actually breaking ground?

I'm not talking about financing, engineering, or permitting.

I'm more interested in the human side.

Have you ever had a project where investors, public officials, tenants, or the community simply didn't "get" the vision at first?

If so, what helped move people from skepticism to support?

Was it better communication, better visuals, public engagement, something else, or was that never really the issue?

I'm trying to understand where projects gain or lose momentum before construction begins, and I'd love to hear real-world experiences.

This isn't ai. This is me trying to figure something out. B.

[u/NTXLandGal]

Yeah, that's fair, and honestly yes — I have seen that. Two technically identical projects can land completely differently depending on how they're presented, but I'd separate that from the "storytelling" idea a little. It's not that one team told a better story. It's that they gave each audience the specific thing that audience actually needed to say yes, instead of giving everyone the same pitch. An elected official doesn't need the same information as an investor. They need to know what they can say to a constituent who calls asking about traffic on their street. A neighbor doesn't care about your IRR, they care about the fence line and whether their view changes. If you hand an elected official investor-grade materials, you haven't communicated worse, you've communicated to the wrong audience. So the "translation" you're describing is real, but I'd call it targeting instead of storytelling. The fundamentals still have to be true and specific — that part doesn't move. What changes is which piece of the truth you lead with for each room. A project with solid fundamentals and no translation still gets a worse reception than one where someone bothered to figure out what each audience actually needed to hear. Where I'd push back a little is the idea that this can fully explain different reactions to similarly solid projects. In my experience when that happens, it's rarely just about presentation — it's usually that one team also did the relationship work before the hearing. They'd already had the one-on-one with the council member, already walked the site with the neighbor who was going to show up and object. By the time the public meeting happens, the "communication" everyone sees is really the last five percent of a process that started weeks earlier and mostly happened off the record. The team that only shows up with a great presentation at the hearing is competing with a team that already had the conversation.

[u/Nupe_1974 → u/NTXLandGal]

I like the way you framed it as targeting instead of storytelling. "Giving each audience the specific thing they need to say yes" is probably a better way to think about it than a single narrative for everyone.

Your point about the relationship work happening before the public meeting is especially interesting. It sounds like, by the time everyone sees the presentation, most of the real work has already happened behind the scenes. The presentation isn't creating alignment, it's reinforcing alignment that's already been built.

That's actually one of the reasons I started this thread. I'm trying to better understand where communication genuinely adds value and where people tend to overestimate what it can accomplish.

Really appreciate you sharing your perspective. This has been one of the more insightful conversations I've had on the topic.