Customer Value and Lean Service Logic

Introduction

Lean begins with a deceptively difficult question: what does the customer actually value? An activity may be important to an organisation, convenient for employees, or required by a regulator, yet still fail to create value from the customer’s perspective. Conversely, a short conversation, a reliable status update, or a clear explanation may create substantial value even though it produces no physical product.

Customer value is therefore the foundation of Lean Manufacturing and Service Blueprinting. Lean does not mean simply reducing cost or eliminating people. It means designing and managing a system that reliably delivers what matters to customers and stakeholders, with minimum delay, effort, error, risk and resource consumption. Service blueprinting complements this logic by making visible the customer journey, front-stage interactions, backstage activities, support processes and points at which value is created or lost.

In manufacturing, value is often associated with product features, conformance, delivery and price. In services, value is co-created through interactions, access, information, trust, responsiveness and outcomes. In both settings, value must be defined by the recipient of the process rather than assumed by the producer.

Learning objectives

By the end of this chapter, the reader should be able to:

1. Explain customer, stakeholder and perceived value in Lean contexts.
2. Use Voice of the Customer, Kano analysis and critical-to-quality requirements to translate needs into operational specifications.
3. Construct a value proposition and analyse demand across a customer journey.
4. Distinguish value-added, business-necessary and non-value-added work.
5. Apply Lean service logic and service-blueprinting concepts to improve a process.
6. Evaluate the limitations, ethical risks and managerial implications of customer-value analysis.

1. The meaning of value

A useful starting definition is:

Value is the combination of outcomes and experience that a defined customer or stakeholder considers worthwhile relative to the sacrifices required to obtain it.

The sacrifices may include price, time, physical effort, cognitive effort, inconvenience, uncertainty, privacy loss and risk. Value is thus multidimensional and contextual. A hospital patient may value clinical effectiveness most strongly, but also dignity, understandable information and short waiting time. A business customer may value process reliability, integration capability and total cost of ownership more than a product’s appearance.

1.1 Customer value and stakeholder value

The direct customer is not always the only relevant evaluator. A service may affect:

• the user, who experiences the service;
• the purchaser, who pays for it;
• the beneficiary, who receives the outcome;
• employees, who deliver the process;
• suppliers and partners;
• regulators and professional bodies; and
• communities and the environment.

These groups can hold conflicting expectations. A purchaser may seek the lowest price, while the user seeks speed and personal attention. A regulator may require documentation that the customer regards as burdensome. Lean analysis must make these tensions explicit rather than treating one perspective as universally correct.

A practical value statement identifies three elements: the customer segment, the desired outcome and the conditions that define acceptable delivery. For example: “For outpatient patients requiring diagnostic imaging, value means receiving an accurate result safely, at the promised time, with understandable communication and minimal unnecessary effort.”

1.2 Perceived value is not identical to technical performance

Technical quality and perceived value are related but not equivalent. A technically excellent service can be judged poorly if access is difficult or communication is confusing. Conversely, a pleasant interaction cannot compensate indefinitely for an unsafe or ineffective outcome. Lean managers should therefore examine both outcome quality and experience quality.

A conceptual representation is:

This is not a universal measurement equation; it is a conceptual model. The function depends on the customer segment and the situation. In emergencies, speed may dominate price. In a highly regulated process, compliance and traceability may be non-negotiable.

2. Voice of the Customer

Voice of the Customer (VoC) is the systematic collection and interpretation of customer statements, behaviours, complaints, expectations and usage evidence. It is not limited to surveys. Useful sources include interviews, observation, call-centre records, online reviews, complaint analysis, customer support tickets, transaction data, social listening, ethnographic research and frontline-employee knowledge.

2.1 Stated, unstated and latent needs

Customers express needs in different forms:

• Stated needs: “I want an appointment within two days.”
• Unstated needs: The customer expects staff to protect confidentiality even if this is not mentioned.
• Latent needs: The customer may value a capability that has not previously been available, such as automatic progress notifications.

