Service Innovation Research: The Academic Foundations -- From Service-Dominant Logic to the 6-Dimensions Model

Why should you, as a practitioner, care about what academics have written on service innovation? Because theory is not abstract — it determines which methods work and why. Most service innovation initiatives fail not because of missing ideas or insufficient budgets but because they rest on assumptions that research has refuted for decades.

When you develop a service the way you would develop a product, involve customers only at the end, and reduce innovation to technology, you are repeating mistakes that the scientific literature has documented dozens of times. The good news: three decades of research have established clear reference points. Knowing them helps you avoid the costliest errors and leverage the most effective instruments.

This article synthesizes the six most important research streams in service innovation and translates them into actionable insights: from Vargo and Lusch’s Service-Dominant Logic to den Hertog’s 6-Dimensions Model, Gallouj and Weinstein’s innovation typology, and service ecosystem research. Each section answers two questions: What does the research say? And what does it mean for your practice?

Service-Dominant Logic: The Paradigm Shift (Vargo & Lusch)

What Changed Fundamentally in 2004

In 2004, Stephen Vargo and Robert Lusch published an article in the Journal of Marketing that fundamentally changed the understanding of value creation. Their central thesis: the entire economy is based not on the exchange of goods but on the exchange of service — the application of competencies (knowledge and skills) for the benefit of another actor.¹

That may sound academic at first. The practical consequences are radical.

Five Foundational Premises for Practitioners

Vargo and Lusch formulated their Service-Dominant Logic (SDL) through a series of foundational premises that they refined across several publications (2004, 2008, 2016). Five of these are directly actionable for service innovation:

1. Service is the fundamental basis of exchange. It is not the physical product that creates value but the service it enables. A drill has no value in itself — the hole in the wall is the service. A car has no value in itself — mobility is the service. For service innovation, this means: start not with the product but with the performance the customer actually needs.

2. Value is always co-created with the customer. Organizations can make value propositions, but value only emerges when the customer integrates them into their own context. An insurance product has no value on its own — value is created when the customer receives the right support at the moment of a claim. This explains why services developed without customer involvement systematically miss the mark.

3. All economic actors are resource integrators. Neither the organization nor the customer acts alone. Both integrate resources from multiple sources — their own knowledge, technology, networks, information. Service innovation therefore means: not optimizing a single resource but changing how resources interact.

4. Value is uniquely and phenomenologically determined by the beneficiary. What a service is worth is decided not by the provider but by the customer — individually, context-dependently, and subjectively. An identical consulting service can be transformative for a startup and worthless for a corporation. This has consequences for measuring service innovation success: standardized output metrics do not capture actual value.

5. Service innovation = reconfiguring actors and resources in value-creating service ecosystems. In their 2016 refinement, Vargo and Lusch emphasize that innovation does not occur within a single organization but in ecosystems — networks of providers, customers, partners, and institutions. Anyone who looks only at their own organization sees, at best, half of the innovation space.

Why This Is Decisive for Practice

SDL explains why methods from product development structurally fail for services. A stage-gate process assumes that value is created within the firm and then handed over to the customer. SDL demonstrates: this model is wrong for services. Value emerges in the interaction, not in manufacturing. Any development process that does not involve the customer from the outset misses its target — not because of poor execution but because of flawed foundational assumptions.

This is precisely the pattern that the article Why Service Innovation Fails documents under the label “co-production blindness”: services developed “for” rather than “with” customers.

The 6-Dimensions Model of Service Innovation (den Hertog)

What the Model Describes

Pieter den Hertog initially developed a four-dimensional model (2000), which he expanded with Wietze van der Aa and Mark de Jong into a six-dimensional framework (2010). It answers a central question: What exactly changes during a service innovation?²

The six dimensions:

Dimension 1: New service concept. A fundamentally new idea of what value the service creates for the customer. Not an incremental improvement of the existing offering but a new value proposition. Example: An insurer no longer sells a policy but a prevention-and-protection ecosystem that prevents damage before it occurs.

Dimension 2: New customer interaction. How the customer experiences the service, contributes, and co-creates. The interface between organization and user. Example: An automotive manufacturer transforms the workshop visit from a passive waiting experience into transparent real-time tracking with proactive communication.

Dimension 3: New business model and revenue model. How the service generates revenue — subscription, pay-per-use, freemium, commission models, hybrid models. Example: Kaeser Compressors sells compressed air instead of compressors (servitization).

Dimension 4: New delivery system (technology and organization). The technological and organizational infrastructure behind the service: platforms, APIs, processes, team structures, governance. Example: Allianz builds a Global Digital Factory that scales local claims innovations into global platform solutions.

