Customer Value, Waste and Lean Assessment

Introduction

Lean manufacturing and service operations begin with a deceptively difficult question: what does the customer value? The answer is not simply “low cost” or “high quality.” Value is determined by the benefits a stakeholder receives relative to the sacrifices made to obtain them. In manufacturing, value may involve function, reliability, delivery speed, conformance, safety and price. In services, it may also include accessibility, empathy, confidence, privacy, convenience and the quality of the experience.

Lean management is therefore not merely a collection of tools for reducing inventory or increasing labour productivity. It is a management philosophy for designing and improving end-to-end value streams. Its central discipline is to distinguish activities that create value from activities that consume resources without creating value, while preserving the capabilities needed for safety, compliance, reliability and customer trust.

This chapter develops four connected capabilities. First, it explains value from the perspectives of customers and other stakeholders. Second, it examines unevenness, overburden and the eight commonly recognized wastes. Third, it classifies work as value-adding, necessary non-value-adding or pure waste. Finally, it presents practical methods for gemba observation and organizational Lean maturity assessment.

Learning Objectives

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

1. Define customer value and distinguish customer, business, employee, regulatory and societal perspectives.
2. Explain mura, muri and muda and their relationship within a Lean system.
3. Identify the eight wastes in manufacturing and service processes.
4. Classify activities as value-added, necessary non-value-added or wasteful.
5. Conduct a structured gemba observation using facts rather than assumptions.
6. Assess Lean maturity and identify appropriate improvement priorities.
7. Evaluate the limitations and governance risks of Lean assessment.

1. Value as a Stakeholder Construct

1.1 What is value?

A useful operational definition is:

Value is the combination of product or service attributes that satisfy a legitimate stakeholder need, delivered at an acceptable total cost, risk and time.

The word “legitimate” matters. A customer may request an unsafe shortcut, but safety remains a non-negotiable requirement. Similarly, an activity may not be visible to the customer yet may be essential for legal compliance, cybersecurity, clinical safety or product reliability.

In Lean thinking, an activity is conventionally described as value-adding when it transforms the product or service in a way the customer is willing to pay for, the work is done right the first time, and the transformation is necessary for the requested output. This definition is useful but not universal. Service customers may value reassurance, accurate information or respectful treatment even when no physical transformation occurs.

Value can be represented conceptually as:

Here, V is perceived value; B is the bundle of benefits; P is monetary price; T is time and effort spent by the customer; R is perceived risk; and E is emotional or cognitive effort. The expression is a conceptual model, not a universal accounting equation. The components may be measured differently across customers and contexts, and perceived value is not necessarily additive.

A Lean improvement that reduces internal cost but increases customer effort or risk may destroy value. For example, moving a call centre to an inexpensive digital channel may reduce operating cost but lower value for customers who require accessible human assistance.

1.2 Multiple stakeholder perspectives

Customer value is central, but an organization operates within a wider stakeholder system.

Stakeholder perspectives can conflict. A faster process may increase employee strain; a lower inventory policy may increase supplier instability; a cheaper service may reduce inclusion. Lean assessment must therefore ask not only, “Did the process become faster?” but also, “For whom, at what cost, and with what consequences?”

1.3 Quality, delivery, cost and experience

Customers usually experience value through several dimensions:

• Quality: conformance, performance, reliability and fitness for use.
• Delivery: availability, lead time, punctuality and dependability.
• Cost: price and the broader cost of ownership or use.
• Flexibility: ability to respond to changing volume or requirements.
• Experience: ease, dignity, communication, confidence and emotional comfort.
• Safety and sustainability: absence of unacceptable harm and responsible resource use.

These dimensions interact. A hospital appointment delivered quickly but with incorrect patient identification is not high-value service. A manufactured component with excellent conformance but unreliable delivery may still fail the customer’s need. Managers should therefore avoid optimizing a single measure in isolation.

2. Lean’s Three Conditions: Mura, Muri and Muda

Lean analysis traditionally uses three Japanese terms:

• Mura: unevenness, variation or irregularity in workload and flow.
• Muri: overburden, meaning excessive demand placed on people, equipment or systems.
• Muda: waste, meaning resource consumption without corresponding value creation.

These conditions reinforce one another. Uneven demand may create overburden during peaks, which produces errors, breakdowns and rework. The resulting instability creates queues, excess inventory, overtime and other forms of waste. Waste then hides the underlying variation and makes the system appear to require still more capacity.

