Advertise on podcast: Civic Tech Chat

Ryan Koch explores the parallels between historical railroad gauge conflicts and modern data infrastructure challenges, emphasizing the importance of standardization and network effects in overcoming systemic friction. Key Topics Historical railroad gauge conflicts and their modern parallelsThe role of standardization and network effects in overcoming systemic frictionThe challenges of web scraping and data integration across states and agenciesThe concept of coordination traps and how to overcome themCase studies including GTFS, health data, and railroad gauge changesChapters 00:00 Introduction: What Railroad Gauges Teach Us About Data Infrastructure02:00 Historical Overview of Railroad Gauges in America03:55 The Economics and Politics Behind Gauge Choices05:52 Coordination Traps and the Power of Standardization07:03 The Webcomic XKCD and the Universality of Standards08:11 Modern Data Challenges: Inconsistent APIs and Data Shapes10:02 Web Scraping and the Complexity of State Data Portals11:57 The Risks and Frustrations of Maintaining Web Scrapers12:55 The Incentive Structures in Data Standardization15:11 The Erie Gauge War and Its Lessons on Local Resistance17:06 Health Data and the Monopoly of Epic Systems19:59 The 1886 Gauge Change in the American South21:51 The Emergence of GTFS and Its Impact on Transit Data23:49 Network Effects and the Power of Standardization26:00 Identifying Your Own Hoisting Machines and Frictions27:58 Strategies for Overcoming Systemic Friction29:52 The Moral of the Railroad and Data Standardization Stories31:13 Conclusion: Moving Forward with Awareness and Cooperation Music credit: Tumbleweeds by Monkey Warhol

Summary When H.R. 1 put new pressure on states to cut SNAP payment error rates, Nava PBC had six weeks to help Pennsylvania stand up a way to catch bad document uploads before they reached a caseworker. That rapid-response build became Document AI, an open-source service that checks whether an uploaded document is legible and the right type, then extracts key fields for review. Product manager Sophia Philip and senior software engineer Laurence Goolsby of Nava Labs join Ryan to talk about the project, which has since been adapted for a Maryland pilot that's set to scale statewide by December. They cover: - Why the tool is deliberately kept out of eligibility decisions, with no policy coded into it- How applicants can opt in, opt out, or proceed anyway when a document is flagged- How it handles gig-work and handwritten invoices, plus Spanish-language documents- Why a confidence score is not the same as accuracy- How they're approaching AWS dependence and data security- How other agencies can fork the repo and adapt it to their own needs This episode is sponsored by Nava PBC. Keywords Document AI, intelligent document processing, Nava PBC, Nava Labs, open source, SNAP, H.R. 1, payment error rates, Maryland, Pennsylvania, benefits delivery, administrative burden, human-in-the-loop, consent, Amazon Bedrock, government technology, civic tech Key Topics - How AI-assisted prototyping ("demos over memos") is changing collaboration between product and engineering- Document processing as a shared problem across benefits, licensing, permits, and more- Building a six-week rapid response to H.R. 1 in Pennsylvania, then adapting it for Maryland- Why open source: avoiding vendor lock-in while keeping PII inside each agency's environment- The three users: applicants, caseworkers, and the people who administer the service- Consent that is plain-language, just-in-time, and reversible- Supporting nonstandard documents like handwritten invoices from gig and informal work- Guarding against caseworker over-reliance: confidence scores, and no determinations made by the tool- Under the hood: Amazon Bedrock and Bedrock Data Automation, plain-language document schemas, and Textract- Meeting states on the infrastructure they already use, and the path to being cloud-agnostic- Security by default: data that never leaves the agency, and extracted values that aren't returned unless requested- How to contribute, deploy, or request demo access Sound Bites - "Confidence does not mean accuracy."- "Fundamentals are the building blocks of fun."- "Document AI isn't making any decisions about whether the document should be uploaded. That lives with the person who's uploading it."- "It's not the person who uploads it's fault that we haven't defined it."- "You are not in a vacuum." Chapters 00:00 Intro  00:21 Meet Sophia Philip and Laurence Goolsby of Nava Labs  00:49 Their personal "why"  02:16 What's changed, and what hasn't, in product management and engineering  05:59 How AI prototyping changes collaboration across practices  08:33 Why document processing is a problem worth solving  12:38 Designing around burdens imposed by policy, and building reversible consent  15:15 What is Document AI?  16:26 Origin story: a six-week rapid response to H.R. 1 in Pennsylvania  20:10 Did it move payment error rates?  21:21 What "open source" means here, and why it matters  24:25 The three user personas  26:23 The applicant experience and opt-out fallback  28:41 The caseworker experience, gig-work invoices, and multilingual documents  33:26 Avoiding rubber-stamping: human-in-the-loop and no automated determinations  37:36 Shaping the product vision, from Postman demos to a management layer  41:32 Handling surprises: agile delivery and the Maryland pilot timeline  46:04 Under the hood: how Document AI uses AI  50:12 Why confidence isn't accuracy  51:13 Unsupported languages and undefined document types  54:07 AWS dependence and the path to cloud-agnostic  58:39 Security, privacy, and keeping data inside the agency  1:01:37 Governing Document AI after adoption  1:02:26 How to contribute  1:04:10 Final takeaways Links - Document AI open-source GitHub repository- Nava demo day

