Service Design: Definition, Process & Practical Example

Services account for 70% of German gross value added. 99.4% of German companies are SMEs. And yet: most mid-market companies have invested heavily in digitalization — but rarely do new digital services or scalable business models emerge.

The reason: most services were never consciously designed. G. Lynn Shostack — not an academic, but Senior Vice President at Bankers Trust Company — put it plainly in 1984 in the Harvard Business Review: poor service quality doesn’t stem from inadequate optimization, but from the fact that services emerge through chance and trial-and-error rather than being systematically designed [1].

Service design is the discipline that changes this: a strategic approach that determines whether a company consciously designs its services or whether they remain a byproduct of its organizational structure. Stickdorn et al. (2018) capture it with an image: “Owning a pile of bricks does not make you an architect” — knowing methods alone isn’t enough; you need the ability to think about services as a whole [10].

What Is Service Design?

Service design is the discipline that systematically shapes services — from the customer’s perspective, but taking into account all internal processes, systems, and actors that support the customer experience.

The critical distinction: UX design shapes what the customer sees and experiences (the frontstage). Service design additionally orchestrates what happens behind the scenes — the internal resources, handoffs, and systems (the backstage) [2]. Birgit Mager, the world’s first professor of service design (TH Cologne, since 1995) and co-founder of the Service Design Network, puts it precisely: “You cannot change the frontstage if you don’t impact the backstage” [3].

Shostack’s 1982 origin is revealing: the term “service design” didn’t emerge from a design school but from a marketing journal — the European Journal of Marketing [4]. Shostack argued that services need their own design discipline because they differ fundamentally from products: they are intangible, exist only in time, and cannot be produced in advance. Her tool for this — the Service Blueprint — remains the standard method for making front- and backstage visible together.

The theoretical foundation came from Vargo and Lusch in 2004 with the Service-Dominant Logic: it’s not the product itself that creates value, but the service it enables [5]. If value emerges through the interplay of provider and customer (co-creation), then designing this interplay is strategic — not cosmetic. The consequence: service design is not a one-time measure that produces a “finished” result — it’s the development of an organizational capability to continuously design services.

Terminology note: Service design as used in this article refers to the strategic design discipline for services — not “ITIL Service Design,” the phase in the IT service management lifecycle. Both use the same term but address different questions: SD asks “How do we design a service that works for the customer?”, ITIL asks “How do we plan the IT infrastructure for a defined service?”.

The 5 Principles of Service Design

Stickdorn and Schneider defined five principles in 2010 that distinguish service design from other design disciplines [6]. They form the conceptual foundation on which all methods and processes are built:

1. User-Centered

Service design starts with the customer’s experience — not the internal org chart. But “user” means more than the end customer: employees, partners, and third-party providers who deliver the service are also users of the system. A service that works perfectly for the customer but overburdens its own employees is not a good service.

2. Co-Creative

All relevant stakeholders participate in the design — not just designers. Customers, employees, IT, management, and external partners bring their perspectives into the design process. The reason is practical: a service designed without the people who will later deliver it fails against the reality of their workflows.

3. Sequential

A service is not a single moment but a sequence of interactions over time. Service design visualizes this sequence — before the service, during the service, and after the service — and identifies the transitions between phases where the most friction occurs. The Customer Journey Map is the central tool for this.

4. Evidencing

Services are intangible — the customer can’t touch or display them. Service design makes the invisible visible through physical or digital artifacts: a confirmation email after booking, a personalized dashboard during use, a final report after the project. These “service souvenirs” help the customer perceive and communicate the service’s value.

5. Holistic — The Most Frequently Violated Principle

The entire service environment is considered — emotional, physical, and digital touchpoints, internal processes, and external dependencies. In practice, “holistic” is the principle most companies fail at — because organizational silos make it the hardest to implement. A service blueprint captures not only the customer interaction but also the support processes three layers below. Jamin Hegeman, who transformed a business unit at Capital One, implemented exactly this principle: 100% of the organization worked from the same customer understanding — with journey maps, vision stories, and service blueprints as a shared language [7].

