Service Design as Innovation Method: Why SD Is the Operational Core of Service Innovation

Many organizations treat service design and service innovation as separate disciplines — different teams, different budgets, different KPIs. This separation is the structural reason why service innovation fails.

This article shows why service design is not merely a “helpful input” to innovation but the operational methodology through which service innovation happens. The relationship is not “SD helps with SI” — it is “SD is how SI gets done.”

The Foundation: Why Services Need Their Own Innovation Methods

Services are fundamentally different from physical products¹:

• Intangible: You cannot touch a service before purchasing it
• Co-produced: The customer is a co-producer — without their participation, the service does not exist
• Temporal: Services unfold over time as a sequence of interactions
• Heterogeneous: Every service delivery is different because people are involved

Innovation methods designed for tangible products (Stage-Gate, classical NPD) fail systematically for services². Kurtmollaiev and Pedersen analyze 886 articles on service innovation (1981—2019) and demonstrate: classical New Service Development processes (NSD) are “rigid processes involving linear phases, with lack of flexibility being a main limitation.”

Service design addresses exactly this limitation — through non-linear, iterative, human-centered design.

Four Unique Contributions of SD to Innovation

What distinguishes service design from Design Thinking, Lean Startup, Stage-Gate, or Agile? Four properties that no other innovation method provides:

1. Designing Frontstage and Backstage Simultaneously

Design Thinking designs the user experience (frontstage). Service design designs the user experience and the delivery system that produces it (backstage)³.

The service blueprint — SD’s signature tool — is the only method that maps customer actions, frontstage employee actions, backstage processes, and support systems on a single diagram. Birgit Mager, the world’s first professor of service design (TH Cologne, since 1995): “You cannot change the frontstage if you don’t impact the backstage.”

Why this matters for innovation: A service innovation that only redesigns the customer interface without redesigning the delivery system will fail at implementation. This is why the majority of innovation initiatives fail to scale — the backstage was never redesigned.

2. Ecosystem Perspective Instead of Dyad

Lean Startup tests a hypothesis about product-market fit. Service design maps the entire ecosystem in which a service operates: customer, provider, partners, regulators, technology, physical environment⁴.

Patricio et al. demonstrate this with their SD4VN method (Service Design for Value Networks): designing for value networks, not just individual customer-provider interactions.

Why this matters for innovation: Services do not exist in isolation. A B2B service innovation typically involves the client organization, their end customers, technology partners, regulatory bodies, and internal departments. Only SD maps all of these simultaneously.

3. Co-Creation as Method, Not Just Principle

Many innovation methods claim to be “customer-centric.” SD operationalizes co-creation through specific methods: co-creation workshops, participatory design sessions, experience prototyping with real users and employees⁵.

Yu and Sangiorgi distinguish clearly: “designing WITH users” rather than “designing FOR users.” Wetter-Edman et al. put it precisely: “The result of service design is a value co-creation system.”⁶

Why this matters for innovation: Services are co-produced by definition — the customer participates in delivery. An innovation method that does not structurally involve the customer in the design process produces services that look good on paper but fail in co-production.

4. Temporal and Processual Design

Product innovation designs an artifact (static, tangible). Service design designs a process that unfolds over time (dynamic, intangible)⁷.

Customer journey mapping, service blueprinting, and storyboarding capture the temporal dimension of services — the sequence of interactions, the waiting times, the emotional arc. Kimbell puts it this way: “designing for service means designing a platform for action with which diverse actors will engage over time.”

Why this matters for innovation: Services are experienced as sequences, not objects. Innovation methods designed for products (Stage-Gate, NPD) produce specifications for what the service IS. SD produces specifications for how the service UNFOLDS.

SD Methods in the Innovation Phases

How does service design map to the phases of service innovation?

