Whenever we submit a development application for a new project, we typically get a ton of inbounds from people who are looking to sell us something, partner in some way, or buy/rent space in the development. These can be positive connections and we have completed deals based on these sorts of inbounds.
But what is clear to me is that many people do not understand the development process and how long it takes to actually bring a new building to fruition. By the time a development application is filed, it is not uncommon for the developer to have already been working on the project for at least a year, and oftentimes longer in the case of more complicated projects.
And after the application is filed, it is not uncommon (at least in this city region) for the approvals process to take another few years. We have projects that are on year 7 and we still can't put shovels in the ground. This is a bit of a unique situation, but even still, when it's all said and done, a "typical" mid-rise or high-rise project could take 7-10 years from beginning to end. And sometimes longer.
A decade is a long time. So it's no wonder that low-rise sprawling cities with permissive land-use policies tend to have more elastic housing supply. Quicker builds. And quicker approvals.
I say all this not because I expect everyone to understand how the development process works. I'm saying it because maybe if more people knew how long everything takes, they'd be more open to streamlining the delivery process and to encouraging the construction of more missing middle housing.
Public consultation is broken. And by that, I mean that the way in which municipalities, developers, and other city builders solicit feedback from communities is fundamentally flawed.
For new developments, the process works more or less like this: The developer makes an application to the city. The city reviews it and then agrees to move towards a public/community meeting (the goal of which is to solicit feedback on the proposal). Once a date is set, notices go out, and the developer secretly hopes that no one will show up.
Because what often ends up happening is that it’s only the people with the time or a bone to pick who actually go to these things. Rarely do people go simply to voice their support for a project. That’s why the benchmark for success is usually no community opposition – it’s rarely about support.
But from writing Architect This City, I know that many of you care deeply about your community and about cities in general. The problem, is that I don’t think most of you get a chance to voice your opinions. How many of you have actually gone to a community meeting in order to show your support for a development project or city initiative? I’d be curious to know, but I suspect most of you haven’t.
The result is a system whereby the voice of a few (often naysayers) have a disproportionate amount of weight. They set the tone. But that’s not how community input works best. It needs to be representative of a broad and diverse cross section of the population. It needs to be inclusive. Everyone in the community should have a say.
So today I was thinking that there’s an opportunity for somebody out there to create an online platform for community feedback. Developers would post up their project and then everyone in the community, as well as in the larger city, would have an opportunity to vote on it and provide their feedback.
To make it fair, you could assign higher weights to people the closer they live to the project. But the idea would be to make it as easy as possible for everyone to provide feedback – whether they’re on their smartphone or at the regular community meeting.
Obviously this would require greater openness, but I don’t think that pulling back is the answer to this problem. The solution isn’t to hide from the potential naysayers; it’s to galvanize the supporters.
If your community already has a platform like this, please share it in the comment section below. I’d love to see it.