Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Fireside chat with Sarah Brooks and Jen Pahlka
Summary
For our second gathering of the Civic Design Community, we’ll learn from Jennifer Pahlka, founder and former Executive Director of Code for America who served. as US Deputy Chief Technology Officer from June 2013 to June 2014 and helped found the United States Digital Service. We’ll explore the importance of designers inside and outside government moving upstream to work alongside policymakers to make alliances and push back when needed to strengthen conditions for designers and digital technologists to do work that delivers improved outcomes for residents and citizens.
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
"I was largely wrong about how we thought technology and design would just implement policy."
"People implementing policy see the problems with the policy long before anyone else does."
"The policy was about walking distance as the crow flies, but that wasn’t walkable—so the policy needed to change."
"In traditional government projects, policy writers are often gone long before implementations fail or need revising."
"Healthcare.gov was a blow, but it opened the door to new ways to work in government technology."
"If leaders tell me to build a concrete boat, I will build a concrete boat—and that’s damaging to government."
"Designing a service is really designing a new relationship between government and people, who come with enormous baggage."
"User research in government is often done without knowing what it’s called, and people aren’t always empowered to do it."
"We need to push back when we see the concrete boat coming, but it’s really hard to know how."
"Community and ‘the phone a friend’ are what get you through the hardest parts of working in government."
Or choose a question:
More Videos
"Some of the most important decisions for service design happen on whiteboards among engineers, often without service design representation."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"I felt on edge and physically depleted after our interactions."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"One of the biggest challenges is balancing freedom for creative work with necessary consistency and governance, as Dave Kronin pointed out."
Dave GrayGroup Activity: Making Sense of DesignOps
November 7, 2017
"Executives only like things in threes, but if you do a three by three, you can get away with nine boxes—that's the max executive information processing."
John CutlerThe Alignment Trap
November 29, 2023
"Just because you can color code something doesn’t mean you should."
Abby CovertStuck? Diagrams Help
October 27, 2022
"We started to build an API for how other teams could interact with us like a contract."
Mark InterranteCollaboration Flows in Product Development
June 9, 2017
"We can’t just think technology or innovation will solve our problems; we have to embrace and work with those problems."
Devon PowersImagining Better Futures
March 9, 2022
"Share your learning quickly and often—don’t wait for big reports. Your deliverable as a designer doing research is the design itself."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"Don’t overcomplicate workflows; the simplest thing that could possibly work is often best."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
