Service Design
The design of a whole service across every channel and touchpoint, including the staff processes and systems the customer never sees.
Design DisciplinesService design treats the digital product as one component among many: the app, the emails, the phone call, the paperwork, the person at the desk and the internal tools they use. Its characteristic artefacts are the customer journey map and the service blueprint, which adds the backstage layer showing which team and which system supports each visible step.
It matters most where the experience spans organisations — healthcare, banking, logistics, public services. In those settings the worst moments are usually invisible to a product team because they happen in a handoff, and no amount of interface work fixes a step that depends on someone re-typing data from a fax.
In practice
A clinic's patient experience was blamed on the booking app. A blueprint showed confirmations were sent by a scheduler manually, once a day, from a separate system. Before: patients waited up to 24 hours to know if a slot was confirmed. After connecting the two systems, confirmation was immediate. The catch — schedulers lost a review step they used to catch double-bookings.
Learn more
You may ask
Frequently Asked Questions
How is service design different from UX design?
UX design is bounded by the product; service design includes offline touchpoints, staff processes and internal systems. If fixing the problem requires changing what an employee does, it is service design.
What is a service blueprint?
A journey map extended downward: the customer's steps on top, then the frontstage staff actions, then the backstage processes and supporting systems. It makes visible which internal dependency causes each customer-facing failure.
Related terms
All terms- Customer Journey MapA visualisation of everything a customer does, thinks and feels across the whole relationship with a company, including steps outside the product.
- User ResearchThe systematic study of users' goals, behaviour and context — through interviews, observation and analysis — to inform what gets designed and built.
- UX DesignThe design of how a product works from the user's point of view — what it does, in what order, and how it behaves when things go wrong.
- Information ArchitectureThe structure of a product's content and navigation — how things are grouped, labelled and related so people can find what they need.
Let's talk about your product.
Happy to look at what you're building and say where design would move the needle.
Contact Us