Every few years, a new wave of investment hits a neighborhood. New renderings go up on billboards. Press conferences happen on vacant lots. Promises get made about transformation, revitalization, renewal. And almost every time, the people doing the building are designing for someone who hasn't arrived yet, not the person who's been there all along.
I've watched this cycle play out across Detroit for over a decade. A new mixed-use development goes up on a corridor that lost half its businesses during the recession. The ground-floor retail spaces get priced for boutique coffee shops and coworking concepts. The apartments above target young professionals relocating from other cities. The marketing materials feature stock photos of people who look nothing like the residents on the surrounding blocks.
And then everyone wonders why the community pushes back. Why the neighborhood association shows up angry at the zoning meeting. Why the longtime residents feel like the city is being built around them, not for them.
The Myth of the Ideal User
In tech, they call it building for the "ideal user" -- a fictional persona that represents who you wish your customer was. In urban development, the ideal user is the newcomer with disposable income, no existing ties to the neighborhood, and an appetite for whatever aesthetic the developer imagines will attract more people like them.
The problem is that the ideal user doesn't exist in a vacuum. They move into a neighborhood that already has people, history, relationships, and infrastructure -- even if that infrastructure is informal. The corner store that extends credit. The church that runs the food pantry. The block captain who knows every family within three streets. These aren't legacy systems waiting to be replaced. They are the system.
When you build for the ideal user, you're not just ignoring the existing community. You're actively undermining the social infrastructure that holds the neighborhood together. And once that infrastructure breaks, it doesn't come back.
The person who stayed through the worst of it isn't a barrier to progress. They're the foundation you should be building on.
Who Is the Person Who Stays?
The person who stays is the homeowner who kept paying property taxes when the house next door got torn down. The small business owner who kept the lights on when three competitors closed. The grandmother raising grandchildren because she refused to leave the neighborhood she grew up in. The barber who knows the name of every kid on the block.
These people didn't stay because they lacked options. Many of them had every reason to leave and chose not to. They stayed because they believe in the place. That kind of loyalty is the most valuable asset a neighborhood has, and we treat it like it's invisible.
When I think about what makes a community resilient -- actually resilient, not just the version you put in a grant application -- it comes down to the people who stayed. They're the ones who maintained relationships when institutions failed. They're the ones who created informal systems when formal ones collapsed. They are the connective tissue of the neighborhood.
Design for Loyalty, Not Attraction
Most development strategies are attraction strategies. How do we bring new residents, new businesses, new investment? The assumption is that the neighborhood needs outside energy to thrive. But attraction without retention is just gentrification with better branding.
What if we flipped the model? What if the first question in every development meeting was: "How does this serve the people who are already here?"
That doesn't mean you can't build new things. It means the new things should strengthen the existing community first and attract newcomers second. A grocery store that stocks what the neighborhood actually eats, not what a market study says the target demographic prefers. A community space that's priced for the people who live within walking distance, not the people driving in from the suburbs. Job training that connects to employers who are hiring now, not industries that might arrive in five years.
This isn't charity. It's strategy. The person who stays is your most reliable customer, your most credible ambassador, and your most honest feedback loop. They'll tell you what works and what doesn't because they have to live with the results.
Attraction without retention is just gentrification with better branding.
What This Looks Like in Practice
Building for the person who stays means a few concrete things.
Ownership pathways, not just access. Don't just invite longtime residents to use the new facility. Give them equity in it. Community land trusts, cooperative ownership models, revenue-sharing agreements -- these aren't radical ideas. They're proven structures that align incentives between developers and communities.
Pricing that reflects reality. If the median household income on a block is $32,000, a $1,400/month apartment isn't "affordable housing." It's a signal that the building wasn't designed for anyone who lives there. Build the pro forma around real numbers, not aspirational ones.
Hiring from within. Construction jobs, management positions, vendor contracts -- every new development is a hiring opportunity. The default should be local first, external only when necessary. This isn't a feel-good policy. It's how you circulate investment back into the community instead of extracting it.
Listening before designing. Not a public comment period where decisions are already made. Actual design input from the people who know the neighborhood best. The woman who's walked that street for forty years knows more about what it needs than any urban planner with a six-month study.
The Long Game
Building for the person who stays is slower. It doesn't produce the kind of before-and-after photos that win design awards. The returns show up over decades, not quarters. And it requires something that most development models aren't built for: trust.
But here's what I know from building over forty ventures across Detroit and beyond: the projects that last are the ones where the community feels ownership. Not just access, not just proximity, but genuine stake in the outcome. When people feel like something was built for them -- actually for them -- they protect it, they improve it, they build on top of it.
That's the difference between a project and a legacy. Programs end. Buildings get sold. But a community that has been strengthened, not displaced, keeps compounding long after the ribbon-cutting is forgotten.
Stop designing for the person you hope will come. Start building for the person who never left.