Rebecca Woodbury and Luke Fretwell discuss their collaborative process in writing 'Proudly Serving,' a book aimed at making civic tech and government more accessible, responsive, and effective. They share insights on open source principles, the importance of plain language, and fostering a culture of transparency and public service. The Book: https://proudlyservingbook.com Key Topics The origin story of civic tech and government responsivenessThe collaborative process of writing 'Proudly Serving' with over thirty contributorsThe importance of working in the open and transparency in government projectsThe role of plain language in improving government communicationThe concept of everyone being a public servant and fostering collective responsibilityThe challenges and lessons learned in remote, asynchronous collaborationThe significance of guiding principles and shared values in public organizationsStrategies for balancing innovation with accountability in civic techChapters  00:00 Introduction to Civic Tech and Public Service00:22 Rebecca's Origin Story in Civic Tech04:04 Luke's Path to Civic Tech and Digital Government07:06 Personal Why: Making Government Better08:03 The Inspiration Behind 'Proudly Serving'12:29 Target Audience for the Book16:05 Writing the Book Like an Open Source Project19:23 Collaborative Process and Contributor Engagement23:40 Design and Accessibility in the Book26:45 Working Remotely and Asynchronously33:57 Chapter Review and Quality Gates40:12 Reflections on Personal Challenges and Growth42:14 Plain Language and Clear Communication47:31 Everyone as a Public Servant55:36 Living Up to the 'Why' in Civic Tech01:00:37 Key Message: Default to Open and Say Yes01:02:51 How to Access the Book and Final Thoughts

AI tools have quietly moved out of isolated dev environments and into the middle of how real work gets done. That shift is genuinely exciting, and it brings a fresh set of risks worth sitting with. In this solo episode, Ryan works through what it takes to govern AI well, all of it anchored on one idea he keeps coming back to: a human has to stay accountable for the decisions that matter. He gets into why AI strains the governance habits IT already leans on, how to weigh centralized, decentralized, and hybrid approaches against your own risk tolerance, what ISO 42001 and the NIST AI RMF actually ask of you, and where the law is heading. He closes with a practical playbook for pulling shadow AI into the open while keeping the room for creativity that made folks reach for these tools in the first place. In this episode Why AI puts pressure on the governance habits IT already has, from non-determinism to data drift and concept drift, and the blind spots those quietly createSplitting your governance model (who holds the decision rights) from your operating model (how the work actually gets run)The three big archetypes: the fortress-style centralized model, the fast and messy decentralized model, and the hybrid in between, plus how to match one to your risk tolerance and threat modelA few examples from Ryan's own teams — engineers getting their bearings in old repos in about twenty minutes instead of a full day, designers prototyping fast enough to have a richer discovery conversationWhat ISO 42001 and the NIST AI Risk Management Framework actually require, including named human owners and a real kill switchThe principle the whole episode hangs on: an AI tool can't be the one held accountable, since a machine isn't a legal or moral agentWhere regulation is going, including EU GDPR Article 22, California's coming CCPA automated-decision rules, EU NIS2, and a White House executive order on AI and national securityThe frontier-developer laws worth knowing about even if they never regulate you directlyWhy these efforts stall out, and a grounded playbook: sanctioned tools folks will actually use, a living AI inventory, cross-functional discovery, and metrics anchored in real valueKey takeaways Lower the barrier to secure tools so people stop quietly routing around youKeep a human clearly accountable on every RACI chartGet real value to real people fast, then learn from how they actually use the toolsTreat the AI in your stack as something to govern, not just something you installedResources and shoutouts ISO/IEC 42001, the AI management system standardNIST AI Risk Management FrameworkEU GDPR, Article 22 (solely automated decisions)California's CCPA automated decision-making technology (ADMT) rules, enforced by the CPPA, in effect Jan 1, 2027EU NIS2 DirectiveCalifornia's frontier-model transparency law, plus the state's AI content-transparency and watermarking rulesThe June 2026 White House executive order on AI and national securityRelated episodes: SpecOps → https://civictech.chat/episodes/the-specops-method AI Readiness with Brian Chidester of Adobe → https://civictech.chat/episodes/what-is-ai-readinessLegacy Lockpicks with David D'Silva of Nava, the one that ran just ahead of this → https://civictech.chat/episodes/legacy-lockpicksMusic credit: Tumbleweeds by Monkey Warhol

We're joined by David D'Silva, Principal Product Manager at Nava, for a conversation about legacy lockpicks: the reusable tools, playbooks, and patterns that help government teams move out of legacy systems faster and with less risk. We talk about why trust is the real currency of modernization work, why so many efforts stall at the data layer, and how to choose between patterns like strangler fig and lift and shift. We also dig into where AI is genuinely useful in modernization today and where it's mostly hype. - David’s LinkedIn: https://www.linkedin.com/in/daviddsilva/ - Prior episode on Strata: https://civictech.chat/episodes/nava-strata-open-source-government-technology - Strata page: https://www.navapbc.com/strata - Legacy modernization page: https://www.navapbc.com/legacy-modernization - Our prior episode covering the strangler fig pattern: https://civictech.chat/episodes/the-specops-method