The Service Design Process: The Double Diamond

The Design Council UK developed the Double Diamond in 2004 as a visual framework for the design process [8]. It describes two successive phases of exploration and synthesis:

    UNDERSTAND THE PROBLEM     DEVELOP THE SOLUTION
   /                \        /                \
  /    Discover      \      /    Develop       \
 /                    \    /                    \
/                      \  /                      \
\                      /  \                      /
 \    Define          /    \    Deliver         /
  \                  /      \                  /
   \                /        \                /

Phase 1: Discover

The goal is to open up the problem space: what do customers actually experience? Not what the CRM shows, not what management assumes — but what happens when a customer tries to accomplish a task. Methods: customer interviews, shadowing (observing daily work), diary studies, service safaris. The objective is divergent thinking — taking as many perspectives as possible.

Phase 2: Define

Insights from the Discover phase are distilled: which problems are most important? Where is the greatest leverage? This is where the “How might we…” question emerges, formulating the design brief. Methods: personas, journey maps, insight clustering. The objective is convergent thinking — deriving a focused problem definition from many observations.

Phase 3: Develop

The solution space is opened: what could the service look like? Ideation, co-creation workshops with customers and employees, sketching service scenarios. Multiple solution approaches emerge in parallel — not a single “right” solution.

Phase 4: Deliver

The most promising approaches are prototyped, tested, and iterated. Service prototypes can be simple role-plays (customers and employees act out the new service) or digital click dummies. Only when the prototype convinces in testing does implementation follow.

From practice: We regularly observe that teams treat the Double Diamond as a linear project plan: “First Discover, then Define, then Develop, then Deliver.” In reality, teams oscillate between phases — an insight from the Develop phase can completely overturn the Define phase. Ramsden (2023) documents eight limitations of the Double Diamond, including the artificial separation of problem and solution space and the lack of communication about co-design methods [9]. The Double Diamond is a communication tool that helps explain and plan the process — not a project plan to be executed linearly. In our Integrated Service Development Process (iSEP — Integrierter Service Entstehungs Prozess), we’ve explicitly built iterative loops between phases: after each phase, a stakeholder review validates the results with all participants — because enterprise projects with 15+ stakeholders cannot run linearly. When a Develop insight shifts the problem definition, the process must accommodate that rather than treating it as a deviation from the plan.

Service Design vs. Design Thinking vs. UX Design

The distinction between service design, design thinking, and UX design is among the most common questions — and among the most poorly answered. Here is the systematic differentiation:

Criterion	Service Design	Design Thinking	UX Design
Focus	Entire service: frontstage + backstage	Innovation and problem-solving	Digital and physical user experiences
Perspective	Customer AND organization	Primarily user	Primarily user
Scope	End-to-end service across all channels	Single challenge or project	Single products or interfaces
Output	Service blueprint, journey map, org design	Prototype, MVP, concept	Wireframes, interaction design, UI
Time horizon	Long-term service architecture	Project-based (weeks to months)	Feature-based (sprints)
Core question	”How do we design the entire service?"	"How do we solve this problem creatively?"	"How do users experience this product?”

The relationship between the three disciplines is complementary, not competitive:

• Design Thinking provides the mindset: empathetic, iterative, prototype-based. Stickdorn et al. (2018) put it this way: Design Thinking brings forth the innovation approach; service design provides the implementation across touchpoints, roles, and processes [10].
• UX Design shapes individual touchpoints — the app, the website, the form. The NNgroup framework (Gibbons 2021) puts it succinctly: UX and SD are “two sides of the same coin” — UX defines the what (what the user experiences), SD orchestrates the how (which internal structures support the experience) [2].
• Service Design integrates both: it uses the mindset of design thinking and the user focus of UX, but extends the view to the entire service architecture — including backstage processes, employee experience, and organizational design.

A word of caution: Arico (2024) documents a problematic pattern in companies — design thinking was “sold with the promise of solving all problems.” When DT fails to meet inflated expectations, service design is tried next with the same attitude (“apply method, problem solved”) and the same result. The truth is: design thinking overcomes thinking blocks in teams; service design shapes complex service ecosystems. Confusing the two gets you neither [13].

