Customer Value, Lean Thinking and Waste

Introduction and context

Lean Management is a systematic approach to delivering greater customer value with fewer resources, shorter lead times and less instability. It is not simply a cost-reduction programme, a set of workplace-cleaning practices, or a collection of manufacturing tools. Lean is a management philosophy and operating system concerned with how work flows, how problems are exposed, and how people continuously improve processes.

The central question is deceptively simple: What does the customer value, and how can the organisation deliver it reliably with the least unnecessary effort? Answering that question requires more than listening to general customer opinions. It requires translating the voice of the customer (VOC) into measurable critical-to-quality (CTQ) requirements, examining the complete value stream, distinguishing useful work from avoidable work, and addressing the conditions that create waste.

Lean thinking applies in factories, hospitals, banks, universities, logistics operations, software development, government services and construction. In every setting, a customer or user receives an outcome through a process. The process may include information, decisions, materials, movement and human interaction. Some activities transform the product or service in a way the customer needs; others are necessary because of current controls or regulations; still others consume resources without creating value. Lean improvement makes these distinctions visible and then redesigns the system.

Learning objectives

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

1. Explain customer value and relate VOC to CTQ requirements.
2. Apply the five principles of Lean thinking.
3. Distinguish value-added, necessary non-value-added and pure waste.
4. Explain Muda, Mura and Muri and their relationship.
5. Identify the eight common wastes in operational processes.
6. Use process observation and value-stream analysis to locate waste.
7. Recommend practical, ethical and sustainable improvement actions.

1. Customer value: the starting point of Lean

A process creates customer value when its output satisfies a real customer need. In operational terms, an activity is normally regarded as value-adding when it meets three tests:

• The customer recognises the outcome as valuable and would require it.
• The activity transforms the product, service or information.
• The activity is performed correctly the first time.

For example, machining a component to the required dimension can be value-adding. In a medical service, a clinically appropriate examination may be value-adding. In a university, accurate assessment and useful feedback may be value-adding. By contrast, waiting for authorisation, searching for a missing file or correcting an avoidable error does not create value for the customer.

Value is contextual. A customer may value speed, reliability, safety, compliance, accessibility, personalisation, low environmental impact or total cost of ownership. The organisation must therefore avoid defining value only from its internal viewpoint. A department may consider a report complete when it has been produced, while the customer values a correct decision delivered before a deadline.

Voice of the customer and critical-to-quality requirements

VOC is the systematic collection and interpretation of customer needs, expectations, complaints and experiences. Sources include interviews, surveys, observations, call-centre records, warranty data, social media, complaints, service-level agreements and direct-use research. VOC statements are often expressed in subjective language, such as “I need the service quickly” or “The product must be dependable.” These statements must be translated into CTQs: measurable characteristics that define acceptable performance.

A CTQ should be operationally defined. “Fast” is not a useful specification until the organisation identifies the start point, end point, population, time unit and acceptable threshold. CTQs should also be prioritised: a critical safety requirement cannot be traded casually against a minor convenience feature.

A useful translation sequence is:

VOC statement → customer need → quality characteristic → measurable CTQ → process requirement → control and improvement action.

This sequence prevents a common Lean failure: improving internal efficiency while damaging the customer experience. For example, reducing staff handling time may appear efficient but could increase unresolved enquiries and repeat contacts.

2. The five principles of Lean thinking

The five principles, associated particularly with the work of Womack and Jones, provide a logical progression from customer need to continuous improvement.

2.1 Specify value

Value is specified from the perspective of the end customer at a particular time and for a particular product or service. The organisation should identify the purpose, required quality, acceptable cost, delivery expectation, safety conditions and experience attributes. Internal convenience is not automatically customer value.

Specification requires segmentation where customers have different needs. A hospital emergency patient, an elective patient and a clinical researcher do not have identical CTQs. A single average requirement may conceal important safety or access needs.

2.2 Identify the value stream

