A city launches a 311 app so residents can report potholes. A neighboring city builds its own. A county contracts with a vendor for a third. Each system works, after a fashion, but none can talk to the others. A resident who lives in one jurisdiction and commutes through two more must learn three tools. The data each one collects stays locked inside the system that captured it.

This fragmentation is one of civic technology's quietest problems. It inflates costs, because every government pays to solve the same problem from scratch. It limits choice, because switching vendors means abandoning data. And it constrains innovation, because no outside developer can build something useful across a landscape of incompatible formats.

Technical standards are the usual answer. They are shared specifications that let systems exchange information predictably. But standards are not neutral plumbing. They encode decisions about what matters, who decides, and whose needs count. Understanding why some succeed and most stall means looking at three things together: the benefits standards unlock, the politics built into their design, and the barriers that keep good specifications on the shelf.

Interoperability Benefits: Why Shared Formats Change the Economics

The clearest success story in civic data standards began with a transit agency and a search company. In 2005, Portland's TriMet worked with Google to publish schedules in a simple format later known as the General Transit Feed Specification, or GTFS. The idea was modest: a set of plain text files describing stops, routes, and timetables. Today, thousands of agencies worldwide publish GTFS feeds. Riders can plan trips in dozens of apps without any agency having built one.

That outcome illustrates the first benefit: cost reduction through shared infrastructure. When every agency publishes in the same format, a tool built once serves everyone. Validators, visualization tools, and analysis software become public goods rather than bespoke projects. Smaller jurisdictions rarely have budgets for custom development, yet they gain capabilities once reserved for large cities. Each additional adopter costs the ecosystem almost nothing.

The second benefit is choice. Standards loosen vendor lock-in by making data portable. A government whose records follow a common specification can change providers without a costly migration. That credible threat of exit tends to discipline pricing and service quality. For residents, choice means picking the interface that suits them. It might be a mainstream app, an accessibility-focused tool, or a text-message service built by a local nonprofit.

The third benefit is permissionless innovation. Open311, a standard for reporting non-emergency service requests, allowed developers to build reporting tools that worked across participating cities without negotiating separate integrations. The Open Contracting Data Standard lets journalists and auditors compare procurement patterns across agencies. In each case, the standard made building something new cheap enough that people outside government could contribute. The value came from combinations no single institution planned.

Takeaway

A standard's value lies less in any single implementation than in what it lets strangers build. Interoperability turns isolated systems into an ecosystem where the next useful tool can come from anywhere.

Standards Politics: The Value Choices Hidden in Specifications

It is tempting to treat standards as engineering problems with correct answers. In practice, every specification is a set of choices about what to record and how. Which fields are required, and which are optional? What categories are permitted? Those decisions determine what becomes visible, comparable, and actionable. They also determine what quietly falls out of view.

Consider restaurant inspection data. When Yelp worked with cities including San Francisco to create the LIVES standard, the goal was to display hygiene scores alongside reviews. But jurisdictions grade inspections differently. Some use letter grades, others pass-fail systems, others numerical scores. Any common format must decide whether to normalize those differences or preserve them. Normalizing aids comparison but can misrepresent local practice. Preserving them protects nuance but weakens the point of standardizing at all.

Power shapes these choices through who sits at the table. Standards bodies tend to be dominated by actors with the resources to participate: large vendors, well-funded cities, and major technology platforms. Their priorities become the defaults. A dominant platform may favor fields that serve its product, and vendors may push specifications that match their existing architectures. Residents, community organizations, and small jurisdictions are often absent. They are rarely excluded outright, but participation demands time and expertise they lack.

Governance matters as much as content. Google stewarded GTFS closely in its early years, and broader community governance came later through the nonprofit MobilityData. Open Referral's Human Services Data Specification grew through a deliberately participatory process involving service providers and referral networks. These different paths produce different kinds of legitimacy. A standard seen as one company's format invites suspicion. One built through visible, inclusive deliberation earns trust that eases adoption. How a standard is made becomes part of what it is.

Takeaway

Every data field is a small policy decision. Asking who defined a standard, and who was absent, reveals as much as reading the specification itself.

Adoption Barriers: Why Good Standards Stay on the Shelf

If standards deliver such benefits, why do so many go unused? Civic technology is full of well-designed specifications that a handful of pioneers adopted and everyone else ignored. Technical quality is rarely the deciding factor. The barriers are economic, institutional, and organizational.

The core problem is a collective action dilemma. Adopting a standard imposes immediate costs on the agency: reformatting data, modifying systems, and training staff. The benefits mostly go to others, such as developers, neighboring jurisdictions, and future users. With few adopters, a standard offers little value, so each agency rationally waits for others to move first. Legacy systems make this worse. Many governments run software that cannot export data in new formats without expensive vendor modifications.

Incentives also cut in uncomfortable directions. Some vendors benefit from proprietary formats that make switching painful. Some agencies worry that comparable data invites unflattering comparisons. Procurement cycles lasting years mean that even willing governments may be locked into contracts written before a standard existed. And standards that try to capture everything often become too complex for under-resourced teams to implement.

Successful efforts tend to share a few strategies. They secure an anchor consumer, as Google Maps did for GTFS, giving agencies a visible reason to publish. They start minimal and expand later, keeping the first implementation easy. They write requirements into procurement language, so compliance arrives with new contracts rather than as an extra project. And they invest in free validators, documentation, and peer networks, which lighten the load on the agencies least able to carry it. Adoption is less a technical milestone than a coordination achievement.

Takeaway

Standards succeed when someone makes adoption immediately worthwhile for the adopter. Designing the incentives deserves as much attention as designing the specification.

Interoperability standards hold an unusual place in civic technology. Residents rarely see them, yet they determine whether digital public services form a connected ecosystem or a patchwork of isolated tools.

Three principles follow from this analysis. Standards should be judged by the ecosystem they enable, not the elegance of their schema. Their design should be treated as governance, with deliberate attention to whose interests shape the defaults. And adoption should be planned as carefully as the specification, with incentives that reward early movers rather than penalize them.

For practitioners, the implication is clear. The most consequential civic technology work may happen in working groups and procurement documents rather than in apps. Quietly negotiated shared agreements are what let public technology scale.