Have you ever tried to renew your driver’s license online, apply for a permit, or navigate a state unemployment website?

If you have, I’m willing to bet my morning coffee that you wanted to throw your laptop out a window.

For years, I assumed the government was just cheap. I figured they hired bad coders or bought bargain-bin servers. I couldn’t understand how a company like Netflix could stream millions of 4K movies simultaneously without a glitch, yet my local city portal crashed if three people tried to pay a parking ticket at the same time.

It was baffling. It was infuriating. And frankly, it made me lose faith in our public systems.

Then, I picked up Power to the Public: The Promise of Public Interest Technology by Tara Dawson McGuinness and Hana Schank.

Reading this book felt like sitting down with a couple of incredibly smart, empathetic friends who finally handed me the decoder ring to the universe of government failure. They completely shattered my assumptions. They showed me that the problem isn’t broken code (though if you want to explore how tech systems can go off the rails in other sectors, you might enjoy our summary of Broken Code); the problem is broken processes.

They introduced me to a quiet revolution called “Public Interest Technology,” and let me tell you, it completely changed how I view the future of our public systems.

Why Should You Even Bother Reading It?

You might be thinking, “I’m not a software engineer, and I don’t work in politics. Why should I care about public interest technology?”

Here’s the honest truth: you should care because you are a user of these systems. We all are.

Whether you’re paying taxes, looking up zoning laws, or trying to access public health data during a crisis, your life is directly impacted by how well the government delivers its services. This book isn’t a dry technical manual filled with coding jargon. It’s a deeply human, incredibly hopeful playbook about solving real-world problems.

If you are a curious citizen, a designer, a non-profit worker, or just someone who is tired of seeing billion-dollar public projects fail, this book will give you hope. It proves that we can actually fix things.

The Core Framework That Rescued Healthcare.gov (And Can Fix Any System)

When massive government initiatives fail, it’s rarely because the underlying policy was ill-intentioned; it’s almost always because the execution was profoundly out of touch with reality. The authors of this book spent years studying the spectacular crashes and quiet triumphs of public projects to isolate the specific principles that actually drive success.

1. Human-Centered Design (Not Just Pretty Buttons)

Imagine hiring an architect to design a state-of-the-art, million-dollar commercial kitchen.

The architect builds it with gleaming stainless steel, touch-screen ovens, and beautiful ambient lighting. But there’s a massive problem: they never actually spoke to a chef. When the restaurant opens, the chefs realize the sinks are too far from the stoves, the aisles are too narrow for two people to pass, and the touch-screens don’t work when your fingers are wet.

The kitchen is beautiful, but it is entirely useless.

This, the authors explain, is how the government typically builds systems. They lock a bunch of lawyers and bureaucrats in a room to write policies, then they hand a checklist to IT contractors. They never once talk to the single mother trying to apply for food stamps, or the overloaded social worker trying to navigate a foster care database.

Human-centered design flips this completely upside down. It demands that before a single line of code is written, you must go sit with the actual human beings who will use the system. You watch them struggle. You listen to their frustrations. (If you want to explore the foundational principles of this approach, you might appreciate our summary of Change by Design).

A great real-world example from the book involves programs like WIC (a food assistance program for women, infants, and children). For years, mothers felt humiliated at the grocery store checkout line because the payment process was clunky, complicated, and drew unwanted attention. By actually observing these mothers, public interest technologists realized they didn’t need a fancier database; they needed an app that let them discreetly scan barcodes in the aisles to know exactly what items were approved before they got to the register.

Design isn’t about making a website look pretty. It’s about designing a system that respects the dignity and reality of the user.

Simple Terms: Build tools based on how real people actually behave, not how you assume they should behave.
The Takeaway: If you don’t talk directly to the end-users before you build a solution, you are virtually guaranteed to build the wrong thing.

2. Data as a Flashlight, Not a Report Card

Think about how you navigate a dark, unfamiliar room. You don’t take a guess at where the furniture is, run full speed across the room, and then grade yourself a “D-minus” when you smash your shin into the coffee table.

