SERVICE STANDARD · POINT 4
Make the service simple to use
Simplicity is not dumbing down — it is respecting someone's time and cognitive load. Every extra field, jargon term, or unnecessary step is a cost borne by the user.
Strip away steps that do not help the user. Use plain language, sensible defaults, and progressive disclosure. Complexity in policy or process should be handled behind the interface, not dumped on the user.
Teams simplify by removing steps that do not change outcomes, rewriting content in plain language, and using sensible defaults. Complex policy rules should be encoded in the service logic rather than exposed as puzzles for users to solve.
Simplicity is tested, not assumed. Usability testing and analytics often reveal steps that seemed obvious to the team but confuse real users.
How teams usually demonstrate this
- Content design that uses plain English and active voice
- Task completion flows with minimal unnecessary questions
- Usability test evidence showing users can complete realistic tasks
- Iteration history where complexity was removed based on evidence
Phases where this often matters
See also delivery phase guides and how frameworks fit together.
Related standard points
- Point 1: Understand users and their needs
- Point 5: Make sure everyone can use the service
- Point 8: Iterate and improve frequently
Point 4 of the Service Standard is published by the Government Digital Service on GOV.UK. Content is available under the Open Government Licence v3.0. UCD Services explains the standard in its own words and is not affiliated with GOV.UK or the Government Digital Service.