A direct quotation is not yet a requirement. “I want the process to be easier” must be investigated. The analyst should ask: easier in what way—fewer forms, fewer visits, clearer instructions, shorter waiting, or less uncertainty?

2.2 A disciplined VoC process

A robust VoC process normally involves:

1. Define the customer and decision context. Identify users, purchasers, beneficiaries and affected stakeholders.
2. Select appropriate listening methods. Combine qualitative depth with quantitative breadth.
3. Capture the customer’s language. Record verbatim statements before interpreting them.
4. Group similar needs. Use affinity analysis to identify themes.
5. Separate needs from solutions. “A mobile application” is a proposed solution; “easy status visibility” is a need.
6. Prioritise. Consider importance, dissatisfaction, frequency, strategic relevance and feasibility.
7. Translate into measurable requirements. Define observable indicators and acceptable limits.
8. Validate. Return to customers or compare requirements with behavioural evidence.

A common failure is to ask customers to design the process. Customers are usually authoritative about their problems and desired outcomes, but they may not know the most efficient technical solution. Cross-functional design is therefore required.

3. Kano analysis: different kinds of requirements

The Kano model classifies requirements according to their relationship with satisfaction. Its traditional categories are:

A clean, safe hotel room may be a must-be attribute. Waiting time may be one-dimensional: shorter waiting generally produces greater satisfaction. A surprise upgrade may be attractive. However, categories are not permanent. An attractive feature can become a must-be expectation as competitors adopt it. Online parcel tracking illustrates this migration.

Kano analysis is commonly conducted by pairing functional and dysfunctional questions. For example:

• Functional: How would you feel if appointment confirmation were immediate?
• Dysfunctional: How would you feel if appointment confirmation were not immediate?

Response options typically include “I like it,” “I expect it,” “I am neutral,” “I can live with it,” and “I dislike it.” The resulting classifications should be interpreted cautiously because wording, culture, customer segment and context influence responses.

Kano analysis is especially useful for avoiding two errors: investing heavily in features that customers do not value, and underinvesting in basic requirements whose absence causes dissatisfaction even though their presence receives little praise.

4. From customer language to critical-to-quality requirements

Critical-to-quality (CTQ) requirements translate customer needs into measurable operational characteristics. The translation chain is often expressed as:

Need → driver → measurable requirement → specification → process measure

Example:

• Need: “I want confidence that my insurance claim is progressing.”
• Driver: visibility and predictability.
• Requirement: claim status is accessible without contacting an agent.
• Specification: status is updated after every defined process milestone.
• Process measure: percentage of milestones generating a timely customer update.

A good CTQ has a clear unit, measurement method, target and tolerance. “Fast response” is weak. “Ninety-five percent of web enquiries receive an initial response within four business hours” is stronger because it defines population, measure, target and time window.

For a measurable characteristic x, conformance may be expressed as:

where L is the lower specification limit and U is the upper specification limit. The limits must be appropriate to the customer requirement and the measurement system. For a one-sided requirement such as “response time no greater than four hours,” only an upper limit may be relevant:

Specification limits are not the same as control limits. Specification limits represent customer or regulatory requirements; control limits are statistically estimated boundaries used to judge process stability. Confusing the two can lead to incorrect conclusions about quality.

4.1 CTQ trees

A CTQ tree helps decompose broad needs. For “easy account opening,” the branches might be:

• low effort: limited repeated data entry;
• clarity: understandable instructions;
• speed: completion within a defined time;
• reliability: no loss of entered information; and
• assurance: secure handling of personal data.

Each branch should be tested with customers. Decomposition is not merely an internal exercise; it is a hypothesis about what creates value.

5. Value propositions and demand analysis

A value proposition explains why a defined customer segment should choose an offering. It should connect a problem, a promised outcome and credible differentiation. A useful structure is:

For [target segment] who need [job or outcome], our offering provides [principal benefit] through [distinctive mechanism], unlike [alternative], because [evidence or capability].

