Open Data Isn't Enough

A few years ago, cities got very excited about open data. They built portals. They published spreadsheets. They hired open data coordinators and held hackathons and gave TED talks about government transparency.

Some of it was genuinely useful. Some of it still is.

But here's what happened in most cities: the data went up. Journalists and researchers dug into it. Occasionally a story ran. Occasionally a council member expressed concern. The underlying thing the data revealed — the pattern of neglect, the inequity in service delivery, the money flowing to the same contractors year after year — mostly continued.

The data was visible. The decisions weren't touched.

This isn't a mystery. It's the difference between being able to see a system and being able to change it.

Seeing is not the same as doing

Imagine you can watch every move in a chess game — but you're not one of the players. You can see the bad moves. You can see the strategy unfolding. You might even be able to predict what happens next. But you can't touch the board.

That's what transparency without participation looks like. You get information. You don't get agency.

Open data, at its best, gives citizens a clearer view of the board. That's not nothing — a clearer view is better than a foggy one, and it can create political pressure that eventually moves things. But pressure from outside a system is much weaker than participation inside it. A city that publishes its pothole data but routes all repair decisions through a central department hasn't changed who controls the board. It's just let you watch more closely.

The question open data doesn't answer

Every dataset has a question baked into it that most people don't think to ask: who decides what gets done with this?

Your city publishes response times for service requests. Great. Who decides whether slow response times in certain neighborhoods get addressed? Not you. The data shows the problem. The decision about whether to fix it belongs to someone else.

Your city publishes building permit records. Useful. Who decides whether a pattern of permits in a neighborhood signals something worth investigating? A planner, maybe. A journalist if you're lucky. You get to read about it afterward.

Your city publishes budget expenditures. Informative. Who decides how next year's money gets allocated? The council, with input from departments, shaped by lobbyists and longtime relationships and the political cost of changing anything. The spreadsheet you downloaded doesn't vote.

The data shows you what's happening. The routing architecture determines what happens next. Open data reforms the first part. It mostly leaves the second part alone.

What open actually means

In software, "open" means something more specific than "visible." Open source code isn't just code you can read. It's code you can run, modify, and improve. The openness isn't just about transparency — it's about participation. Anyone can find a bug. Anyone can propose a fix. Anyone can build on what exists.

That's a fundamentally different relationship to information than publishing a dataset and hoping someone writes a story about it.

The difference isn't cosmetic. A system where citizens can contribute information — not just consume it — produces different data. It captures things the official systems miss: the flooding that happens at 2am and drains before anyone from the city arrives, the harassment that goes unreported because the reporting process is itself intimidating, the informal economy that keeps a neighborhood running but never appears in any official count.

And a system where some decisions belong to the people with direct knowledge — not just advisory input, but real authority over defined things — produces different outcomes. Not always better ones. But different ones, informed by people who actually have to live with the consequences.

Who benefits from transparency theater

There's a reason most open data reforms stop at visibility and don't touch participation.

Visibility is cheap to provide and hard to act on. Publishing a dataset costs relatively little. It generates goodwill. It satisfies reformers who can point to it as progress. And crucially, it doesn't change who makes decisions. The people currently controlling those decisions — department heads, longtime contractors, council members with established relationships — don't have to give anything up.

Real participation costs something. It means sharing authority. It means some decisions getting made differently than they would have been. It means established interests competing with people who previously had no seat at the table. That's why it's rare, and why it usually requires sustained pressure to achieve — not just a hackathon and a data portal launch.

The routing question

Every system has a routing architecture — a set of rules about what connects to what, who can do what, where things go after they happen. Content flows through that architecture. The architecture shapes everything content can do.

Open data changes the content. You can see more. You know more. But if the routing stays the same — if all decisions still travel the same channels, get made by the same people, run through the same processes — the content you can now see will mostly produce the same outcomes it always has, just with better documentation.

The harder, more important work is changing the routing. Which decisions get made where. Who has authority over what. How local knowledge actually reaches the people responsible for acting on it. How communities build track records that earn them real authority over things that directly affect them.

That's not a data problem. That's a power problem. And data, however open, doesn't solve it on its own.