On a Thursday morning, Leah comes into a fictional council office carrying a paper folder. She is trying to renew her father’s travel concession. The website appointment has expired, the mobile application asks for a security detail he cannot recover, and a staff member has already told her to “just do it online.” At the counter, the adviser knows there is an internal route for recording the application. She also knows that Leah is not asking for special treatment. Yet the answer comes almost automatically: “Everything is done through the app now.”
Nothing in that exchange needs to look dramatic. The application may be operating as specified. The adviser may be trying to keep a queue moving. No manager may have written an instruction saying that older residents, people with shared devices or anyone struggling with an identity check should lose a benefit. But exclusion often arrives through habits rather than declarations. A debatable choice is repeated so often that it begins to sound like a fact of nature. The screen stops being one organisational tool among others and becomes an authority no one believes they are allowed to question.
That is why the problem is cultural as well as technical. Culture here does not mean the personality of one employee. It means the accumulated signals that tell a team what counts as good work: which figures managers reward, whether a longer conversation is treated as failure, who can approve a different route, and what language colleagues use about people who cannot complete the standard journey. A well-designed interface cannot by itself protect rights if the organisation around it has learned to defend the routine before it understands the obstacle.
A phrase that hides a decision#
“Use the app” sounds like neutral guidance, but it can conceal several choices. Perhaps digital records are easier to count. Perhaps staff fear making an error outside an automated workflow. Perhaps a supplier has sold channel migration as proof of modernisation. Perhaps a manager wants fewer calls and less paper. Those reasons may explain why the organisation prefers a channel; they do not establish that every resident can use it safely, privately and in time.
“Use the app” sounds like neutral guidance, but it can conceal several choices. Perhaps digital records are easier to count.
The habit survives because its benefits are visible while its costs are dispersed. A dashboard can report fewer appointments, fewer manual entries and more completed online forms. It rarely records the person who tried three times and stopped, the daughter who had to take unpaid time to help, or the resident who decided that asking again was humiliating. Their additional work is carried outside the system, so the system learns to call itself efficient. An uncounted burden is easily mistaken for no burden at all.
Words contribute to this mistake. If staff meetings refer to “difficult users” or “people who will not adapt,” the problem appears to reside in the visitor. If they instead refer to access conditions, equivalent routes and burdens created by the service, responsibility becomes easier to locate. This is not a matter of softer vocabulary alone. It changes whether a team asks how to correct a person or how to repair a rule that has made a common circumstance into a barrier.
Most procedures have gaps that no manual can cover. A shared phone, a lost password, a document a camera cannot read, a temporary injury, unreliable connectivity or a notification written in unfamiliar terms can interrupt an apparently simple task. In those gaps, staff do not make entirely new choices each time. They follow the behaviour their workplace has made safest. When the only protected answer is referral back to the application, the application becomes an automatic refusal. The incident is removed from view instead of being treated as evidence about the service.
Find the incentives behind the routine#
Telling staff to be more caring will not change a routine if their incentives point the other way. An office may measure visits in minutes even when helping someone finish an application takes twenty. It may celebrate the percentage of applications moved online without measuring how many people completed them without a relative’s help. It may have no budgeted hours for assisted access, making every alternative seem like a favour rather than part of the public service. In that setting, a request for empathy asks individuals to compensate for a design they do not control.
The first practical step is to make the hidden work visible. For a limited period, the office could record, without identifying visitors, when someone arrives after an unsuccessful digital attempt, which step failed, what assistance was offered and whether the application was actually completed. The record does not need to build a profile of vulnerability. It should distinguish concrete conditions: a blocked identity check, unclear documents, an inaccessible appointment, a device problem, a missing confirmation or a rule that allows only one channel.
Collecting that information matters only if it reaches someone who can act. When the same blockage appears repeatedly, a named owner should be able to change instructions, authorise assisted verification, fix a notice, request a supplier change or introduce an equivalent route. If reports go into a spreadsheet with no decision attached, the organisation is asking people to recount their difficulty without reducing it. Feedback should travel both ways: staff need to know what changed because of the cases they raised, and residents need a clear answer about what will happen next.
Equivalence is more important than sameness. A telephone, in-person or supported route does not have to reproduce every click in an app. It does have to provide the same access to the request, the same deadline, a proof of submission and a way to correct an error. A route that is processed last, depends on a staff member’s personal favour or leaves no receipt is not an alternative in any meaningful sense. It is a fragile exception. Public equality means that needing a different route does not reduce the chance of completing the right at stake.
Give staff permission to challenge the rule#
A healthy service does not rely on one unusually confident adviser to notice a problem and bend the rules. It establishes a known authority: when a person cannot complete the digital path, the member of staff can activate a defined alternative, record the friction and request review without being criticised for slowing the queue. That permission has to appear in training, shift planning and performance review. If it exists only as informal advice between colleagues, it will vanish on a busy day or when the team changes.
Case-based learning can make that authority practical. Teams can examine anonymised situations: a resident who cannot control the phone registered to a partner, an application that disappeared after an upload failed, a person who received a message they could not interpret, or a form requesting a piece of information that does not exist for their circumstances. The purpose is not to turn every worker into a specialist in every hardship. It is to identify the precise point at which an ordinary life condition became a disproportionate administrative obstacle.
Managers need to take part. When a manager says, “That is what the system does,” everyone learns that raising concerns is pointless. When they review recurring failures, decide what the office can change and explain what must be escalated to a supplier, the screen returns to its proper place: a tool governed by people. A supplier can maintain a function, but it cannot be the final owner of a public decision about who is allowed to reach a service.
Testing should also move beyond ideal conditions. An office can simulate a lost phone, a broken document reader, a resident with ten minutes available, or a failed notification. The meaningful question is not whether the product gives a polished demonstration. It is whether the resident receives an understandable next step, whether staff know who can act and whether the application remains protected while the fault is resolved. Such tests reveal whether inclusion is a claim in a strategy document or a capability exercised in daily work.
Make learning part of the service#
Leah does not need a promise of cultural transformation before her father’s concession can be renewed. She needs someone who can start the application, explain what remains and provide a receipt with a clear response time. She should not obtain that outcome because she knows the right employee or persists more forcefully than someone else. Yet her visit can also help prevent the same barrier from being repeated for the next family.
One modest experiment would be a supported-access session with the power to record applications, not merely explain how to use the app. Each week, a responsible manager could review the most frequent points of failure and approve small repairs: clearer recovery text, an announced telephone route, earlier document guidance or an appointment rule that does not expire without warning. The target would not be more downloads. It would be fewer abandoned applications, fewer repeated journeys and less dependence on private favours.
That approach also protects employees. With a defined route in place, the adviser at the counter no longer has to improvise a personal exception. She can say what the office will do, what evidence the resident will receive and when a review is available. Consistency does not come from forcing every person through one interface. It comes from preserving the service’s guarantees when that interface is not enough.
Digital rights are weakened when a repeated phrase outweighs the person standing in front of the desk. They become more real when an organisation can notice friction, inspect the incentives that normalised it and turn it into a change in practice. The demanding question for any public team is simple: once we know that someone cannot move forward, do we send them back to the same blockage, or do we treat that knowledge as a reason to change how we serve them?
