Why Government Services Are Built to Frustrate Citizens

A father spends his lunch break renewing his child's school registration. He uploads the same birth certificate he uploaded last year, answers three questions the system already has the answers to, gets bounced to a payment page that doesn't recognise his card, and ends the transaction at a counter he was told he wouldn't need to visit. None of this is a technology failure. It's a design choice, made somewhere upstream, by someone who never had to live with it.

That's the thing about friction in government services: it's rarely an accident. It's inherited. Every extra document, every repeated field, every "please visit your nearest centre" is a decision someone made — usually to protect a process, satisfy an audit, or avoid a risk — and that decision outlives the person who made it. The fix isn't a slicker portal. It's treating friction as a variable you deliberately design, measure and remove, the same way a private-sector team treats checkout abandonment or cart drop-off.

Reducing friction in public-sector journeys means identifying every point where a citizen must supply effort, information, or waiting time the service doesn't actually need, and re-engineering the process — not just the interface — to remove it. Some of that effort is unavoidable and even necessary for due process. Most of it isn't. The job of citizen experience work is telling the two apart.

What does friction actually cost in public services?

In the private sector, friction shows up as abandoned carts and churn — visible, measurable, tied to revenue. In government, the same friction shows up as missed appointments, unclaimed benefits, non-compliance, and a slow, corrosive loss of trust that rarely gets attributed to its actual cause. A citizen who gives up on renewing a permit doesn't file a complaint about the nineteen-field form. They just don't renew it, or they pay a fine, or they show up angry at a counter for something that could have been fixed online in April.

The UK's Behavioural Insights Team demonstrated how directly this plays out when it worked with HM Courts & Tribunals Service on reducing missed court appearances. A simple, personalised text reminder — replacing a generic notice — measurably reduced no-shows, because it lowered the cognitive effort required to act rather than relying on citizens to remember, plan and follow through unaided. The Behavioural Insights Team built an entire practice on this insight: most compliance failures in public services aren't defiance, they're friction wearing a disguise.

That reframing matters. If non-compliance is friction rather than attitude, the fix is process redesign, not more enforcement. Public-sector leaders who treat low take-up of a benefit or service as an awareness problem end up running expensive campaigns to tell people about a process still too painful to complete. The campaign spends the budget the redesign should have had.

Why do government journeys accumulate more friction than private-sector ones?

Government services carry a structural disadvantage private companies don't: they are built by process owners, not journey owners. A passport renewal touches immigration, payments, biometrics, sometimes police clearance, sometimes a separate courier service — each with its own system, its own legal basis for collecting data, and its own department head who did not design the other three steps. The citizen experiences one journey. The organisation runs four unconnected processes and hands the coordination cost to the person least equipped to carry it.

Private companies eventually get punished for this by the market — a bank that makes onboarding painful loses the customer to a competitor. Public services often have no competitor, no exit option, and no revenue signal tied to convenience. Friction can persist for a decade because the people paying for it (citizens, in wasted time) are not the people who'd have to approve the fix (department budgets, measured on their own KPIs, not the citizen's total effort).

This is why service design work in the public sector has to start above the department, not inside it. You cannot fix a journey by improving one agency's step in isolation; you have to map the full citizen journey across every organisation it touches, because that's the only unit at which friction is actually visible.

What's the difference between friction and sludge?

Not all friction is neutral. Cass Sunstein, in his book Sludge: What Stops Us from Getting Things Done and What to Do about It (MIT Press, 2021), draws a sharp distinction that public-sector teams should adopt as policy language, not just theory. Friction is unavoidable effort a process requires; sludge is excess friction that serves no legitimate purpose — the extra form, the redundant verification step, the appointment that could have been a form, the requirement to appear in person to submit a document that could be uploaded. Some friction is deliberate and correct: identity verification before releasing a pension, a cooling-off period before a major benefit decision, a witness requirement for a legal change of guardianship. That's friction functioning as a safeguard — behavioural economists call this a productive "ordeal," a deliberate cost imposed to filter for genuine need or prevent hasty error. Sludge has no such justification. It exists because removing it was never anyone's job.

