Key Takeaways
Treat the whole customer experience as the offering, not just its core product.
Every layer shapes value. Customers encounter an organization through staff behavior, staff knowledge, processes, systems, and finally the underlying product or service. A failure at any layer can make the core offering feel worse. A study of hospital patients found that none of the 15 leading satisfaction factors concerned whether patients’ health improved. Instead, people emphasized information, considerate staff, involvement in decisions, and feeling cared for. Medical outcomes still matter, especially when treatment fails, but patients often take competent treatment for granted and judge the surrounding experience closely.
Design around the lived experience. A new burger recipe cannot compensate for a confusing order, just as a trusted bank can still frustrate customers with a painful login. The organization’s task is not only to improve what it sells, but to improve how people encounter and use it.
This reframing connects service design to systems thinking: perceived quality emerges from interactions among components, not from a single feature considered in isolation. It also explains why frontline behavior and mundane processes can carry strategic weight. Yet satisfaction is not a substitute for effectiveness. A pleasant hospital stay cannot compensate for unsafe treatment, and a charming interface cannot rescue an unreliable product. The useful distinction is between the value delivered and the conditions that let people access it. Strong design protects both.
Map the full journey across departments before optimizing any single handoff.
Silos make customers do the joining. A customer’s experience may pass through sales, human resources, IT, legal, and operations, while each department measures its own performance. Traditional process diagrams can miss what happens outside the organization, including waiting, advice from friends, and third-party reviews. Dave Carroll’s damaged guitar became a nine-month dispute with United Airlines. After the company refused his claim, he made a music video that reached one million views in four days. Reports linked the story to a substantial fall in the airline’s market value, although the precise impact is not established here.
Design across boundaries. The lesson is not that every complaint becomes viral. It is that a customer can experience the company as one system, while the company experiences the customer as a series of departmental cases. Shared views of the journey help teams see where their decisions collide.
The episode illustrates a mismatch between organizational boundaries and the boundaries customers use. In organizational sociology, departments often develop local goals and specialized language; those can improve expertise while making coordination harder. A shared journey gives teams a common object to discuss without requiring them to abandon their specialist knowledge. Still, maps cannot erase power differences. A department with budget authority may override a customer-centered recommendation, so cross-functional understanding needs decision rights and accountability behind it.
Observe real behavior, then make every insight traceable to evidence.
Research should challenge the brief. Service design research investigates people’s behavior, needs, and context rather than treating an initial request as the true problem. Interviews can reveal why an experience matters; observation can expose gaps between what people say and what they do; quantitative measures can show how widespread a pattern may be. The book recommends combining methods, researchers, and data types so conclusions do not rest on one lens. Teams can stop qualitative fieldwork when additional research no longer reveals meaningful new patterns, a judgment known as theoretical saturation.
Keep the evidence connected. In a project to prevent electricity shutoffs in Germany, the team linked customer statements to research insights, opportunity areas, concepts, and the eventual service. That trail made decisions easier to inspect and harder to replace casually with opinion. Research-based maps and personas should also be distinguished from early drafts built on assumptions.
The approach resembles scientific inquiry in its emphasis on explicit questions, evidence, and revisable interpretations. Traceability is especially valuable when a project crosses departments, because it lets people inspect how an observation became a design decision. Qualitative saturation, however, does not establish how common a problem is across a population. It supports discovery, not prevalence estimates. A careful team treats field research as a way to find consequential patterns, then uses appropriately designed quantitative work when scale or distribution matters.
Use maps as shared working objects, not polished claims of reality.
Choose the map for the question. A journey map shows one person’s experience over time, including actions, emotions, channels, and steps that may occur beyond the provider’s control. A service blueprint adds the visible employee actions and the hidden processes that support them. Stakeholder and ecosystem maps show who and what is connected, while value network maps show exchanges such as money, information, services, and trust. These tools simplify complexity so a team can work with it; no single map captures every possible path.
Start from people’s goals. Someone moving house may need electricity, but the larger task is settling into a new home. Mapping only the energy company’s sign-up process misses the surrounding pressures and opportunities. Maps can be built from research or used as provisional assumptions to guide research. Their credibility depends on making that distinction clear.
These visual tools act as boundary objects: a shared representation that different specialists can interpret from their own roles. A developer may notice system dependencies, while a frontline employee sees an awkward handoff. That productive ambiguity can support collaboration without forcing premature agreement. The danger is that a clean graphic can look more complete than its evidence warrants. Teams should label uncertainty, identify whose perspective is absent, and revise the map when reality refuses to fit its lanes.
Alternate possibility-making and evidence-based narrowing, without locking into a linear recipe.
Create options, then reduce them. Design work repeatedly moves between divergence, which opens up possibilities, and convergence, which selects promising directions. Research can produce new questions; ideation can expose knowledge gaps; prototypes can send a team back to either activity. The core activities are research, ideation, prototyping, and implementation, but they are not a fixed sequence. The right mix depends on the challenge, people, resources, and organizational context.
Give uncertainty a structure. Planned iterations are timeboxed cycles with space to plan, work, and review. They make an exploratory process more predictable without pretending every next step is knowable. In idea selection, a team might compare potential customer impact with feasibility, then carry several promising options forward rather than betting everything on one favorite. The project plan is a guide to adaptation, not a script to obey.
This flexible structure has an affinity with adaptive management: when outcomes are uncertain, short learning cycles can limit the cost of mistaken assumptions. Alternating expansion and selection also prevents endless brainstorming from masquerading as progress. But iteration is not automatically productive. Teams need explicit questions, decision owners, and stopping rules, or repeated cycles can become motion without learning. Timeboxes help, provided they protect reflection and do not reward speed at the expense of evidence.
Prototype the service in context, not merely its screen or slogan.
Make the experience testable. A service prototype is a staged, early version of an experience or process that lets a team learn from use. It may involve employees acting out a conversation, cardboard representing a counter, a paper interface, or a simulated business model. Prototypes can explore possibilities, evaluate specific questions, or communicate a concept. Their fidelity should be only as high as needed to answer the question, and several alternatives are often more informative than one polished favorite.
Test where life happens. Airbus teams tested rough digital interfaces and material-delivery carts with workers on the factory floor, then revised them through repeated feedback. The setting revealed workflow issues that a meeting-room demonstration could not. A prototype is not merely an object to show; its value comes from the interaction it enables and the evidence gathered from that interaction.
Prototyping turns abstract disagreement into observable behavior, a move shared with experimental engineering and usability testing. A rough model can expose a workflow flaw before a costly production commitment, while contextual trials reveal constraints hidden by laboratory conditions. Still, one successful test does not prove a service will work at scale. Novelty, coaching, and the presence of the design team can affect behavior. Good prototypes specify what they test, who tests them, and which conclusions the evidence can support.
Design implementation around employees, systems, and incentives, not just customer-facing concepts.
A concept is not an operating service. Implementation moves a tested idea into everyday use, where employees, technology, rules, partners, and existing measures must work together. That means planning for training, organizational changes, software or physical production, and the realities of rollout. In change management, the book uses Leavitt’s Diamond to examine four connected elements: tasks, people, technology, and organizational structure. Changing one can affect the others.
Change the backstage to change the experience. At Oslo University Hospital, a redesigned breast diagnosis process cut the wait from as long as 12 weeks to 7 to 28 days, depending on urgency, a reported reduction of up to 90 percent. The change included daily case reviews and clearer staff responsibilities, not simply a more reassuring patient-facing message. Pilots help test both the service and the way it will be introduced.
Implementation is where design meets organizational behavior. The four-part analysis is useful because it resists the common habit of treating training as the whole change plan. A new task may require different authority, tools, staffing, or performance measures. The hospital example also shows how operational redesign can improve a human experience without adding a decorative layer. A caution: a successful pilot can rely on exceptional attention or extra resources, so rollout plans should test whether the result survives ordinary workloads.
Facilitate the room so disagreement becomes useful work, not meeting theater.
Make collaboration concrete. A facilitator guides the task, the group, and individual participants, while building enough trust for people to experiment and disagree. Participants may have different status, expertise, and comfort with ambiguity. A safe working environment is built through clear expectations, appropriate activities, and permission to try rough versions without treating every idea as a final proposal. Silent sketching, role-play, and shared visual tools can give people ways to contribute beyond speaking most confidently.
Match the method to the moment. During a five-day project at Brazilian bank Itaú, staff and users examined customer journeys, developed a clearer digital tone of voice, and tested communication prototypes with real customers. The compressed format worked because the preparation, participant mix, and activities were designed for that specific question. A workshop is a working session, not a magic idea generator.
Facilitation is a form of process design. It shapes whose knowledge enters the room and how quickly a group moves from competing interpretations to something testable. The emphasis on varied participation is important because verbal confidence is not the same as expertise. Yet a workshop can also create the appearance of inclusion while decisions remain elsewhere. Participants need clarity about how their contributions will be used, who makes final choices, and what happens to ideas that are not adopted.
Embed service design through small wins, protected time, and repeatable learning loops.
Start where change can take root. Organizations can build capability through small projects, supportive sponsors, visible results, and time for employees to participate. Service design becomes fragile when it is an extra task layered onto full workloads or isolated in a special studio. A core team can guide methods while cross-functional project teams bring operational knowledge and ownership.
Build the habit into operations. The Swedish Public Employment Service invited seven local offices to adapt and test service changes as “Greenhouses.” In the first meeting, redesigned registration reduced practical intake time from 50 minutes to 10, leaving more room to discuss people’s needs. The initiative expanded to 24 offices, and thousands of employees and managers received an introduction to the approach. The goal is not a permanent workshop campaign, but ongoing research, testing, and improvement as part of ordinary work.
Embedding a method is a cultural and governance challenge, not simply a training program. The Greenhouse model gives frontline teams room to adapt solutions while retaining organizational support, combining local knowledge with a broader learning system. That balance is difficult: too much central control suppresses adaptation, while too much local variation can fragment service quality. Useful measures should therefore track both operational results and experience, and leaders must protect the time and decision authority that make experimentation possible.
Analysis
The book’s central achievement is to make service design less mysterious and more operational. Its argument begins with a customer’s experience, then follows that experience backstage through processes, technology, organizational roles, and business models. The practical consequence is a shift in what counts as design: not just creating an attractive interface, but coordinating a system so people can achieve something with less friction and more confidence.
Its strongest contribution is the connection between human-centered inquiry and organizational execution. Journey maps and prototypes are not presented as artifacts with inherent power. They matter because they help people with different expertise see, discuss, and test the same service. Research challenges assumptions; ideation widens options; prototypes make consequences visible; implementation turns learning into routine. Iteration keeps these activities connected while limiting the risk of committing too early.
The book also recognizes a political reality often hidden by toolkits: services are delivered by organizations with conflicting incentives, unequal authority, and limited time. A map may reveal a broken handoff, but only leadership, budgets, and changed responsibilities can repair it. Participation can build ownership, yet co-creation is not automatically democratic. Meaningful inclusion requires clarity about who decides and whether participants’ contributions have influence.
A further strength is its insistence that a service must make sense for users, employees, and the organization. Customer delight alone is not a sustainable strategy, just as internal efficiency alone can export costs and confusion to customers. The balance is not a formula; it is a set of tensions to investigate through evidence and experimentation.
The limitation is breadth. A handbook spanning research, facilitation, software, architecture, change, and strategy risks making a demanding discipline look easier than it is. The book’s answer is practice: start with a real problem, use modest experiments, document the evidence, and learn from implementation. Its most durable lesson is that design is not a workshop or a map. It is an organizational capacity to keep noticing, testing, coordinating, and improving how value is experienced.
Review Summary
This Is Service Design Doing receives high praise from readers, with an average rating of 4.35/5. Reviewers appreciate its comprehensive approach, practical tools, and real-world case studies. Many consider it an essential reference for service designers and professionals involved in product development. The book is lauded for its holistic perspective, offering insights into methodologies, facilitation techniques, and prototyping. While some find it occasionally verbose or complex, most agree it's a valuable resource for both newcomers and experienced practitioners in the field of service design.
Glossary
Service design
Designing connected service experiencesAn approach to improving or creating services by understanding people’s needs, coordinating the activities and systems that deliver value, and testing possible solutions in practice. It combines research, collaboration, visualization, prototyping, and implementation. The approach considers the experience of customers, employees, and other affected stakeholders, alongside operational and business requirements.
Service-dominant logic
Value created through exchangeA framework for understanding economic activity in which service, broadly understood as applying resources to help another actor, is the basis of exchange. Goods are treated as ways of delivering service, and value is created through interactions among multiple actors. Value is determined by the beneficiary in context, rather than being inherent in an object.
Boundary objects
Shared cross-disciplinary artifactsRepresentations or artifacts that people from different professional groups can use together, even when each group interprets them differently. In service design, a journey map may help designers identify experience problems, managers consider business opportunities, and developers spot technical dependencies. Its shared structure supports collaboration without requiring everyone to use the same specialist vocabulary.
Journey map
Experience shown over timeA visualization of one main actor’s experience across a sequence of steps. It can include stages, actions, emotions, channels, people, and relevant context, including activities outside an organization’s direct control. Maps may describe an existing experience or a proposed future one, and can range from a broad life cycle to a detailed interaction.
Service blueprint
Experience linked to operationsA map that connects customer actions and visible service interactions to the backstage work and support processes that make them possible. It typically distinguishes frontstage actions, backstage actions, and organizational support processes. By showing the links between them, a blueprint helps teams identify operational causes of customer-facing problems and plan changes across departments.
Theoretical saturation
A stopping point in researchA practical judgment in qualitative research that further data collection is no longer producing meaningful new patterns relevant to the research questions. It helps teams decide when they have learned enough to proceed, given their purpose and resources. It does not demonstrate that a finding is statistically representative or establish how common a pattern is in a larger population.
Kano model
Classifies customer expectationsA model of how different attributes of an offering relate to satisfaction. Basic qualities cause dissatisfaction when absent but may be taken for granted when present. Performance qualities tend to raise satisfaction as they improve. Attractive qualities can delight when offered but are not necessarily expected. Over time, an exciting feature can become ordinary, then a basic expectation.
Leavitt’s Diamond
Maps organizational change impactsA framework for examining the relationship among four organizational elements: tasks, people, technology, and structure. A service change can affect several elements at once. For example, a new frontline process may require different staff skills, tools, decision authority, or performance measures. The framework helps teams identify these linked implementation requirements.
Planned iterations
Timeboxed learning cyclesScheduled work cycles that give an adaptive design process predictable points for planning, activity, and reflection. Teams commit to completing each cycle within agreed time and resource limits, then revise the next cycle in light of what they learned. This creates structure for stakeholders without requiring the team to predict every activity in advance.
FAQ
What’s "This Is Service Design Doing" by Marc Stickdorn about?
- Comprehensive service design manual: The book is a hands-on guide for applying service design thinking in real-world projects, covering the entire process from research to implementation.
- Emphasis on practical application: It moves beyond theory, focusing on actionable methods, tools, and facilitation techniques for practitioners.
- Co-creation and collaboration: Created with input from over 200 reviewers and 96 co-authors, it reflects diverse perspectives and real-world relevance.
- Bridging theory and practice: Through detailed case studies and expert insights, it connects service design frameworks with actionable steps for organizations.
Why should I read "This Is Service Design Doing" by Marc Stickdorn?
- Actionable, step-by-step methods: The book provides detailed instructions for service design activities, making it accessible for both beginners and experienced practitioners.
- Real-world case studies: It features examples from industries like aviation, healthcare, and technology, illustrating how service design solves complex challenges.
- Focus on collaboration: Readers learn how to break down organizational silos and foster cross-disciplinary teamwork for better customer and employee experiences.
- Guidance on change management: The book addresses the critical implementation phase, offering strategies for embedding service design in organizations.
What are the key takeaways from "This Is Service Design Doing"?
- Human-centered and iterative: Service design is about understanding people’s needs, co-creating solutions, and iterating through prototyping and testing.
- Holistic and systemic approach: The book stresses designing for the entire service ecosystem, including backstage processes and organizational culture.
- Practical facilitation skills: It offers techniques for running effective workshops, managing stakeholders, and building safe spaces for innovation.
- Sustainable organizational change: Readers learn how to embed service design into company culture, processes, and leadership practices.
How does "This Is Service Design Doing" by Marc Stickdorn define service design?
- Multi-faceted definition: Service design is a mindset, process, toolset, cross-disciplinary language, and management approach for creating seamless service experiences.
- Rooted in design thinking: It applies creative and practical design processes to innovate or improve services, balancing customer and business needs.
- Focus on co-creation: Service design choreographs processes, technologies, and interactions to co-create value for all stakeholders.
- Emphasis on real-world context: The approach grounds research and prototyping in actual user environments and organizational realities.
What are the core principles and mindset of service design in "This Is Service Design Doing"?
- Human-centered and co-creative: The process involves understanding and engaging all stakeholders to co-create valuable solutions.
- Iterative and experimental: Encourages rapid prototyping, learning from failure, and refining ideas through continuous feedback.
- Holistic and systemic: Considers the entire service ecosystem, including touchpoints, backstage processes, and organizational culture.
- Collaborative and adaptive: Promotes cross-disciplinary teamwork and flexible adaptation to project needs and complexity.
What is the service design process framework in "This Is Service Design Doing"?
- Four core activities: The process centers on research, ideation, prototyping, and implementation, forming the backbone of service design projects.
- Iterative and non-linear: The framework supports cycles of divergent and convergent thinking, allowing teams to explore and refine solutions.
- Flexible tailoring: The process is adapted to the project’s people, goals, and resources, rather than following rigid steps.
- Managing uncertainty: It is designed to work effectively in volatile, uncertain, complex, and ambiguous (VUCA) environments.
What are the basic service design tools introduced in "This Is Service Design Doing"?
- Research data: Collects and interprets qualitative and quantitative data to understand user needs and contexts.
- Personas and journey maps: Uses fictional archetypes and visualizations of user experiences to build empathy and guide design.
- System maps and prototypes: Visualizes stakeholder relationships and creates early experiential forms to explore and communicate ideas.
- Business Model Canvas: Links service design to organizational strategy by sketching and analyzing business models.
How does "This Is Service Design Doing" by Marc Stickdorn approach research in service design?
- Beyond assumptions: Research uncovers real user motivations, behaviors, and contexts, enabling empathy and insight-driven design.
- Iterative research loops: Plans research as a sequence of loops, refining questions and methods based on emerging findings.
- Method triangulation: Combines desk research, ethnography, interviews, and workshops for richer, more reliable data.
- Data synthesis and visualization: Uses tools like research walls, personas, and journey maps to make sense of complex data and communicate insights.
What ideation methods and advice are provided in "This Is Service Design Doing"?
- Diverse ideation techniques: Includes brainstorming, brainwriting, bodystorming, and analogy-based thinking to generate and deepen ideas.
- Cards and checklists: Uses ideation cards and checklists to focus sessions, break thinking patterns, and ensure comprehensive coverage.
- Managing ideation sessions: Emphasizes preparation, participant selection, and balancing divergent and convergent thinking for effective idea generation.
- Decision-making tools: Recommends clustering, voting, and physical commitment to select and prioritize ideas while maintaining momentum.
How does "This Is Service Design Doing" describe prototyping in service design?
- Exploration and evaluation: Prototyping is used to explore options, test hypotheses with users, and communicate concepts to stakeholders.
- Experience vs. imagine-like prototyping: Differentiates between direct user interaction (experience prototyping) and scaffolding thinking when direct interaction isn’t possible.
- Diverse prototyping methods: Presents techniques like investigative rehearsal, cardboard prototyping, paper prototyping, and Wizard of Oz.
- Iterative and risk-reducing: Encourages early, low-fidelity prototyping to reduce risk and uncertainty before investing in full-scale solutions.
What strategies does "This Is Service Design Doing" recommend for managing stakeholders and co-creators?
- Clear communication of roles: Explains why stakeholders are involved, what’s expected, and how their input impacts the project.
- Onboarding and engagement: Stresses careful onboarding, regular updates, and avoiding a "co-create-and-forget" mentality.
- Conflict management: Uses boundary objects and prototypes to reduce early conflicts and recommends conflict resolution training for teams.
- Continuous involvement: Encourages ongoing engagement and feedback to build trust and commitment throughout the project.
What are the best quotes from "This Is Service Design Doing" by Marc Stickdorn and what do they mean?
- “If a picture is worth 1,000 words, a prototype is worth 1,000 meetings.” — Highlights the power of prototypes to communicate ideas efficiently and foster collaboration.
- “Designing a service is never done. It’s only over when you go out of business.” — Emphasizes the ongoing, iterative nature of service design and the need for continuous improvement.
- “Talk to your fing customer!”* — A blunt reminder that authentic user engagement is essential for meaningful innovation.
- “We always want whatever we are doing to be instantly good... invite them to aim for average. It enables them to get that essential sh!tty first draft out.” — Encourages embracing imperfection early to foster creativity and progress.
- “The goal of facilitation... is content driven and not process driven.” — Stresses that facilitation should focus on achieving meaningful outcomes, not just managing the process.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.