The practical test: if your team does UX redesigns and customer satisfaction still doesn’t improve, the problem likely isn’t in the frontstage but in the backstage. A typical pattern: the company redesigns the customer application form (frontstage) without adjusting internal approval processes and system interfaces (backstage) — the customer gets a prettier form but still waits three weeks for approval. That’s when you need service design.

Key Service Design Methods

Service design draws on a library of over 54 documented methods [10]. The most important for getting started:

Customer Journey Map — Visualizes the entire customer experience across all channels and phases, from the customer’s perspective. Use in the Double Diamond: Phase 1 (Discover) and Phase 2 (Define), to understand the current state. -> Detailed guide: Customer Journey Mapping

Service Blueprint — Extends the journey map with the backstage perspective: which internal processes, systems, and support functions stand behind each touchpoint? Use: Phase 2 (Define) and Phase 4 (Deliver), to identify the backstage causes of frontstage problems. -> Detailed guide: Service Blueprint

Personas — Archetypal user profiles based on research data (not assumptions). In service design, this includes not only customer personas but also employee personas — because the service is delivered by people whose experience must be designed just as carefully.

Stakeholder Map — Visualizes all actors involved in service delivery and their relationships. Particularly relevant in B2B contexts: buying centers, internal approval bodies, and third-party providers.

Service Prototyping — Role-plays in which customers and employees act out the new service before it’s implemented. More cost-effective and revealing than any PowerPoint presentation, because breaks in the service chain become immediately visible.

For root cause analysis of service problems, the Ishikawa Diagram (structured cause-and-effect analysis) and the Kano Model (prioritizing service features by customer impact) are valuable complements.

How do you know if the result is good? The Double Diamond describes the process — but not what makes a good service. This complement comes from Lou Downe (former Director of Design at the UK Government Digital Service) with the 15 Principles of Good Services [16]: a service should be findable, clearly communicate its purpose, set expectations it can meet, and be named with verbs (“Apply for a driver’s license,” not “Driver’s license office”). Downe’s principles are the quality criteria after the design process — they answer the question: “We’ve designed a service. Is it actually good?”

Service Design in Practice: Onboarding at an IT Service Provider

Imagine a mid-market IT systems house (80 employees, 200+ managed service customers) selling server monitoring, helpdesk, and network management. Sales are strong, but the churn rate after 12 months sits at 18% — well above the industry average. The cause isn’t technical performance (monitoring metrics are stable) but onboarding: new customers report chaotic first weeks, changing contacts, and unclear responsibilities.

This is a classic service design trigger: individual touchpoints work (sales: good, technology: good, support: good), but the transitions between them were never designed. This pattern runs across the DACH service economy. In a 2016 academic study, NUERNBERGER Versicherung documented (The Design Journal, Taylor & Francis) that the problem wasn’t customer satisfaction itself but the lack of organizational change capability behind it — the study’s title: “Beyond customer satisfaction: Supporting organisational change through Service Design” [14].

Discover: What Do Customers Actually Experience? (Weeks 1-2)

A three-person team (project lead, a service designer, a sales representative) conducts interviews with five recently churned and five recently acquired customers. Result: the problem isn’t technology but the expectation gap. During the sales process, the customer gets to know a personal advisor. After contract signing, they’re handed off to an onboarding team they’ve never met. The handoff happens internally via CRM ticket — the customer experiences it as a sudden shift in style.

Define: What’s the Real Problem? (Week 3)

The journey map reveals three critical handoffs: (1) Sales -> Onboarding team, (2) Onboarding team -> Technical setup, (3) Technical setup -> Ongoing support. At each handoff, the contact person changes, the communication medium shifts (in-person -> email -> ticket system), and the information depth drops (sales knows the business goals, tech only knows the server configuration). The problem definition: “How do we create an onboarding where the customer never feels they have to start over?”

