Small city innovation tends to work when a modest team picks a narrow problem, shares data openly, borrows tools from peers and builds on volunteer help. Large budgets matter less than commitment and shared practice, according to published research on city data programmes.
Readers interested in one local case can start with the guide to Elyria Ohio, which places these ideas in a specific city.
Why smaller cities face a different innovation problem
Most writing about civic technology comes from big metropolitan areas with dedicated innovation offices, large IT departments and philanthropic attention. A smaller city has the same duties, from permits and water bills to street repair and public safety, but fewer staff to spread across them. A technology project in that setting competes directly with daily operations for the same few people.
The funders behind well-known city programmes have said as much. When the Brookings Institution published an interview about the launch of Bloomberg Philanthropies What Works Cities, the initiative was described as pledging $42 million to target 100 mid-sized cities, with populations between 100 thousand and 1 million. The same interview, dated May 2015, explained the reasoning: America’s mid-sized cities typically have little support to help them enhance how they use data and evidence. If that holds for cities of that size, the gap is wider still below them.
The practical conclusion is that a small city rarely wins by copying a large city’s innovation office. It wins by choosing a few projects that fit its capacity, and by using outside help that is free or already built.
Commitment beats size
A research paper by staff of What Works Cities and Results for America, posted as a preprint on arXiv, studied 67 cities that had gone through the programme’s discovery process. Its central finding was that a city’s stated commitment to using data is the strongest predictor of overall performance. Leadership intent, rather than headcount or budget, carried the most weight in that sample.
The same paper reports one exception that matters to small places. Larger cities were more adept at adopting open data policies and programmes, independent of their performance using data overall. In other words, a small city can be strong at using data internally and still lag on publishing it, because releasing datasets takes sustained effort that a thin staff may not have. The sample was made up of applicant cities, so it describes cities that wanted to take part rather than every city in the country.
For a town council or city manager, the lesson is concrete. Naming a data owner, writing down a few goals and reviewing progress at a regular meeting are inexpensive steps that match what the research ties to stronger performance.
Borrowing a framework instead of inventing one
Small cities do not need to design a measurement framework from scratch. Bloomberg Philanthropies launched What Works Cities in 2015. Its about page dates the recognition side to 2017, describing it as celebrating local governments for their exceptional use of data to inform policy decisions, allocate funding, improve services and evaluate programmes.
The entry point is deliberately light. According to the programme’s certification page, the first step is completing the Data Snapshot, a short questionnaire that provides cities with an initial benchmark of their data practices. Certification is then awarded in tiers. Cities that achieve between 51% and 67% of the Certification criteria are recognized at the Silver level, and cities that achieve 85% or more are recognized at the Platinum level.
The underlying Standard is broad. A page of leading examples, dated March 30, 2026, says the Standard has 43 criteria under eight foundational practices. A small city does not have to meet them all at once. Used as a checklist, the criteria show which habits to build first, such as keeping a data inventory, protecting resident privacy and measuring whether a programme worked.

Volunteers and peer networks as extra capacity
Where staff time is the limit, outside talent can help. In an announcement dated August 30, 2018, Code for America described Brigades as local networks of technologists, community leaders and local officials passionate about using technology to help government work for people, and said its network had grown from 3 to 77 Brigades and from an initial group of under 100 volunteers to 25,000 people, techies and non-techies alike.
A 2017 Q&A published in Route Fifty shows what that can mean for one city. In the interview dated August 16, 2017, the chief innovation officer of the Municipality of Anchorage said he first learned about civic tech and Code for America in June 2012 during the inaugural Anchorage Hackathon. The same piece describes a network of 85 cities using data and evidence at that date.
The founder of Code for America, speaking in that interview, made the capacity argument directly: no local government has the capacity to do everything they could do for their citizens, especially in the tech and data realm. Her answer was to treat local residents with technical skills as part of the city’s capacity, not as outsiders. A hackathon, a volunteer night or a student project can be a low-cost way to start that relationship, as long as the city agrees in advance who owns the result and who maintains it.
What tends to work in practice
Pulling the sources together gives a short list of patterns that smaller places can reasonably follow. These are editorial conclusions drawn from the published material above, not guarantees.
- Start with one visible service. A single resident-facing improvement, such as a clearer request form or a simple dashboard, builds trust and shows whether the team can deliver.
- Write down the commitment. The research on city data practice points to stated commitment as the strongest predictor of performance, so a short public statement and a named owner are worth the effort.
- Reuse before building. Free frameworks, shared datasets and open tools from peer cities save staff time that a small team cannot spare.
- Treat volunteers as partners. Agree on scope, data access and maintenance before a project starts, so that work does not stall when volunteers move on.
- Measure and publish simply. Even a small set of tracked indicators lets a city tell whether a change helped.
Infrastructure sets the ceiling for all of this. Services that depend on residents going online assume reliable access, which is why the guide to Ohio broadband is a useful companion to any discussion of digital projects in small Ohio places.
Lessons from the pandemic years
Remote work, online meetings and digital service delivery moved from optional to routine for many local governments during the pandemic, and smaller cities had to adapt with the staff they already had. The ideas that surfaced then, from open dashboards to virtual public meetings, are collected in the guide to post-pandemic cities, which looks at how data and technology can support recovery.
The common thread across both periods is that small cities progress through steady habits rather than one large launch. A modest, well-scoped project that is finished and maintained does more for residents’ trust than an ambitious platform that outruns the staff available to run it.
Frequently asked questions
Can a small city really run a data programme without a big budget?
The published research suggests budget is not the deciding factor. The arXiv paper on What Works Cities found that a city’s stated commitment to using data was the strongest predictor of overall performance, and the programme’s Data Snapshot is a short questionnaire rather than a large project.
What was a Code for America Brigade?
Brigades were volunteer chapters of the Code for America network, and in the network announcement cited above the organization said they included non-technical participants as well as developers and designers. Code for America later wrote that it had decided to sunset the Brigade program, ending its fiscal sponsorship of volunteer brigades; some local civic-tech groups continue independently, so readers should check what is active locally.
Why is open data harder for smaller places?
The arXiv analysis found that larger cities were more adept at adopting open data policies and programmes. Publishing data on a regular schedule needs staff time for cleaning, documenting and updating files, which is scarce in a small administration.
Is this guide connected to any city or programme?
No. It is an independent editorial guide that summarises public sources and has no affiliation with any city, government, programme or organisation named in it.
