Your City Knows Less About Your Street Than You Do

You know the intersection where kids cut through every morning because the crossing signal is timed wrong. You know the landlord who lets the building go to rot while collecting rent. You know which neighbors would help in an emergency and which ones wouldn't. You know the store that quietly started accepting EBT after the last one closed. You know where it floods after a hard rain.

City hall doesn't know any of this.

Not because they're lazy. Because they can't. A city of any real size produces more local knowledge every single day than any central office could possibly gather, process, and act on. The knowledge lives in the people who are there — on the block, in the building, in the neighborhood — and the current system has almost no way to use it.

This is a massive problem. Not just for fairness. For basic competence.

Take stock of what you actually know

Here's a small exercise. Think about your block, your building, your immediate neighborhood. Compare what you know to what your city government probably knows.

This isn't a knock on city workers. The planner who designed that intake form has never needed to use it. The councilmember who approved the program gets updates from a director who gets them from a manager who gets them from a staffer who reads the numbers. By the time information travels that chain, the friction and failure and workarounds people have invented — all of that is gone.

What arrives at the top is a cleaned-up version of reality. The actual situation stays at the bottom.

This isn't just unfair — it produces bad decisions

There's a temptation to frame this purely as a justice issue: the community should have a say. That's true. But there's a harder, more practical argument that doesn't depend on fairness at all.

Decisions made without local knowledge are worse decisions. Not sometimes — reliably, structurally, as a matter of how information works.

The transit agency that cuts a bus route because ridership numbers look low doesn't know that the stop serves a shift-worker population that doesn't show up in peak-hour data. The housing authority that builds units with no storage space doesn't know that residents in that neighborhood run small informal businesses out of their homes. The parks department that closes a "underused" basketball court doesn't know it's the de facto community center for three square blocks and the main reason teenage boys in that area aren't somewhere worse.

These decisions get made constantly, at every level of every city. Not because officials are indifferent — though some are — but because the information required to make a good decision never made it into the room.

The hierarchy filtered it out on the way up. That's what hierarchies do. By design, they simplify. They compress. They remove the noise. Unfortunately, a lot of what gets called noise is the thing you most needed to know.

Why cooperation is smarter, not just nicer

The argument for involving residents in local decisions is usually framed as a values argument: people deserve a voice, representation matters, communities should be empowered. All of that is true.

But there's a completely separate argument that has nothing to do with values. It's a practical one: distributed systems are better at processing complex information than centralized ones.

Consider how your immune system works. It doesn't route every threat through a central decision-maker that evaluates it and issues a response. Each cell responds to what it directly encounters. The response is local, fast, and informed by direct contact with the problem. A centralized immune system would kill you — too slow, too far from the action, working from secondhand information.

Or consider how the internet routes data. When a packet travels from one place to another, it doesn't follow a route predetermined by a central authority. Each node passes it along based on what that node can see. The system responds to actual conditions in real time. It's robust precisely because no single point holds all the decisions.

Cities are not immune systems or packet networks. But the principle holds: when you concentrate decision-making at the top of a hierarchy, you get decisions that are only as good as the information that survives the climb. A lot doesn't survive.

When you push decision-making closer to the people with direct knowledge — when you build systems where local information can actually reach the decisions it should be informing — you get better outcomes. Not because people are inherently wise or good, but because they know things the center can't know.

What this asks of us

The uncomfortable part of this argument is where it leads.

If local knowledge is genuinely valuable — if the people closest to problems really do know things the center can't — then effective governance doesn't just mean asking for community input before making the real decision. It means building structures where that knowledge shapes the decision. Where residents aren't consultants who get thanked and ignored, but participants with real authority over things that directly affect them.

That's a different kind of city. It requires a different kind of participation, too — not just showing up to a meeting to voice a preference, but taking on some genuine responsibility for outcomes. That's harder than filing a complaint. It's also more powerful.

The knowledge you have about your street, your building, your neighborhood — it's not just frustration waiting to be discharged at a council meeting. It's infrastructure. It's what good decisions are built from.

Right now most of it goes nowhere. That's a design choice. And it can be made differently.