Instead, you turn on a flashlight. You use that beam of light to take one step at a time, adjusting your path as you get new information about your surroundings.

For decades, the government has used data like a report card. They launch a massive, multi-year program, wait three years to see what happens, and then publish a 500-page PDF report detailing exactly how and why the program failed. By the time the data is analyzed, it’s completely useless. The money is spent, and the people are still suffering.

Power to the Public argues passionately for using data as a flashlight. It’s about real-time feedback loops.

Take a modern tool like a Roomba vacuum. It doesn’t have a pre-programmed map of your house. It bumps into a chair, realizes there’s an obstacle, records that data point, and instantly adjusts its path. Governments need to act more like a Roomba.

A prime example is how Spotify uses data for its “Discover Weekly” playlists. Spotify doesn’t send you an annual survey asking what genres you like; they watch what you actually skip and what you actually replay in real-time to adjust your feed. When governments start using small, real-time data metrics to see if a policy is actually helping people week-by-week, they can pivot before millions of dollars are wasted.

Simple Terms: Use data to constantly steer your decisions in real-time, rather than using it to judge your failures after the fact.
The Takeaway: Data is only valuable if it is collected fast enough and clearly enough to help you change course before a project crashes.

3. Delivery: The End of “Waterfall” Planning

Imagine you are hired to bake a towering, intricate, six-tier wedding cake for a high-profile client.

Using the traditional government method, you would spend two years planning the cake. You’d write a 400-page document detailing the exact chemical composition of the flour, the precise Pantone color of the frosting, and the structural integrity of the tiers. Then, you’d spend three weeks baking the massive cake all at once. When you finally serve it, you discover the bride is allergic to gluten and the cake tastes like wet cardboard.

This is called “Waterfall” project management. It requires knowing every single requirement up front, building the whole thing in secret, and launching it in one giant, terrifying “Big Bang.”

📖 “We have separated the making of policy from the delivering of policy, and in doing so, we have broken government.”

The authors point to the infamous 2013 launch of Healthcare.gov as the ultimate casualty of Waterfall planning. The government spent hundreds of millions of dollars and years of planning to launch a massive website all at once. When millions of people logged on, the entire system instantly collapsed.

The heroes who flew in to save Healthcare.gov didn’t use Waterfall; they used Agile methodology. They built a cupcake first. They fixed the login page. Then they tested it. Then they fixed the database connection. Then they tested it.

They built the system piece by piece, testing it with real users at every single step. In the world of public interest tech, delivering small, working pieces quickly is infinitely better than delivering a massive, broken system years too late.

Simple Terms: Build small things, test them immediately, fix your mistakes, and then build the next small thing.
The Takeaway: Massive, multi-year “Big Bang” tech launches are almost always doomed to fail; progress must be made in small, testable increments.

4. The “Tech-Washing” Trap

Imagine you own a 1995 Honda Civic with a blown engine, four flat tires, and a family of raccoons living in the backseat.

You desperately want a better driving experience. So, what do you do? You buy a $2,000 top-of-the-line touchscreen stereo system and bolt it into the dashboard. Does it make the car drive any better? Of course not. You just put a shiny digital band-aid on a fundamental mechanical failure.

This is what McGuinness and Schank call “Tech-Washing.”

Tech-washing happens when politicians or agency leaders believe that buying an expensive, cutting-edge piece of software will magically fix deeply broken human processes. They hear buzzwords like “Artificial Intelligence,” “Blockchain,” or “Machine Learning” and assume these tools are magic wands.

The authors share chilling examples of this. Imagine a city spending millions on an advanced predictive AI algorithm to manage a broken parole system. The AI might perfectly predict who is likely to miss a parole hearing, but it completely ignores why they are missing it (like a lack of reliable public transit or conflicting work schedules).

Technology cannot fix bad policy. If your underlying rules are contradictory, confusing, or needlessly cruel, digitizing them will only make them contradictory, confusing, and cruel at the speed of light.

