UX Glossary · S
Service design
Designing the whole service including the parts the customer never sees, so the visible parts can work.
Service design covers the entire service a person experiences, across channels and over time, including the staff, systems and processes behind it. G. Lynn Shostack set out the service blueprint in 1984, and it remains the discipline’s central artefact.
Front stage and back stage
A blueprint separates what the customer sees from what makes it possible:
- Physical evidence: what the customer encounters
- Customer actions: what they do
- Frontstage: staff and interfaces they interact with
- Backstage: staff actions they never see
- Support processes: the systems underneath
A line of visibility runs between frontstage and backstage. Most service failures originate below it, which is why fixing the interface alone so often fails.
Why it matters to product work
Digital products are frequently one touchpoint in a longer service. An excellent booking screen attached to a dispatch process that cannot honour the slot produces an unhappy customer, and no interface change fixes it.
The blueprint makes that visible, and it makes ownership visible, which is usually the real problem: every department owns its own step and nobody owns the sequence.
In practice
Look hardest at handoffs. The points where responsibility passes between teams or systems are where services break, because they are the only points nobody is accountable for.