Key Takeaways
Design the whole service, not just its visible interface.
The experience is the design. Service design thinking is an interdisciplinary way to shape how a service works and feels, rather than a specialty concerned only with its appearance. Its concern can include staff behavior, digital interfaces, organizational processes, physical spaces, and the relationships connecting them. A polished website cannot rescue a service whose policies or support systems repeatedly frustrate people. The book’s own creation followed this logic: editors interviewed students and educators, invited practitioners to contribute tools, and used 1,188 online votes to select methods for inclusion. The textbook was treated as a designed experience, not merely a container for information.
Look across the system. A service succeeds when its parts make sense together from the user’s point of view. That requires understanding the organization’s needs too, because the experience depends on what staff and systems can reliably deliver.
The book’s strongest move is to shift design from the object to the relationships that make an experience possible. This resembles systems thinking: a change in one component can alter behavior elsewhere, sometimes in unexpected ways. It also explains why interface redesign alone so often disappoints. Still, “the whole service” can become an impossibly broad assignment. Teams need to define which users, moments, and organizational boundaries matter most, then revise that scope as evidence accumulates. Holism is best treated as disciplined attention to connections, not a claim that every consequence can be anticipated.
Study people in their real context, beyond what demographics predict.
Context explains the person. Two customers can share age, income, family status, and other statistics while having sharply different habits, expectations, and motivations. The book illustrates this with a pair of British men who match on a list of demographic traits but differ dramatically in identity and everyday life. Such profiles can describe a market; they cannot, by themselves, explain what a person needs from a service.
Watch, ask, and listen. Design ethnography means studying people’s routines and experiences to inform design. Researchers can observe a service in use, interview someone where the activity happens, or invite participants to record experiences themselves. Seeing a customer navigate a process may expose a problem they would not think to mention in a survey. The aim is to understand the circumstances behind behavior, not just collect stated preferences.
Contextual research helps correct a familiar weakness of segmentation: groups that look alike on paper can behave differently in practice. This is compatible with cognitive science, where decisions are understood as responses to particular environments and cues, rather than as stable preferences detached from circumstance. Observation also has limits. A researcher’s presence can change behavior, and a handful of vivid stories cannot establish how common a pattern is. Strong teams combine qualitative insight with other evidence, and treat personas as research summaries, not as fictional people whose imagined opinions replace actual users.
Treat a service as a journey, not a single encounter.
Time shapes the experience. A service unfolds through connected interactions, or touchpoints, across time. A haircut, for instance, begins before the customer enters the shop: a need arises, the person discovers an option, books, arrives, receives the service, pays, and remembers the visit afterward. Each moment influences the next. A long pause can feel reassuring in one setting and irritating in another; a rushed interaction can feel efficient or stressful.
Map the whole sequence. A customer journey map is a visual account of a person’s experience, including touchpoints and, where possible, the feelings and circumstances associated with them. It can reveal moments of confusion, unnecessary effort, or opportunity. It should include informal influences such as advice from friends, not only interactions controlled by the provider. The book compares a well-orchestrated service to a performance, with visible interactions supported by backstage preparation.
Journey mapping makes duration and transition visible, which conventional process charts often miss. It can help teams notice that an apparently minor delay accumulates across several steps, or that a customer begins forming expectations before the organization considers the service to have started. The theatrical analogy is useful because it connects pacing, anticipation, and behind-the-scenes coordination. Yet a map can give a false impression of one standard path. People take detours, use different channels, and leave altogether. Multiple journeys and exceptions should be considered, rather than treating an attractive diagram as a complete picture of lived experience.
Invite users, staff, and partners to shape the service together.
Many people make one service. A customer may encounter front-line employees, managers, back-office teams, contractors, websites, machines, and partner organizations. Each can shape the experience, even when the customer sees only one part of the system. Co-creation means involving relevant stakeholders in exploring problems and developing possible responses. It does not mean handing every decision to a workshop. A design team still has to interpret, select, and test ideas.
Make participation workable. People may stay quiet if they fear looking foolish, disagreeing with a manager, or disrupting familiar routines. A facilitator can use clear prompts and simple shared materials to help participants contribute. The book’s examples include employees and customers helping to develop services together. This can improve the design and create familiarity with the changes people may be asked to deliver. The earlier that practical knowledge enters the process, the less likely a concept is to collide with everyday work.
Participation brings distributed knowledge into the room. Front-line workers often understand operational workarounds that senior teams never see, while customers can identify burdens that internal language makes seem normal. This is a governance advantage as well as a creative one: people who help shape a change may be better equipped to explain or sustain it. But participation is not automatically representative or fair. A confident participant can dominate, and the people most affected may be hardest to recruit. Good facilitation must attend to power, access, and whose perspective is missing, not just count how many people attended.
Rehearse an intangible service before committing to its full launch.
Make the future testable. A service prototype is a simulation of a proposed service experience. It might be a rough roleplay, a paper interface, a small model of a service environment, or a fuller enactment with staff and customers. Because a service cannot simply be placed on a table, a description alone often fails to show how people will respond. Stories, sketches, and staged interactions give participants something concrete to react to.
Learn while change is cheap. In service staging, people act out a scenario, try different roles, and adjust the design as problems appear. A clinic project at the University of Pittsburgh Medical Center used observation, patient discussions, storyboards, and concepts to rethink waiting and wayfinding. The team also tested ideas with patients. Some proposed changes were simple, such as rearranging chairs to make room for wheelchair users. Early tests help reveal whether a concept works before the organization invests in a complete rollout.
Prototyping converts speculation into observable behavior. That is valuable because people often struggle to judge a future service from an abstract description, while a rough rehearsal can expose awkward handoffs, confusing language, or emotional discomfort. The technique also supports organizational learning: participants can discuss a specific moment instead of arguing over vague aspirations. A prototype still is not proof of success. A staged encounter may lack the workload, incentives, or stress of real operations. Testing should therefore progress from low-cost simulations toward realistic settings, with findings treated as evidence to refine, not as a ceremonial sign-off.
Make invisible work visible, then connect it to customer-facing moments.
Show what supports the encounter. Services often depend on backstage tasks customers do not see, from staff preparation to information systems and maintenance. A service blueprint is a visual description linking customer interactions with visible provider actions and the supporting work behind them. It helps teams locate breakdowns, duplicated effort, and dependencies that a customer-facing journey alone may conceal.
Use evidence with care. Physical or digital signs, messages, receipts, and other artefacts can make an intangible service easier to understand or remember. In a hotel, for example, a visible clue may help a guest recognize that housekeeping has occurred. But evidence can also become clutter or unwanted messaging. The useful question is not whether to add more visible material, but whether a clue clarifies an important part of the experience and fits the service’s overall sequence.
Blueprinting connects experience design to operational analysis. It resembles process mapping in engineering, but gives particular attention to what customers can see and where their actions depend on internal work. That connection is practical: a confusing customer interaction may originate in an unclear staff handoff, not in the interface itself. Making backstage work visible can also support accountability by clarifying who owns a failure. The risk is that a blueprint becomes a static chart that documents the intended process rather than the actual one. It should be checked against observation and updated when working conditions change.
Balance efficiency with the experience customers actually want.
Operational logic has consequences. Operations management often seeks consistent delivery, lower cost, and efficient use of resources. The book traces this logic through fast-food systems that standardize tasks, narrow roles, and sometimes ask customers to do work themselves. Such designs can make high-volume services faster and more predictable. They can also reduce discretion and make an experience feel impersonal when the customer needs flexibility.
Design the right mix. Digital interaction design distinguishes what a service does from how easy it is to use and how it makes people feel. A service may be functional yet hard to navigate, or straightforward yet unpleasant. The appropriate emphasis depends on the promise: a no-frills airline need not imitate a luxury brand, but its basic interactions still need to support the bargain it offers. Consistency matters across channels, staff, and systems, not only in the screen or storefront.
Efficiency and experience are not natural enemies. Clearer steps can reduce both customer effort and operating cost, while excessive standardization can transfer work or risk to users without acknowledging it. The important question is whose time and labor are being optimized. A self-service system may appear efficient to the provider while imposing complexity on customers who need human help. This makes service design a useful meeting point for operations research and human factors: performance measures should include reliability and throughput, alongside errors, accessibility, and the effort imposed on users.
Let customer evidence overturn the offer you thought was obvious.
Test the proposition, not just its presentation. SEB bank planned to bundle common services for hundreds of thousands of customers and believed an online offer would be attractive. In early tests, fewer than five percent of customers said they would sign up as presented. People missed the banner, misunderstood the package, and suspected the bank was pushing an unwanted credit card. The issue was not simply a bad page. Customers saw little reason to spend effort consenting to a change that mainly reduced the bank’s administrative burden.
Change the service itself. After several rounds of customer testing, SEB stopped asking customers to take an unnecessary action. It automatically moved affected accounts into the lower-cost package, explained the change by letter, and made the credit card optional. The case reports that all targeted customers were enrolled, exceeding the original 80 percent goal, while card sales also surpassed campaign targets.
The SEB case shows why testing should be allowed to challenge the business proposition, not merely polish its wording. Customers were judging the exchange of value and effort, not failing to appreciate a clever campaign. This is closely related to behavioral economics: friction, ambiguity, and perceived loss can change whether an offer feels worthwhile. The case also raises a boundary condition. Automatic changes can benefit customers when the terms are clear and the change is favorable, but consent and choice remain important in other contexts. Customer-centered design should improve relevance without treating convenience as permission to remove meaningful control.
Treat implementation as part of design, not the handoff after it.
A strong concept can still stall. Service design requires organizational change as well as a new customer journey. Employees need to understand the intended experience, see how their work contributes, and have the support to deliver it. Storyboards, roleplay, and shared blueprints can help translate an idea into behavior and clarify responsibilities. Involving staff early is more effective than presenting them with a finished plan and expecting effortless adoption.
The clinic case is a warning. The UPMC design team studied patients, families, physicians, and staff, then proposed a set of changes, including a welcome booklet and new ways to communicate. The clinic staff valued the work and began making small adjustments, but leadership and organizational changes followed, and the project was not implemented as a whole. The case shows that a useful design process can build understanding and local initiative, yet still lack the authority or continuity needed to secure broader adoption.
Implementation is a question of institutional capacity, not merely persuasive presentation. Staff commitment helps, but changes also depend on budgets, leadership continuity, incentives, and ownership after a project team leaves. The UPMC example is especially useful because it resists a simple success story: the work improved insight and encouraged local action, yet the larger package did not proceed. That distinction matters for evaluation. Teams should ask not only whether a concept is desirable, but who has the mandate, resources, and time to maintain it. Implementation planning belongs inside the design problem from the beginning.
Use service design to improve social systems, not just commercial experiences.
Design has public consequences. Social design applies design processes to changing societal needs. It can help a group understand a complex issue, involve affected people, and turn an abstract proposal into something others can assess. The book’s ColaLife case began with an idea to use Coca-Cola’s distribution network to help deliver medical supplies to children in Africa. Online supporters and people with different skills helped develop the idea, make it understandable, and build partnerships for a pilot in Zambia.
Start with the lives involved. The book also argues that designing a product or service means understanding the everyday activity it enters. A device for older people, for example, should not be designed from technical specifications alone; it must fit the person’s home, abilities, relationships, and routines. This broader view makes service design a way to coordinate people, tools, and institutions around a human need.
The social-design argument extends the book’s method beyond customer satisfaction toward public value. Complex social problems rarely belong to one profession or organization, so shared maps and prototypes can make dependencies discussable across boundaries. ColaLife illustrates how a proposal can gather a network around a practical possibility. Yet collaboration and a compelling concept do not establish long-term impact. Social projects must also confront local authority, infrastructure, distribution, and who defines success. A human-centered process is a valuable starting point, not a substitute for accountability to the communities it aims to serve.
Analysis
This book is best understood as a field guide assembled at a moment when service design was still defining its vocabulary. Its central contribution is less a single new tool than a change in unit of analysis: away from the isolated product, transaction, or interface, toward an experience produced over time by people, organizations, technologies, and physical settings. The five guiding commitments, the research methods, and the case studies all support this shift.
The book’s practical strength is its insistence that design is investigative and iterative. The SEB case makes the point unusually clearly: customer research did not merely improve a web page, it exposed that the proposed customer action made little sense. The UPMC case adds an important complication. Insight, prototypes, and staff enthusiasm cannot guarantee adoption when organizational authority and continuity fail. Together, these cases make the book more credible than a collection of uncomplicated success stories.
Its interdisciplinary ambition is also a source of tension. Marketing, interaction design, ethnography, operations, and strategy contribute different definitions of value and different standards of evidence. Combining them can produce a richer service, but it can also conceal conflict. Lower cost for a provider may mean more effort for a customer; a seamless journey may require extensive backstage labor. Service design therefore benefits from asking who gains, who carries the work, and whose experience is missing from the research.
The toolbox should be read as a set of adaptable instruments, not a recipe. Maps and personas make complexity discussable, but they are representations, not the service itself. Their usefulness depends on whether they remain connected to observation, operational realities, and decisions with owners. The book’s durable lesson is that good service design joins empathy to implementation: understand how people actually live through a service, make the invisible system legible, test alternatives cheaply, and ensure the organization can sustain what the evidence supports.
Review Summary
This is Service Design Thinking receives mixed reviews. Readers appreciate its overview of service design concepts and tools, but many find it too basic or repetitive. The book's structure and design are seen as innovative by some, distracting by others. Positive aspects include real-world examples and a useful toolbox section. Criticisms focus on lack of depth, outdated case studies, and excessive emphasis on the importance of service design. Overall, it's considered a decent introduction to the field, but not comprehensive enough for experienced practitioners.
People Also Read
Glossary
Service design thinking
Interdisciplinary service designAn approach to improving or creating services by combining methods from design, management, research, and operations. It considers the experience from the user’s perspective while also attending to the people, processes, physical or digital touchpoints, and organizational systems needed to deliver it. The book presents it as a way of thinking, not a separate single discipline.
Customer journey map
Map of service experienceA visual account of a person’s experience with a service over time. It links touchpoints such as conversations, websites, visits, and messages, and can include the person’s circumstances, actions, and emotional responses. Teams use it to find weak moments, compare different journeys, and identify opportunities to improve the overall experience.
Service blueprint
Map of delivery systemA visual representation connecting a user’s actions and visible interactions with the provider’s front-stage work and backstage processes. It can also show supporting systems, staff responsibilities, and other parties involved in delivery. By linking the customer experience to the work that produces it, a blueprint helps teams identify dependencies, gaps, and duplication.
Design ethnography
Contextual research for designQualitative research conducted within a design process to understand people’s everyday routines, motivations, concerns, and experiences. Methods can include observation, contextual interviews, and participant-generated material. The findings are shaped so that designers and other stakeholders can use them to develop and evaluate concepts, rather than being isolated as research reports.
Cultural probes
Participant self-documentation kitA package of prompts and materials given to research participants so they can document aspects of their own lives over time. It might contain a diary, camera, map, or activity instructions. Because participants record experiences without a researcher constantly present, probes can surface intimate or easily forgotten details and inspire design ideas.
Service prototype
Simulation of service experienceA testable enactment of a proposed service, ranging from an informal roleplay to a fuller recreation involving people, props, and touchpoints. Prototypes help participants experience a service concept rather than imagine it from description alone. Teams observe what works, gather responses, and revise the concept before broader implementation.
AT-ONE
Five service innovation lensesA workshop approach for exploring early service concepts through five complementary perspectives. The lenses examine the people and organizations involved, the points of contact with customers, the proposition being delivered, the needs being addressed, and the experience created. Workshops can be run separately or combined to expand and focus the solution space.
Customer Journey LAB
Iterative customer research workshopA workshop-based approach described in the NL Agency case for understanding and improving customer experience. Participants map stakeholders, create customer profiles, trace journeys and emotional highs and lows, prioritize issues, develop ideas, and connect proposed changes to service delivery. It aims to establish an ongoing conversation between an organization and its customers.
FAQ
What's "This Is Service Design Thinking" about?
- Interdisciplinary Approach: The book introduces service design thinking as an interdisciplinary approach that combines methods and tools from various fields to improve service experiences.
- Structure: It is divided into three main parts: Basics, Tools, and Cases, each focusing on different aspects of service design.
- Target Audience: It is intended for a wide audience, including students, teachers, researchers, managers, and company owners from diverse professional backgrounds.
- Purpose: The book aims to serve as an introduction, reference, and case study book, providing inspiration and motivation for future work in service design.
Why should I read "This Is Service Design Thinking"?
- Comprehensive Guide: It offers a thorough introduction to the principles and practices of service design thinking.
- Practical Tools: The book provides a toolkit of methods and tools that can be implemented in real-world service design projects.
- Case Studies: It includes case studies that illustrate how service design thinking is applied in various contexts.
- Community-Driven: The book is created with input from the service design community, making it a collaborative and well-rounded resource.
What are the key takeaways of "This Is Service Design Thinking"?
- Five Principles: The book outlines five core principles of service design thinking: user-centered, co-creative, sequencing, evidencing, and holistic.
- Iterative Process: Service design is an iterative process that involves exploration, creation, reflection, and implementation.
- Interdisciplinary Nature: Service design thinking integrates methods from design, management, engineering, and other fields.
- Focus on Experience: The ultimate goal is to enhance customer experiences and create value for both users and service providers.
What are the best quotes from "This Is Service Design Thinking" and what do they mean?
- "Services should be experienced through the customer’s eyes." This emphasizes the importance of understanding and designing services from the user's perspective.
- "Everyone can be creative!" Highlights the book's belief in co-creation and involving all stakeholders in the design process.
- "Imagine a service as a movie!" Encourages viewing services as dynamic sequences of interactions, much like scenes in a film.
- "Make the intangible tangible!" Stresses the need to visualize and evidence services to make them more understandable and relatable.
How does "This Is Service Design Thinking" define service design?
- Interdisciplinary Approach: Service design is defined as an interdisciplinary approach that combines methods and tools from various disciplines.
- Focus on Experience: It aims to create well-thought-out experiences using a combination of intangible and tangible mediums.
- Holistic and Integrative: Service design is described as a holistic, multi-disciplinary, and integrative field.
- Value Creation: The practice focuses on creating value for both users and organizations through improved service experiences.
What are the five principles of service design thinking according to Marc Stickdorn?
- User-Centered: Services should be designed from the customer's perspective.
- Co-Creative: Involves all stakeholders in the design process to ensure diverse input and collaboration.
- Sequencing: Visualizes services as sequences of interrelated actions to ensure a smooth flow.
- Evidencing: Makes intangible services tangible through physical artifacts and visualizations.
- Holistic: Considers the entire environment and context in which a service operates.
What is the iterative process of service design thinking as outlined in the book?
- Exploration: Understanding the problem from both the organization's and the customer's perspectives.
- Creation: Generating and developing solutions based on identified problems and insights.
- Reflection: Testing and refining ideas through prototyping and feedback.
- Implementation: Applying the refined solutions and managing change within the organization.
How does "This Is Service Design Thinking" integrate motivational psychology?
- Understanding Motivation: The book discusses motivation as the energization and direction of human behavior, crucial for designing effective services.
- Intrinsic vs. Extrinsic: It distinguishes between intrinsic motivation (internal) and extrinsic motivation (external) in the context of service design.
- Empowering Users: Service design should empower users by considering their motivations and needs.
- Visualizing Motivation: Suggests integrating motivation with journey mapping and service blueprinting to better understand user behavior.
What are some of the tools and methods presented in "This Is Service Design Thinking"?
- Stakeholder Maps: Visual representations of the various groups involved with a service to understand their interactions.
- Service Safaris: Exploring real-world service experiences to gain insights into customer needs and problems.
- Customer Journey Maps: Visualizing the user's experience through touchpoints to identify areas for improvement.
- Prototyping: Creating simulations of service experiences to test and refine concepts.
How does "This Is Service Design Thinking" address the challenges of service design research?
- Establishing Structure: The book highlights the need for a structured approach to service design research.
- Interdisciplinary Integration: Encourages integrating practices and ideas from non-design fields like marketing and engineering.
- Methodological Rigor: Emphasizes the importance of rigorous methodologies in service design research.
- Case Studies: Calls for more academically scrutinized case studies to build a robust body of knowledge.
What role does co-creation play in service design according to "This Is Service Design Thinking"?
- Collaborative Process: Co-creation involves working with stakeholders, including customers, staff, and management, to develop solutions.
- Diverse Perspectives: It brings together different viewpoints to ensure a comprehensive understanding of the service experience.
- Shared Ownership: Encourages a sense of shared ownership over the service design process and outcomes.
- Innovation Driver: Co-creation is seen as a key driver of innovation and improvement in service design.
How does "This Is Service Design Thinking" suggest implementing service design in organizations?
- Change Management: Emphasizes the importance of managing change effectively when implementing new service concepts.
- Employee Involvement: Involves employees from the beginning to ensure their support and understanding of the new service.
- Communication Tools: Uses various tools like storyboards and videos to communicate the service concept to stakeholders.
- Iterative Evaluation: Encourages ongoing evaluation and iteration to refine and improve the service over time.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.