Definition
Service design is the practice of designing the end-to-end experience of a service across customer touchpoints, employee processes, and back-end systems — including the parts the customer never sees.
Service design extends UX past the screen. A bank's website might be excellent; the call centre, the ATM and the in-branch experience are all part of the service. Service designers map the full journey across channels, identify failure points (often at the seams between channels), and redesign the system, not just the interface.
The classic deliverable is a service blueprint — a diagram showing the customer journey, touchpoints, frontstage employee actions, backstage processes, and supporting systems. The blueprint exposes where the wheels come off — usually at handoffs between teams or between digital and human channels.
Origin
Lynn Shostack's 1984 HBR article 'Designing Services That Deliver' introduced service blueprints. The discipline matured in the 1990s through Live|Work and IDEO. Government and healthcare adopted service design through the 2010s; UK GDS and Singapore GovTech remain the highest-profile practitioners.
How it works
- Pick a customer journey to redesign (e.g. opening an account, filing a claim, returning a product).
- Map the customer-facing actions (frontstage).
- Map the employee-facing actions (backstage).
- Map the supporting systems and data flows.
- Mark the failure points — where the customer or employee gets stuck.
- Redesign the seams. Most service-design wins come from fixing handoffs.
When to use it
Use when
- When the customer experience spans multiple channels (web, app, phone, in-person).
- When complaints concentrate at handoffs between teams.
- After a digital transformation — the digital piece may be great while the rest of the service degrades.
Skip when
- When the product is purely digital and self-serve.
- Without leadership buy-in. Service design recommendations cross team boundaries; they fail without authority.
Key metrics
- Customer satisfaction (CSAT) by journey stage.
- Time-to-resolution across the full service.
- Cost-to-serve per customer.
- Frontline employee NPS — the second-most-predictive metric of customer experience.
Examples
- The mobile app was perfect; the customer was stuck in the call centre. Service design fixed the handoff.
- We blueprinted the claims process and found 11 systems each held a piece of one customer's data.
- Service design: stop optimising the screen and start optimising the seams.
In practice at Makreate
Makreate's UX work occasionally extends into service design — particularly for clients with operations, support and digital all touching the same customer. A recent enterprise client had a brilliant onboarding flow that handed off to a back-office team using a different system; the seam was where 40% of accounts went dormant. We mapped the full blueprint, identified four failure points, and recommended changes to both the digital flow and the backstage process. The client's ops team made the backstage changes; we shipped the digital ones; activation climbed from 38% to 71% in a quarter.
UX Design →Common mistakes
- Mapping the customer journey without the backstage. Half the picture is invisible.
- Treating service design as 'UX for non-digital'. It's broader than that.
- Designing without involving frontline staff. They know where the seams break.
- Recommending changes nobody can act on. Service design needs cross-team authority to ship.
Frequently asked
Service design vs UX design?
UX is one piece of service design. UX designs digital touchpoints; service design covers all touchpoints plus the systems behind them.
Who should run service design?
A service designer if you have one; a senior UX designer with operations experience can fill the role for smaller engagements.
Where does service design fit organisationally?
It crosses CX, UX, operations and product. Most successful programs report to a Chief Customer Officer or equivalent.