In this interview, Brian Chidester from Adobe discusses the importance of AI readiness in government, data governance, and the future of AI in public sector transformation. Learn how organizations can start small, build trust, and leverage AI to improve citizen services and drive mission outcomes. Music Credit: Tumbleweeds by Monkey Warhol

Christian Martinez shares his journey from cognitive neuroscience to civic tech, highlighting the importance of open data, reproducible research, and building accessible tools like R packages. Discover how relevance drives rigor in education and data projects, and learn practical tips for getting started with open data and open source development. Resources and ShoutoutsNYC Open Data Portal: https://opendata.cityofnewyork.us/ NYS Open Data Portal (MTA data also lives here): https://data.ny.gov/ NYC Open Data Student Gallery Book: https://martinezc1-nyc-open-data-student-gallery.share.connect.posit.cloud/ Music Credit: Tumbleweeds by Monkey Warhol

Ryan Koch discusses the importance of understanding supply chain attacks in cybersecurity, illustrating how they exploit trust in software components and build systems, and offering practical strategies to mitigate these risks. Resources and Shoutouts:- GRC Engineering Presentation by AJ Yawn: https://engage.isaca.org/events/event-description?CalendarEventKey=bd0c09c0-662f-4fe8-a0d2-019adaab6cc4&Home=%2fevents%2fcalendar

We're joined by Mark Headd author The SpecOps Method: A New Approach to Modernizing Legacy Technology Systems. We talk about good modernization practices like the strangler fig pattern as well as ways teams can use artificial intelligence to develop specifications that can be understood and validated across both technical and programmatic teams.  Music Credit: Tumbleweeds by Monkey Warhol

We’re joined by Ed Mullen, Technical Solutions Director and Lauren Ciferri Director of Product, over at Nava PBC. We’ll have a conversation about open source government technology, using Nava’s Strata project as a key example. The chat will dive into importance of open source in the space, maintaining projects like this one, and how one can get involved. Resources and shoutouts: Email EdEmail LaurenNava’s StrataNava Strata GithubContributing to Nava StrataMusic Credit: Tumbleweeds by Monkey Warhol

We're joined by Mike Paciello (https://www.linkedin.com/in/mike-paciello-1231741/), Chief Accessibility Officer at AudioEye (https://audioeye.com) for a conversation about web accessibility standards. We'll talk about upcoming deadlines for local and state governments, foundational principles, and what goes into establishing and updating standards. Resources and shoutouts: - Civic Plus (www.civicplus.com) - US Access Board (https://www.access-board.gov/) - ADA Fact Sheet (https://www.ada.gov/resources/2024-03-08-web-rule/) ##### Music Credit: Tumbleweeds by Monkey Warhol

Our host Ryan Koch talks about the Dutch Government's invocation of the 1952 Good Availablity Act. This action recently led to what's been referred to as the 'Nexperia Crises' creating a scenario where technical hardware manufacturing, supply chains, and geopolitics collided. ##### Music Credit: Tumbleweeds by Monkey Warhol Join us on Discord: https://discord.gg/hECzBJh

We’re joined by Senongo Akpem (https://www.linkedin.com/in/senongoakpem/) Vice President of Design and Research at Nava PBC (https://navapbc.com/). Together we talk about shifts in the direction of the design and research practice, innovative practices to build capacity and leadership within it, and its future as new tools like artificial intelligence emerge and become part of it. Resources and shoutouts: Cross-Cultural Design (Book by Senongo) | https://bookshop.org/p/books/cross-cultural-design-senongo-akpem/7700a228f8e33947 Plain Language with Indiana DWD | https://www.in.gov/mph/files/DataDayPresentation-Plain-Language_v3-Comp.pdf Music Credit: Tumbleweeds by Monkey Warhol

We're joined by Amanda Renteria (https://codeforamerica.org/people/amanda-renteria/) CEO of Code for America (https://codeforamerica.org). We dive into a conversation about what's needed to make 'good' government forms and we let you know about a neat event coming up on 9/30/2025 called FormFest(https://formfest.org/). Register for the event here: https://formfest.org/register/ . Music Credit: Tumbleweeds by Monkey Warhol

We're joined by Brett Ferrin (https://www.linkedin.com/in/brett-ferrin-8504b8346/) VP of Sales at Traffic Logix. Together we have a conversation about how technology and data can be used to proactively improve traffic safety. If you're into data, urban planning, or transportation, this is an episode for you. Resources and Shoutouts: - Traffic Logix: https://trafficlogix.com/ - Vision Zero: https://www.cdc.gov/transportation-safety/vision-zero/index.html Music Credit: Tumbleweeds by Monkey Warhol