Innovation Phase	SD Methods	SD’s Unique Contribution
Strategic Framing	Stakeholder mapping, ecosystem mapping, service safari, contextual inquiry	The ecosystem perspective: not just “What is the customer problem?” but “Who are all the actors, and how does value flow between them?”
Discovery	User research (ethnography, interviews, diary studies), customer journey mapping (as-is), persona development, empathy mapping	Primary qualitative research with multi-stakeholder scope. Not just customer research but provider, partner, and backstage actor research.
Ideation & Concept	Service blueprinting (to-be), co-creation workshops, morphological box, experience prototyping, business model canvas integration	Designs frontstage experience AND backstage delivery system simultaneously. No other method produces a blueprint mapping customer actions to support processes.
Prototyping & Validation	Service prototyping, desktop walkthroughs, experience prototyping, Wizard of Oz testing	Prototypes the SERVICE SYSTEM (not just the interface). A service prototype tests the interaction between customer, employee, and system.
Implementation & Scaling	Operational blueprints, service specifications, training design, service standards, KPI definition	Translates “validated concept” into “operational service” through detailed blueprints that operations teams can execute.

Where SD Stops and Broader Innovation Methodology Begins

Honest boundaries matter for setting the right expectations:

SD covers (uniquely and completely):

• Understanding user/customer/stakeholder contexts through primary research
• Synthesizing research into actionable insights
• Generating and visualizing service concepts (frontstage + backstage)
• Prototyping and testing service interactions
• Designing the service delivery system (people, processes, technology, physical evidence)

SD stops and broader methodology takes over at:

1. Strategic portfolio decisions. SD can inform which services to develop. The portfolio question (“Should we invest in service innovation, product innovation, or process optimization?”) requires strategic management tools — the domain of business design and innovation management⁸.

2. Business model architecture. SD produces service concepts; translating those into viable business models requires business model innovation methodology⁹.

3. Organizational transformation. SD can catalyze organizational change¹⁰, but sustained structural transformation requires change management, governance redesign, and cultural development — the domain of innovation culture and business transformation.

4. Scaling and operations. SD designs the service system specification; actually building and scaling the operational infrastructure requires operations management and technology implementation.

From SD Projects to Innovation Capability

The critical distinction: SD as project vs. SD as organizational capability.

Kurtmollaiev et al. study a major telecommunications company in a longitudinal study and demonstrate: SD drives “far-reaching changes in the organizational mindset and routines” — not just new services but new ways of working¹⁰. The organizational transformation is the capability; individual service innovations are the output.

The SDN Maturity Model

The Service Design Network describes five stages of embedding¹¹:

Stage	Description	Innovation Capability
1. Explore	Enthusiasts explore SD as a new methodology; first initiative.	Innovation is accidental. Individual champions run isolated experiments.
2. Prove	Painstaking pioneering. SD projects + evidence building.	Innovation is project-based. Evidence grows but is not systematic.
3. Scale	SD expands through unified tools and training.	Innovation becomes repeatable. Methods are standardized, teams trained.
4. Integrate	Siloed structures transform into a design-led foundation. SD embedded in daily work.	Innovation is systemic. SD is how the organization develops new services.
5. Thrive	Everyone is involved. SD is culture, not just methodology.	Innovation is cultural. The organization continuously innovates because that is how it operates.

Critical insight: “The maturity stage can differ across company departments, teams, and even people. Differences in maturity across the organization often explain tensions or resistance occurring during transformation.”

Four Levels of Embedding

Synthesizing the maturity model with the academic literature:

Level 1: SD as Outsourced Project (Stages 1—2)

• Organization hires an SD consultancy for a specific initiative
• Knowledge stays with the consultancy; internal team observes but does not internalize
• Risk: consulting dependency

Level 2: SD as Internal Competency (Stages 2—3)

• Organization builds an internal SD team (2—5 people)
• Team runs projects; methods are documented but not organization-wide
• Risk: SD team becomes a bottleneck

Level 3: SD as Organizational Capability (Stages 3—4)

• SD methods are embedded in how cross-functional teams work
• Non-designers (product managers, engineers, operations) use SD tools routinely
• Risk: methodological dilution

Level 4: SD as Innovation Infrastructure (Stages 4—5)

