Last updated: 16 September 2020
Service Standard for Wales
- Focus on Welsh well-being
- Promote the Welsh language
- Understand users and their needs
- Iterate and improve frequently
- Use data and user research to make decisions
- Consider ethics, privacy and security throughout
- Every service needs an empowered service owner
- Every service needs a multidisciplinary team
- Use scalable technology
- Work in the open
This is a prototype that we’re sharing in the open for feedback.
This standard takes inspiration from other digital standards around the world (including that published by the Welsh government). It explains what’s expected from new or redesigned digital services, funded by Welsh public sector organisations. We will collaborate with people across Wales to iterate and improve on this version.
In more detail:
Focus on Welsh well-being
We’re here to make a positive difference to the lives of people in Wales. We should be driven by outcomes that benefit them, not by lists of technical specifications or requirements. Digital service design means thinking about the future as much as we think about today. Teams should** consider the well-being of future generations**, and think about the social, economic, environmental and cultural well-being of Wales. Services should contribute to the 7 well-being goals of Wales.
Promote the Welsh language
Services in Wales should meet the needs of people who use the Welsh language in their everyday lives. Teams should design and build services that promote and facilitate the Welsh language, and treat users who speak it equally with those who prefer English.
- Read Welsh Government guidance on promoting Welsh language
- Support and promoting the Welsh language (PDF), by the National Assembly
- How we’re making our services better by improving our use of the Welsh language, by Beth Owen
Understand users and their needs
User needs should drive service design, whoever those users are. User needs matter more than the constraints of business structures, organisational silos or technologies.
Teams should aim to address the user journey from start to finish, understanding the different ways and channels people will interact with services, whether that’s online, over the phone, or in person. Public services are for everyone, so considering accessibility is essential. Every encounter, online or offline, should move a user closer to their goal.
- Most of government is mostly service design, most of the time, by Matt Edgar
- The importance of product management in government, by Chris Johnston and Kelly O’Connor
- What we mean when we talk about accessibility, by Alistair Duggin
Iterate and improve frequently
We should use an incremental, fast-paced development approach to get working software into users’ hands as early as possible, as often as possible. This will help teams rapidly iterate, based on user feedback.
- Iterative UI design, by Paul Boag
- Iterative user interface design, by Jakob Nielsen
- Designing the Windows 95 user interface, by Kent Sullivan
Use data and user research to make decisions
We should constantly measure how well services are performing for users. Teams should use performance data to find and prioritise improvements. Where possible, that data should be automated and real-time, to make it as objective and easy to collect as it can be.
Teams should conduct user research on iterative changes to their services. Senior leaders should take part in research on a regular basis, to stay in touch with the work.
- Making user research work in government (20 minute video), by Katy Arnold
- If I could tell you 3 things, by Leisa Reichelt
Consider ethics, privacy and security throughout
Digital services must protect sensitive information and keep data secure. Teams should assess, understand and address ethical issues associated with all digital services at every stage of their development.
- Read Doteveryone’s Consequence Scanning guide for understanding the potential impact of a product or service on people and society.
- Boiling Frogs, by GCHQ
Every service needs an empowered service owner
There should be a single empowered service owner who has the authority and responsibility to make all business, product, and technical decisions about a service.
The same person is accountable and responsible for how well the service meets the needs of its users, which is how its success will be evaluated.
Every service needs a multidisciplinary team
Teams are how we build services for Wales. Each one should be a diverse mix of people, experience, expertise and disciplines.
As well as having the right mix of skills and experience for the current stage of development, the team should be able to explain how the make-up of the team may change over time, and what funding will be needed to support a team responsible for the service’s continuous improvement.
- Download The Team Onion, a free ebook by Emily Webber
- Agile for teams who don’t build software, by Ross Gregory
Use scalable technology
We should make technology decisions that help teams do their work and deliver. We should always aim to use the simplest, most appropriate tool, and avoid vendor lock-in to specific technologies.
Teams should be empowered to use the tools that work for them , and encouraged to consider tools that meet open standards, are cloud-based, and that have widespread adoption and support.
- Characteristics of internet-era CTOs, a series of posts by James Stewart
- More useful insight in Toxic Technology, by Dave Rogers
Work in the open
We should aim to make the services we build, and the techniques we use to build them, as open as possible.
As they develop a service, teams should communicate in the open about the decisions they’re making and what they are learning. They should also share code, patterns and insights as freely as possible to help others seeking to build excellent public services in Wales.
- A blog is your brain, over time, on the internet, by Giles Turnbull
- Blog posts from the team working on alpha.gov.ca in California
- How coding in the open can make you release faster, by Anna Shipman