For example: “For small manufacturers needing predictable maintenance, the service provides rapid restoration and transparent status updates through remote diagnostics and standardised response protocols, unlike ad hoc repair arrangements.”

A value proposition is not a slogan. It is a set of operational promises. If the organisation promises rapid restoration, the process must have capacity, information, skills and escalation rules to deliver it.

5.1 Customer jobs and journey stages

Customer-journey analysis examines what the customer is trying to accomplish across stages such as:

1. becoming aware of an option;
2. evaluating alternatives;
3. requesting or purchasing;
4. receiving the product or service;
5. using it;
6. obtaining support; and
7. renewing, switching or recommending.

At each stage, analyse customer goals, actions, emotions, information needs, failure points, channels and measures. The journey is not necessarily linear. Customers may repeat stages, abandon the process or enter through a service failure.

Demand has both volume and variety. Volume concerns how many requests arrive; variety concerns differences in type, urgency, complexity and service requirements. A process designed for average demand may fail when demand is variable. Managers should distinguish:

• value demand: requests that the service exists to fulfil;
• failure demand: requests caused by a previous failure, such as “Where is my order?” after an absent notification; and
• avoidable demand: requests created by unclear information, unnecessary approvals or poor channel design.

Reducing failure demand often creates more customer value than simply processing calls faster.

Where demand and capacity require quantitative analysis, the following relationships are useful:

Both workload and capacity must use the same unit, such as cases per hour. Utilisation near 100% leaves little protection against variability and often increases waiting. In queueing systems, waiting can increase disproportionately as utilisation approaches full capacity; therefore, capacity planning must consider variability rather than rely only on average demand.

For a paced process, the available time per period and required output can be related through takt time:

Takt time is a planning rhythm, not the actual cycle time and not a promise that every customer will arrive uniformly. For example, if a service centre has 420 available minutes in a day and demand is 70 completed cases, takt time is 6 minutes per case. Breaks, planned meetings and unavailable resources should be excluded from available time. Takt is meaningful only when demand and available time are defined consistently.

6. Service blueprinting and Lean service logic

A service blueprint is a visual representation of how a service is experienced and delivered. It normally includes:

• customer actions;
• visible employee or technology interactions;
• the line of interaction between customer and provider;
• backstage activities not visible to the customer;
• support processes and suppliers;
• evidence of service, such as messages, forms, receipts or physical facilities; and
• failure points, controls and performance measures.

The blueprint connects the customer journey to the operating system. It prevents a common design error: improving a front-stage interaction while leaving the backstage process slow, repetitive or error-prone.

Figure: A simplified service blueprint linking customer actions with delivery and support processes.

6.1 Lean service logic

Lean service logic applies familiar Lean principles to intangible, information-rich and interaction-based work:

• define value from the customer’s perspective;
• identify the end-to-end value stream;
• establish flow of information and work;
• use pull where demand triggers delivery;
• pursue continuous improvement; and
• build quality into the process.

Service work differs from factory work in important ways. Customers may participate directly in production, demand is often uncertain, capacity is perishable, and quality may be judged during the interaction. Standardisation must therefore be balanced with human judgement. A script can reduce omission risk, but excessive scripting can destroy empathy and responsiveness.

7. Classifying work: value-added, business-necessary and non-value-added

A central Lean discipline is to classify every significant activity according to its relationship with customer value.

7.1 Value-added work

An activity is generally value-added when it:

1. changes the product, service or information in a way the customer values;
2. is performed correctly the first time; and
3. is required to deliver the customer’s intended outcome.

Examples include assembling a required feature, diagnosing a patient accurately, transferring funds correctly, or providing a decision the customer needs.

7.2 Business-necessary work

Business-necessary work does not directly create customer value but is currently required for legal, regulatory, safety, financial-control, risk or organisational reasons. Examples include statutory reporting, identity verification, audit trails and some reconciliations.

The category should not become a permanent excuse. The Lean response is to simplify, automate, integrate or redesign such work while preserving its legitimate purpose. A duplicate approval may be described as “necessary” only because the process has not been redesigned.

