- Atlas
- Arts & Architecture
- Service Design
Service Design
Service design is the practice of planning and shaping services—the arrangements of people, processes, communications, and physical or digital touchpoints through which an organisation delivers value to those who use it.
11 frameworks, from 1970 to today · Design · Arts & Architecture
- Participatory Design 1970-Present
- Service blueprint 1984-Present
- Service Encounter Theory 1984-Present
- User-centered design 1988-Present
- Customer Journey Mapping 1990-Present
- User-Centred and Participatory Design 1990-Present
- Design Thinking 2005-Present
- Omnichannel Service Design 2010-Present
- Public-Sector Service Design 2010-Present
- Systems-Oriented Service Design 2010-Present
- Transition Design 2015-Present
Overview
Service design is the practice of planning and shaping services—the arrangements of people, processes, communications, and physical or digital touchpoints through which an organisation delivers value to those who use it1. Where product design shapes an object, service design shapes an experience that unfolds over time and often across many separate encounters: booking a flight, checking into a hospital, opening a bank account, renewing a licence. What is at stake is that most of what people experience as a "service" is invisible to any single department that runs it. A customer meets a website, a phone agent, a queue, a form, and a bill as one continuous thing; the organisation behind them meets them as separate silos. Service design exists to close that gap—to make the whole journey designable, and to design it around the person on the other side rather than around the org chart.
From industrial engineering to the service encounter
The intellectual roots lie in mid-twentieth-century management and marketing rather than in art school. Service industries were long treated as a residual category—everything not manufacturing—and early work tried to make them legible. In the 1970s and 1980s, marketing scholars began arguing that services have distinct properties: they are intangible, produced and consumed at the same moment, and variable from one delivery to the next. From this came service encounter theory, the study of the "moment of truth" when a customer and a service provider meet. The term is usually credited to Richard Normann, whose 1984 book Service Management framed the encounter as the point where a service is created in the interaction itself. The insight was that quality is not built into a product at the factory but performed, live, by frontline staff and customers together—so the design problem includes the behaviour, script, and setting of that meeting, not just the back-office process.
A parallel strand came from operations. G. Lynn Shostack's 1984 Harvard Business Review article "Designing Services That Deliver" argued that services could be designed with the same rigour as products, and introduced the idea of mapping a service's components and their relationships. This is the direct ancestor of service blueprinting: a diagram that lays out, in parallel lanes, what the customer does, what frontline staff do, what backstage staff and systems do, and where the visible "line of interaction" and "line of visibility" fall12. The blueprint's power is that it shows the hidden machinery behind a visible moment—why a checkout is slow, say, by tracing it to a backstage approval step the customer never sees.
Design methods enter the picture
Through the 1980s and 1990s, design's own methodological tradition fed in. The Design Methods movement had, since the 1960s, tried to make design a systematic, teachable process rather than a mysterious craft skill3. User-centred design, codified in the 1980s (notably in Donald Norman's The Design of Everyday Things, 1988), insisted that designers study real users' tasks and mental models rather than designing from the maker's intuition. Participatory design, emerging from Scandinavian workplace-democracy projects in the 1970s, went further: the people affected by a system should help design it, not merely be observed. Both ideas migrated from products and software into services, where the "user" is a customer or citizen and the "system" is an organisation.
The 1990s saw the first self-conscious service design practice. The Cologne-based agency Köln International School of Design and consultancies such as Livework (founded 2001 in Norway and the UK) and Engine (founded 2000 in the UK) began selling service design as a distinct offer, borrowing tools from interaction design and ethnography. Customer journey mapping became the signature artefact: a timeline of a person's experience across touchpoints, annotated with their actions, thoughts, and emotional highs and lows. Where the blueprint maps the organisation's machinery, the journey map maps the customer's lived sequence—the two are complementary views of the same service.
Design thinking and the spread into organisations
The 2000s brought service design into the mainstream of business and public life, carried by the broader rise of design thinking—the packaging of designerly habits (empathy with users, rapid prototyping, iteration, reframing problems) as a general problem-solving method for non-designers. IDEO's work and the design school at Stanford (the Hasso Plattner Institute of Design, "the d.school," founded 2005) popularised it; Tim Brown's 2008 Harvard Business Review article "Design Thinking" gave it a canonical statement. For service design this was double-edged: it won budgets and seats at the strategy table, but critics argued that design thinking's workshop-and-sticky-note version often stripped out the craft, evidence, and implementation that real service change requires.
In the public sector the same years saw public-sector service design take hold, especially in the UK, Denmark, and later Singapore and Australia. Governments, facing complex citizen journeys that cut across agencies, adopted journey mapping and co-design to redesign everything from tax filing to hospital discharge. The UK's Policy Lab (founded 2014) and the Government Digital Service (2014) are prominent examples of embedding design methods in state services. Here the "user" is also a citizen with rights, and the design problem includes equity and access, not just satisfaction.
Systems, channels, and the widening frame
As digital channels multiplied, omnichannel service design became a central concern: making a service coherent whether a person starts on a phone app, continues in a branch, and finishes with a letter4. The problem it addressed was channel fragmentation—each channel optimised separately, producing a service that felt like several unrelated ones. The design response was to treat the whole channel mix as one system with consistent state and handoffs.
That impulse pushed toward systems-oriented service design, which treats a service not as a linear journey but as part of a wider socio-technical system with feedback loops, multiple actors, and unintended consequences. Tools from systems thinking—causal loop diagrams, actor maps, service ecosystems—entered the designer's kit. The claim was that many service failures are systemic (incentives, policy, infrastructure) and cannot be fixed at the touchpoint alone.
Most recently, transition design has extended the field's horizon from improving existing services to shaping long-term societal change—sustainability, equity, and the redesign of whole systems over decades. Associated with Carnegie Mellon's School of Design (where Terry Irwin and colleagues articulated it in the 2010s), it draws on systems and futures thinking and asks designers to work at the scale of transitions rather than single services. It remains more a research and educational programme than a settled commercial practice.
Where the field stands
Today service design is an established profession with its own conferences, degree programmes, and in-house teams in banks, hospitals, and governments, alongside a research community publishing in journals such as The Design Journal and Touchpoint. Its core toolkit—blueprints, journey maps, co-design workshops, prototyping of service moments—descends directly from the strands above: operations mapping, encounter theory, user-centred and participatory methods, and design thinking's process vocabulary. The live questions are the ones its history keeps returning to: how to design for many actors with conflicting interests rather than a single "user"; how to move from mapping a system to actually changing it; how to measure whether a redesigned service is genuinely better and for whom; and whether the field's methods, born largely in wealthy Northern European and North American contexts, travel well to very different settings.
References
- Service design (introduction, Early service design and theory), Wikipedia
- Service blueprint (History), Wikipedia
- Design methods (Background), Wikipedia
- Omnichannel, Wikipedia
The frameworks of Service Design
Each framework is a way of working the field has used: when it held, and the question it answers.
- 1970-Present
- 1984-Present
- 1984-Present
Service Encounter Theory
What happens when a customer meets a service provider?
- 1988-Present
User-centered design
How should designers understand the people they design for?
- 1990-Present
Customer Journey Mapping
What does a person experience across a whole service?
- 1990-Present
User-Centred and Participatory Design
How can users and designers shape services together?
- 2005-Present
- 2010-Present
Omnichannel Service Design
How can a service stay coherent across many channels?
- 2010-Present
Public-Sector Service Design
How should governments redesign services for citizens?
- 2010-Present
Systems-Oriented Service Design
How do services fit within wider social systems?
- 2015-Present
How the ideas connect
Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.
User-Centred and Participatory Design grew out of Participatory Design
Participatory design's commitment to involving affected people in shaping systems was carried into service design practice in the 1990s, where co-design workshops with customers and staff became a standard method. The later label simply names the fusion of participatory and user-centred traditions as applied to services.
Carried by Scandinavian workplace-democracy projects; Köln International School of Design.
Public-Sector Service Design influenced by Participatory Design
Public-sector service design adopted co-design workshops with citizens and frontline staff, a method inherited from participatory design's workplace-democracy projects. Governments redesigning cross-agency citizen journeys used these participatory techniques to involve service users directly.
Carried by UK Policy Lab; Government Digital Service.
Customer Journey Mapping influenced by Service blueprint
Service blueprinting's parallel-lane mapping of frontstage and backstage activity established the diagrammatic vocabulary that journey mapping adapted to the customer's lived sequence. Journey mapping kept the timeline structure but shifted the viewpoint from organisational machinery to customer experience.
Carried by G. Lynn Shostack; Designing Services That Deliver (1984).
Systems-Oriented Service Design influenced by Service blueprint
Systems-oriented service design built on blueprinting's insight that hidden backstage machinery drives visible failures, widening the frame from a single organisation's process to socio-technical systems with feedback loops and multiple actors. Causal loop diagrams and actor maps supplemented the blueprint's lanes.
Customer Journey Mapping influenced by Service Encounter Theory
Service encounter theory's focus on the moment of truth and the customer's experience of frontline interaction supplied the experiential emphasis that journey maps annotate as emotional highs and lows. The mapping artefact made the sequence of encounters visible as a single timeline.
Carried by Richard Normann; Service Management (1984).
User-Centred and Participatory Design grew out of User-centered design
User-centred design's insistence on studying real users' tasks and mental models was absorbed into service design practice, where the 'user' became the customer or citizen. The combined label marks the merger of this tradition with participatory methods in service contexts.
Carried by Donald Norman; The Design of Everyday Things (1988).
Design Thinking influenced by User-centered design
Design thinking packaged user-centred design's empathy-with-users stance and iterative prototyping into a general method for non-designers. IDEO and the Stanford d.school drew directly on the user-centred tradition when popularising it in the 2000s.
Carried by IDEO; Hasso Plattner Institute of Design; Tim Brown.
Omnichannel Service Design influenced by Customer Journey Mapping
Omnichannel service design extended journey mapping's timeline across multiple channels, treating the whole channel mix as one continuous experience with consistent state and handoffs. The journey map's cross-touchpoint view was the basis for diagnosing channel fragmentation.
Public-Sector Service Design influenced by Customer Journey Mapping
Journey mapping became the central tool of public-sector service design, used to visualise citizen journeys that cut across separate government agencies. The UK Policy Lab and similar units applied journey maps to tax filing, hospital discharge and licence renewal.
Carried by UK Policy Lab.
Transition Design grew out of Systems-Oriented Service Design
Transition design grew out of systems-oriented service design's claim that service failures are systemic, extending the horizon from improving existing services to shaping long-term societal transitions. Terry Irwin and colleagues at Carnegie Mellon drew on systems and futures thinking to reframe design at the scale of decades.
Carried by Terry Irwin; Carnegie Mellon School of Design.
Beyond the field
Where Service Design's ideas came from in other fields, and what they led to there: the strongest 12 of 43 links.
Customer Journey Mapping grew out of Service blueprint in Service Operations
Journey mapping is a refinement of the service blueprint's front-stage sequence, simplified and refocused on the customer's perspective rather than operational process detail.
Carried by G. Lynn Shostack.
Customer Journey Mapping grew out of Service blueprint in Services Marketing
Customer journey mapping grew directly out of the service blueprint, taking its timeline of customer-visible steps and recasting it as a narrative of the customer's experience across touchpoints.
Carried by G. Lynn Shostack.
Design Thinking influenced by Reflective Practice in Design Research
Schön's reflective practice, especially The Reflective Practitioner (1983), supplied design thinking with its account of design as reflection-in-action and its critique of technical rationality; later design thinking writers drew directly on it.
Carried by Donald Schön; The Reflective Practitioner (1983).
Omnichannel Service Design grew out of Service Design in Interaction Design
Omnichannel service design grew out of service design: the same customer-journey and touchpoint methods were extended to coordinated cross-channel delivery.
Systems-Oriented Service Design grew out of Service Design in Interaction Design
Systems-oriented service design is service design extended with systems thinking, growing directly out of the service design field.
Transition Design influenced by Sustainability Transitions in Sustainability Science
Sustainability transitions research (socio-technical transitions, multi-level perspective) supplied the core theory that Transition Design drew on and adapted for design practice.
Participatory Design influenced Service Design in Interaction Design
Participatory design's stakeholder workshops and co-design techniques were adopted into service design as methods for involving customers and staff.
Participatory Design influenced by Sociotechnical system in Participatory Design
Sociotechnical systems theory, developed at the Tavistock Institute from the 1950s, supplied participatory design with the idea that workers should jointly optimise social and technical systems, carried into Scandinavian cooperative design.
Carried by Eric Trist; Fred Emery.
Participatory Design influenced by Participatory democracy in Democratic Theory
Participatory design drew on ideals of participatory democracy, especially workplace democracy movements, when Scandinavian researchers began involving workers in the design of computer systems.
Carried by Kristen Nygaard.
Service Encounter Theory influenced Self-Service Technology Research in Services Marketing
Self-service technology research framed the SST as a service encounter in which the customer performs the employee's role, taking the encounter concept from service encounter theory.
Service Encounter Theory influenced by Service blueprint in Service Operations
Service blueprints gave encounter researchers a way to locate and analyse the moments of customer-provider contact within the wider service process.
Carried by G. Lynn Shostack.
Service Encounter Theory influenced by Nordic School of Services Marketing in Relationship Marketing
The Nordic School's view of services as relational processes shaped service encounter theory's treatment of interactions as episodes within ongoing relationships.
Carried by Christian Grönroos; Evert Gummesson.

Service Design is a planet in Nousfarer
Its city has a tower for each of these 11 frameworks. Land, walk in, and climb one concept at a time.
Land on Service DesignRelated fields
Fields its ideas are linked to
- Service Operations 7 links
- Human Computer Interaction 5 links
- Interaction Design 5 links
- Retailing 4 links
- Services Marketing 4 links
- Industrial Design 3 links
- Participatory Design 2 links
- Design 1 link
- Design Research 1 link
- Interaction Design Theory 1 link
- Speculative Design 1 link
- Sustainability Science 1 link