The value stream is the complete set of actions required to bring a product, service or information flow from request to fulfilment, including actions that add value and actions that do not. It crosses departmental and organisational boundaries.

Value-stream analysis records material and information flows, queues, decisions, rework, hand-offs and controls. A process map limited to one department may miss the largest delays, which often occur between departments or organisations. Current-state mapping should be based on observation and evidence rather than assumptions.

2.3 Make value flow

After waste and unnecessary interruptions are understood, work should move smoothly toward the customer. Flow means that items progress without avoidable waiting, batching, backtracking or repeated hand-offs. Flow does not mean rushing people or removing necessary checks. It means designing the process so that work is neither stopped by preventable obstacles nor pushed into large queues.

Flow is supported by clear work sequences, appropriate layout, reliable equipment, standard work, quick information transfer, balanced workloads and rapid response to abnormalities. In service work, flow may involve a case moving through a digital workflow rather than a physical line.

2.4 Establish pull

A pull system authorises production or service activity in response to actual downstream demand rather than speculative upstream forecasts alone. The customer signal may be an order, a replenishment card, a confirmed appointment or a controlled work request.

Pull reduces overproduction and excessive work-in-progress, but it does not eliminate the need for forecasting, capacity planning or safety stock. Pull is constrained by demand variability, replenishment time, resource availability and risk. A poorly designed “pull” system can simply shift queues or create shortages.

2.5 Pursue perfection

Perfection means continuous improvement toward the complete elimination of waste and the consistent fulfilment of customer requirements. It is a direction, not a claim that a process can become literally flawless. Improvement depends on repeated cycles of observation, problem definition, root-cause analysis, experimentation and learning.

Perfection includes both incremental kaizen and larger redesign. It also includes sustaining gains. An improvement that disappears after two weeks because standards, training or ownership were not established is not a successful Lean result.

Figure: The five Lean principles form a continuous cycle rather than a one-time project.

3. Three categories of process activity

A practical classification distinguishes three categories.

Value-added work

Value-added work directly creates the product or service characteristic required by the customer and is performed correctly. Examples include assembling a required feature, executing an accurate payment, or delivering an appropriate clinical intervention.

Necessary non-value-added work

Necessary non-value-added (NNVA) work does not create customer value directly but may currently be required for legal, regulatory, safety, financial-control or technical reasons. Examples include statutory reporting, identity verification, required calibration and some inspections. NNVA work should not be labelled “waste” in a way that encourages unsafe elimination. The correct questions are whether it is genuinely necessary, whether it can be simplified, automated, integrated or performed closer to the point of need, and whether the underlying requirement can be redesigned.

Pure waste

Pure waste consumes resources without creating value and without being required by an external necessity. Examples include avoidable searching, duplicate data entry, unnecessary movement, rework caused by an error and waiting created by poor scheduling. Pure waste should be removed or prevented at its root.

The classification depends on the customer requirement and process design. A final inspection may be necessary under a current regulatory regime, but repeated inspection caused by an unstable process can signal a deeper quality problem. A hand-off may be necessary for specialist expertise, but unnecessary hand-offs create delay and communication risk.

4. Muda, Mura and Muri

Lean uses three related Japanese terms to describe harmful conditions.

Muda: waste

Muda is the consumption of resources without creating customer value. The eight wastes provide a practical diagnostic taxonomy. Muda is often the visible symptom of deeper causes such as unstable demand, poor standards, inadequate capability or flawed management decisions.

Mura: unevenness

Mura is variation, imbalance or irregularity in workload, demand, production or process performance. Examples include month-end surges, irregular batch release, changing priorities and uneven staffing. Mura generates queues during peaks and idle capacity during troughs. It also makes performance data difficult to interpret.

Muri: overburden

Muri is excessive physical, cognitive or organisational strain placed on people, equipment or systems. Examples include lifting beyond safe limits, unrealistic workload, excessive overtime, poorly designed interfaces and operating machinery beyond its capability. Muri increases errors, injuries, breakdowns and turnover.