Before you buy the shiny new software, you have to do the messy, difficult human work of fixing the underlying process.

Simple Terms: Slapping fancy new software over a broken, confusing process will only result in a broken, confusing digital process.
The Takeaway: Technology is just an amplifier; it will only magnify the efficiency of a good process, or the chaos of a bad one.

5. Policy and Implementation Are the Same Thing

Picture an incredibly talented architect who sits in a glass office drafting blueprints for a magnificent 50-story skyscraper. The blueprints are flawless. The physics are perfect.

But when the blueprints are handed to the construction workers on the ground, the workers look around and realize they only have access to wood, duct tape, and Elmer’s glue. The architect’s brilliant vision is completely useless because it is totally disconnected from the reality of the materials and the builders.

In government, we have a terrible habit of treating “Policy” (the architect) and “Implementation” (the builders) as two completely separate universes.

Politicians will sit in a legislative chamber and pass a sweeping, highly complex unemployment relief bill over a weekend. They celebrate, hold a press conference, and declare the problem solved. But they have no idea that the actual state computers responsible for sending out those checks are running on a 1970s programming language called COBOL.

📖 “When technology is treated as a magic wand, the results are almost always disastrous. The real magic happens when we change how we solve problems.”

The book hammers home the idea that a policy is only as good as its delivery. If a law entitles a veteran to healthcare, but the website to apply for it takes three hours to navigate and crashes constantly, then the veteran does not have healthcare.

The implementation is the policy. Public Interest Technology demands that the people writing the laws and the engineers building the websites must sit in the same room, from day one, to ensure the grand vision can actually survive contact with reality.

Simple Terms: A brilliant law or policy is completely worthless if the technology required to deliver it doesn’t actually work.
The Takeaway: You can no longer separate the people who write the rules from the people who build the tech; they must work together as one cohesive unit.

My Final Thoughts

Reading Power to the Public was an incredibly validating experience. It took my vague, simmering frustrations with government bureaucracy and gave me a crystal-clear vocabulary to explain exactly why things are broken.

But more importantly, it left me feeling incredibly optimistic. We aren’t doomed to live in a world of spinning loading wheels and crashing portals forever. If you are tired of administrative headaches and unnecessary corporate clutter, you might find some useful strategies in our summary of The Ministry of Common Sense. There is a growing army of public interest technologists out there – designers, data scientists, and empathetic civil servants – who are quietly rebuilding our civic infrastructure from the inside out.

They are proving that government can actually work for the people it serves. It just takes a little less focus on shiny new tech, and a lot more focus on the humans using it.

Join the Conversation!

I’d love to hear from you! What is the absolute worst experience you’ve ever had with a government website or public service? Looking back on it now, do you think it was a failure of technology, or a failure of human-centered design? Drop your stories in the comments below!

Frequently Asked Questions (The stuff you’re probably wondering)

1. Do I need to know how to code to understand this book?
Not at all! There is zero code in this book. The authors focus entirely on project management, human behavior, design thinking, and policy. It’s written for everyday people, not software engineers.

2. Is the book just bashing the government?
Actually, it’s quite the opposite. While it honestly critiques how systems fail, it is incredibly sympathetic to the civil servants trapped inside bad processes. It’s a highly optimistic book filled with stories of incredible turnarounds and dedicated government workers saving the day.

3. Who is the ideal reader for this book?
Anyone who works in the public sector, non-profits, or policy. However, if you are a project manager, a UX designer, or a business leader who struggles with getting large teams to deliver successful products, the frameworks in this book will blow your mind.

4. What does “Public Interest Technology” actually mean?
It’s a relatively new field that combines technology, data, and design with public policy. It focuses on using tech tools to solve societal problems, protect human rights, and deliver equitable government services to everyone.

5. Will reading this help me in the private sector?
Absolutely. The lessons on avoiding the “Waterfall” trap, stopping “Tech-Washing,” and focusing relentlessly on human-centered design are directly applicable to building a startup, managing a corporate team, or launching a new commercial product.