Dimension 5: New partner and network configuration. Which partners, suppliers, or platform participants are involved in service delivery. Example: VW opens vehicle data to third-party providers — the car becomes a platform for ecosystem services.

Dimension 6: New internal organizational system. Changes in human resource development, corporate culture, organizational structure, and internal processes that enable the new service. Example: Deutsche Telekom establishes an autonomous CX team that operates without management approval for individual decisions.

The Strategic Finding: The Single-Dimension Trap

The most important insight from den Hertog’s research for practitioners: most organizations change only one or two dimensions — typically Dimension 4 (new technology) — and call the result “service innovation.” Truly transformative service innovation touches three or more dimensions simultaneously.

This explains a phenomenon familiar to many organizations: the new technology is implemented, but the expected impact fails to materialize. Not because the technology is poor, but because the service concept, customer interaction, business model, and organization did not co-evolve.

Practical application: Use the six dimensions as a diagnostic checklist. For every service innovation initiative: Which dimensions are we changing — and which are we leaving unchanged, consciously or unconsciously? If the answer is “only technology,” you are probably looking at digitization, not service innovation.

This diagnostic perspective complements the service innovation process, which describes how innovation initiatives are governed phase by phase. Den Hertog’s dimensions clarify the “What is being innovated?” while the process clarifies the “How is it being innovated?”

Innovation Typology for Services (Gallouj & Weinstein)

Beyond “Radical vs. Incremental”

The common distinction between radical and incremental innovation is insufficient for services. In 1997, Faiz Gallouj and Olivier Weinstein demonstrated that service innovation encompasses six qualitatively different types, each with distinct management requirements:³

Type	What happens	Practical example	Management implication
Radical	Entirely new service concept with new competence and technology vectors	Car-sharing as an alternative to vehicle ownership	High uncertainty; requires explore metrics and ambidexterity
Improvement	Existing characteristics significantly enhanced without changing the core concept	Claims processing reduced from 14 days to 1 hour	Measurable ROI; integrable into existing structures
Incremental	Step-by-step extension or addition of individual characteristics	New feature in an existing customer app	Low risk, low strategic leverage
Ad hoc	Situational, one-off solution in customer interaction	Consultant develops a bespoke solution for a single client	Valuable knowledge, but not scalable without formalization
Recombinative	New combination of existing service elements	Telematics + insurance + prevention = pay-how-you-drive	Highest ROI at moderate risk; requires modular thinking
Formalization	Systematization of informal or implicit practice	Tacit consultant knowledge becomes a documented methodology	Leverages existing knowledge; almost never pursued deliberately

Why Recombinative Innovation Is Underestimated

Gallouj and Weinstein’s most important contribution to practice is making recombinative innovation visible. In a service economy where services consist of modular elements, the greatest innovation potential often lies not in inventing something entirely new but in reassembling existing building blocks.

Consider an example: an insurance company has a telematics platform, claims data, a prevention advisory service, and a customer retention program. Each element exists independently. The innovation is combining them into an integrated “predict-prevent-protect” service. That is neither incremental (no single characteristic is improved) nor radical (no entirely new concept). It is recombinative — and precisely this type falls through the cracks in conventional innovation processes because it is neither spectacular enough for the innovation department nor trivial enough for the business unit.

Why Ad Hoc Innovation Is Overrepresented

At the other end of the spectrum stands ad hoc innovation: individual problem-solving in customer interactions. It happens constantly, generates valuable knowledge — and is almost never systematically captured. Customer advisors, service technicians, and sales staff solve problems every day that exist in no knowledge base. This knowledge stays in individual heads until those individuals leave the organization.

The connection to formalization is direct: formalization makes ad hoc knowledge scalable. But it requires a systematic process of knowledge extraction — and very few organizations actively pursue one.

New Service Development: Why Services Need Their Own Process (Johnson et al.)

The NSD Process Compared with NPD

In 2000, Johnson, Menor, Roth, and Chase published the first comprehensive model for New Service Development (NSD) — documenting the fundamental difference from New Product Development (NPD):⁴

NPD (product development) follows a linear model: specification -> development -> test -> launch. The customer enters at the end as buyer or non-buyer. The product is finished before market entry.

NSD (service development) follows a cyclical model: design -> analysis -> development -> launch, with feedback loops between every phase. The customer is a co-producer from the very first moment. The service is never “finished” — it evolves through use.

Johnson et al. identified four central differences:

