Key Insights

• •

  Civic Tech work is not just implementation; it must influence policymaking for real impact.

• •

  The Boston school selection project revealed how policy assumptions (e.g., walking distance) need revising based on implementation feedback.

• •

  Traditional government projects often lack timely feedback loops between policy writers and implementers, leading to failures.

• •

  Healthcare.gov’s failure catalyzed the creation of the U.S. Digital Service and a new model focused on agile, collaborative development.

• •

  Long-term embedding of designers and technologists in government enables deeper learning and more effective change.

• •

  Many career public servants do user research unofficially but need permission and training to do it effectively.

• •

  Low trust in government systems causes users, such as doctors interacting with CMS portals, to feel frustrated and opt out.

• •

  Successful Civic Tech requires partnerships that blend technology, policy, and frontline user understanding.

• •

  Private sector frameworks like Customer Experience (CX) may not fully apply to public services without adaptation.

• •

  Community support and strong relationships are essential for sustaining Civic Tech efforts within challenging government environments.

Notable Quotes