The practical value of this distinction is that it gives public-sector teams permission to say no to friction without sounding like they're cutting corners on due process. "We're removing sludge, not safeguards" is a defensible position in a room full of risk officers. "We're making things easier" is not — it invites the question "easier for whom, and at what risk?"

How should a team audit friction before redesigning a journey?

Journey redesign in government fails most often when it starts with the interface instead of the process. A prettier form on top of an unnecessary requirement is still an unnecessary requirement. The audit has to come first, and it has to be structured enough to survive scrutiny from legal, security and finance stakeholders who will each defend their piece of the friction as essential.

1. Map the full journey end to end, across every department and channel it touches — not just the piece one team owns. Build it as a proper customer journey map with stages, steps and touchpoints, so hidden handoffs between agencies become visible rather than assumed away.
2. Log every data request and document the citizen must supply, and ask a single question of each one: does government already hold this information somewhere? Repeated data entry is the single most common form of sludge in public services, and it is almost always solvable through integration rather than through asking the citizen to be the human API between two databases.
3. Classify every step as productive friction, sludge, or unclear. Force a decision on the "unclear" category rather than letting it default to "keep it" — that default is exactly how sludge survives audit after audit.
4. Time and count each step: minutes required, number of visits, number of documents, number of distinct systems logged into. These numbers, not satisfaction scores, are what justify budget for redesign to a finance committee.
5. Identify the exit points — where citizens abandon, get referred elsewhere, or resort to an intermediary (an agent, a broker, a relative who "knows how these things work"). A thriving informal economy of fixers around a public service is the clearest possible signal that the official journey has too much friction.
6. Pilot the removal, not the redesign. Cut one document requirement, remove one verification step, eliminate one in-person visit — and measure the effect before rebuilding the whole journey. Public-sector change is expensive to reverse; small, measured removals build the evidence base for bigger ones.

This is where a formal CX maturity assessment earns its keep — it tells you whether the organisation even has the governance, data-sharing agreements and measurement discipline to sustain friction removal, or whether the redesign will quietly re-accumulate sludge within eighteen months because nobody owns the journey after launch.

Which behavioural levers reduce friction without weakening safeguards?

Three behavioural mechanisms do most of the useful work here, and none of them require new legislation or new systems — they require better defaults.

• Smart defaults. Choice architecture research consistently shows that whatever option requires no action from the citizen is the option most people end up with — not because they prefer it, but because acting requires effort and most people are running on System 1, fast and default-seeking, rather than System 2, deliberate and effortful. Auto-enrolling eligible citizens into a benefit, with an easy opt-out, converts take-up from an active-effort problem into a passive one. Requiring active application for the same benefit does the opposite.
• Loss aversion, used honestly. Citizens respond more strongly to the threat of losing something they already have than to the promise of gaining something new — a bias documented by Daniel Kahneman and Amos Tversky in their foundational work on prospect theory. A renewal notice framed as "your registration expires in 14 days and access will be suspended" drives more action than one framed as "renew now to keep your benefits active," even though the substance is identical. Used well, this reframing helps citizens avoid genuine harm. Used badly — manufacturing false urgency to mask a broken process — it curdles into the kind of manipulative design regulators are increasingly scrutinising.
• Reducing choice at the point of highest anxiety. Citizens facing an unfamiliar bureaucratic process — a first-time benefit claim, a bereavement notification, a business licence application — are in an anxious, effortful cognitive state. This is the wrong moment to present branching menus and optional pathways. It's the right moment for a single, guided default route, with complexity available only for the minority who genuinely need it.

These are the same behavioural levers a well-run behavioural economics practice would apply to a bank's onboarding flow or a retailer's checkout. Government services aren't behaviourally different from commercial ones — citizens carry the same biases into a passport office as they do into a supermarket. What differs is the stakes of getting the intervention wrong, which is exactly why it has to be done deliberately rather than borrowed from a growth-hacking playbook.

