# Service Design

Service design coordinates people, processes, touchpoints, and supporting systems so an organization can deliver a coherent user experience.

- Type: practice
- Domain: Leadership & teams
- Level: Foundational
- Last reviewed: 2026-10-20
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/service-design/>)

## What it means

Service design is the practice of shaping how a service works across the user’s interactions and the organization’s delivery activities. It includes digital and physical channels, staff responsibilities, policies, and backstage processes. A service blueprint is one artifact used in this practice, rather than the practice itself.

## Why it matters

A smooth website cannot compensate for a failed handoff to support or contradictory information at a physical location. Examining the whole service helps teams find problems whose causes and solutions cross interface or departmental boundaries.

## When to use it

Use service design when customer outcomes depend on several channels, teams, or organizations. A local interface improvement may be sufficient when the problem is contained; wider redesign requires access to operational evidence and decision makers.

## How it works

1. Define the user outcome and the service boundary.
2. Research users and the staff who deliver and support the service.
3. Map touchpoints, backstage work, dependencies, and breakdowns.
4. Develop changes to both the experience and its operational support.
5. Prototype key encounters and handoffs with the people involved.
6. Assign ownership and measure whether the revised service delivers the intended outcome.

## A practical example

A booking company finds that customers can request an accessible room online but staff never receive the requirement. The redesign adds confirmation, operational routing, and a follow-up owner. The screen change is only one part of fixing the failed handoff.

## Where it breaks

Teams may lack authority over the systems or policies creating a problem. Broad maps can become documentation without implementation. Service design also requires maintaining coordination as staffing, suppliers, and operating rules change.

## Common mistakes

- Reducing service design to a journey-map workshop.
- Improving customer-facing screens while ignoring delivery constraints.
- Mapping a whole service without an owner for improvements.

## Sources

1. [Service Design 101](<https://www.nngroup.com/articles/service-design-101/>) — Nielsen Norman Group · Professional guidance
2. [2\. Solve a whole problem for users](<https://www.gov.uk/service-manual/service-standard/point-2-solve-a-whole-problem>) — Government Digital Service · Government guidance

## Related topics

- [Service Blueprint](<https://wiki.soroush.uk/topic/service-blueprint/>)
- [Customer Journey Map](<https://wiki.soroush.uk/topic/customer-journey-map/>)
- [Ecosystem Map](<https://wiki.soroush.uk/topic/ecosystem-map/>)
