The Problem With Treating Citizens as Users

Public institutions have clearly been taking notes from Silicon Valley. Government websites now greet you with login screens that feel lifted from social media. Civic portals track engagement like a startup obsessing over daily active users. City services ping your phone the way a grocery app announces a flash sale. On the surface, it reads like progress—a digital-first state that meets people where they are. But tucked beneath the convenience is a quiet shift in language and logic, and that shift rewires the whole relationship. When a government starts calling a citizen a user, it isn’t just swapping out a word. It’s redrawing the contract between the individual and the state.

The Seduction of User-Centered Government

The impulse to treat citizens as users springs from a generous place. Public agencies watch the private sector spin up frictionless experiences and they want to bring that same relief to renewing a driver’s license or applying for food assistance. User-centered design has honestly made government services better. Paper forms have turned into online wizards. Phone trees have bowed to chatbots. The UK’s Government Digital Service, for example, reimagined hundreds of services around the real journeys people take, which saved a mountain of time and frustration. That labor is genuine, and it counts.

Still, there’s a snare hidden inside the word user. In tech, a user is somebody who consumes a product. The whole connection is transactional. The platform hands over a service, and the user takes it—usually in trade for data, attention, or cash. The user’s job is to navigate choices that somebody else already framed. If a button confuses people, you A/B test it. If they bail, you tweak the flow. The aim is to make the experience slick enough that the user keeps using, keeps sticking around, keeps converting.

When that mindset spreads to civic life, something foundational begins to corrode. A citizen is not a consumer of government. A citizen is a co-owner. The democratic relationship isn’t about pulling out value; it’s about sharing power. When you’re a user, you’ve got preferences. When you’re a citizen, you’ve got rights—and duties that stretch way past clicking “I agree.”

When Participation Becomes a Funnel

One of the sharpest consequences of the user frame is how it remolds public participation. Picture a city that rolls out an online portal for residents to weigh in on a new zoning plan. The designers, schooled in user experience, naturally think about cutting friction. They craft a clean interface, write cheerful prompts, maybe even toss in a progress bar. The goal is to get as many people as possible to finish the survey.

But democracy is not a conversion funnel. A towering response rate doesn’t show whether people grasped the trade-offs, whether marginalized voices got picked up, or whether the process built any residue of trust. In fact, optimizing for ease can actively eat away at democratic depth. Real deliberation is slow, knotty, and sometimes awkward. It means bumping into views you disagree with, sitting inside complexity, and recognizing that your personal preference might not win the day. A frictionless interface can scrub away all of that texture, leaving a hollow ritual of clicking and rating.

Worse, the user model tends to squeeze collective action into individual transactions. You report a pothole, you rate your experience at the DMV, you sign up for a newsletter. Each action floats disconnected from the rest. There’s no space for the kind of organizing that turns a cluster of pothole complaints into a sustained push for budget reform. The system sees you as a solo node, not as part of a public.

The Data Trade-Off Nobody Debated

Underneath every user-centric government service sits an architecture that harvests data. That data can be used to polish services, absolutely. But it also builds a profile of you that the state didn’t possess before. In the private sector, we’ve grown numb to the bargain: you get a free email account, and in return the company scans your messages to serve ads. So what’s the bargain when the provider is the government?

There’s no equivalent of a terms-of-service pop-up for citizenship. You can’t opt out of dealing with the state without forfeiting basic rights and protections. When a public agency treats you as a user, it begins to see your data as an asset—something to gather, analyze, and maybe pass around across departments. The logic of personalization, so seductive in retail, turns queasy in civic settings. Should your browsing history on a government health portal color how a caseworker judges your eligibility? Should your pattern of interactions with the Department of Motor Vehicles feed a predictive algorithm for tax audits?

These aren’t thought experiments. Governments across the globe already lean on data analytics to flag fraud, dish out resources, and rank enforcement priorities. The hitch isn’t that data gets used; it’s that the user frame makes these practices feel natural and unstoppable. When you’re a user, you expect the platform to learn from what you do. When you’re a citizen, you should expect the state to justify its intrusions through public argument and law, not through a silent tweak to a privacy policy you’ll never crack open.

Accountability Without a Face

Maybe the most corrosive gift of the user paradigm is how it scatters accountability. In a functioning democracy, there’s a line—however snarled—between a decision and the official who owned it. You can vote someone out, show up at a town hall, file an appeal. But when government presents itself as a platform, that line smears. Decisions get made by “the system.” Errors are glitches. Injustices become bugs.

