Reducing Friction in Public-Sector Service Journeys

Most government services are not broken because of bad intentions. They are broken because friction has been designed in — often accidentally, sometimes structurally — and nobody with authority has been asked to remove it. The citizen who gives up on a benefits application halfway through, the small-business owner who abandons a licence renewal because the portal times out, the elderly resident who cannot complete an identity verification without assistance: these are not edge cases. They are the ordinary cost of public services that were built for administrative convenience rather than human use.

Reducing friction in public-sector journeys is not a digital project. It is not a communications project. It is a service-design discipline that requires understanding why friction accumulates, where it does the most damage, and what it actually takes to remove it — permanently, not just for the pilot cohort.

The short answer: Friction in public-sector journeys accumulates at three structural points — identity and eligibility verification, document submission, and status uncertainty. Removing it requires mapping the citizen's actual journey (not the process flowchart), applying behavioural principles to reduce cognitive load, and building feedback loops that catch new friction before it calcifies into policy.

Why public-sector friction is structurally different from commercial friction

In a commercial context, friction costs a business revenue. That signal is fast and legible: conversion drops, churn rises, and a product team gets a mandate to fix it. In government, the signal is slower and the incentive structure is inverted. A citizen who gives up on a service application does not take their business elsewhere — they simply go without the service, or they call a helpline, or they turn up in person. The cost lands on the citizen, not visibly on the department's performance metrics.

This is what Richard Thaler and Cass Sunstein, in their foundational work on choice architecture, would call sludge — friction that is not accidental but that persists because the organisation bearing the cost of removing it is not the one experiencing the pain of keeping it. Sludge in government is particularly durable because the feedback loop between citizen suffering and institutional response is long, indirect, and often mediated by political rather than operational priorities.

There is a second structural difference: compulsory use. A citizen applying for a driving licence, a planning permission, or a social welfare payment cannot choose a competitor. This removes the market pressure that forces commercial services to improve. The result, over time, is that public-sector journeys accumulate procedural requirements that would be commercially suicidal elsewhere — repeated identity checks, mandatory paper submissions for processes that are otherwise digital, eligibility assessments that ask the same question three times across three different forms.

Understanding this structural context matters because it shapes the intervention. You cannot fix public-sector friction with a UX refresh alone. You need to change the incentive structure, the measurement framework, and — most importantly — whose perspective the journey is designed from.

Where friction actually lives: the three structural pressure points

After working across government services in the MENA region and beyond, the friction does not distribute evenly. It concentrates at three points with remarkable consistency.

1. Identity and eligibility verification

The first and most damaging friction point is the requirement to prove who you are and whether you qualify — repeatedly, across channels, often with documents that are difficult to obtain. This is where the largest share of abandonment occurs. A citizen who must gather a national ID, a utility bill, a bank statement, and a residency certificate before they can even begin an application faces what behavioural economists call a high upfront cost — a cognitive and logistical burden that triggers loss aversion before any benefit has been experienced.

The fix is not to eliminate verification — governments have legitimate reasons for it. The fix is to shift when verification happens (later in the journey, once the citizen is invested), to pre-populate what the government already knows, and to accept digital verification where it meets the security threshold. Estonia's X-Road infrastructure, which allows government databases to share verified data so citizens do not re-submit what the state already holds, is the canonical example of what this looks like at scale. The principle is simple: do not ask citizens to carry information the government already has.

2. Document submission and format requirements

The second pressure point is document submission — specifically, the mismatch between how citizens hold information and how governments require it to be presented. A citizen who holds a PDF of their tenancy agreement but is required to submit a certified paper copy, or who has a digital bank statement but needs a branch-stamped version, is experiencing a format friction that has nothing to do with the underlying policy requirement and everything to do with legacy process design.

Format friction is particularly costly because it is invisible to the people who designed the process. From inside the department, the requirement looks reasonable — it is how it has always been done, it satisfies the audit trail, it is what the legal team approved. From the citizen's perspective, it is an arbitrary obstacle that requires a trip to a branch, a notary, or a government service centre that may only be open during working hours they cannot access.

3. Status uncertainty and the silence gap

The third pressure point is what happens after submission: nothing. Or rather, nothing visible to the citizen. Applications disappear into processing queues with no acknowledgement of receipt, no indication of where in the process they sit, no estimated timeline, and no proactive notification when something changes. This silence creates what I think of as the anxiety tax — a sustained cognitive burden that citizens pay throughout the processing period, manifesting as repeated status-check calls, in-person visits, and escalations that consume service-centre capacity.

