Trust in Government Is Built at the Counter, Not in a Campaign

A citizen doesn't lose trust in the state because of a headline. She loses it while queuing for forty minutes at a service centre because the online form crashed, again, and nobody apologised. Trust in public institutions isn't won in a campaign or a ministerial speech. It is won or lost, transaction by transaction, at the counter, on the app, in the call queue.

That's the argument this piece makes, and it runs against how most governments still budget for trust: as a communications problem, solved with better messaging. It isn't. Trust in government is a service-design output — the residue left behind after thousands of small, repeated interactions between citizens and the state. Get the interactions right and trust accumulates quietly, without a campaign. Get them wrong and no campaign fixes it.

What actually builds trust in public institutions?

Trust in public institutions is built through consistent, low-friction, procedurally fair interactions delivered over time — not through single grand gestures. Citizens generalise from their most recent and most difficult encounter with a service to their view of the whole institution. A government earns durable trust the same way a bank earns credit: by reliably doing the unglamorous thing it promised, every time, especially when nobody is watching.

This matters more in 2026 than it did a decade ago. Digital government has multiplied the number of touchpoints a citizen has with the state — apps, portals, chatbots, SMS notifications — and every one of them is now a trust event, whether the ministry intended it to be or not. The OECD's work on trust in government has for years tracked how citizens' confidence in public institutions is shaped less by macro-political events than by direct experience of public services: healthcare, policing, tax administration, local permits. The mechanism is unglamorous and consistent: reliability compounds, and failure at the point of service travels further than failure anywhere else in the system.

Why do citizens distrust government even when the policy is sound?

Because policy is invisible and delivery is not. A citizen rarely evaluates a subsidy scheme, a licensing reform, or a national strategy on its economic merits — she evaluates it on how it felt to apply, wait, and receive (or not receive) what was promised. Good policy delivered through a broken process reads as bad governance. This is where procedural justice does more analytical work than most CX metrics: research in public administration and legal psychology has long shown that citizens judge institutions less on outcomes than on whether they were treated with respect, given a voice, and processed fairly and transparently along the way. A rejected application handled with clear reasoning and dignity builds more trust than an approved one delivered through opacity and delay.

Loss aversion sharpens this further. Kahneman and Tversky's foundational work on prospect theory established that losses are felt roughly twice as intensely as equivalent gains — and citizens experience almost every interaction with the state through a loss frame. A delayed refund, a revoked permit, a benefit that's harder to renew than to claim: these register as losses, even when the underlying entitlement hasn't changed. Institutions that don't design for this asymmetry — that treat a renewal like a fresh application, or a complaint like an inconvenience — pay a trust penalty that's disproportionate to the actual service failure.

How does friction erode institutional trust faster than bad policy does?

Friction is the tax citizens pay in time, effort, and confusion to get what they're entitled to — and unlike a fee, it's rarely visible to the people who designed it. Richard Thaler's concept of sludge — friction deliberately or carelessly built into a process that makes a desired action harder than it needs to be — was developed to describe corporate practices, but nowhere does it apply more corrosively than in government, because citizens usually have no alternative provider to switch to. A private company that makes cancellation hard loses a customer. A government agency that makes appeal hard just loses trust, silently, with no exit option to signal the failure.

The pattern repeats across public services worldwide: multiple logins for one citizen record, documents required in person that were already submitted digitally, and status updates that vanish once a case is escalated. Each of these is a small procedural choice, made for the institution's convenience rather than the citizen's. None of them shows up in a satisfaction survey question about "policy quality." All of them show up in the answer to "do you trust this institution to treat you fairly."

Handoffs are the clearest example. Every time a citizen's case moves from one department, channel, or agent to another, she has to re-explain herself, and the institution risks losing context, urgency, and accountability in transit. We've written before about why handoffs frustrate customers in commercial settings; in public services the effect is amplified because the citizen usually has no choice but to keep trying.

What role does a single bad experience play in undoing years of good delivery?

A disproportionate one. Daniel Kahneman and colleagues' research on the peak-end rule found that people judge an experience overwhelmingly by its most intense moment and its ending, not by the average of every moment within it. Applied to public services, this means a citizen who has quietly renewed a licence online without issue for five years will still recalibrate her entire view of the institution around the one year the system failed and no one could tell her why.

This is why institutional trust is asymmetric and slow to rebuild once broken: it is accumulated in small increments across many interactions but can be wiped out in a single badly handled one, particularly if that one involves a loss, a denial, or an unresolved complaint. Institutions that understand this design deliberately for the ending of difficult journeys — the appeal, the escalation, the refusal — because that is where the peak-end effect does the most damage or the most repair.

Institutional trust is not an average of good and bad interactions. It is set by the worst one, remembered at the end.

How can governments rebuild trust through service design rather than communications?

Trust repair starts with the service, not the story. The following sequence reflects how we run this work with public-sector clients, moving from diagnosis to durable change rather than a one-off fix.