These conditions reinforce one another. Uneven demand can create overburden, and overburden can produce defects and downtime, which then create more waste. Conversely, wasteful rework and queues can make workloads uneven and push staff into emergency effort. Sustainable Lean improvement therefore addresses the system rather than blaming individuals.

5. The eight wastes

A widely used mnemonic is TIMWOODS. Different organisations use slightly different labels, and some include underused human capability as a separate waste. The following eight categories are a practical framework.

The categories can overlap. A defective item may be transported repeatedly, wait for a decision and require rework. Classification is useful only if it leads to understanding and action; counting waste categories without addressing causes creates little improvement.

A caution about “skills underutilisation”

The original operational list commonly refers to seven wastes, while many contemporary Lean programmes add the eighth waste of non-utilised talent. This addition is especially important in knowledge work. Employees possess process knowledge that may not be visible in formal data. Excluding them from improvement can produce technically elegant but impractical solutions. Involving people must be genuine: collecting suggestions without feedback or authority can itself damage trust.

6. Finding waste in practice

Waste is best identified by going to the place where work occurs, often called gemba. The observer should follow a real customer request through the process and record facts without prematurely judging the worker. Useful observations include:

• elapsed time and actual processing time;
• queue size and location;
• number of hand-offs and approvals;
• defects, rework and repeat contacts;
• distance travelled and searches made;
• information unavailable at the point of decision;
• interruptions, breakdowns and workload peaks;
• safety, privacy and ergonomic risks.

A process should be observed across different times because a single snapshot may hide Mura. Staff should be asked what makes the job difficult and what failures recur. Evidence may be quantitative or qualitative, but claims should be traceable to observations, records or customer data.

Lead time and processing time

Lead time is the elapsed time from the customer request to fulfilment. Processing time is the time during which work is actively performed. A simple process-flow-efficiency indicator is:

The numerator is the time spent performing activities classified as value-adding; the denominator is total elapsed lead time for the same unit or case. Both times must use the same units and boundaries. The measure is diagnostic, not a complete measure of performance: a high percentage does not prove that the output meets CTQs, and a low percentage may reflect necessary regulatory controls.

Worked example. A customer order takes 10 working days from receipt to delivery. The activities that transform the order and product total 2 hours. Assuming an eight-hour working day, total lead time is 80 hours. Therefore:

Process Flow Efficiency = (2 ÷ 80) × 100% = 2.5%

The result does not mean that 97.5% of employee time is personally unproductive. It indicates that the order spends most of its elapsed time waiting, being transferred, queued or otherwise outside active transformation. Investigation is needed before deciding which time can safely be removed.

Root causes rather than symptoms

A queue may be caused by insufficient capacity, but it may also result from batching, prioritisation rules, unreliable equipment, poor information quality or unnecessary approvals. Tools such as the five whys, cause-and-effect diagrams, Pareto analysis and failure-mode analysis help structure investigation. These tools should be used with evidence; repeatedly asking “why” without verification can generate speculation.

7. Pull, flow and basic operational measures

Lean decisions benefit from a small set of carefully defined measures. Possible measures include lead time, first-pass yield, on-time delivery, work-in-progress, queue time, defect rate, complaint rate, safety incidents and employee suggestions implemented. Each measure needs a clear operational definition, data source, frequency and owner.

For a stable process, Little’s Law provides a useful relationship:

Here, WIP is the average work-in-progress, throughput is the average completion rate per unit of time, and lead time is the average time a unit spends in the system. The units must be consistent—for example, cases, cases per day and days. The relationship assumes a sufficiently stable system over the period considered, with average inflow approximately equal to average outflow. It is not a promise that reducing WIP alone will automatically reduce lead time; bottlenecks and variability must also be addressed.

Worked example. If an office completes 120 applications per week and average lead time is 2 weeks, average WIP is:

WIP = 120 applications/week × 2 weeks = 240 applications

If the office reduces WIP by restricting new work without improving throughput or demand management, it may merely create an external backlog. Measures must therefore be interpreted as a system.