Kahneman's peak-end rule tells us that people judge an experience by its most intense moment and its ending. A long, anxious wait — even if the outcome is positive — degrades the citizen's overall perception of the service. Proactive status updates, even simple ones, reduce this anxiety tax and improve satisfaction scores without changing the underlying processing time at all. The experience improves before the operation does.

The journey map versus the process flowchart: why most friction-reduction efforts fail

The most common mistake in public-sector service improvement is mapping the process rather than the journey. These are not the same thing. A process flowchart shows what the department does and in what order. A citizen journey map shows what the citizen experiences — including the steps that happen outside the department's direct control, the emotional state at each point, and the moments where the citizen is most likely to give up or make an error.

Process flowcharts are optimised for departmental efficiency. Journey maps are optimised for citizen outcomes. When a service-improvement team works from a process flowchart, they improve the process. When they work from a journey map, they improve the experience. These produce different interventions. A process optimisation might reduce internal handoffs from four to two; a journey optimisation might eliminate the need for the citizen to re-enter information they already submitted in step one.

The practical implication is that friction-reduction work must begin with research — specifically, with watching real citizens attempt to complete real tasks. Not user testing on a prototype, but observation of the live service: who gets stuck, where, for how long, and what they do next. This research almost always surfaces friction that nobody in the department knew existed, because the people who designed the process have never had to use it as a citizen.

A practical framework for reducing friction in public-sector journeys

The following is a sequenced approach that works in practice — not a theoretical model, but a set of steps that reflect how friction-reduction actually gets done in government contexts where political constraints, legacy systems, and procurement cycles are real.

1. Map the citizen's actual journey, end to end. Start from the moment the citizen becomes aware they need the service — not from the moment they arrive at the department's front door. Include pre-service research, channel selection, identity preparation, and post-submission waiting. Use a combination of observation, call-centre transcript analysis, and structured interviews with citizens who have recently completed (or abandoned) the journey. The goal is a map that reflects reality, not aspiration.
2. Identify and quantify friction points. For each step in the journey, assess three dimensions: the effort required (cognitive, logistical, and time), the failure rate (what proportion of citizens cannot complete this step without assistance), and the emotional valence (how does this step make the citizen feel). Quantifying friction — even roughly — transforms it from a subjective complaint into a manageable problem. A step that 40% of citizens cannot complete unassisted is a different conversation with a minister than "the form is a bit confusing."
3. Classify friction as necessary or unnecessary. Not all friction is removable. Some verification steps exist because the policy requires them; some eligibility checks are legally mandated. The discipline is to distinguish friction that serves a legitimate policy purpose from friction that serves only administrative habit. The latter is your first target. A useful heuristic: if the friction protects the citizen or the public, it is probably necessary; if it protects the department from audit risk, it is worth scrutinising.
4. Apply the pre-population principle. For every piece of information the journey requires, ask: does the government already hold this? If yes, pre-populate it. This single principle, applied systematically, can reduce form completion time by a significant margin and dramatically cut the abandonment rate at the document-gathering stage. It requires data-sharing agreements between departments, which is a governance challenge — but it is a solvable one, and the citizen experience dividend is large.
5. Redesign the status communication layer. Build proactive notification into every journey that has a processing period longer than 24 hours. Acknowledgement of receipt, estimated processing time, notification when a decision is made, and — critically — a clear explanation of what happens next. This does not require a new platform; it requires a decision that citizen communication is part of the service, not an optional extra.
6. Build a feedback loop that catches new friction. Friction is not static. New regulations create new requirements; system upgrades introduce new failure modes; changes in citizen demographics shift where the hardest steps are. A voice-of-customer mechanism embedded in the live service — short, in-journey feedback prompts, regular analysis of call-centre contacts by reason, and a named owner responsible for acting on what it surfaces — is the only way to ensure that friction reduction is a continuous practice rather than a one-time project.

The inclusion dimension: friction is not experienced equally

Any serious discussion of public-sector friction must address inclusion. Friction that is merely inconvenient for a digitally confident, time-flexible, English-literate citizen is exclusionary for someone who is elderly, has a disability, speaks a minority language, or lacks reliable internet access. The same document-submission requirement lands differently on a professional who can take an hour to visit a notary and on a shift worker who cannot leave work during opening hours.

This is not a peripheral concern. Government services exist to serve everyone, including — especially — those who are most dependent on them. A service that is frictionless for 80% of users but impenetrable for the 20% who most need it has failed at its core purpose, regardless of how well it scores on average satisfaction metrics.

