12 Books Every Service Designer Should Read

Service design has no single agreed curriculum. What a practitioner needs to read next depends on whether the immediate problem is a method, a theory, an organisation, or a stakeholder who will not commit to anything. These twelve books cover that whole range, and what follows explains what each one is actually for.

Which books should come first if the field is new to you?

The obvious first stop is This Is Service Design Doing — Marc Stickdorn, Markus Edgar Hormess, Adam Lawrence and Jakob Schneider (O'Reilly, 2018). It is the field's most widely used practitioner handbook, and its strength is that it stays close to daily work: research, journey mapping, blueprinting, prototyping, facilitation. It is a reference more than a narrative, and most people do not read it front to back. They open it when a specific method is about to be used on a real project, which is exactly how it was designed to be used.

Good Services: How to Design Services that Work — Lou Downe (BIS Publishers, 2020), is the shortest book here and often the most immediately useful. Downe writes from public service delivery and frames quality as a set of principles a service either meets or does not: it is easy to find, it explains its own purpose, it works in a way people expect, it requires as few steps as possible. The value of that framing is that it gives a team something to argue about concretely. A principle can be tested against a real booking flow or a real application form in an afternoon.

Service Design: From Insight to Implementation — Andy Polaine, Lavrans Løvlie and Ben Reason (Rosenfeld Media, 2013), sits between the two. It is older than most of this list and still the clearest account of how research insight becomes an implemented change rather than a workshop output. Read together, these three cover method, standard and delivery.

Where does the theory underneath the practice actually come from?

At some point the methods stop explaining themselves, and that is where Designing for Service: Key Issues and New Directions — Daniela Sangiorgi and Alison Prendiville (editors) (Bloomsbury Academic, 2017), earns its place. It is an academic collection rather than a handbook, gathering researchers who examine the systemic and relational side of service design directly. It is most useful to a practitioner who has already felt a method strain, because it names the assumptions causing the strain: a single protagonist, a single path, a service that can be understood fully from one vantage point.

The theory those researchers build on is set out in Service-Dominant Logic: Premises, Perspectives, Possibilities — Stephen L. Vargo and Robert F. Lusch (Cambridge University Press, 2014). Vargo and Lusch describe value as co-created through interaction among actors rather than delivered by a firm to a passive customer, and their later work replaced producer and consumer language with actor-to-actor networks. It is the most conceptually demanding book here.

It is also the one most often abandoned when read first. Placed fourth or fifth, it reads as an explanation rather than an abstraction.

What to read when mapping is no longer the hard part

Mapping Experiences: A Complete Guide to Creating Value through Journeys, Blueprints, and Diagrams — James Kalbach (O'Reilly, 2016), is the reference for anyone whose diagrams have started doing more than one job at once. Kalbach treats journey maps, blueprints, ecosystem maps and other alignment diagrams as a family of related instruments, each with a purpose and a failure mode, which is genuinely useful once a team owns several maps and cannot say what any of them is for. Orchestrating Experiences: Collaborative Design for Complexity — Chris Risdon and Patrick Quattlebaum (Rosenfeld Media, 2018), takes the next problem: coordinating many touchpoints, teams and channels so that a service holds together across all of them.

Both books eventually point at systems, which is why Thinking in Systems: A Primer — Donella H. Meadows, edited by Diana Wright (Chelsea Green Publishing, 2008), belongs on a service design list at all. Meadows explains stocks, flows, feedback loops, delays and leverage points in ordinary language. Anyone who has watched a well-designed improvement create a queue somewhere else in the organisation already has the intuition. This book gives it vocabulary.

Systems Thinking for Social Change — David Peter Stroh (Chelsea Green Publishing, 2015), applies that vocabulary to multi-organisation problems where no single actor is in charge.

Systems reading also sharpens a disagreement the field has not settled. Platform businesses such as Airbnb and Uber are read by some as the clearest working examples of an ecosystem coordinating many actors at scale, and by others as arrangements that extract value asymmetrically from the participants who create it. Both readings are defensible on the available evidence. None of these books resolves it, and neither will this list. What ecosystem reading does is complement journey work rather than replace it: the journey still describes the lived path, and the ecosystem describes the conditions that path depends on.

Why two of these books are about organisations rather than services

Service Design for Business — Ben Reason, Lavrans Løvlie and Melvin Brand Flu (Wiley, 2015), is written from an agency perspective and answers a question the more idealistic books avoid. It asks what service design changes about how work gets scoped, sold, resourced and defended commercially. For anyone who has to justify a research phase to a sceptical budget holder, that is not a peripheral concern.

Org Design for Design Orgs: Building and Managing In-House Design Teams — Peter Merholz and Kristin Skinner (O'Reilly, 2016), is about building and running in-house design teams: structure, seniority, hiring, where design should report and what happens when it reports to the wrong place. It is included because a very large share of service design failure is organisational rather than methodological. The blueprint is often correct and the organisation is often not shaped to act on it.

That pattern is worth naming plainly, because it is usually misread as a design problem. A team maps an application process, identifies the point where people give up, proposes a change, and then discovers that the change spans three departments with different budgets, different targets and no shared owner. Nothing in the research was wrong. The obstacle was structural, and structural obstacles do not yield to better artefacts. These two books are the ones that treat that obstacle as the actual subject rather than an inconvenience.

What to read when the evidence, not the design, is the weak link

Convivial Toolbox: Generative Research for the Front End of Design — Elizabeth B.-N. Sanders and Pieter Jan Stappers (BIS Publishers, 2012), is the outlier on this list and the one most likely to change how someone works. It is about generative research: the practice of giving people materials and structures that let them express needs and experiences they cannot easily articulate in an interview. Service design leans heavily on early qualitative work, and this is the most substantial treatment of how that work is actually constructed.

It pairs well with everything in the first section, because a good method applied to thin evidence still produces a confident, wrong answer.

There is a practical reason to put a research book on a service design list rather than assuming the research is somebody else's job. Services are generally experienced in fragments, across long periods, by people who are tired, rushed or anxious at the moment they use them. Someone booking a medical appointment or applying for financial support rarely describes that experience accurately from memory in a half-hour interview. Generative methods exist to reach what direct questioning tends to miss, and a service designer who cannot run that kind of session is dependent on whatever evidence happens to arrive.

How to sequence the twelve

A reasonable path is to start with Good Services and This Is Service Design Doing, add Service Design: From Insight to Implementation when delivery becomes the problem, and only then move to Sangiorgi and Prendiville and to Vargo and Lusch. Bring in Kalbach and Risdon and Quattlebaum when the artefacts multiply, Meadows and Stroh when the problem crosses organisational boundaries, and Reason, Løvlie and Brand Flu together with Merholz and Skinner when the constraint is clearly commercial or structural. Keep Sanders and Stappers for the moment the research itself feels thin.

Read in that order, the twelve build on each other. Read in any order at all, they still cover the four things this work keeps demanding: a method, a reason, an organisation, and evidence.

Companion resource: 📚 12 Books Every Service Designer Should Read