Develop: What Could It Look Like? (Weeks 4-5)

In a half-day co-creation workshop with sales, technology, and two existing customers, three solution approaches emerge:

1. The “Onboarding Navigator”: A dedicated contact accompanies the customer through the first 90 days — as a bridge between all internal teams
2. The “Handoff Ritual”: Sales and the onboarding team meet the customer together for kick-off — no internal CRM ticket, but a human transition
3. The “Customer Dashboard”: A digital board that transparently shows the customer where they stand in onboarding, who’s currently responsible, and what comes next

Deliver: Prototype and Test (Week 6)

The team combines all three approaches in a service prototype: the navigator uses the dashboard as a communication tool, and the handoff ritual is formatted as a 30-minute video call. Two new customers go through the prototype. Result: the perceived support gap between contract signing and ongoing support shifts from “chaotic” to “structured.” The service blueprint makes the backstage changes visible: the CRM needs a field for the navigator, technology needs access to the sales notes, and the navigator needs a clear mandate to escalate across departmental boundaries.

For projects of this scope, typical effort is 6-8 weeks with a core team of 3-4 people. The most common measurable outcomes: 30-50% reduction in onboarding duration, lower early churn, higher NPS scores in the first 90 days.

From practice: In our work with service companies, we observe this pattern regularly: onboarding is the service moment with the highest expectations and the least design attention. The reason: it’s the moment with the most internal handoffs, and handoffs are almost never consciously designed. German insurers have recognized this — id-fabrik, founded in 2019 jointly by Versicherungskammer, SV SparkassenVersicherung, and Provinzial, institutionalizes exactly this capability: service innovation not as a one-off project but as a permanent organizational competency [15].

When Is Service Design Worth It — and When Not?

Check these three questions for your organization — if you answer “yes” to any of them, you need service design, not process optimization:

The 3 Service Design Triggers: A Quick Test

1. Is your NPS declining even though every department meets its KPIs? Then the problem isn’t individual touchpoints but how they work together. The transitions between departments, systems, and channels were never designed. Polaine, Lovlie & Reason (2013) define it precisely: perceived service quality is the difference between customer expectation and actual experience — and this difference arises between touchpoints, not at them [17].

2. Are you digitizing processes but not services? Forms go digital, but the customer experience remains fragmented. The step from product sales to an integrated product-service system requires a new service architecture, not a new interface.

3. Have you redesigned the frontstage without customer satisfaction improving? New app, redesigned website, simplified form — but NPS doesn’t move. The problem is backstage: in internal handoffs, system breaks, or organizational silos that manifest as frontstage frustrations.

One “yes” is enough: then you need the systemic perspective of service design, not more touchpoint optimization.

When service design is less suitable: In pure commodity and price markets where the customer experience isn’t a purchase driver, SD doesn’t deliver proportional ROI. Nemeth (2024) uses the Ryanair example: the airline became Europe’s largest carrier through radical cost optimization — not through service design [11]. In differentiated service markets, however — insurance, B2B IT services, financial services, consulting — the customer experience IS part of the product. Here, service design isn’t an optional method but a strategic necessity.

The decisive perspective shift — and the central argument of this article: service design is not a one-time measure that produces a “finished” service design. It’s the development of an organizational capability to continuously design and improve services. The individual design solution isn’t the competitive advantage — the ability to keep redesigning is. Capital One — whose Principle 5 transformation under Hegeman was described above — demonstrated this over 9 years: not a single service redesign, but 1,000+ employees with SD training, journey maps as a shared language across all functions, and growth of the SDGC conference from 200 to 900 participants as an indicator of broad impact [7].

Frequently Asked Questions About Service Design

What’s the difference between service design and service design thinking?

In practice, the terms are often used synonymously. Strictly speaking, “service design thinking” describes the mindset (user-centered, co-creative, iterative), while “service design” encompasses the entire discipline — including methods, processes, and organizational embedding [6,10].

Do I need service design for digital transformation?

