Evidence Domain

Service Design

What it studies

The design of services as systems: user journeys, touchpoints, front-stage and back-stage operations, and the orchestration of people, processes and artefacts into coherent service experiences. It supplies the methods — journey mapping, blueprinting, prototyping — for designing what happens rather than what stands.

Why it matters

A workplace is a service as much as a space: booking, arrival, IT, catering, support and events are operated systems whose failures register as workplace failures. Service design gives the methodology its process-side design discipline — the blueprint that connects an employee's journey to the back-stage operations that make it work or break it.

Questions it answers
  • What service journeys does this workplace consist of, and where do they fail?
  • Which back-stage operations produce the front-stage experience?
  • How should new services (and their norms) be prototyped before rollout?
  • Where do spatial design and service design depend on each other?
Evidence sources
  • Service design methodology and service management research
  • Journey and blueprint evidence from the workplace's own operation
  • Service failure data: complaints, requests, abandonment
  • Prototype and pilot results
Design and policy implications

Workplace services blueprinted alongside spatial design; booking, arrival and support journeys designed and tested as deliberately as settings; service prototypes run before building-wide rollout; norms treated as service components with owners and operations.

Related methods
Common misuse

Journey-map decoration: personas and journey posters produced as workshop artefacts, disconnected from the back-stage operations and budgets that would make them real. A journey map without a blueprint is an aspiration with sticky notes.

Further research

Service design's integration with spatial design remains more practised than theorised; the workplace is arguably its richest under-documented application domain.