By the end of this lesson you can
- Explain service design and how it differs from product design.
- Create a service blueprint.
- Design across channels and backstage processes.
The idea
Service design looks at the whole service: every channel (online, phone, in person, post), the people delivering it and the processes and systems behind the scenes.
Front stage and backstage
The front stage is what users see: websites, letters, staff conversations. The backstage is what makes it work: staff processes, systems, policies and partners. Many user problems are caused backstage.
Service blueprints
A blueprint maps, in rows:
- User actions.
- Front-stage interactions (touchpoints and staff).
- Backstage actions.
- Support processes and systems.
- Evidence (what the user sees or receives).
Lines separate what users see from what they do not. Pain points and opportunities are marked on the map.
Working across channels
People move between channels. Make sure information and progress carry across, so people do not repeat themselves.
Collaboration
Service design involves frontline staff, operations, policy and technology teams. Workshops and co-design are central.
Why it matters in real projects
Polishing a screen cannot fix a broken process behind it. Service design finds the root causes of problems, such as handoffs between teams, slow approvals or missing data, and improves the whole experience. It is widely used in public services, healthcare, banking and retail.
A realistic example
A council's blue badge (disabled parking permit) applications take 12 weeks. The online form is fine, but a blueprint reveals that applications are printed, posted to an assessment team and manually re-entered. Redesigning the backstage process so applications flow digitally to assessors cuts the time to four weeks, with no change to the form.
Step by step
Define the service
Choose a service and its start and end.
Map user actions
List each step the user takes.
Add front stage
Add touchpoints and staff interactions.
Add backstage
Interview staff to map hidden processes and systems.
Mark pain points
Highlight delays, handoffs and failures.
Design improvements
Co-design changes with staff and users.
Common mistakes
Mistake Only designing screens.
Instead Look at the whole service including backstage.
Mistake Mapping without staff input.
Instead Interview and involve frontline staff.
Mistake Channels that do not connect.
Instead Carry information across channels.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 1 h
Blueprint a service
Create a service blueprint for a service you know.
Steps
- Choose a service such as returning a parcel.
- Map user actions and front-stage touchpoints.
- Add likely backstage actions and systems.
- Mark three pain points and opportunities.
Deliverable
A service blueprint.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Service design covers the whole service.
- Map front stage and backstage.
- Use blueprints to find root causes.
- Work across channels and teams.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- Service blueprints: definition (opens in a new tab)Nielsen Norman Group
- Service manual: service design (opens in a new tab)GOV.UK Service Manual
Your notes
Marking complete updates your course and roadmap progress.