Proximity Is a Strategy, Not a Sentiment

I once sat in a planning session where a genuinely smart group of people made a decision about a neighborhood that none of them had spent an unscheduled hour in. The room was impressive. There was a demographic analysis on the screen, a funding model that balanced, and a timeline everyone could defend. The plan was reasonable in every way a plan can be reasonable on paper. It was also wrong, in a way that anyone who had stood on those blocks at the wrong time of day would have caught in about five minutes. No one in that room had stood there. So the error sailed through, well-dressed and unchallenged, and it cost real time and real money before the ground finally corrected it.

I think about that meeting often, because the failure wasn't a failure of intelligence or intention. Everyone there cared. The failure was one of distance, and distance is something we almost never name as the culprit.

We tend to treat proximity as a virtue. We admire it in others. We feel a faint guilt about not having more of it ourselves. We file it under values, somewhere near humility and compassion, the kind of thing you affirm in a mission statement and then move past to get to the real work of strategy. That filing is the mistake. Proximity is not a sentiment. It is a method, a way of generating information about a place that no survey, no dashboard, and no windshield tour can replicate. And in community development, where almost every consequential decision is made about people by those who do not live among them, it may be the single highest-leverage discipline available to a leader.

I want to make the case for proximity as strategy, not feeling. To do that I'll work through three things: why closeness is a genuine source of data and not just a warm one, what distance actually costs you when you manage from above, and how to build proximity into how you operate even when you cannot, and probably should not, move into every neighborhood you touch. Because that last point matters to this audience especially. If you fund, govern, or lead across many places, you will never be proximate to all of them by biography. The good news is that proximity can be designed, resourced, and delegated. The leaders who understand that build it on purpose. The ones who don't keep making confident decisions from the top of the funnel and wondering why the ground keeps surprising them.

Proximity Is a Data Source, Not a Feeling

Here is the uncomfortable truth that the planning-session story points to: the most decision-relevant facts about a neighborhood are often the ones that appear in no dataset at all, because no one was ever close enough to be told them.

Think about what a dashboard can show you. It can tell you that enrollment at a school dropped this year. It cannot tell you that it dropped because a bus route changed over the summer, and a few grandmothers who had quietly organized the morning walk for half the block could no longer make the timing work, so families scrambled and some kids landed somewhere else entirely. The number is real. The number is also useless without the story underneath it, and the story underneath it lives at a kitchen table, not in a spreadsheet. You only get it if you are close enough that someone trusts you enough to mention it in passing. That is not soft information. That is the actual mechanism driving the metric you're trying to move.

This is what proximity gives you that instruments cannot. Data gathered from above tells you what is happening. Proximity tells you why. And in a complex system, which is exactly what a neighborhood is, the why is the whole game. Systems reveal themselves through their behavior, watched closely and over time, not through a snapshot taken from outside the window. You cannot understand how a neighborhood actually runs by studying a still photograph of it. You have to watch it move, and you have to be near enough to see the parts that don't photograph.

The trouble is that we have built a strong cultural bias toward exactly the wrong instinct. Information that arrives in a chart feels rigorous and gets treated as objective. Information that arrives through relationship feels anecdotal and gets discounted, often by the same leaders who would never admit they trust a vendor's dashboard more than a resident's account. This is backwards, or at least it's lazy. Both sources are partial. The chart is a wide, shallow view that misses causation. The relationship is a narrow, deep view that misses scale. Neither one is the truth by itself. The leader's job is to hold them against each other, to triangulate, and the failure mode is privileging the spreadsheet by default simply because it looks more like work.

I have watched this play out in a way that should worry anyone who funds by the numbers. I once worked with a program that reported strong participation figures, the kind that make a board nod and a funder renew. By the metrics it was a success. But spend any real time on the ground and a different picture emerged, because a large share of the people being counted did not actually live in the neighborhood the program existed to serve. The dashboard wasn't lying. It was answering a question no one had asked carefully enough, and only proximity revealed the gap between the number on the page and the people on the block. A leader far from the ground would have celebrated that program. A leader close to it knew there was work to do.

So I'll leave you with the question that sits underneath all of this. When your data and your most proximate people disagree, which one do you instinctively believe? And, more honestly, is that instinct actually serving you, or just making you feel rigorous?

The Hidden Cost of Managing from a Distance

We treat distance as if it were neutral, a simple fact of scale. It is not neutral. Distance introduces its own predictable errors, and those errors compound quietly until they show up as a failed initiative or a displaced family. We just don't put the cost on the ledger, because it never arrives as a line item labeled "we were too far away to see this coming."

The first cost is subtle and almost gravitational. From a distance, you can only act on what is legible, on what your instruments can actually capture. So without ever deciding to, you begin redefining the problem as whatever fits your instruments. The thing you can measure becomes the thing you work on, and the thing you cannot measure quietly drops out of the strategy, not because it stopped mattering but because it stopped being visible. A neighborhood's real challenge might be a frayed web of relationships that no one funds and no one counts, but if your dashboard tracks housing units and test scores, those become the problem by default. Distance doesn't just limit what you see. It edits what you believe the problem to be.

