Thinking of Becoming a Service Designer? Five Things to Understand First
Most people who move towards service design do it because of a map. They see a service blueprint or a journey map, recognise a better way of looking at problems they already work on, and decide this is the job they want. I did something similar. I came from graphic design and then UX, and I assumed the move was mostly about learning new methods.
It was not. The methods are the visible part of a job that is mostly about scope, systems, people and organisations. This guide sets out five things I think are worth understanding before you commit to the move, each with a small way to try it in the job you already have.
A different job, not a bigger version of the one you have
The UK government's capability framework for digital and data roles describes the role in two sentences: "Service designers design the end-to-end journey of a service. This helps a user complete their goal and government deliver a policy intent." Notice that the second sentence names two outcomes. The person has to get what they came for, and the organisation has to achieve what it set out to do. Holding both at once is most of the difficulty.
The Nielsen Norman Group's definition, written by Sarah Gibbons in 2017, points the same way. Service design is "the activity of planning and organizing a business's resources (people, props, and processes)" so that the employee's experience improves directly and the customer's experience improves as a result. Neither definition mentions a screen. If you are coming from UX or product, that absence is the first thing to take seriously.
One: the scope is the whole service
Lou Downe's description from the Government Digital Service is deliberately plain: "service design is the design of services". The scope that goes with it is end to end, front to back, and across every channel. In practice that means the letter, the phone line, the reminder text, the member of staff at the desk and the three weeks of waiting are all part of the design, whether or not anyone drew them.
This changes what a normal week looks like. You will spend less time making one thing excellent and more time making several ordinary things fit together. Some people find that a relief. Others miss the craft badly, and it is better to know which you are.
To try it: pick a service you have used recently and write down every step, including the ones that happened on paper, on the phone or in silence. Count how many of them a designer could have touched.
Two: systems decide more than design does
On the first larger projects I joined, I kept hearing the same sentences. The policy doesn't allow that. The system can't do that. Another team owns that process. None of them were about the design, and all of them decided what the design could be.
A service sits inside rules, technology and operations that were mostly settled before you arrived. You do not need to become an engineer or a lawyer. I am not a technical person and I still cannot code. What you do need is enough understanding to ask where a constraint comes from, who owns it and whether it is a rule or a habit.
To try it: ask an engineer or an operations colleague to draw, on paper, what happens after someone presses submit. Then ask which parts could change this year.
Three: facilitation is a large part of the work
One of the seven skills the UK framework lists for the role is called Designing together. A government blog post on working with service designers puts it more informally: "Service designers are the glue". The same post warns teams to expect overlap with user researchers, product managers and business analysts.
Being the glue means a lot of your output is not a document. It is a room of people from different teams who now see the same problem, or a decision that finally has an owner. If you dislike meetings on principle, this will be hard. If you like helping a group think, it may be the part you enjoy most.
To try it: offer to run one short session where two teams walk through the same case together. Notice whether you found it draining or interesting.
Four: research goes beyond users
UX research usually centres on the person using the product. Service research keeps that and adds everyone who makes the service happen. The NHS service standard is explicit that users include patients, carers, frontline staff and back office staff.
The people who run a step often know exactly where it breaks, and nobody has asked them.
The evidence also gets broader. Alongside interviews you will read complaints, contact centre notes, process documents and performance data. The framework calls the skill Evidence-based design, and the evidence is rarely tidy.
To try it: interview one person who operates a step of a service you work on. Ask what they do when the process does not fit the case in front of them.
Five: the work crosses organisational lines
The UK Service Standard asks teams to solve a whole problem for users, "working with other teams and organisations where necessary". Whole problems rarely respect an organisation chart. The outcome a person needs often depends on a supplier, a partner body or another department that nobody in your room manages.
This is the slowest part of the job. Progress comes through agreement, not instruction, and agreement takes time. The reward is that these joins are where services most often fail, so work done there tends to matter.
To try it: list every team and organisation one service depends on. Mark the handovers where nobody is clearly responsible.
How to decide
These five things do not make service design better than UX or product design. They make it different. The feedback is slower, the work is more political and you will ship fewer things that are recognisably yours. In return you get to work on the causes of problems instead of their surface.
If you tried the five small experiments and wanted to do more of them, that is a good sign. If you found them frustrating, that is useful too, and nothing has been lost.
It is easier to choose a job once you know what the job is.
Template: the companion resource for this article is a duplicable try-out plan, with the five experiments, an evidence log and a page for making the decision.
Join The Curious Society Learning Path
Explore practical learning resources designed to help you build deeper knowledge, stronger judgement and real-world capability.