What happens when you remove too much friction?

This is where public-sector teams have to hold a line the private sector rarely worries about. Removing friction to make fraud, error or abuse easier is not a service improvement — it's a liability transferred from the citizen's time to the public purse and, eventually, back to the citizen in the form of tighter controls imposed after something goes wrong. The 2021 collapse of the UK's Bounce Back Loan Scheme fraud controls is the cautionary tale every public-sector CX lead should know, even without quoting a specific figure: a scheme designed with minimal friction to get emergency funds to businesses quickly during a crisis also became, by design, easy to exploit, because speed and verification were treated as opposites rather than as a design problem to solve together.

The discipline this demands is straightforward to state and hard to execute: distinguish friction that protects the citizen or the public purse from friction that exists purely because removing it was inconvenient. An identity check before releasing a pension payment is not sludge — it's a safeguard with a clear beneficiary. A requirement to submit the same proof of address for the third time to a different department within the same ministry has no beneficiary at all. Every friction-removal decision should be able to name, specifically, who the friction was protecting before it gets cut. If the answer is "no one, really," it's sludge, and it should go.

What does a genuinely low-friction citizen journey look like?

The reference points worth studying aren't abstractions. The UK's Government Digital Service set out design principles in 2012 — still published today as Government Design Principles on gov.uk — built around "do the hard work to make it simple," a mandate that puts the burden of complexity on the institution rather than the citizen. That single reframing, institutionalised rather than left as a slogan, is arguably GDS's most durable contribution to public-sector design: it made simplicity a design KPI rather than a nice-to-have.

Estonia's digital identity infrastructure achieves something similar through architecture rather than interface: because most government data is connected through a shared exchange layer, citizens are rarely asked to resubmit information the state already holds, and most administrative interactions can be completed without a single office visit. The lesson isn't "go digital" — plenty of digitised services are still full of sludge, just sludge with a nicer font. The lesson is that friction reduction that lasts is usually a data and governance decision before it's a design decision.

The OECD's Digital Government Index, published by the OECD in 2023, frames digital maturity in public administrations around exactly this point: the leading governments are the ones that treat data-sharing, once-only registration, and cross-agency journey ownership as the infrastructure of good service, not an optional layer on top of it. That's the difference between a portal and a journey.

How does friction removal actually get sustained, not just launched?

Most public-sector friction-removal projects work at launch and decay within two years, because the governance that removed the sludge in the first place doesn't survive the reorganisation that follows. Sustaining it requires the same discipline as any operating model change:

• Name a journey owner who outranks any single department's process owner, with the authority to force a cross-agency fix rather than escalate it into a committee that meets quarterly.
• Put friction metrics on the same dashboard as compliance metrics — minutes to complete, number of visits, abandonment rate — so a risk officer defending a document requirement has to defend it against a visible cost, not an invisible one.
• Build a re-audit into the calendar, not just the launch. Sludge regrows quietly, one "temporary" verification step at a time, usually added after a single high-profile incident and never removed once the panic passes.
• Give citizens a way to flag friction directly, and treat that feedback with the same seriousness as an audit finding, through a structured feedback management discipline rather than an occasional satisfaction survey.

Structured this way, a CX implementation roadmap for a government journey looks less like a digital transformation project and more like a standing operating discipline — closer to how a finance department runs a budget cycle than how a typical IT project runs a launch and moves on.

Where this leaves public-sector leaders

The uncomfortable truth is that most public-sector friction survives not because removing it is hard, but because no one owns the discomfort of the citizen who has to absorb it. Fix the ownership question — put someone's name against the total effort a journey demands, not just its individual steps — and the technical fixes turn out to be the easy part.

Renascence works with public-service organisations across the region on exactly this problem: mapping the full citizen experience across public services, separating productive friction from sludge, and building the governance that keeps a redesigned journey simple after the launch team has moved on. If you want a sense of how mature your organisation's journeys currently are, the CX Maturity Assessment is a useful starting point — and a candid one, which is usually the point where the real work begins.