7.3 Non-value-added work

Non-value-added work consumes resources without improving the customer outcome and without a valid present necessity. Examples include rework caused by incorrect data entry, duplicate transcription, searching for information, waiting for avoidable approval, unnecessary movement, excessive handoffs and producing reports that nobody uses.

The classic Lean wastes—transport, inventory, motion, waiting, overproduction, overprocessing, defects and underused human capability—appear in services as email queues, excessive work-in-progress, repeated customer explanations, duplicated data entry, avoidable escalation and unused employee knowledge.

The distinction is analytical, not moral. An employee who waits for an approval is not personally wasteful; the system may be designed to create waiting. Improvement should address the process and its constraints rather than blame individuals.

A useful test is to ask: “Would the customer willingly pay for this activity if its purpose were explained?” This test is not conclusive—customers may not pay directly for safety or compliance—but it stimulates disciplined inquiry.

8. Worked application: reducing failure demand in a municipal permit service

Background

The following is an illustrative case. A municipal authority processes small-business outdoor seating permits. Applicants complain that decisions are slow and that requirements are unclear. The authority believes it needs more staff, but preliminary observation suggests that many enquiries are caused by process failures.

Problem and analysis

A four-week review finds 800 applications and 1,200 telephone or email contacts. Of these contacts, 480 ask whether an application has been received, 300 ask which documents are missing, 240 request status information, and 180 concern substantive questions. Interviews identify three principal CTQs:

• acknowledgement of a complete submission within one business day;
• a clear decision or reasoned request for information within ten business days; and
• status visibility without repeated contact.

The current blueprint shows that applicants submit a form through one channel, staff re-enter the data into a case system, supervisors review completeness, and applicants receive no automatic notification. Missing information is often discovered late. The service contains duplicate data entry, waiting for batch review and failure demand.

Approach

The redesigned process uses a single structured intake form, immediate confirmation, mandatory document checks, a case-status portal and automated notifications at defined milestones. Staff retain discretion for unusual cases. A daily visual management board displays ageing cases and exceptions. A pilot is conducted with one permit category before wider implementation.

The authority measures:

• first-time-complete submission rate;
• percentage of acknowledgements within one business day;
• median and 90th-percentile decision time;
• number of status enquiries per application;
• rework rate; and
• applicant satisfaction, segmented by business size and accessibility needs.

Outcome

After the pilot, status enquiries fall substantially because applicants can see progress. Rework also falls because incomplete submissions are identified at the beginning. However, some applicants with limited digital access report difficulty using the portal. The authority therefore retains assisted telephone and in-person channels and ensures that accessibility is treated as a CTQ rather than as an exception.

Learning points

1. Demand analysis should distinguish value demand from failure demand.
2. A front-stage improvement requires backstage data and workflow redesign.
3. Automation can remove waste but can also create exclusion if access needs are ignored.
4. Measures should include speed, quality, equity and customer effort—not just staff productivity.
5. A pilot provides evidence while limiting the risk of scaling a flawed design.

9. Managerial, ethical and governance implications

Customer-value work involves choices about whose voice is heard. Heavy users, digitally confident customers and articulate respondents are often overrepresented. Managers should deliberately include vulnerable, infrequent and dissatisfied users. Segmentation should not be used to justify inferior safety or dignity for less profitable groups.

Data collection raises privacy and governance concerns. VoC programmes should define purpose, collect proportionate information, protect personally identifiable data, control access and communicate how feedback will be used. AI-based text analysis can identify themes in complaints, but automated classifications may reproduce language, cultural or accessibility bias. Human review, auditability and sampling checks remain necessary.

There is also an ethical risk in treating perceived value as a licence to manipulate customers. Dark patterns, hidden charges and excessive personalisation may increase conversion while reducing informed choice. Lean improvement should reduce customer effort without reducing transparency or autonomy.