8. Applied case: reducing delay in a university admissions process

This is an illustrative case. It is designed to demonstrate Lean analysis and does not describe a particular institution.

Background

A university admissions office receives applications through an online portal. Applicants complain that decisions are slow and that they are repeatedly asked to submit documents already provided. Staff report heavy workload near programme deadlines.

Problem

A sample of 100 complete applications shows an average elapsed lead time of 15 working days. Processing activities total approximately 5 hours per application, while the remainder is waiting, transfer, clarification or rework. The CTQs are: a decision within 10 working days for complete applications, accurate document status, protection of personal data, and clear communication.

Analysis

A cross-functional team maps the process from submission to decision. It finds:

1. Applications are downloaded in large batches twice a week, creating waiting.
2. Two departments independently enter the same applicant data.
3. Missing-document queries are sent by email, and responses are difficult to track.
4. Reviewers receive uneven workloads because programmes release applications in batches.
5. A final manual check detects errors that could have been prevented at entry.
6. Staff frequently search shared folders for supporting documents.

The wastes include waiting, overprocessing, defects, motion, inventory in the form of pending applications, overproduction of duplicate records and underused staff knowledge. Mura appears in programme-based batches, while Muri appears during deadline peaks.

Approach and solution

The team first confirms the CTQs with applicants, admissions staff, academic reviewers and data-protection officers. It then introduces a controlled daily pull of complete applications, a single source of application data, a standard electronic checklist, and a visible queue showing status and age. A rules-based validation prevents submission when mandatory fields are incomplete, while exceptions remain available for legitimate special cases. Work is levelled across trained reviewers rather than assigned only by programme.

The changes do not remove legally required identity and eligibility checks. Instead, they integrate those checks earlier and record evidence once. Privacy permissions, access control and retention rules are reviewed before automation is introduced. Staff test the revised process through a pilot and use daily problem-solving meetings to identify abnormal cases.

Outcome

In the pilot, average lead time falls from 15 to 8 working days, repeated document requests decline substantially, and the proportion of complete applications decided within 10 days increases. Staff report fewer searches and less deadline overtime. The result is not attributed merely to faster individual work; it follows from reducing queues, duplication, variation and error opportunities.

Learning points

• VOC must be translated into CTQs before process changes are selected.
• A departmental improvement would have missed the batch-release problem.
• Automation is useful only when the underlying process and rules are understood.
• A faster process is not Lean if it weakens privacy, fairness, accessibility or decision quality.
• Standard work and visual status controls are needed to sustain the improvement.

9. Implementation principles and professional responsibilities

Lean implementation should begin with a clear problem and customer requirement, not with a fashionable tool. Senior leaders provide direction and resources, but the people doing the work must participate in diagnosis and design. A typical improvement cycle is:

1. Define the customer, CTQs, scope and problem.
2. Observe the current process and collect baseline evidence.
3. Classify activities and identify Muda, Mura and Muri.
4. Analyse causes and assess risks.
5. Design and test a future process with those who perform it.
6. Pilot changes, measure CTQs and unintended effects.
7. Standardise the improved method and train relevant staff.
8. Review performance and continue learning.

Ethical and governance considerations

Lean must never be used as a justification for unsafe work, unreasonable workload, concealment of defects or indiscriminate job cuts. Removing “idle time” without understanding recovery, training, safeguarding or cognitive limits can create Muri. Measures can also produce dysfunctional behaviour: a call centre judged only on call duration may end calls quickly while increasing repeat contacts.

Data-driven Lean requires responsible data governance. Personal information should be collected only for legitimate purposes, protected against unauthorised access, retained appropriately and interpreted fairly. AI or automation may help classify requests, detect anomalies or predict demand, but it can reproduce bias, make opaque decisions or create new errors. Human oversight, validation, audit trails, accessibility and an appeal route are necessary where automated decisions affect people.