The practical implication is that friction-reduction work must segment its research. Average journey completion rates mask the experience of the hardest-to-serve citizens. Designing for the most constrained user — the person with the least digital access, the least time, the least language fluency — tends to produce a service that works better for everyone. This is the public-sector equivalent of the curb-cut effect: accessibility improvements designed for specific needs create universal benefits.

What good looks like: the design principles that reduce friction durably

Across the services that have made sustained progress on friction reduction, a consistent set of design principles emerges. These are not aspirational values — they are operational commitments that shape specific decisions.

• Once only. Citizens should never be asked to provide information the government already holds. Every duplicate data request is a friction point that can be eliminated through data sharing.
• Default to digital, design for analogue. Digital channels should be the default because they are faster, cheaper, and more scalable — but every digital service must have a non-digital fallback that is genuinely usable, not a degraded afterthought.
• Progress visibility at every stage. Citizens should always know where they are in a process, what comes next, and what — if anything — is required from them. Uncertainty is friction.
• Errors caught early, not at submission. Validation should happen as citizens complete each field, not when they submit the whole form. A submission error after 45 minutes of form-filling is a trust-destroying event.
• Assisted digital as a genuine alternative. For citizens who cannot use digital channels, assisted digital — a human who completes the digital process on their behalf — must be available, well-staffed, and treated as a first-class service channel, not a legacy cost to be minimised.
• Plain language, always. Legal and policy language is not citizen language. Every citizen-facing communication — forms, letters, notifications, error messages — should be written to the reading level of the service's most constrained user.

The governance question: who owns friction?

The hardest part of public-sector friction reduction is not the design work. It is the governance question: who has the authority and the accountability to remove friction that crosses departmental boundaries?

Most friction-generating requirements exist because a rule, a system, or a process in one department creates a burden for citizens navigating a journey that spans multiple departments. The identity check that requires a physical document exists because the legal team in one directorate has not signed off on digital verification. The duplicate data entry exists because two departments' systems do not talk to each other. The mandatory in-person step exists because the policy was written before digital channels existed and nobody has been asked to update it.

None of these can be fixed by the service-design team alone. They require a cross-departmental authority — a CX governance structure with the mandate to identify friction-generating rules, escalate them to the appropriate owner, and track their resolution. Without this, friction-reduction projects improve individual touchpoints while the structural causes of friction remain untouched.

This is why the most effective government service-improvement programmes treat citizen experience as a cross-cutting function with executive sponsorship, not as a project owned by a single department's digital team. The design capability matters; the governance structure is what makes it stick.

Measuring progress: the metrics that actually tell you friction is reducing

Average satisfaction scores are a lagging indicator of friction. By the time a satisfaction score moves, the friction has been experienced by thousands of citizens. The metrics that give earlier, more actionable signal are operational: task completion rate (what proportion of citizens who begin a journey complete it without assistance), time-on-task (how long the journey takes end to end, not just the digital portion), and contact rate (how often citizens need to call or visit to resolve a problem that should have been self-service).

These metrics are harder to collect than a post-service survey score, but they are far more useful for identifying where friction is highest and whether interventions are working. A structured feedback management approach that combines operational metrics with qualitative citizen research gives a complete picture: the numbers tell you where friction is concentrated; the research tells you why.

For teams wanting to benchmark their current state before beginning a friction-reduction programme, a structured CX maturity assessment can identify which capabilities — journey mapping, feedback infrastructure, governance, digital channel design — are most underdeveloped and therefore where investment will have the greatest impact.

The political economy of friction removal

One final point that rarely makes it into service-design guides but shapes everything in practice: friction removal in government is a political act. Every requirement that creates friction exists because someone, at some point, decided it was necessary. Removing it means overriding that decision — which requires either new evidence that the requirement is no longer serving its purpose, or sufficient political will to accept the risk of changing it.

This is not an argument for accepting friction as inevitable. It is an argument for framing friction-reduction work in terms that resonate with decision-makers: the cost of the contact volume that friction generates, the inclusion risk of services that exclude the most vulnerable citizens, and the reputational cost of government services that citizens regard as adversarial rather than helpful. Friction is not just a design problem. It is a policy problem, a resource problem, and — ultimately — a question of what government believes it owes the people it serves.

The services that have made the most durable progress on friction reduction are the ones where that question has been answered clearly, at the highest level, and where the answer has been translated into specific design principles, measurable targets, and named accountability. The design work follows from that commitment. Without it, friction-reduction projects improve individual touchpoints while the system that generates friction continues, undisturbed, to produce more.

Public services that are genuinely easy to use are not a luxury. They are the baseline of a functioning relationship between government and citizen — and the gap between that baseline and the current reality of most public-sector journeys is, for anyone paying attention, one of the most tractable and consequential design problems of our time.