Power Explained Glossary Wire
Piece 04 — Capturing vs. Building
#004

Two Ways to Fix a Pothole

There's a hole in the road. Everyone knows it's there. This is a story about two different ways it gets fixed — and why the difference matters far beyond potholes.

Potholes in a city street
The pothole — who fixes it, and how? — Wikimedia Commons, CC BY-SA 3.0

There's a pothole on your street. It appeared after the last winter. You've been driving around it for three months. Your neighbor hit it last week and bent a rim.

Everyone on the block knows about it. The mail carrier knows about it. The delivery drivers know about it. You know who doesn't know about it? The people in charge of fixing it.

This is how most cities work. The people with the most information about a problem have no way to act on it. The people with the power to act have no way to get the information. Both sides spin their wheels. Nothing happens. The pothole gets worse.

Here's the same problem, run two different ways.

The way it works now

Way One: You're a complaint, not a resource.

You call the city. Or you find the app. You file a report. A complaint number gets assigned. It goes into a queue with every other complaint in the city.

Somewhere downtown, someone looks at the queue. They weigh your pothole against every other pothole. They schedule a crew. The crew has a full calendar. Your pothole isn't urgent enough to jump the line, so it waits.

When the crew finally comes, they fill the hole. Maybe they fix it well. Maybe they patch it quick because they have twelve more stops. Six weeks later, the patch fails. The pothole is back. You file another complaint. The clock starts over.

Nobody who fixed it knows why it keeps coming back. Nobody who knows why it keeps coming back had any say in how it was fixed.

You were useful to this system exactly once — when you filed the complaint. After that, you were just waiting.

A different way it could work

Way Two: You're an expert, not a problem.

You report the pothole in an app. You take a photo. You note that it's been there since February and that it keeps coming back in the same spot after every repair.

The app shows you three other reports from the same intersection. It asks: same hole? You confirm. The reports get combined.

A neighborhood group — people who live there, who've agreed to take responsibility for this block's small repairs — reviews it. They recognize the pattern. They know there's a drainage problem underneath that's been ignored for years. They flag it.

The city allocates a portion of the road budget to that neighborhood group. The group decides: this one is worth doing right. They post the job publicly — city crews and local contractors can both bid. Someone who actually lives nearby takes the job. The fix addresses the drainage. The whole thing — report, decision, contract, payment — is public record.

A year later, when a city planner is looking at drainage problems across the district, that record is sitting there. It connects to five other records from five other blocks. A pattern emerges that nobody could see when the complaints were sitting in separate queues.

Your knowledge didn't get filed. It got used.

In Way One, the city needs your complaint.
In Way Two, the city needs your knowledge.
Those are completely different systems.

Why it matters beyond potholes

One system gets more efficient at processing complaints. The other gets smarter over time.

Apply that to schools. To housing. To transit. To who gets hired and for what. To how money gets spent. Every decision a city makes that affects the people who live there can be run like Way One or like Way Two. Most are currently run like Way One — not because the people running them are corrupt or lazy, but because Way One is the template. It's what managing a city is supposed to look like.

The template is the problem. Not the people following it.

What gets captured and what gets built

There's a useful question to ask about any system: does it capture or does it build?

A system that captures takes something from you — your time, your knowledge, your energy — and converts it into something useful for the system. Your complaint becomes a data point. Your vote becomes a mandate. Your tax dollar becomes a budget line. You gave something real. The system used it for its own purposes. You don't get it back.

A system that builds takes what you offer and makes it larger. Your knowledge combines with your neighbor's knowledge. The combination produces something neither of you had alone. It stays visible. It compounds. The more people contribute, the more useful it becomes for everyone who contributes.

Way One captures. Way Two builds.

Most of what we interact with every day captures. Your attention, your behavior, your social connections — platforms take these things and turn them into money. The anger you feel scrolling through the news isn't an accident. It's the product. You're not the customer. You're the raw material.

But here's the thing that gets missed: building is also happening, all the time. Neighbors sharing information about a dangerous intersection. Parents coordinating pickup schedules. A block association tracking which houses are vacant. A community garden where everyone knows what's growing and what's needed.

None of that gets headlines. None of it has a stock price. But it's the reason cities function at all. The people closest to the problems are quietly holding things together — mostly without credit, mostly without resources, mostly without a way to connect their knowledge to the decisions that affect them.

Way Two isn't a fantasy. It's just what building looks like, taken seriously.

The question isn't whether this is possible

Open source software has worked this way for decades. Thousands of strangers, spread across the world, with different goals and different abilities, building something together — something more reliable and more useful than anything any one company or government could have built alone.

They didn't do it by agreeing on everything. They did it by building a system where contributions stay visible, where mistakes are part of the record, where the people closest to a problem have real power to fix it.

That's not ideology. It's engineering. And it works.

The same logic applies to cities. The knowledge is already there — in the people who live in them, who fix things informally, who see what's broken and why. The question is whether that knowledge gets captured and filed away, or whether it gets built into something that lasts.

Right now, it mostly gets filed.

That's a choice. It can be made differently.

Back to all pieces Next: Open Data Isn't Enough

Part of a series on how power works and what people can do about it.