Digital transformation without service design optimizes processes but doesn’t create new services. Fraunhofer IAO has shown across 220+ practical projects with SMEs that mid-market companies invest heavily in digitalization but rarely produce new digital services or scalable business models [12]. Service design bridges this gap by shifting the question: from “How do we digitize our process?” to “What service do we want to offer?”.

How does service design differ from Customer Experience (CX)?

CX describes the total experience a customer has with a company — it’s an outcome, not a process. Service design is the methodology used to consciously shape that experience.

CX measures, SD designs. — That’s the shortest distinction: Customer Experience is the result; service design is the path to get there.

Where can I learn service design?

TH Cologne (KISD) offers Europe’s oldest service design education (since 1995, Birgit Mager). Other programs: Hochschule Coburg (Master Business & Service Design), SRH Fernhochschule (Master UX & Service Design, part-time), PFH Goettingen (distance learning). For practitioners, Stickdorn’s books This is Service Design Thinking (2010) and This Is Service Design Doing (2018) offer the best starting point [6,10].

How much does service design cost and how long does a project take?

That depends on scope. A focused project (one service, one customer segment) typically takes 6-12 weeks with a core team of 3-5 people. Costs lie primarily in internal work time (interviews, workshops, prototyping), not in external consulting or software licenses. Stickdorn et al. (2018) emphasize: SD deliberately scales small — “start with a pilot project, not a company-wide transformation” [10]. An initial pilot run through the Double Diamond with a concrete service problem is achievable in most mid-market companies with manageable effort.

How do I measure the success of service design?

Three levels: (1) Short-term: customer satisfaction (NPS, CSAT), churn rate, onboarding duration, support tickets — measurable within 3-6 months. (2) Medium-term: cross-sell rate, customer lifetime value, referral rate — measurable after 6-12 months. (3) Long-term: organizational learning ability — how quickly can the company develop new services and adapt existing ones? This third level is the most important but hardest to measure.

How does service design work in agile organizations?

This is a real tension: sprint pressure prevents deep user research, feature optimization displaces systemic thinking. The solution is a dual-track approach: service design runs parallel to agile sprints, providing strategic orientation (service vision, personas, journey maps) that informs the backlog — without interfering with sprint mechanics. Specifically: SD delivers the service vision in Sprint 0, which serves as the backlog foundation; design sprints validate hypotheses between development sprints. Stickdorn recommends: “Adapt SD process to existing culture in small increments — not a big-bang transformation” [10].

Related Methods

Service design doesn’t stand in isolation but connects with a range of tools used across different phases of the design process:

• Service Blueprint: The central tool for making front- and backstage visible together. Every service design project should produce a blueprint.
• Customer Journey Mapping: Visualizes the customer experience across all touchpoints. Often the first step in an SD project.
• Ishikawa Diagram: For structured root cause analysis when a service blueprint has identified a pain point.
• Kano Model: For prioritizing service features by their impact on customer satisfaction.
• PDCA Cycle: For continuous improvement after implementation — service design is not a one-time project.

In our Integrated Service Development Process (iSEP — Integrierter Service Entstehungs Prozess), we orchestrate these methods in a coherent framework that explicitly builds iterative loops between Discover, Define, Develop, and Deliver and adapts to the realities of enterprise organizations — longer timelines, more stakeholders, more complex decision pathways.

Methodology & Sources

This article is based on a systematic review of 17 directly cited sources (academic studies, practice research, professional books) and 21 additional context sources. All DOIs were verified before inclusion. The SERP analysis covers 8 German-language competitor articles. This article contains editorial assessments (“From practice”) — these are based on published sources and industry observations and are marked as such.

Limitations: Service design is a rapidly evolving field; new research may supplement or nuance individual claims in this article. The cited case examples (Capital One, NUERNBERGER Versicherung, id-fabrik) come from published sources, not from our own evaluation. Time and effort estimates in the practical example are typical ranges, not guarantees for specific projects.

Disclosure: SI Labs advises companies on service design and has a commercial interest in the discipline. We have endeavored to base recommendations on published sources and to honestly name the approach’s limitations (see “When Is Service Design Worth It — and When Not?”).