2.1 Mura: unevenness

Mura can arise from seasonal demand, batch scheduling, uneven staffing, product mix changes, unreliable suppliers, variable cycle times or management practices that release work in large waves. In services, appointment bunching and end-of-month administrative surges are common examples.

Mura is not the same as all variation. Some variation is inevitable and may be legitimate. The Lean concern is variation that disrupts flow, creates avoidable waiting or causes the organization to alternate between idle capacity and crisis response.

Responses include demand smoothing, level scheduling, smaller batches, flexible staffing, standard work, better information and closer coordination with suppliers. Smoothing demand must not become a way of denying urgent or vulnerable customers access to service.

2.2 Muri: overburden

Muri occurs when a person, machine or process is required to perform beyond safe or reasonable capability. Indicators include excessive overtime, awkward work, repeated interruptions, unstable priorities, equipment operated outside its design conditions, and chronic dependence on heroic effort.

Overburden is a system condition, not evidence of individual weakness. A manager who responds to recurring overload by demanding greater effort may temporarily increase output but will often increase defects, absenteeism, injuries and turnover.

Countermeasures include ergonomic redesign, workload balancing, preventive maintenance, realistic staffing, training, escalation mechanisms and removal of conflicting priorities.

2.3 Muda: waste

Waste is not limited to visible scrap. It includes time, motion, information, energy, capacity and attention consumed without improving the output or protecting a legitimate requirement. Waste is best understood in relation to the value stream and customer need.

3. The Eight Wastes

The traditional seven wastes are often expanded to eight by adding unused human potential. A common mnemonic is TIMWOODS: Transportation, Inventory, Motion, Waiting, Overproduction, Overprocessing, Defects and Skills or unused talent.

3.1 Transportation

Transportation is unnecessary movement of materials, products, documents or information between locations. Examples include repeated movement between departments, shipping items to an intermediate warehouse and returning them, or routing a digital case through unnecessary approval queues.

Transportation may not always be avoidable. The assessment question is whether the movement is necessary to deliver the required output and whether the layout or information architecture creates avoidable movement.

3.2 Inventory

Inventory includes raw materials, work-in-process, finished goods, documents, unresolved cases and digital work queues. Inventory can protect against uncertainty, but excessive inventory hides defects, consumes space and cash, increases obsolescence and delays problem detection.

In services, a queue of unprocessed claims or laboratory samples is inventory. Reducing it responsibly requires addressing arrival patterns, capacity, process variation and prioritization—not merely pressuring employees to work faster.

3.3 Motion

Motion is unnecessary movement by people. Searching for tools, walking to shared equipment, repeated screen navigation, awkward reaching and searching for information are typical examples. Motion differs from transportation because transportation concerns the movement of items or information, whereas motion concerns the movement of people.

Ergonomic consequences make motion a safety issue as well as an efficiency issue.

3.4 Waiting

Waiting occurs when people, materials, information or equipment are idle while value could otherwise be created. Causes include approvals, machine downtime, missing information, queues, batch release, unavailable staff and rework.

Waiting time is often the largest component of total lead time. Managers should identify what is waiting, why it is waiting, who controls the release and whether the waiting is visible in performance data.

3.5 Overproduction

Overproduction means producing earlier, faster or in greater quantity than the next customer requires. It is frequently regarded as a particularly serious waste because it generates other wastes: inventory, handling, storage, defects and obsolescence.

Examples include manufacturing to a forecast without a demand signal, preparing reports no one uses, or opening more service cases than the downstream team can process. Forecasting is necessary in many environments, but forecast-driven output should be controlled by risk, capacity and actual demand signals.

3.6 Overprocessing

Overprocessing is doing more work than required or using a more complex method than necessary. Examples include duplicate data entry, excessive inspection, unnecessary formatting, repeated approvals, producing specifications beyond customer need and requiring signatures that do not influence a decision.

A control is not waste merely because it is inconvenient. If it prevents serious harm or meets a legal requirement, it may be necessary non-value-adding work. The question is whether the control is effective, proportionate and designed efficiently.

3.7 Defects

Defects are errors, omissions, failures or outputs that do not meet requirements. In services, defects include incorrect invoices, inaccurate records, wrong advice, missed appointments and incomplete applications. Defects create rework, complaints, compensation, delays and reputational damage.

Lean emphasizes prevention at the source, clear standards, mistake-proofing, capable processes and rapid feedback. Inspection alone detects problems after resources have been consumed; it does not necessarily prevent recurrence.

