A service is easy to underestimate. It can look like a single form, a phone call or a webpage, but it is really a connected set of activities that helps a person achieve something, such as opening an account, reporting a fault or receiving a diagnosis. What sets service design apart from other forms of design or improvement is not one clever idea but several habits of practice working together: user-centred design, end-to-end design, systems thinking, design thinking and service-dominant logic.
User-centred design means starting with the people who use and deliver a service, rather than with assumptions about what they need. The Skills England (2023) occupational standard describes service designers as taking a user-centred, collaborative and exploratory approach, working directly with users and frontline staff before shaping a solution. This differs from customer service, which is one part of how a service is delivered, and from user experience design, which usually focuses on a single interface or product (Penin, 2018).
End-to-end design means treating a service as one continuous journey rather than a series of separate touchpoints. The same Skills England (2023) standard describes designing services end to end, front to back and across every channel a person might use, covering both what a user sees, such as information and digital screens, and the internal processes, data and teams working behind the scenes. GOV.UK (2016) guidance for government services makes a similar point, asking teams to design a service from beginning to end and across digital and non-digital channels, rather than treating each channel as a separate project. Problems rarely stay inside neat organisational boundaries, so a gap in one team’s process easily becomes a complaint that lands in another team’s inbox.
Systems thinking extends that whole-journey view further, to the wider structures, policies, technology and culture that shape how a service behaves. Design Council (2021) describes systemic design as recognising the interconnectedness of a challenge, rather than treating it as an isolated problem to be fixed in one place. Applied to a service, this means a repeated complaint or delay is rarely caused by one broken step; it is usually a symptom of how several systems interact, which is why local, single-team fixes so often fail to stop the same issue recurring elsewhere.
Design thinking supplies the method for working through that complexity. Design Council’s (2019) Framework for Innovation describes an iterative cycle of discovering a problem through direct engagement with the people affected, defining it clearly, developing possible responses collaboratively, and testing them at a small scale before wider delivery. Rather than committing to one fixed solution early, service designers expect to prototype, test with real users and revise. This iterative, evidence-informed habit is what allows a service to be adjusted before a costly full-scale rollout, not after.
Underneath all of this sits service-dominant logic: the idea that value is not simply produced by an organisation and handed to a customer, but created together through use (Vargo and Lusch, 2004). A passport, a bank account or a piece of software only becomes valuable once a person actually uses it in their own context, so the user’s experience of enacting a service matters as much as what the organisation intended to deliver. Stickdorn et al. (2018) describe this as a genuinely collaborative practice: frontline staff, specialists, users and decision makers each hold knowledge that no single group has alone, and value is created between them rather than handed down from one to the other.
None of this requires a specialist title. Any leader can start by describing a service the way a user experiences it, gathering real evidence rather than assumption, and asking who else in the organisation shares responsibility for that experience. That shift, from an internal process to a whole, evidence-informed and holistic view of a person’s experience, is the starting point for everything else service design offers.
Action Point
Pick one service you use or deliver at work, such as onboarding a new starter or handling a complaint. Write down what it looks like from the user’s point of view in three or four steps, not from your team’s internal process. Note anywhere in that sequence where responsibility passes to another team, system or organisation. Those handover points are usually where service problems start.