Designing Good Government Services: An Introduction (GOV.UK Service Manual)
The GOV.UK Service Manual’s own list of characteristics shared by good government services, grounded in practice across UK government rather than academic service-design literature.
License: Open Government Licence v3.0 — same basis as GOV.UK Design System.
Key points
- A good service hides its own internal structure from users: if completing a task means pulling from two different back-end systems, the user shouldn’t need to know that — they need one quick way of accessing their information, not an explanation of how it’s stored.
- A good service has no dead ends: every user reaches a clear outcome, even one who isn’t eligible for the service itself is told clearly what to do next, and nobody is left stranded without knowing how to continue.
- Reducing what a user has to do reduces errors as a side effect, not just effort — a postcode lookup instead of manual address entry, or asking a user to review previously-given information rather than re-enter it, both cut opportunities for mistakes at the same time they save steps.
- Where a step carries real risk if a user acts too quickly, a good service deliberately slows them down — a warning screen before a significant change to personal data is the example given.
- Consistency has to hold in real time across every way a user reaches the service: if someone updates their phone number online, they expect a phone agent to see that update immediately, not stale data from before the change.
- Where a service makes a decision using an algorithm, it should be clear to the user that an algorithm was involved and how, and users need a way to challenge or ask for a review of that decision.
- It should be easy to reach a human when self-service fails — an unpredictable technical problem, or a user who can’t produce a piece of required evidence, are the kinds of situations a service should never leave unhandled.