Environmental sustainability is also relevant. Reducing defects, excess transport, energy use and inventory can reduce environmental impact, but Lean changes should be evaluated across the life cycle. A smaller local inventory that causes frequent emergency deliveries may increase emissions. Optimisation of one department must not externalise waste to suppliers, communities or future users.

10. Challenges, limitations and contemporary developments

Lean is sometimes criticised when organisations implement isolated tools—such as visual boards or workplace organisation—without changing leadership behaviour, demand management or process architecture. Another limitation is the assumption that all variation is bad. Some variation reflects legitimate customer choice, clinical complexity or necessary experimentation. The objective is not to eliminate meaningful variety but to distinguish it from harmful instability.

Lean also faces tension with highly customised, uncertain or innovative work. Standard work remains useful, but it should define the current best-known method while allowing controlled learning and escalation. In knowledge work, outputs may be difficult to observe and quality may emerge over time. Measures therefore need to include outcome quality, user experience and professional judgement, not only speed.

Contemporary Lean practice increasingly combines process mining, digital workflow data, remote collaboration tools, real-time visualisation and predictive maintenance. These technologies can reveal queues and variation at scale. However, digital visibility is not the same as process understanding. Data can be incomplete, definitions can be inconsistent and algorithms can amplify an inappropriate target. The Lean principle remains valid: understand customer value and the whole system before optimising a local metric.

Best-practice checklist

Before launching a Lean improvement, ask:

• Who is the customer, and what evidence defines value?
• Which CTQs are measurable, important and protected?
• Have we mapped the entire value stream, including suppliers and customers?
• Which activities are value-added, NNVA or pure waste?
• Where are Muda, Mura and Muri interacting?
• Have the people who perform the process helped design the solution?
• What risks could the change create for safety, privacy, fairness or quality?
• How will the pilot and sustained performance be measured?
• What standard work, training and governance will prevent regression?

Chapter Summary

Lean thinking begins with customer value, not internal activity. VOC provides evidence about what customers need, while CTQs translate that need into measurable requirements. The five principles—specify value, identify the value stream, make value flow, establish pull and pursue perfection—provide a coherent route from customer expectation to continuous improvement.

Process activities should be distinguished as value-adding, necessary non-value-adding or pure waste. The eight wastes are transportation, inventory, motion, waiting, overproduction, overprocessing, defects and underused human capability. Muda describes waste, Mura describes unevenness and Muri describes overburden; each can reinforce the others. Effective Lean work observes the process at the gemba, uses evidence, investigates root causes and protects safety, quality, privacy, fairness and human dignity. Pull systems, flow, standard work, employee involvement and appropriate digital tools can improve performance, but no tool substitutes for understanding the whole value stream.

Key Terms

Customer value: The product, service characteristic or outcome that satisfies a genuine customer need.

Voice of the customer (VOC): Collected information about customer needs, expectations, experiences and problems.

Critical-to-quality (CTQ): A measurable requirement that is essential to customer satisfaction or compliance.

Value stream: All actions required to deliver a product, service or information outcome, including value-adding and non-value-adding actions.

Lean thinking: A management philosophy focused on customer value, flow, pull, waste reduction and continuous improvement.

Value-added activity: Work that transforms the output in a way the customer requires and that is done correctly.

Necessary non-value-added activity: Work that does not directly create customer value but is currently required by law, safety, control or technical conditions.

Pure waste: Resource use that creates neither customer value nor necessary compliance or protection.

Muda: Waste or activity that consumes resources without creating value.

Mura: Unevenness or irregularity in demand, workload or process performance.

Muri: Overburden imposed on people, equipment or systems.

Flow: Continuous movement of work through a process with minimal avoidable interruption.

Pull: Authorisation to produce or perform work in response to actual downstream demand.

Kaizen: Continuous, usually incremental, improvement involving systematic learning.

Gemba: The actual place where work and value creation occur.

Standard work: The current best-known, documented method for performing a process safely and consistently.

Work-in-progress (WIP): Items, cases or information currently within a process but not yet complete.