I’ve watched people try to fight automated decisions about their benefits or their immigration status, and they smack into a wall that’s both digital and bureaucratic. The computer says no, and the human on the phone says they can’t override the computer. Who’s accountable? The software vendor? The product manager? The agency head? The political appointee who signed the procurement contract three administrations ago? The user model trains us to swallow this opacity. Apps crash. Algorithms are opaque. We shrug and hit refresh.

But citizenship asks for something different. It asks that power be findable. It asks that the people who exercise authority on our behalf be reachable, answerable, and removable. A government that treats you as a user is a government that can duck behind a loading spinner.

The Language We Need

None of this argues that governments should ditch digital tools or quit caring about people’s experiences. It argues we need a richer set of words. Instead of user, we might talk about participants, members, or just people. Instead of user journeys, we might map civic pathways—routes that hold not only transactions but also deliberation, protest, volunteering, and voting. The design aims would tilt from ease and retention toward dignity and agency.

This isn’t wordplay. Language carries whole worldviews. When the UK’s National Health Service began calling patients “customers,” it quietly shifted expectations on both sides of the counter. Patients started demanding satisfaction instead of care; administrators started measuring throughput instead of health. The same dynamic works with user, only harder, because it drags along an entire ideology of optimization and control.

Reclaiming the Public in Public Services

There are places where the user frame has been shoved back. Participatory budgeting efforts, for instance, often launch from the idea that residents are decision-makers, not consumers. They use technology to open up collective deliberation, not just individual input. The best of these projects treat digital tools as supplements to in-person assemblies, not stand-ins for them. They grasp that a vote on a spending proposal is fundamentally different from a star rating on an app store.

Another model shows up in how some European cities handle digital identity. Estonia’s e-residency program, beneath all its tech-forward shine, rests on a base of consent and control. Citizens can see every time a government official peeks at their data. There’s a transparency log, not just a privacy policy. The design assumes the person has a stake in steering the system, not just riding it.

These examples gesture toward a different kind of digital state—one erected on the logic of citizenship instead of the logic of platforms. It would prize explainability over seamlessness. It would pour as much investment into public deliberation as into user research. It would treat data as a shared resource to be governed together, not as raw material to be mined.

What’s at Stake

The choice between citizen and user isn’t just a philosophical parlor game. It shapes who gets heard, who gets left out, and who gets to decide. When you’re a user, your voice counts only as far as it helps the system serve you better. When you’re a citizen, your voice is the system. That distinction is the floor under self-government. Lose it, and you lose the ability to tell a public service from a product—a right from a feature request.

I worry we’re sleepwalking toward a future where the state knows every twitch of our behavior but feels zero duty to explain its own. Where participation gets measured in clicks, not in collective muscle. Where accountability is a ticket number that never closes. Reversing that slide doesn’t demand smashing the servers. It demands remembering, and insisting, that we’re not here to use the government. We are the government. And that’s a relationship no user agreement can hold.

Frequently Asked Questions

What is the difference between a citizen and a user in the context of government services?

A citizen is a co-owner of the state, with rights, responsibilities, and a role in collective decision-making. A user, in the tech sense, is a consumer of a product or service, whose primary relationship is transactional. When governments adopt the user frame, they risk reducing civic participation to individual transactions and obscuring the shared power that defines democracy.

Can digital government services still respect citizenship?

Absolutely. The key is to design with civic dignity, not just convenience. This means building systems that are transparent about data use, that provide meaningful avenues for deliberation and appeal, and that treat people as participants rather than passive consumers. Technology can enhance citizenship when it supports accountability, accessibility, and collective action.

Why does the language of “user” matter so much?

Language shapes how institutions see people and how people see themselves. Calling someone a user brings with it a whole set of assumptions about optimization, data extraction, and individual satisfaction. These assumptions can quietly override the principles of due process, public accountability, and shared governance that are essential to a democratic society.

How can ordinary people push back against being treated as users by the state?

It starts with asking questions: Who decided this process? Where does my data go? Can I appeal an automated decision? Supporting local initiatives that emphasize participatory democracy, attending public meetings, and demanding transparency from elected officials all help shift the culture. The goal is not to reject digital tools but to insist that they serve citizenship rather than replace it.