• SD principles are embedded in governance, metrics, and organizational structure
• Innovation is not a project type but a way of operating
• SD stops being a “method” and becomes the operating system for service innovation

The transition from Level 1 to Level 3 requires a deliberate capability transfer plan. Embedding Service Design in Organizations describes how this transfer succeeds.

What This Means for Your Organization

Two diagnostic questions:

1. Where are you on the maturity model?

• Stages 1—2: Start with a pilot project that introduces SD as a methodology. Focus on evidence building.
• Stage 3: Standardize tools and train broader teams. Build a center of excellence.
• Stages 4—5: Integrate SD into governance and performance systems.

2. Are you treating SD as a project or as a capability?

• If every SD project requires external help → Level 1 (dependency)
• If your team can lead the next cycle independently → Level 3 (capability)
• The decisive metric: Does the need for external support decrease with each cycle?

The entry point for this process is described in Getting Started with Service Innovation. Measuring progress is covered in Measuring Service Innovation.

FAQ

Is service design the same as Design Thinking? No. Design Thinking designs the user experience (frontstage). Service design additionally designs the delivery system (backstage). The service blueprint as SD’s signature tool has no equivalent in Design Thinking. More details: What Is Service Design?

Can I innovate with SD alone? SD covers the operational core of service innovation. For strategic portfolio decisions, business model architecture, and organizational transformation, you need complementary methodology — business design, innovation management, and change management.

How long does it take to build SD as organizational capability? From Stage 1 (Explore) to Stage 3 (Scale) typically 18—36 months. The transfer accelerates when each phase is explicitly designed for capability building — not just service output.

What distinguishes service design from user experience design? UX design focuses on digital interfaces. Service design designs the entire service across all channels, including physical touchpoints, employee interactions, and backstage processes. UX is a subset of SD.

Which SD methods are most important for innovation? One for each phase: user research (discovery), service blueprint (concept), service prototyping (validation). These three form the methodological backbone. A complete overview is available in Service Design Methods.

Do I need an internal SD team? From maturity stage 3 onward, yes. Before that, external support and pilot projects suffice. But: every external engagement needs an explicit transfer plan so your team can lead the next cycle independently.

---

Footnotes

1. Lynn Shostack, “How to Design a Service,” European Journal of Marketing 16(1), 1982. Foundational work on the distinction between service and product design. ↩

2. Kurtmollaiev and Pedersen, “Bringing Together the Whats and Hows in the Service Innovation Literature,” International Journal of Management Reviews 24(4), 2022. Analysis of 886 SI articles (1981—2019). ↩

3. Mary Jo Bitner, Amy Ostrom, and Felicia Morgan, “Service Blueprinting: A Practical Technique for Service Innovation,” California Management Review 50(3), 2008. ↩

4. Lia Patricio, Anders Gustafsson, and Raymond Fisk, “Upframing Service Design and Innovation for Research Impact,” Journal of Service Research 21(1), 2018. ↩

5. Eun Yu and Daniela Sangiorgi, “Service Design as an Approach to Implement the Value Cocreation Perspective in New Service Development,” Journal of Service Research 21(1), 2018. ↩

6. Katarina Wetter-Edman et al., “Design for Value Co-Creation: Exploring Synergies Between Design for Service and Service Logic,” Service Science, 2014. ↩

7. Lucy Kimbell, “Designing for Service as One Way of Designing Services,” International Journal of Design 5(2), 2011. ↩

8. Anna-Lisa Ostrom et al., “Service Research Priorities in a Rapidly Changing Context,” Journal of Service Research 18(2), 2015. ↩

9. Lei Wang et al., “Enhancing Value Cocreation Orientation in Service Innovation: An NSD and SD Integrated Process,” Humanities and Social Sciences Communications 12, 2025. ↩

10. Seidali Kurtmollaiev et al., “Organizational Transformation Through Service Design,” Journal of Service Research 21(1), 2018. ↩ ↩²

11. Service Design Network, “The Service Design Maturity Model.” Five stages: Explore, Prove, Scale, Integrate, Thrive. ↩