1. Map the journey as citizens actually live it, not as departments organise it. Most government journeys are designed around internal org charts — one team per stage — while the citizen experiences a single, continuous need. Mapping the end-to-end journey exposes every handoff, duplicate document request, and dead end that internal teams never see because no single owner watches the whole thing.
2. Find the moments of truth, and rank them by loss, not by volume. Not every touchpoint carries equal trust risk. Prioritise the interactions where a citizen stands to lose something — money, time, a benefit, standing — because these are where loss aversion and procedural-justice perceptions concentrate.
3. Strip sludge before adding features. Before building a new app or portal, remove the friction in the current process: redundant verification steps, forms that ask for data the institution already holds, and channels that don't talk to each other. A faster broken process is still a broken process.
4. Redesign the endings, deliberately. Every journey that can end in refusal, delay, or escalation needs its ending designed with the same care as its start — clear reasoning, a real human option, and a visible next step. This is where the peak-end effect can be turned from a liability into a repair mechanism.
5. Build a structured feedback loop that closes. A complaint that disappears into a form with no visible resolution teaches citizens that raising an issue is pointless — which suppresses future feedback and starves the institution of the signal it needs. Structured feedback management means every complaint has a visible owner, a timeline, and a closed loop back to the citizen who raised it.
6. Govern it, don't just launch it. Service redesigns decay without ownership. Trust-critical journeys need standing governance — a named accountable owner, a review cadence, and authority to fix cross-departmental friction — which is precisely the gap that CX governance is built to close in institutions where no single department owns the citizen's whole experience.

What does trust-building through experience actually look like in practice?

The clearest public examples share a pattern: they reduce the number of times a citizen has to prove who she is, restate her situation, or chase a status update. Estonia's digital-identity infrastructure, built around the principle that government should ask a citizen for a piece of information only once, is often cited internationally precisely because it addresses the sludge problem structurally rather than through better customer service on top of a broken back end. The UK's GOV.UK service standard has pushed a similar discipline: consistent design patterns across departments so a citizen doesn't have to relearn how government works with every new service she touches.

None of this required a public-trust campaign. It required treating each service as infrastructure worth designing properly the first time, and treating the citizen's time as a cost the institution should minimise rather than externalise. That's the essence of good service design applied to a public mandate rather than a commercial one — and it is the reason public-sector CX transformation has become its own discipline rather than a rebadged version of retail CX. Citizens are not customers who can churn; that changes the ethics of the design, but not the mechanics of trust.

How should institutions measure whether trust is actually improving?

Satisfaction scores alone won't tell you. A citizen can rate a single transaction highly and still distrust the institution overall, because trust is judged across the relationship, not the interaction. What works better is triangulating three signals: transactional experience data captured at the moment of service, structured complaint and escalation trends over time (rising complaints handled well can indicate growing trust in the channel, not falling trust in the institution), and periodic perception surveys that ask directly about fairness, consistency, and confidence — the closest public-sector proxy to the well-known Edelman Trust Barometer, which has tracked public trust in institutions annually since 2000.

Institutions serious about this discipline benchmark their delivery capability the way a bank benchmarks credit risk — structurally, not anecdotally. A CX maturity assessment gives public-sector leaders a way to see where their journeys, governance, and feedback loops actually stand against the building blocks that predict trust outcomes, rather than relying on the loudest complaint of the month to set the agenda.

Where does culture fit into trust-building?

Process redesign hits a ceiling if the people delivering the service don't believe in the standard they're being asked to hold. A front-line officer who has been told to "prioritise the citizen" without the authority, training, or system access to actually resolve a case will default to the old behaviour, because the new promise was never made real for her either. Trust-building through experience is inseparable from aligning institutional culture with the promises made to citizens, and from the harder, slower work of change management that gives front-line staff the mandate to actually deliver the redesigned journey rather than just describe it in a manual.

• Give staff authority to resolve, not just to escalate. An officer without resolution power becomes another handoff, not a solution.
• Train for judgement, not just scripts. Procedural fairness requires explaining reasoning, which a rigid script often prevents.
• Measure managers on citizen outcomes, not just throughput. Volume-based targets quietly reward the sludge that erodes trust.
• Close the loop back to the front line. Staff who see what happens after a complaint is escalated stay invested in fixing the pattern, not just processing the ticket.

What's the honest constraint governments face that private companies don't?

A private company can fire a bad process by losing the customers who hate it. A government cannot, and that's precisely why the standard for public-sector service design should be higher, not lower, than in retail or banking. Citizens have no alternative provider to signal failure through defection; the institution has to actively seek out its own friction, because the market won't do it for the institution. That asymmetry is the honest case for building trust-repair capability — governance, structured feedback, and journey ownership — into the operating model permanently, rather than treating it as a project that ends when the dashboard goes live.

The institutions that will be trusted in 2027 and beyond are unlikely to be the ones that talk about trust the most. They'll be the ones that quietly stopped making citizens repeat themselves, waited any longer than necessary, or explained a decision badly. Trust, in the end, is just the compound interest citizens pay themselves back in confidence — for every unglamorous transaction the institution got right when it didn't have to.