1. Holistic development. NSD must simultaneously develop the service concept, the service delivery system, and the customer experience — not sequentially.
2. Continuous customer involvement. Not just at the testing stage but from ideation through design to implementation. The reason: since the customer participates in service delivery, a service developed without them cannot structurally function.
3. Iterative nature. Linear processes fail because services vary during delivery. What works in the lab must be adjusted in the field — systematically, not as an emergency measure.
4. Integration of technology and organization. NPD can treat technology development and organizational implementation sequentially. NSD must develop both simultaneously because organizational embedding is part of the service itself.

Governance Implications

The most important governance difference: NPD can be managed with stage-gates because each phase has a definable deliverable (specification, prototype, pilot batch). NSD requires iterative gates that explicitly permit feedback loops — and do not treat them as failure.

Organizations that transfer their product development process to services systematically produce a pattern described in the literature as the “service development trap”: the process produces fully documented service blueprints that fail in implementation because they do not account for the variability and co-production inherent in real service delivery.

The service innovation process shows in detail which frameworks best meet these requirements and where the pitfalls lie.

Service Blueprinting: The Research Foundation of Making the Invisible Visible (Shostack, Bitner)

The Origin: Shostack Makes Services Tangible

In 1982 in the European Journal of Marketing and in 1984 in the Harvard Business Review, G. Lynn Shostack laid the foundations for one of the most influential methods in service design: the service blueprint.⁵ Her central insight: services fail not because individual steps lack quality but because the overall process is invisible. What you cannot see, you cannot manage.

Shostack developed the blueprint as a visualization tool that maps the entire service process — customer actions, visible employee actions, invisible backstage processes, and support systems. The “line of visibility” separates what the customer sees from what happens behind the scenes. This simple distinction proved transformative because it allowed, for the first time, the precise localization of service failure causes.

Empirical Evidence: Bitner, Ostrom, and Morgan

Mary Jo Bitner, Amy Ostrom, and Felicia Morgan provided the empirical evidence in 2008:⁵ service blueprinting measurably improves service quality, customer satisfaction, and operational efficiency. Their most cited case study: ARAMARK at Lake Powell Resort. After systematic blueprinting of all service touchpoints, the complaint rate dropped by 50 percent — not because the service became more elaborate, but because the invisible processes were finally aligned with the visible customer experience.

The Core Research Insight

The blueprinting research delivers an insight that extends far beyond the method itself: The invisible parts of a service determine the visible customer experience. Most service problems originate not where the customer experiences them but in backstage processes, handoffs between departments, and support systems the customer never sees.

For service innovation, this means: innovating only at the customer interface (Dimension 2 in den Hertog) falls short when the underlying systems (Dimensions 4 and 6) are not co-developed. A more attractive frontend on a dysfunctional backend produces frustration, not innovation.

The service blueprint as a method is described in detail in the dedicated practice article. The focus here is the research contribution: Shostack’s and Bitner’s work has empirically demonstrated that visualizing the invisible is the single most effective lever for improving service quality.

Service Ecosystems and Platforms (Lusch & Nambisan)

From the Dyad to the Ecosystem

In 2015, Robert Lusch and Satish Nambisan shifted the focus of service innovation research from the dyad (firm-customer) to the ecosystem (multi-actor network).⁶ Their central thesis: in a digitized economy, service innovation does not occur within individual organizations but in service ecosystems — networks of providers, customers, partners, regulators, and technology platforms.

Three concepts are particularly relevant for practitioners:

Service platforms as innovation infrastructure. Platforms enable innovation not through their own performance but by providing other actors with the tools and access to develop new services. Apple’s App Store is not an innovation in itself — it is the infrastructure on which hundreds of thousands of service innovations take place.

Resource density. Lusch and Nambisan introduced the concept of “resource density”: innovation occurs where many different resources (knowledge, technology, data, competencies) converge in close proximity. Platforms increase resource density by facilitating access to resources — thereby enabling innovation that no single actor could produce alone.

Institutional arrangements. Ecosystems function only when shared rules, norms, and standards exist — Lusch and Nambisan call them “institutional arrangements.” For organizations, this means: ecosystem-based service innovation requires not only technical interfaces (APIs) but also shared governance structures, trust frameworks, and incentive systems.

Implications for DACH Corporates

For large DACH organizations — automotive manufacturers, insurers, financial services providers, mechanical engineering companies — the ecosystem perspective fundamentally shifts the strategic question:

Old: “What new service can we develop as an organization?” New: “What service ecosystem can we build or orchestrate — and what role do we play in it?”

VW’s evolution from car-sharing operator (WeShare) to platform provider (vehicle data for third-party services) is a concrete DACH example of this strategic shift. The failed standalone service became the learning case for the successful ecosystem strategy.