3.8 Unused skills and human potential

The eighth waste is failure to use people’s knowledge, creativity, judgement and improvement capability. It appears when employees are excluded from problem solving, trained inadequately, assigned below capability, denied autonomy or required to follow flawed procedures without a voice.

This waste is especially important in services, where much of the process is knowledge-intensive and customer-facing. Employee participation is not merely motivational; it is a source of process knowledge and risk detection.

4. Classifying Activities Correctly

A process should not be labelled wasteful simply because the customer does not see it. A practical three-part classification is useful.

4.1 Value-added activity

An activity is value-added when it transforms the output in accordance with customer requirements, is performed correctly, and would reasonably be recognized as contributing to the desired result. In manufacturing, machining a component to the required specification may be value-added. In a service, accurately diagnosing a patient, resolving a customer issue or providing a required advisory interaction may be value-added.

4.2 Necessary non-value-added activity

Necessary non-value-added work does not directly transform the product or service from the customer’s perspective but is currently required for safety, law, risk management, coordination or the limitations of the existing system. Examples include regulatory reporting, identity verification, essential inspection, security checks and certain setup activities.

The label “necessary” should be tested rather than accepted permanently. Managers should ask whether the requirement is genuinely external, whether the method is efficient, whether technology can reduce effort and whether the control can be redesigned without increasing risk.

4.3 Pure waste

Pure waste consumes resources without creating customer value or protecting a legitimate requirement. Examples include avoidable searching, duplicate entry, preventable rework, unnecessary movement, redundant meetings and producing output that is not used.

The classification is contextual. A final inspection may be necessary in a regulated process, while the same inspection may be pure waste if a stable, capable process and appropriate controls make it redundant. Lean assessment should record the reason for the classification and the evidence supporting it.

4.4 Process-time analysis

A simple process-time study separates total lead time into processing time and non-processing time:

Where each term is measured in the same time unit. This identity is a classification framework, not a law of nature. A single activity may contain mixed elements and should be decomposed when practical.

A commonly used indicator is process cycle efficiency:

For example, suppose a service request spends 18 minutes in direct resolution, 12 minutes in required identity and compliance checks, and 90 minutes waiting or being reworked. Then total lead time is 120 minutes and:

The result does not mean that 85% of the process can automatically be removed. Some of that time may be necessary, and reducing it may require investment, policy change or risk analysis. PCE is useful for locating improvement opportunity, not for judging employees.

5. Gemba Observation

5.1 Meaning and purpose

Gemba means the actual place where work and value creation occur. A gemba observation is a structured visit to see the process, speak with the people doing the work and compare actual conditions with standards and customer requirements. It is not a management inspection designed to catch individuals making mistakes.

The principle “go and see” counters decisions based only on reports, dashboards or assumptions. Data remains essential, but direct observation reveals interruptions, workarounds, hidden queues, awkward movements, undocumented decisions and social conditions that are often absent from formal records.

5.2 Preparing for a gemba walk

A disciplined observation begins with a clear purpose. The observer should:

1. Define the process boundary, customer and output.
2. Identify the question to investigate, such as delayed delivery, recurring defects or excessive handoffs.
3. Review available performance data without treating it as complete truth.
4. Obtain appropriate permission, especially in clinical, confidential or hazardous environments.
5. Prepare a simple observation sheet based on facts, timestamps and locations.
6. Include process experts and, where possible, employee representatives.

The observer should not arrive with a predetermined solution. A good opening question is, “Please show me how the work is done from request to completion.”

5.3 What to observe

At the gemba, examine:

• customer demand and its pattern;
• the physical or digital flow of work;
• queues, batches and handoffs;
• standard work and actual work;
• information quality and availability;
• equipment condition and interruptions;
• defects, rework and escalation;
• ergonomic, safety and psychological conditions;
• decision rights and approval delays;
• evidence of learning and problem solving.

Use neutral questions: “What happens next?” “How do you know this is correct?” “What makes this difficult?” “How often does this occur?” “What happens when the standard cannot be followed?” Avoid asking questions that imply blame.

5.4 Observation record

A useful record includes time, location, observed fact, immediate consequence, likely waste category, stakeholder affected and evidence required for confirmation.

The phrase “preliminary category” is important. One observation may have multiple causes. A queue may reflect poor scheduling, inadequate capacity, unstable demand or a deliberate safety priority.

5.5 From observation to countermeasure