Environmental and societal stakeholders should be included where an apparently efficient process creates external harm. For example, same-day delivery may increase packaging, emissions and unsafe work practices. A mature value definition considers lifecycle effects, not only immediate customer convenience.

10. Implementation guidance and limitations

Successful application generally follows these practices:

• begin with a clearly defined customer segment and outcome;
• combine qualitative listening with behavioural and operational data;
• map the complete journey rather than one department;
• distinguish symptoms from root causes;
• translate needs into CTQs with operational definitions;
• involve frontline employees and support functions;
• preserve necessary controls while challenging duplication;
• test changes through pilots and experiments;
• segment results to reveal unequal effects; and
• establish ownership for maintaining the blueprint and measures.

Several limitations should be recognised. Customers may report preferences that do not predict actual behaviour. Satisfaction scores can be influenced by expectations, mood and recent events. Kano categories can change over time. Averages may conceal vulnerable segments or long-tail failures. Removing a non-value-added activity may transfer work or risk elsewhere in the system. Finally, local optimisation can damage end-to-end value: reducing call duration may increase repeat calls, and maximising utilisation may increase waiting.

Contemporary service systems increasingly use self-service, conversational interfaces, real-time analytics and generative AI. These technologies can support faster search, triage and personalisation, but they do not remove the need to define value, validate requirements and govern risk. An AI assistant that responds quickly but provides inaccurate or unexplainable advice is not Lean value creation. Technology should be evaluated against CTQs, customer effort, reliability, accessibility, privacy and total system impact.

Chapter Summary

Customer value is defined by the outcomes and experiences that customers and stakeholders consider worthwhile relative to their sacrifices and risks. Lean requires organisations to make this value explicit before redesigning work. Voice of the Customer converts experience and evidence into an understanding of needs; Kano analysis distinguishes must-be, one-dimensional, attractive, indifferent and reverse requirements; and CTQs translate needs into measurable specifications.

Value propositions connect a customer segment and desired outcome to an operational promise. Customer-journey analysis reveals how needs, emotions, channels and failure points evolve across stages. Demand analysis distinguishes value demand from failure demand and recognises the effects of volume, variety and variability. Service blueprints connect customer actions with front-stage interactions, backstage work and support processes.

Work should be classified as value-added, business-necessary or non-value-added. Necessary work should be simplified or redesigned where possible, while waste should be removed without transferring risk or burden. Effective Lean service improvement combines customer evidence, process analysis, ethical governance, employee knowledge and measures of quality, speed, effort, equity and outcome.

Key Terms

Customer value: The worthwhile outcome and experience perceived by a customer relative to the sacrifices required.

Stakeholder value: Value considered from the perspective of all materially affected parties.

Voice of the Customer: Systematic collection and interpretation of customer needs, expectations and experiences.

Latent need: A need that customers may not articulate because it is unrecognised or not yet available.

Kano model: A framework classifying requirements by their effect on satisfaction.

Must-be requirement: A basic requirement whose absence causes strong dissatisfaction.

One-dimensional requirement: A requirement for which satisfaction changes with performance.

Attractive requirement: An unexpected feature that can create delight when present.

Critical-to-quality requirement: A measurable characteristic essential to customer or stakeholder acceptance.

Specification limit: An upper or lower boundary defining acceptable performance.

Value proposition: A statement connecting a target segment, desired outcome and distinctive offering.

Customer journey: The sequence of customer experiences and actions across an offering’s lifecycle.

Failure demand: Demand caused by a previous failure, omission or unclear process.

Service blueprint: A visual map of customer actions, interactions, backstage work and support processes.

Front stage: Activities visible to or directly experienced by the customer.

Backstage: Activities that support delivery but are not normally visible to the customer.

Value-added work: Work that changes the offering in a way the customer values and that is done correctly.

Business-necessary work: Work without direct customer value that is currently required for legitimate control or compliance.

Non-value-added work: Work that consumes resources without creating value or valid necessity.

Takt time: Available operating time divided by customer demand, used as a planning rhythm.

Review Questions

Short Answer Questions