Process Flow Efficiency: Value-added processing time divided by total lead time, expressed as a percentage.

TIMWOODS: A mnemonic for the eight wastes: transportation, inventory, motion, waiting, overproduction, overprocessing, defects and skills underutilisation.

Review Questions

Short Answer Questions

1. What distinguishes a CTQ from a general VOC statement?
2. State the five principles of Lean thinking.
3. Define necessary non-value-added work and give one example.
4. What is the difference between Mura and Muri?
5. List the eight wastes represented by TIMWOODS.

Long Answer Questions

1. Explain how an organisation can translate VOC into CTQs and then into process requirements. Use an example.
2. Discuss the five Lean principles as a connected system rather than as independent tools.
3. Compare value-added, necessary non-value-added and pure waste, including the risks of incorrectly classifying regulatory or safety work.
4. Explain how Muda, Mura and Muri interact and describe management actions that can address all three.
5. Evaluate the benefits and limitations of using digital systems or AI in Lean improvement.

Analytical / Application Questions

1. A service process has a lead time of 12 working days, with 3 hours of value-added processing. Assuming an eight-hour working day, calculate Process Flow Efficiency and explain what the result does and does not prove.
2. A warehouse experiences large monthly order peaks, staff overtime, long picking routes and frequent urgent replenishment. Diagnose the likely Muda, Mura and Muri, and propose a sequence of investigations and countermeasures.
3. Select a familiar process in a university, workplace or community service. Identify three CTQs, classify at least six activities as value-added, NNVA or pure waste, and recommend one improvement while considering safety, privacy and fairness.

Multiple Choice Questions with Answers

Question 1

Which statement best defines a critical-to-quality requirement?

A. An internal preference of a department

B. A measurable characteristic essential to customer satisfaction or compliance

C. Any activity that uses employee time

D. A forecast of future production volume

Correct Answer: B. A measurable characteristic essential to customer satisfaction or compliance

Question 2

Which Lean principle follows the identification of the value stream?

A. Make value flow

B. Specify value

C. Pursue perfection

D. Establish pull

Correct Answer: A. Make value flow

Question 3

Which activity is most clearly value-adding?

A. Searching for a missing file

B. Waiting for an approval

C. Transforming a product to a customer-required specification correctly

D. Duplicating information in a second system

Correct Answer: C. Transforming a product to a customer-required specification correctly

Question 4

What does Mura describe?

A. Customer value

B. Unevenness or irregularity in workload or demand

C. A final inspection

D. A required safety control

Correct Answer: B. Unevenness or irregularity in workload or demand

Question 5

Which example represents overproduction?

A. Producing reports before anyone needs them

B. Walking to a point-of-use tool

C. Correcting a wrong invoice

D. Waiting for equipment repair

Correct Answer: A. Producing reports before anyone needs them

Question 6

Which waste concerns unnecessary movement by people?

A. Transportation

B. Motion

C. Inventory

D. Defects

Correct Answer: B. Motion

Question 7

A process has 80 hours of total lead time and 4 hours of value-added processing. What is its Process Flow Efficiency?

A. 2%

B. 5%

C. 20%

D. 84%

Correct Answer: B. 5%

Question 8

Under the stated stable-system assumptions, an operation completes 50 cases per day and has an average lead time of 3 days. What is its average WIP according to Little’s Law?

A. 16.7 cases

B. 47 cases

C. 150 cases

D. 500 cases

Correct Answer: C. 150 cases

Question 9

Which action best illustrates a pull system?

A. Producing the maximum possible quantity each morning

B. Releasing work in response to a verified downstream requirement

C. Increasing batch size to hide process variation

D. Adding an approval to every transaction

Correct Answer: B. Releasing work in response to a verified downstream requirement

Question 10

Why should Lean improvement involve the people who perform the process?

A. They can replace all customer research

B. They possess practical process knowledge and are affected by the change

C. They eliminate the need for measurement

D. They guarantee that every proposal will succeed

Correct Answer: B. They possess practical process knowledge and are affected by the change