The connection to business model innovation is direct: ecosystem-based service innovation almost always requires a new business model — because the value creation logic shifts from a linear delivery chain to network-based value creation.

German-Language Research Traditions

Why the DACH Perspective Is Distinctive

Anglo-Saxon service innovation research dominates the international literature, but the German-language research tradition has its own priorities and strengths that are particularly relevant for DACH organizations.⁷

Fraunhofer IAO: Service Innovation as an Engineering Discipline

The Fraunhofer Institute for Industrial Engineering (IAO) in Stuttgart has conducted systematic research on service innovation since the 1990s. The emphasis lies on “Service Engineering” — the approach of conducting service development with the same methodological rigor as product development. The Fraunhofer tradition has shaped the German understanding of service innovation: systematic, process-oriented, with a strong focus on formalization and repeatability.

For practice, this means: German organizations find in the Fraunhofer approach an entry point to service innovation that matches their engineering mindset — without losing the creativity and co-creation dimensions emphasized by the Anglo-Saxon design thinking tradition.

Springer-Verlag: The “Dienstleistungsmanagement” Series

The book series published by Springer-Verlag, edited by Manfred Bruhn and others, has shaped the academic discourse on service innovation in the German-speaking world for over three decades. Topics such as service quality, service marketing, and service excellence are covered more systematically here than in the Anglo-Saxon literature, which tends to rely more heavily on individual studies and journal articles.

DFG-Funded Research: Bruhn and Stauss

Manfred Bruhn (University of Basel) and Bernd Stauss (Bundeswehr University Munich) built the empirical foundation for service quality and customer satisfaction research in the German-speaking world through DFG-funded research programs. Their work on SERVQUAL adaptation and complaint management research is internationally influential and particularly relevant for organizations that want to understand service quality as a driver of innovation.

The Cultural Difference: Systematization vs. Disruption

A striking difference between the German-language and English-language research traditions: German research emphasizes formalization, systematization, and methodological rigor. Anglo-Saxon research emphasizes creativity, disruption, and entrepreneurial initiative. Both perspectives are valuable — and the most productive innovation practice combines them.

For DACH organizations, the opportunity lies precisely in this combination: uniting the German strength in systematic implementation (formalization in Gallouj’s sense) with the Anglo-Saxon strength in creative ideation (recombination and radical innovation). SI Labs has methodologically implemented this integrative approach in the Integrated Service Development Process (iSEP).

What This All Means for Your Practice

Three Actionable Insights from 30 Years of Research

1. Use den Hertog’s 6 dimensions as an innovation audit. Assess every service innovation initiative against all six dimensions: service concept, customer interaction, business model, delivery system (technology and organization), partner network, internal organizational system. Most organizations innovate on one or two dimensions — typically technology. If you change only one dimension and leave the other five untouched, the probability is high that the innovation will fail on the dimensions that were not co-developed. The typical failure patterns confirm this pattern empirically.

2. Shift your portfolio toward recombinative innovation. Gallouj and Weinstein’s research shows that most organizations engage in too much ad hoc and incremental innovation and too little recombinative innovation. Recombination — the new assembly of existing service building blocks — offers the highest ROI at moderate risk because the individual components are already proven. This does, however, require an overview of your own service elements, which very few organizations possess. A service module library is the prerequisite.

3. Involve customers throughout — not just at the end. This is not a recommendation; it is a structural condition. Service-Dominant Logic has shown that value emerges in co-creation. NSD research has shown that services must be developed in fundamentally different ways from products. Blueprinting research has shown that the invisible parts of a service determine the customer experience. All three research streams converge on a single statement: customer involvement in services is not optional but constitutive.

Further Reading

The research insights from this article inform all practice articles on service innovation:

• Service Innovation: Definition and Fundamentals — the practical application of the research described here
• The Service Innovation Process — six frameworks compared, based on NSD research
• Introducing Service Innovation — the inside-out approach to building internal innovation capability
• Measuring Service Innovation — a metrics framework that accounts for SDL’s phenomenological value determination
• Why Service Innovation Fails — 16 failure patterns directly derivable from the research
• Service Design — the methodology that emerged from Shostack’s blueprinting research
• Service Blueprint — the practice method with its research roots
• Customer Journey Mapping — a complementary tool for the customer perspective
• Business Model Innovation — Dimension 3 in the den Hertog model as an independent discipline
• Service Innovation FAQ — frequently asked questions with research references

Methodology and Sources