References

[1] Shostack, G. Lynn. “Designing Services That Deliver.” Harvard Business Review 62, No. 1 (January-February 1984): 133—139. [HBR Practitioner Article | Foundational | Quality: High]

[2] Gibbons, Sarah. “UX vs. Service Design.” Nielsen Norman Group (2021). URL: https://www.nngroup.com/articles/ux-vs-service-design/ [Industry Standard Reference | Quality: High]

[3] Mager, Birgit. The Future of Service Design. TH Cologne, 2020. ISBN 978-3-9818990-6-1. [Academic Monograph | First SD Professor worldwide | Quality: High]

[4] Shostack, G. Lynn. “How to Design a Service.” European Journal of Marketing 16, No. 1 (1982): 49—63. DOI: 10.1108/EUM0000000004799 [Academic Article | Foundational — coined “Service Design” | Citations: 1,166+ | Quality: High]

[5] Vargo, Stephen L. and Robert F. Lusch. “Evolving to a New Dominant Logic for Marketing.” Journal of Marketing 68, No. 1 (January 2004): 1—17. DOI: 10.1177/0022242904269303 [Academic Article | Foundational — Service-Dominant Logic | Most cited JoM article since 2000 | Quality: High]

[6] Stickdorn, Marc and Jakob Schneider. This is Service Design Thinking: Basics, Tools, Cases. BIS Publishers, 2010. ISBN: 9781118156307. [Practitioner Book | 5 Principles of SD | 12 languages | Quality: High]

[7] Hegeman, Jamin. “Service Design Leadership at Capital One.” Documented in: SDN Executive Leadership, Carnegie Mellon University, SMU. URL: https://jamin.org/experience/ [Practitioner Case | 9 years VP-level at Capital One | Quality: High]

[8] Design Council UK. “The Double Diamond: A universally accepted depiction of the design process.” Developed 2002—2004. URL: https://www.designcouncil.org.uk/our-resources/the-double-diamond/ [Industry Framework | Open License since 2023 | Quality: High]

[9] Ramsden, Dan. “The Limitations of the Double Diamond.” danramsden.com (2023). [Practitioner Critique | 8 documented limitations | Quality: Medium]

[10] Stickdorn, Marc, Markus Edgar Hormess, Adam Lawrence, and Jakob Schneider. This Is Service Design Doing: Applying Service Design Thinking in the Real World. O’Reilly Media, 2018. ISBN: 9781491927186. [Practitioner Book | 54 Methods | Quality: High]

[11] Nemeth, A. “2024 the Year of Service Design? Hold your horses.” Medium (2024). [Practitioner Critique | Contrarian perspective | Quality: Medium]

[12] Fraunhofer IAO / BIEC. “Kompetenzzentrum Smart Services.” 220+ practical projects with SMEs, 6,200+ participants. URL: https://www.iao.fraunhofer.de [Institutional Source | DACH-specific | Quality: High]

[13] Arico, Maurizio. Design Mavericks: Why Some Designers Drive Innovation (2024). [Practitioner Book | DT/SD miscoupling analysis | Quality: Medium]

[14] NUERNBERGER Versicherung. “Beyond customer satisfaction: Supporting organisational change through Service Design.” The Design Journal (Taylor & Francis, 2016ff.). [Academic Case Study | DACH-specific | Quality: High]

[15] id-fabrik. Joint innovation hub of Versicherungskammer, SV SparkassenVersicherung, and Provinzial (est. 2019). URL: https://id-fabrik.de [Institutional Source | DACH-specific | Quality: Medium]

[16] Downe, Lou. Good Services: How to Design Services That Work. BIS Publishers, 2020. ISBN: 9789063695439. [Practitioner Book | 15 Principles | 35,000+ copies sold | Quality: High]

[17] Polaine, Andy, Lavrans Lovlie, and Ben Reason. Service Design: From Insight to Implementation. Rosenfeld Media, 2013. ISBN: 9781933820330. [Practitioner Book | Expectation gap framework | Quality: High]