The second cost is the one this audience should sit with most carefully, because it is how good intentions turn into harm. Well-funded, well-designed investment, decided from a distance, is precisely the mechanism by which neighborhood improvement becomes displacement. From the top of the funnel you can see the rising property values and the new amenities and the better numbers, and they all look like success. What you cannot see from up there is who is being pushed out underneath the improvement, because the people leaving don't register in the metrics that made you feel good. They simply disappear from the next dataset, and the next dataset, lacking them, looks even healthier. Distance hides the displaced by design. Only proximity puts a face on the cost, and a face is much harder to overlook than an absence.

The third cost is speed. Distance slows the rate at which you learn you are wrong. A leader close to the ground catches a faltering approach in weeks, adjusts, and moves on with most of the resources intact. A leader managing from afar discovers the same error in the three-year evaluation, after the money is spent and the trust is gone. The feedback loop that should be tight and fast gets stretched until it is nearly useless for course correction. By the time the report confirms the problem, the problem has had three years to set.

And underneath all of it sits the cost that makes the others worse, which is trust. Trust is infrastructure. It is the thing that lets a grandmother mention the bus route, that lets a partner tell you the unflattering truth before it becomes a crisis, that lets a community absorb the inevitable disruption of change without concluding you were never on their side. Trust is built slowly, through ordinary presence, long before you need it. What you cannot do is parachute in and request it at the moment of maximum need. Distance erodes this asset continuously and silently, and then one day you reach for it and find the account empty.

So a fair question for any of us: how many decisions are you currently making about a place based entirely on what fit inside a report?

How to Build Proximity When You Can't Move In

Here is where the reframe earns its keep. If proximity were only a sentiment, then this whole argument would belong to the handful of leaders who happen to live in the neighborhoods they serve, and would be a quiet rebuke to everyone else. But proximity is a strategy, and the whole point of a strategy is that you can design it, fund it, and assign it. Most of the people reading this will never live in the communities they shape, and that is not a moral failing. The failing is not building deliberate channels to close the distance anyway.

The most important of those channels is proximity by proxy. Fund, hire, and genuinely defer to people who are authentically close to the ground, and then, this is the part that gets skipped, structure your decisions so their knowledge carries real authority rather than a comment period. There is an enormous difference between input and power. Input is when proximate people are invited to speak and then watch the decision get made without them. Power is when their account can actually change the call. If the people closest to the consequences cannot move the decision, you have not built proximity. You have built a focus group and given it a nicer name.

The second channel is treating proximity as something you budget and schedule, because anything that isn't budgeted and scheduled doesn't happen. Unstructured time on the ground, resident-led governance with teeth, staff who are embedded rather than dispatched, all of this costs money and time, and all of it tends to be the first thing cut when the spreadsheet gets tight. That instinct is exactly backwards. Closeness is not the soft expense you trim to protect the real work. It is the thing that tells you whether the real work is working. Put it in the budget and the org chart, or admit you've chosen distance and accept what distance costs.

The third channel is the willingness to recognize proximity theater for what it is, and to refuse it. The listening tour that informs nothing. The site visit choreographed down to the minute. The advisory board that convenes quarterly and decides nothing of consequence. Performative closeness is in some ways worse than honest distance, because it launders a decision made from afar and stamps it "community-informed," which makes the decision harder to question and the distance harder to see. If you are going to build proximity, build the real thing, and be ruthless about telling the difference.

For the funders in particular, this changes the questions you ask. The most revealing question on an application is not "show me your logic model." It is "who that actually lives here is in the room when you decide, and what, specifically, can they change?" Reward genuine proximity in the organizations you back, and you will fund fewer confident plans that fall apart on contact with the ground.

For government leaders, it changes the timing. The agencies that get this build standing relationships before they need them, not consultation processes bolted on after the plan is already drafted. Consultation after the fact is proximity theater with a public-meeting sign-in sheet. Relationship before the fact is strategy.

The honest test of all of it is simple. If proximity is a strategy, then it should be visible in your budget, your org chart, and your decision rights, not just in your values statement. Where does it actually show up?

The Risk We Misname

Go back to that planning session, the impressive room with the balanced model and the wrong plan. What proximity would have changed there was not the intelligence in the room or the care behind the decision. It would have changed the information the decision was built on. One person who had stood on those blocks at the wrong hour could have turned a defensible plan into a correct one, and the whole expensive correction could have happened in conversation instead of in consequences.

The choice in front of this audience was never whether to care about communities. Nearly everyone doing this work cares, sometimes to the point of exhaustion. The real choice is whether to treat closeness as an operational discipline you build and resource, or as a sentiment you admire and then outsource to someone else's biography. Those lead to very different organizations and very different outcomes.

And it is worth naming the risk we usually have backwards. We worry that being too close to a community will cost us our objectivity, that proximity clouds judgment. In my experience the far more dangerous position is the opposite one. It is being just far enough away to feel certain. Certainty is cheap at a distance. It gets a lot more honest the closer you stand.

So I'd offer one thing to try this week. Take a single decision you are currently making about a place, and audit where your information is actually coming from. Then ask who, that is genuinely proximate to it, would tell you something you don't currently know. Go find out what they'd say. It is the cheapest strategy you have, and most of us are leaving it on the table.