1. Define customer value and identify three sacrifices that may influence perceived value.
2. What is the difference between a stated need and a latent need?
3. Explain the distinction between a CTQ specification limit and a process control limit.
4. Define failure demand and provide one service example.
5. What distinguishes business-necessary work from non-value-added work?

Long Answer Questions

1. Explain how Voice of the Customer data can be transformed into CTQs. Use an illustrative service example.
2. Discuss the Kano model and explain why requirement categories may change over time.
3. Describe the principal components of a service blueprint and explain how it supports Lean improvement.
4. Critically evaluate the use of customer satisfaction as a measure of value.
5. Explain how Lean service logic must be adapted to account for customer participation, demand variability and human judgement.

Analytical / Application Questions

1. A university helpdesk receives repeated enquiries asking whether tickets have been received and when they will be resolved. Construct a mini customer journey, identify likely failure demand and propose three CTQs.
2. A claims process takes 18 minutes of staff work per case, but only 6 minutes directly changes the claim outcome. Classify the remaining work using the three-category framework and explain what evidence is needed before eliminating it.
3. A service centre has 420 available minutes per day and expected demand of 70 completed cases. Calculate takt time and explain why management must not treat it as a guaranteed individual service time.

Multiple Choice Questions with Answers

Question 1

Which statement best defines customer value in Lean service logic?

A. The total amount of work performed by employees

B. The outcome and experience the customer considers worthwhile relative to required sacrifices

C. The lowest possible operating cost

D. The number of features included in a service

Correct Answer: B. The outcome and experience the customer considers worthwhile relative to required sacrifices

Question 2

Which Kano category describes a requirement whose absence causes strong dissatisfaction but whose presence may not generate praise?

A. Attractive

B. Reverse

C. Must-be

D. Indifferent

Correct Answer: C. Must-be

Question 3

Which is the strongest example of a critical-to-quality requirement?

A. Customers want better service

B. Employees should work efficiently

C. The website should look modern

D. Ninety-five percent of enquiries receive an initial response within four business hours

Correct Answer: D. Ninety-five percent of enquiries receive an initial response within four business hours

Question 4

A customer asks for a mobile application, but investigation shows the underlying need is visibility of order progress. What has the analyst identified?

A. A solution disguised as a need

B. A regulatory specification

C. A control limit

D. A business-necessary activity

Correct Answer: A. A solution disguised as a need

Question 5

Which activity is most likely to be classified as failure demand?

A. A customer requesting the service for the first time

B. A customer asking where an order is because no promised status update was sent

C. A customer purchasing an optional feature

D. A regulator requesting a statutory report

Correct Answer: B. A customer asking where an order is because no promised status update was sent

Question 6

A service centre has 420 available minutes per day and demand for 70 completed cases. What is the takt time?

A. 4 minutes per case

B. 5 minutes per case

C. 6 minutes per case

D. 7 minutes per case

Correct Answer: C. 6 minutes per case

Question 7

Which element of a service blueprint represents activities that support delivery but are normally invisible to the customer?

A. Customer actions

B. Backstage activities

C. Physical evidence only

D. The value proposition

Correct Answer: B. Backstage activities

Question 8

Which statement about business-necessary work is most accurate?

A. It always creates direct customer value

B. It should never be questioned

C. It may be required for legitimate compliance or control and should be simplified where possible

D. It is identical to defective work

Correct Answer: C. It may be required for legitimate compliance or control and should be simplified where possible

Question 9

If workload is 80 cases per hour and available capacity is 100 cases per hour, utilisation is:

A. 0.20

B. 0.80

C. 1.25

D. 180

Correct Answer: B. 0.80

Question 10

Why should customer-value analysis include vulnerable and infrequent users?

A. They always generate the highest revenue

B. They may be underrepresented in ordinary feedback and experience unequal effects

C. They eliminate the need for operational data

D. They make Kano analysis unnecessary

Correct Answer: B. They may be underrepresented in ordinary feedback and experience unequal effects