Observation should lead to a problem statement, not an immediate solution. A strong problem statement specifies the process, condition, gap, frequency and consequence. For example: “During weekday mornings, 35–45% of service requests wait more than 20 minutes for an approval that does not alter the decision in routine cases.”

The team can then investigate causes using process mapping, five-whys analysis, cause-and-effect diagrams, data stratification and direct consultation with process users. Countermeasures should be tested on a controlled basis and evaluated against quality, safety, service, employee and cost outcomes.

6. Assessing Organizational Lean Maturity

Lean maturity concerns how consistently an organization creates value, manages flow, solves problems and develops people. It is not the number of tools displayed or the number of workshops completed. A mature organization can sustain improvement under changing conditions and can explain why a practice exists.

6.1 Dimensions of maturity

A practical assessment can examine the following dimensions:

1. Customer and value orientation: Requirements are explicit, segmented and translated into operational standards.
2. Process visibility: End-to-end flows, queues, constraints and defects are visible.
3. Standard work: Critical work has clear, current and usable standards developed with employees.
4. Flow and pull: Work is released according to demand and capacity rather than habitually pushed in batches.
5. Quality at source: Problems are detected and contained close to where they occur.
6. Structured problem solving: Teams use evidence, root-cause analysis and verified countermeasures.
7. Leadership behaviour: Leaders go to the gemba, ask learning questions and remove systemic barriers.
8. People development: Employees receive training, psychological safety and opportunities to improve work.
9. Cross-functional alignment: Measures and decisions support the whole value stream.
10. Sustainability and governance: Improvements protect safety, fairness, compliance and environmental responsibility.

6.2 A maturity scale

The following five-level scale is illustrative rather than a universal standard.

A maturity score should be treated as a diagnostic conversation, not an employee ranking. If ten dimensions are scored from 1 to 5, an average can summarize the profile:

Here, s_i is the score for dimension i, and n is the number of dimensions. The arithmetic average assumes that dimensions are equally weighted. That assumption may be inappropriate where safety or regulatory capability is a threshold requirement. Therefore, the profile and evidence should accompany any overall score.

6.3 Evidence-based assessment

Evidence may include direct observation, employee interviews, standard-work audits, process data, customer feedback, incident records, improvement logs and leadership routines. Self-assessment alone is vulnerable to optimism bias; external assessment alone may miss local context. Triangulation is stronger.

Assessment questions should distinguish the existence of a tool from its effectiveness. For example:

• Is there a visual board, and does it support timely decisions?
• Is standard work documented, and can employees use it under normal conditions?
• Are improvement actions completed, and are gains sustained?
• Are problems escalated without fear?
• Do performance measures encourage the desired behaviour?

7. Applied Case: Reducing Delay in an Insurance Claims Service

Background

The following is an illustrative case. A regional insurer receives motor-claim notifications through telephone, web and partner garages. Customers complain that simple claims take too long to acknowledge. Management believes that staff productivity is low because the average acknowledgement lead time is 2.4 days.

Problem

A cross-functional team defines the customer requirement as: “For a complete, low-risk claim, provide an acknowledgement and next action within one business day.” The team maps the process from notification to acknowledgement and conducts gemba observations in the contact centre, claims office and digital workflow.

Analysis

The team finds that cases are frequently transferred between three queues. Customer information is entered once by the contact-centre agent and again by a claims processor. A supervisor approval is required for all cases, although routine low-risk cases rarely need judgement. Claims arrive in large batches from partner garages at the start of each day. Employees report that missing photographs and inconsistent descriptions create repeated customer contacts.

The observed wastes include:

• Waiting: cases wait for batch release and supervisor approval;
• Overprocessing: duplicate data entry and universal approval;
• Defects: incomplete information causes rework;
• Overproduction: some internal reports are prepared but not used;
• Mura: partner submissions are concentrated in a narrow time window;
• Muri: employees experience morning peaks and late-day overtime.

Suppose a sample of 40 cases shows the following average times per case: 22 minutes of direct assessment, 8 minutes of required verification, and 210 minutes of waiting or rework. Total lead time is 240 minutes. The process cycle efficiency is:

The low percentage does not prove that employees are inefficient. It indicates that most elapsed time occurs outside direct assessment and deserves investigation.

Approach and solution

The team pilots four countermeasures:

1. A standardized digital intake form with mandatory fields and examples.
2. A risk-based approval rule allowing trained staff to process low-risk cases without routine supervisor approval.
3. A smaller, more frequent release of partner submissions rather than one large batch.
4. A daily visual review of ageing cases, defects and customer callbacks.

The team also introduces a weekly employee problem-solving meeting. Compliance specialists review the revised approval rule, and an accessibility check ensures that customers unable to use the digital form retain a telephone option.

Outcome

After four weeks, the pilot shows fewer incomplete submissions, reduced duplicate entry and a substantial decline in approval waiting. Management evaluates acknowledgement time, first-time-right rate, customer complaints, employee overtime and compliance incidents together. The pilot is not declared successful merely because lead time falls; it must also preserve decision quality and fair customer access.

Learning points

The case demonstrates that a visible performance problem may be produced by system design rather than individual effort. It also illustrates the relationship among mura, muri and muda: batch arrivals create unevenness, unevenness creates overload, and overload produces waiting and defects. Finally, the case shows why Lean improvement must involve employees, customers, risk specialists and governance owners.

8. Challenges, Limitations and Ethical Considerations

Lean categories can oversimplify complex work. A conversation that appears to be “waiting” may provide reassurance and prevent a serious misunderstanding. A compliance step may seem non-value-adding but protect vulnerable people. A highly utilized resource may look efficient while creating long queues and fragile recovery capacity.

Common implementation failures include:

• treating Lean as headcount reduction;
• using maturity scores to punish departments;
• collecting observations without acting on employee concerns;
• optimizing a local process while worsening the end-to-end value stream;
• removing controls without risk assessment;
• using automation to accelerate a defective process;
• relying on averages that hide variation or inequity;
• ignoring emotional labour and psychological safety in services.

Ethically sound Lean practice requires informed participation, safe working conditions, non-discrimination, privacy protection and transparent use of performance data. Technology and AI can help identify queues, predict demand, transcribe observations or detect recurring defects. However, automated recommendations may reproduce historical bias, expose confidential information or encourage surveillance. Human review, data minimization, explainability and clear accountability are necessary, particularly in healthcare, finance, employment and public services.

9. Best-Practice Guidance

A robust Lean assessment follows these principles:

1. Start with a clearly defined customer and value requirement.
2. Study the entire value stream rather than isolated departments.
3. Go to the gemba and distinguish observed facts from interpretations.
4. Separate mura, muri and muda instead of treating every problem as generic waste.
5. Protect safety, legality, inclusion and dignity while seeking efficiency.
6. Involve employees as experts in the work.
7. Use data to reveal patterns, but investigate causes directly.
8. Prioritize systemic countermeasures over heroic effort.
9. Measure quality, delivery, cost, people and sustainability together.
10. Verify that improvements are sustained and produce the intended stakeholder value.

Chapter Summary

Lean begins with a disciplined definition of value from customer and stakeholder perspectives. Value includes benefits such as quality, reliability, speed, convenience, safety and trust, offset by price, effort, time and risk. The three conditions of mura, muri and muda describe unevenness, overburden and waste; they interact dynamically and should be addressed as system conditions.

The eight wastes are transportation, inventory, motion, waiting, overproduction, overprocessing, defects and unused human potential. Activities should be classified as value-added, necessary non-value-added or pure waste, with careful attention to safety, regulation and context. Gemba observation provides direct understanding of actual work and should use neutral questions, factual records and employee participation. Lean maturity is assessed through dimensions such as customer orientation, flow, standard work, quality at source, problem solving, leadership, people development, cross-functional alignment and governance. Maturity scores are useful only when supported by evidence and interpreted as learning tools rather than rankings. Effective Lean practice improves the whole system while protecting people, customers and society.

Key Terms

Value: The benefits delivered to a stakeholder relative to price, effort, time, risk and other sacrifices.

Stakeholder: A party affected by or able to affect an organization’s activities and outcomes.

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

Muri: Overburden placed on people, equipment or systems.

Muda: Resource consumption that does not create value or protect a legitimate requirement.

Transportation: Unnecessary movement of materials, products, documents or information.

Inventory: Accumulated materials, work, cases or information awaiting use or processing.

Motion: Unnecessary movement by people while performing work.

Waiting: Idle time caused by queues, approvals, missing inputs, downtime or other interruptions.

Overproduction: Producing earlier, faster or in greater quantity than required.

Overprocessing: Performing unnecessary or excessive work.

Defect: An output that fails to meet a specified or legitimate requirement.

Unused human potential: Failure to use employees’ knowledge, creativity, judgement or capability.

