Six Lessons from Neighborhood Civic Tech
Cross-cutting lessons from the documented wins: phone-first beats app-first, paper is part of the stack, pay local stewards, small apps remix best, subtract friction before adding features, and measure relational outcomes.
Six patterns recur across this shelf's stories, each earned somewhere specific:
- Phone-first beats app-first. Bed-Stuy Strong's intake was a Google Voice number, deliberately — 'if we were depending on an app or online form submissions we would miss a huge swath of people in need,' as a fellow COVID network's engineer put it. The neighbors who most need the tool are least likely to install it.
- Paper and doorsteps are part of the stack. E-Democracy's Twin Cities forums became inclusive through 129 in-person outreach events, door-knocking in ten languages, and three thousand paper sign-ups. Front Porch Forum started as paper flyers. 596 Acres zip-tied signs to lot fences. If the stack has no offline layer, it has a class filter.
- Pay local stewards. Red Hook's mesh network and Detroit's Equitable Internet Initiative both survived because trained neighborhood residents were *paid* to build and maintain them. Infrastructure that must persist can't run on volunteer enthusiasm alone.
- Small, single-relationship apps remix best. Adopt-a-Hydrant encoded one relationship — 'this civic object is mine to care for' — and was re-skinned within months for sirens and storm drains. Big platforms spread only when a local institution adopts them.
- Subtract friction from existing rights before adding features. Chicago's Large Lots reduced a byzantine city land-purchase process to a one-page application — and blocks bought over a thousand lots. The highest-leverage build is often a deletion.
- Measure relational outcomes. Front Porch Forum's 13,000-user study (more informed, more likely to volunteer and talk with neighbors) and Large Lots' crime findings (biggest drops when *near neighbors* bought the lots) are the proof pattern: the question is never 'did people use the tool' — it's 'do neighbors know each other better because of it.'
Details
- lessons: phone-first, paper in the stack, pay local stewards, small apps remix best, subtract friction, measure relational outcomes
- practice kind: framework
-
Build prompt
Build: A Front-Porch Digest for One Block
A starter build: fork Front Porch Forum's constitution, not its code — real names, one geography, one email a day, a rotating…
-
Build prompt
Build: A Living Asset Map
A starter build bridging both new shelves: an asset-based community development map where the assets are neighbors' own declared gifts,…
-
Build prompt
Build: A Third-Places Map for Your Neighborhood
A starter build: a local Ushahidi — neighbors collectively map the porches, stoops, cafés, courts, and corners where the neighborhood…
-
Build prompt
Build: Adopt-a-Thing for Your Block
A starter build: the Adopt-a-Hydrant pattern, remixed — a map of small civic objects (tree wells, storm drains, benches, little libraries)…
-
Build prompt
Build: Participatory Budgeting for a Very Small Budget
A starter build: run real participatory budgeting on a block association's actual money — propose, develop, vote, do — sized so the whole…
Contributed by Relational Technology Project · Synthesized from the documented stories on this shelf
See something to fix or add? Suggest an edit on GitHub — the commons lives in git too, and its history is the changelog.
local-civic-techcivic-tech-frameworkdesign-lessonsequity