Loading field map
For most of the twentieth century, operations management was built around factories. Goods could be inspected before delivery, stored in inventory, and produced in long, predictable runs. Services, by contrast, are intangible, perishable, and often produced in the presence of the customer. A haircut cannot be warehoused; a hospital stay cannot be quality-checked before the patient arrives. This fundamental difference forced a new subfield—service operations—to develop its own frameworks, borrowing from manufacturing but also breaking with it. The history of service operations is not a simple parade of better tools; it is a layered accumulation of frameworks that each addressed a different facet of the service puzzle: how to design, measure, justify, improve, and ultimately reconceive the nature of service itself.
The earliest frameworks in service operations tackled two distinct problems simultaneously. One was the problem of design: how do you map a process when the customer is part of it? The other was the problem of measurement: how do you assess quality when the product is an experience?
Service Blueprinting, introduced in 1984, answered the design question. It provided a visual tool that separated service activities into "onstage" actions visible to the customer and "backstage" actions hidden from view, connected by a line of visibility. Crucially, the blueprint also mapped the customer's own actions and the physical evidence the customer encounters. This was a direct adaptation of industrial process flowcharts, but with a new emphasis on the customer's role as a co-producer of the service. Service Blueprinting did not reject manufacturing thinking; it extended it by making the customer's presence a structural element of the process design.
At nearly the same moment, SERVQUAL (1985) addressed the measurement problem. Its developers argued that service quality could be captured by comparing customer expectations with their perceptions of actual performance across five dimensions: reliability, assurance, tangibles, empathy, and responsiveness. The gap between expectation and perception became the operational definition of quality. Where Service Blueprinting gave managers a design tool, SERVQUAL gave them a survey instrument. The two frameworks coexisted without much conflict because they targeted different stages of the service cycle—design before delivery, measurement after it. But they rested on different assumptions: Service Blueprinting treated quality as something built into process architecture, while SERVQUAL treated it as something perceived by the customer after the fact.
By the early 1990s, service operations had design and measurement tools, but it lacked a compelling argument for why senior executives should invest in them. The Service Profit Chain (1994) supplied that argument. It proposed a causal chain: internal service quality drives employee satisfaction, which drives employee retention and productivity, which drives external service value, which drives customer satisfaction and loyalty, which drives revenue and profit. This was not a narrow operational tool but a strategic framework that linked front-line operations to financial outcomes.
The Service Profit Chain coexisted with Service Blueprinting and SERVQUAL, but it narrowed the conversation in an important way. It treated customer satisfaction primarily as a means to profitability, not as an end in itself. By the late 2000s, the framework's influence waned not because it was wrong, but because its core insight—that service operations matter for financial performance—had been absorbed into the broader field of operations strategy. The chain's causal logic became background knowledge rather than a standalone research program.
While service academics were developing their own frameworks, practitioners began importing two powerful improvement methodologies from manufacturing: Lean Production and Six Sigma. Their adaptation to services created Lean Services and Six Sigma in Services, which entered the service operations toolkit in the 1990s.
Lean Services (1990–Present) applied the principles of waste reduction, flow, and pull to service processes. The distinctive shift, as the evidence pack notes, is that "the customer being in the system during the production and delivery of the service" distinguishes services from manufacturing. Lean Services adapted tools like value-stream mapping to include the customer's journey, and it redefined waste in service terms—waiting time, unnecessary handoffs, redundant data entry. It shared with Service Blueprinting a focus on process visualization, but Lean Services added a relentless emphasis on eliminating non-value-adding steps.
Six Sigma in Services (1995–Present) brought a different manufacturing inheritance: statistical control of variation. In manufacturing, Six Sigma aimed to reduce defects to 3.4 per million opportunities. In services, the "defect" was harder to define—a rude call-center agent, a delayed claim payment, a confusing website. Six Sigma in Services adapted the Define-Measure-Analyze-Improve-Control (DMAIC) cycle to service contexts, using data to identify root causes of variation in customer experience. It overlapped with SERVQUAL's concern for measuring quality gaps, but where SERVQUAL relied on perceptual surveys, Six Sigma demanded objective process metrics.
Lean Services and Six Sigma in Services often coexisted in practice, eventually merging into "Lean Six Sigma" in many organizations. But they preserved different emphases: Lean Services focused on flow and waste, Six Sigma on variation and statistical control. Both remained active frameworks, and both were narrower than Service Blueprinting in scope—they were improvement methodologies, not design or strategy frameworks.
All the frameworks described so far treated service as a type of output—something firms produce and deliver to customers. Service-Dominant Logic (2004) challenged that assumption at its root. It argued that service is not a special kind of good but the fundamental basis of all economic exchange. Goods are merely distribution mechanisms for service; value is always co-created by the provider and the customer through use, not embedded in an output at the factory gate.
This was a conceptual revolution, not a tool or methodology. Service-Dominant Logic reframed every earlier framework as implicitly goods-dominant. SERVQUAL's expectation-perception gap, for example, assumed that value was delivered and then evaluated, rather than co-created during the interaction. Service Blueprinting, despite mapping the customer's actions, still drew a line between provider and customer rather than treating them as joint resource integrators. Lean Services and Six Sigma in Services, by focusing on waste and variation reduction within the provider's process, risked optimizing the wrong thing if value was actually being co-created in unpredictable ways.
Service-Dominant Logic did not replace these frameworks; it repositioned them. It remains active today as a theoretical lens, especially in marketing and service research, but it has not produced a direct operational toolkit. Its influence is felt in the growing emphasis on customer experience management, service ecosystems, and value-in-use.
Today, no single framework dominates service operations. Instead, the field operates with a division of labor among the frameworks that remain active: Service Blueprinting, Lean Services, Six Sigma in Services, and Service-Dominant Logic.
Service Blueprinting is widely used in service design and innovation, especially in digital services and customer experience mapping. Lean Services and Six Sigma in Services are the dominant improvement methodologies in service organizations, often combined in practice. Service-Dominant Logic shapes academic research agendas and informs strategic thinking about value creation, though it has less direct influence on day-to-day operations.
What these leading frameworks agree on is that the customer's presence and participation are central to service operations—a point that earlier manufacturing models ignored. They also agree that service quality cannot be inspected into a process; it must be designed, measured, and improved systematically.
Where they disagree is on the primary lever for improvement. The measurement-driven tradition (Six Sigma in Services, and historically SERVQUAL) treats quality as a problem of variation and perception, solvable through data and statistical control. The process-design tradition (Service Blueprinting, Lean Services) treats quality as a problem of flow and architecture, solvable through visualization and waste elimination. And the value-cocreation tradition (Service-Dominant Logic) treats quality as an emergent property of interactions, not fully controllable by either measurement or design. This tension—between control and emergence, between provider-centric optimization and customer-centric co-creation—remains the central unresolved debate in service operations.
SERVQUAL and the Service Profit Chain, while no longer leading frameworks, left lasting legacies. SERVQUAL's dimensions of service quality are still used in customer satisfaction surveys, even if the gap model itself has been absorbed into broader quality frameworks. The Service Profit Chain's causal logic is now standard background knowledge in operations strategy, no longer needing its own label. The subfield's history is one of accumulation: each framework added a layer of understanding, and the active ones today continue to coexist in productive tension.