Value-added activity: Work that transforms an output in accordance with customer requirements and is done correctly.

Necessary non-value-added activity: Work that does not directly add customer value but is currently required for safety, law, risk or system limitations.

Pure waste: Resource consumption that creates neither customer value nor legitimate protection.

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

Standard work: The agreed, current method for performing a process safely and effectively.

Process cycle efficiency: The proportion of total lead time represented by value-added processing time.

Lean maturity: The organization’s capability to create value, manage flow, solve problems and sustain improvement.

Review Questions

Short Answer Questions

1. Define customer value and explain why it cannot be equated solely with low price.
2. Distinguish mura, muri and muda.
3. List the eight wastes commonly identified in Lean thinking.
4. What is the purpose of a gemba observation?
5. Why should a Lean maturity score be supported by evidence?

Long Answer Questions

1. Explain how customer, employee, regulatory and societal perspectives may conflict in Lean improvement.
2. Discuss the distinction between value-added, necessary non-value-added and pure waste, using examples from a service process.
3. Explain how mura can generate muri and muda in an operational system.
4. Describe a structured method for preparing, conducting and following up a gemba observation.
5. Evaluate the dimensions and limitations of a five-level Lean maturity assessment.

Analytical / Application Questions

1. A claims process contains 15 minutes of direct processing, 10 minutes of required verification and 95 minutes of waiting. Calculate total lead time and process cycle efficiency. Interpret the result cautiously.
2. Select a university registration process and identify at least one example of each of the eight wastes. Explain how you would validate each observation at the gemba.
3. An organization reports that its Lean programme reduced labour hours but increased customer complaints and employee overtime. Diagnose the likely management errors and propose a balanced assessment approach.

Multiple Choice Questions with Answers

Question 1

Which statement best defines value in Lean operations?

A. The amount of work performed by employees

B. The benefits delivered to a stakeholder relative to relevant sacrifices and risks

C. The total quantity produced during a shift

D. The percentage of equipment capacity used

Correct Answer: B. The benefits delivered to a stakeholder relative to relevant sacrifices and risks

Question 2

Which Lean term refers to unevenness in workload or process flow?

A. Muda

B. Muri

C. Mura

D. Gemba

Correct Answer: C. Mura

Question 3

A claims employee enters the same customer information into two systems because the systems are not integrated. Which waste is most directly present?

A. Overprocessing

B. Transportation

C. Overproduction

D. Inventory

Correct Answer: A. Overprocessing

Question 4

Which of the following is an example of necessary non-value-added work?

A. Searching for a misplaced document

B. Repeating a task because of an avoidable error

C. Completing a legally required identity verification

D. Preparing a report that nobody uses

Correct Answer: C. Completing a legally required identity verification

Question 5

What is the principal purpose of going to the gemba?

A. To inspect and rank individual employees

B. To observe actual work and understand conditions directly

C. To replace all process data with opinions

D. To authorize immediate cost reductions

Correct Answer: B. To observe actual work and understand conditions directly

Question 6

A process has 20 minutes of value-added time, 10 minutes of required verification and 70 minutes of waiting. What is its process cycle efficiency?

A. 10%

B. 20%

C. 25%

D. 80%

Correct Answer: B. 20%

Question 7

Which waste is most directly associated with producing items earlier or in greater quantity than the next customer requires?

A. Overproduction

B. Motion

C. Defects

D. Unused human potential

Correct Answer: A. Overproduction

Question 8

Why can overburden be considered a system condition rather than evidence of individual weakness?

A. Because overburden is always caused by customers

B. Because workload, equipment and process design can exceed safe capability

C. Because employees cannot influence any process

D. Because overburden has no relationship to quality

Correct Answer: B. Because workload, equipment and process design can exceed safe capability

Question 9

Which evidence would provide the strongest basis for a Lean maturity assessment?

A. A single manager’s opinion

B. The number of Lean posters displayed

C. Triangulation of observations, employee input and performance evidence

D. The age of the organization

Correct Answer: C. Triangulation of observations, employee input and performance evidence

Question 10

An organization removes a compliance check to reduce lead time without assessing risk. What is the principal Lean governance concern?

A. The process may become too visible

B. The organization may reduce legitimate protection while pursuing local efficiency

C. The organization may create too much employee participation

D. The organization may eliminate all forms of waste

Correct Answer: B. The organization may reduce legitimate protection while pursuing local efficiency