This article synthesizes six academic research streams in service innovation: Service-Dominant Logic (Vargo & Lusch), the 6-Dimensions Model (den Hertog et al.), the innovation typology (Gallouj & Weinstein), New Service Development (Johnson et al.), Service Blueprinting (Shostack, Bitner et al.), and Service Ecosystem research (Lusch & Nambisan). All sources are peer-reviewed and fully cited in their respective sections.

Limitations: The research is predominantly Anglo-Saxon in origin — DACH-specific evidence derives primarily from the Fraunhofer IAO and the Springer series on service management. Gallouj and Weinstein’s taxonomy (1997) was developed for traditional services and captures digital platform services only partially. Den Hertog’s model is descriptive, not normative — it describes what changes but not how to steer the change.

Note: SI Labs supports organizations in building internal service innovation capability. The research presented here forms the scientific foundation of our methodology.

References

Footnotes

1. Vargo, Stephen L. and Robert F. Lusch. “Evolving to a New Dominant Logic for Marketing.” Journal of Marketing 68, no. 1 (2004): 1—17. Updated in: Vargo, Stephen L. and Robert F. Lusch. “Service-Dominant Logic 2025.” Journal of the Academy of Marketing Science 36, no. 1 (2008): 1—10. Further developed in: Vargo, Stephen L. and Robert F. Lusch. “Institutions and Axioms: An Extension and Update of Service-Dominant Logic.” Journal of the Academy of Marketing Science 44, no. 1 (2016): 5—23. Eleven foundational premises and five axioms of Service-Dominant Logic; paradigm shift from goods-dominant to service-dominant logic. ↩

2. den Hertog, Pim, Wietze van der Aa, and Mark W. de Jong. “Capabilities for Managing Service Innovation: Towards a Conceptual Framework.” Journal of Service Management 21, no. 4 (2010): 490—514. Extension of the four-dimensional model (den Hertog, 2000) to six dimensions. Identification of six dynamic management capabilities for service innovation. Original work: den Hertog, Pim. “Knowledge-Intensive Business Services as Co-Producers of Innovation.” International Journal of Innovation Management 4, no. 4 (2000): 491—528. ↩

3. Gallouj, Faiz and Olivier Weinstein. “Innovation in Services.” Research Policy 26, no. 4-5 (1997): 537—556. First systematic innovation taxonomy for services. Six innovation types: radical, improvement, incremental, ad hoc, recombinative, formalization. Services as vectors of characteristics (outcome characteristics, provider competencies, technology, client competencies). ↩

4. Johnson, Susan P., Larry J. Menor, Aleda V. Roth, and Richard B. Chase. “A Critical Evaluation of the New Service Development Process.” New Service Development: Creating Memorable Experiences, edited by James A. Fitzsimmons and Mona J. Fitzsimmons, 1—32. Thousand Oaks: Sage Publications, 2000. First comprehensive NSD process model; four central differences from NPD; cyclical vs. linear model. Supplementary: Menor, Larry J., Mohan V. Tatikonda, and Scott E. Sampson. “New Service Development: Areas for Exploitation and Exploration.” Journal of Operations Management 20, no. 2 (2002): 135—157. ↩

5. Shostack, G. Lynn. “How to Design a Service.” European Journal of Marketing 16, no. 1 (1982): 49—63. Shostack, G. Lynn. “Designing Services That Deliver.” Harvard Business Review 62, no. 1 (1984): 133—139. Founding of service blueprinting as a method. Bitner, Mary Jo, Amy L. Ostrom, and Felicia N. Morgan. “Service Blueprinting: A Practical Technique for Service Innovation.” California Management Review 50, no. 3 (2008): 66—94. Empirical evidence: ARAMARK Lake Powell Resort, 50% fewer complaints after systematic blueprinting. ↩ ↩²

6. Lusch, Robert F. and Satish Nambisan. “Service Innovation: A Service-Dominant Logic Perspective.” MIS Quarterly 39, no. 1 (2015): 155—175. Three key concepts: service platforms as innovation infrastructure, resource density, institutional arrangements. Paradigm shift from dyadic to ecosystemic innovation perspective. ↩

7. Bullinger, Hans-Jorg, Klaus-Peter Fahnrich, and Thomas Meiren. “Service Engineering — Methodical Development of New Service Products.” International Journal of Production Economics 85, no. 3 (2003): 275—287. Foundational work of the Fraunhofer IAO on service engineering. Supplementary: Bruhn, Manfred and Karsten Hadwich, eds. Service Value als Werttreiber: Konzepte, Messung und Steuerung. Wiesbaden: Springer Gabler, 2014. Representative of the Springer series on service management. ↩