MinuteRead
30 min
Loading…
In the fall of 2013, the United States government launched a website that was supposed to let millions of Americans buy health insurance. It cost hundreds of millions of dollars to build. It had been planned for years. It was the centerpiece of the most significant domestic policy achievement in a generation.
**Author:** Jennifer Pahlka **Estimated Reading Time:** 45 minutes
**What You'll Learn:** Why government technology projects fail so consistently, how decades of policy choices created a system that cannot deliver digital services effectively, and what it will take to rebuild the government's capacity to serve people in the digital age.
**Who This Book Is For:** Public servants frustrated by broken systems, technologists who want to understand why government seems immune to modern practices, policymakers who want their laws to actually work, and citizens who have ever wondered why interacting with government feels so much harder than ordering a pizza.
In the fall of 2013, the United States government launched a website that was supposed to let millions of Americans buy health insurance. It cost hundreds of millions of dollars to build. It had been planned for years. It was the centerpiece of the most significant domestic policy achievement in a generation. It crashed on day one. And day two. And for weeks after. The healthcare.gov disaster became a national punchline. Late-night comedians mocked it. Pundits blamed contractors. The Obama administration scrambled to assemble a team of Silicon Valley engineers who worked around the clock to stabilize the site. Eventually, it worked. But the damage was done. What most people missed was that healthcare.gov was not an anomaly. It was a symptom. Jennifer Pahlka has spent her career trying to understand why government struggles so profoundly with technology. She founded Code for America, a nonprofit that brings tech industry talent into government. She served as the U.S. Deputy Chief Technology Officer under President Obama. She has worked inside agencies, alongside career civil servants, and with political appointees. What she discovered is that the problem is not lazy bureaucrats or greedy contractors. The problem is structural. It is cultural. It is the accumulated weight of decades of policies that were designed for a different era. Government does not fail at technology because it lacks smart people. It fails because the entire system is organized around assumptions that no longer hold true. The government treats software as a thing you buy, like paper clips or filing cabinets. But software is not a thing. Software is a process. It is made by people, for people, and it must be maintained and adapted by people who understand it. The consequences are not abstract. When the pandemic hit in 2020, unemployment insurance systems across the country buckled under the surge of claims. Millions of Americans waited weeks or months for benefits they desperately needed. In California, the Employment Development Department was still processing claims on a system built in the 1980s, running on COBOL, a programming language most young engineers have never learned. The state had known…
Continue reading in the MinuteRead app
Get the complete 30-minute summary of Recoding America
Get the complete summary in the appGovernment technology failures are structural, not personal. The system is designed to produce them.
The Kodak Curse: outsourcing core technical functions leads to permanent loss of capability.
Waterfall development guarantees outdated, unusable systems. Agile development delivers value sooner and adapts to user
Bureaucracy is the result of deliberate policy choices, not just incompetence. Both parties contributed.
User-centered design starts with the needs of the people who will use the service. Simple is better.
Government needs product managers, not just project managers. The question "what problem are we trying to solve?" must c
"Recoding America" is a strong fit if you want practical ideas around politics, technology, government, especially themes like government technology failures are structural, not personal. the system is designed to produce them; the kodak curse: outsourcing core technical functions leads to permanent loss of capability. The MinuteRead summary distills these concepts into a focused read, whether you're deciding whether to buy the book or applying its lessons at work.
Jennifer Pahlka is the founder of Code for America and served as the U.S. Deputy Chief Technology Officer under President Obama. With extensive experience in both the tech industry and government, she brings a unique perspective to the challenges of implementing digital solutions in the public sector. Pahlka's work focuses on improving government services through technology and user-centered design. She is known for her efforts to bridge the gap between policymakers and implementers, advocating …
View all summaries by Jennifer PahlkaContinue Reading
Access the complete 30-minute summary and thousands more nonfiction books in the MinuteRead app.
Continue reading the complete summary in the MinuteRead app.
