Lean Operations, Theory of Constraints and Operational Excellence

Introduction

Lean operations and the Theory of Constraints (TOC) are complementary approaches to improving the performance of operating systems. Lean focuses on creating customer value with fewer resources by removing waste, stabilizing processes, and developing the capability of employees. TOC focuses on the system constraint—the factor that most limits overall throughput—and directs improvement effort toward it. Operational excellence combines these ideas with disciplined management systems, reliable processes, strategic alignment, and continuous learning.

These approaches are particularly important in environments characterized by short product life cycles, demanding customers, supply uncertainty, labor shortages, regulatory requirements, and pressure to improve cost, quality, delivery, safety, and sustainability simultaneously. Lean is not simply a collection of tools such as 5S or Kanban. It is a management philosophy concerning how work is designed, how problems are exposed, how decisions are made, and how people learn. Similarly, TOC is not merely a scheduling technique; it is a logic for understanding system performance and prioritizing managerial attention.

A central principle is that local efficiency does not necessarily produce system effectiveness. A department that maximizes its utilization may create excess work-in-process, longer lead times, and poorer customer service. Operational excellence therefore requires managers to optimize the flow and outcomes of the whole value stream rather than isolated activities.

Learning Objectives

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

1. Explain the principles, terminology, and evolution of lean operations.
2. Identify and measure the principal forms of operational waste.
3. Apply takt time, pull systems, Kanban, 5S, SMED, standard work, mistake-proofing, and kaizen.
4. Explain the Theory of Constraints and apply its five focusing steps.
5. Distinguish local efficiency from end-to-end operational performance.
6. Integrate lean and TOC in manufacturing and service settings.
7. Evaluate implementation barriers, organizational change requirements, and ethical risks.
8. Design a practical operational-excellence implementation and performance-control system.

1. Foundations of Lean Operations

1.1 Value and value streams

In lean thinking, value is defined from the customer’s perspective. An activity creates value when it transforms the product or service in a way the customer requires, is done correctly the first time, and would reasonably be paid for by the customer. Activities that do not meet these conditions are either necessary non-value-adding activities—for example, legally required inspection—or pure waste.

A value stream includes all actions required to deliver a product or service, including information flows, material flows, approvals, waiting, transport, processing, and feedback. Value-stream analysis prevents managers from improving one operation while overlooking delays elsewhere. A process with highly productive machines can still have poor performance if orders wait for authorization, materials are unavailable, or rework consumes capacity.

1.2 The five lean principles

The traditional lean framework consists of five connected principles:

1. Specify value. Define the outcome, service attributes, reliability, timing, and price that matter to the customer.
2. Identify the value stream. Map every step and classify it as value-adding, necessary non-value-adding, or waste.
3. Create flow. Remove interruptions, batch delays, unnecessary movement, and unevenness so work progresses smoothly.
4. Establish pull. Authorize production or replenishment in response to actual downstream demand rather than speculative forecasts alone.
5. Pursue perfection. Treat improvement as continuous because customer expectations, technology, and process conditions change.

The principles are mutually reinforcing. Pull is difficult when processes are unstable; flow is difficult when quality problems are hidden; and continuous improvement is weak when standards are absent.

1.3 The three conditions: muda, mura, and muri

Lean analysis commonly distinguishes three related conditions:

• Muda: waste or activity that consumes resources without creating customer value.
• Mura: unevenness or irregularity in demand, work content, staffing, or material flow.
• Muri: overburden placed on people, equipment, or systems.

Reducing only muda may produce limited results if uneven demand continually creates overtime and idle time. Likewise, removing buffers without addressing equipment reliability may transfer overburden to employees. Effective lean design addresses all three conditions.

2. Waste, Flow, and Performance Measures

2.1 The eight wastes

The traditional seven wastes are often expanded to eight by explicitly recognizing unused human capability:

Waste should be identified empirically through observation, process data, customer feedback, and root-cause analysis. A visible queue is a symptom; its cause may be unreliable equipment, uneven arrivals, poor scheduling, or approval rules.

2.2 Flow, lead time, and work-in-process

A useful relationship for flow analysis is Little’s Law:

Here, L is the average number of units in the system, λ is the long-run average throughput rate, and W is the average time a unit spends in the system. Units must be consistent—for example, units, units per hour, and hours. The relationship applies to a stable system over a sufficiently long period, where average inflow and outflow are approximately equal. It is not a short-term promise that every individual unit will follow the average.

For example, if a claims process completes 40 claims per day and the average claim remains in the process for 3 days, average work-in-process is:

If management reduces work-in-process to 80 claims while throughput remains 40 claims per day, the implied average lead time becomes:

This illustrates why reducing queues can improve customer responsiveness, provided throughput and quality are not damaged.

2.3 Takt time and capacity

Takt time expresses the pace of production required to meet customer demand:

Available time excludes planned breaks, scheduled meetings, and other planned non-production periods. If a workday provides 420 available minutes and demand is 105 units, takt time is:

To meet demand under the stated assumptions, the effective cycle time of each required process should be no greater than 4 minutes per unit. Takt time is not the same as cycle time. Cycle time is the actual elapsed time between completed units at a process; takt time is the customer-required pace. Takt may change with demand, whereas a process cycle time may remain unchanged.

The theoretical minimum number of workstations for an assembly line is:

where t_i is the work content of task i and C is the permitted cycle time, often set at or below takt time. Because tasks cannot usually be divided perfectly and precedence constraints apply, the actual number of stations is normally greater than or equal to N_min. Line-balancing efficiency may be expressed as:

where N is the actual number of stations. This measure should not be treated as the sole objective: safety, ergonomic burden, flexibility, quality, and resilience also matter.

3. Core Lean Methods

3.1 Pull systems and Kanban

A pull system authorizes upstream activity only when a downstream customer or process has consumed material or capacity. Kanban is a signaling mechanism that can use cards, containers, electronic messages, or visual signals. A Kanban loop normally specifies the item, quantity, source, destination, replenishment rules, and escalation procedure for abnormalities.

A common sizing relationship for a number of Kanban containers is:

where n is the required number of containers, D is demand per time unit, L is replenishment lead time in the same time unit, S is the safety factor expressed as a decimal, and C is the quantity per container. The result is rounded up to a whole container because partial containers are not normally practical. This equation assumes relatively stable demand, known replenishment time, consistent container quantity, and a safety factor that adequately represents variability.

Suppose demand is 240 components per day, replenishment lead time is 0.5 day, the safety factor is 20%, and each container holds 30 components:

Therefore, at least 5 containers are required under these assumptions. The safety factor is not a substitute for solving chronic quality, downtime, or supplier problems. As reliability improves, the number of containers should be reviewed rather than left permanently inflated.

Kanban is most effective when item specifications are stable, processes are reasonably capable, replenishment is dependable, and demand is not excessively erratic. It may be supplemented by capacity reservations, finite scheduling, or strategic buffers where demand is highly volatile.

3.2 5S

5S creates a visual and disciplined workplace:

1. Sort: Remove unnecessary items.
2. Set in order: Locate and identify necessary items so they are easy to find and return.
3. Shine: Clean while inspecting for abnormal conditions.
4. Standardize: Establish visual and procedural norms.
5. Sustain: Audit, coach, and improve the system.

5S is not housekeeping for its own sake. It reduces search time, exposes leaks and defects, supports safe work, and makes abnormal conditions visible. A weak implementation treats 5S as a one-time cleanup. A strong implementation links standards to ownership, audit evidence, maintenance, and problem solving.

3.3 SMED and setup reduction

Single-Minute Exchange of Die (SMED) is a structured approach to reducing changeover time. Its logic is to:

• distinguish internal activities, possible only when equipment is stopped, from external activities, possible while it runs;
• convert internal activities to external activities where technically and safely possible;
• simplify, standardize, and parallelize remaining tasks;
• verify settings through visual controls, quick-release mechanisms, and first-piece confirmation.

SMED does not mean every changeover must literally take less than ten minutes. It means pursuing single-digit-minute performance where feasible while preserving safety and quality. Shorter changeovers enable smaller batches, which reduce inventory and improve responsiveness. However, managers must consider total economic and operational effects, including cleaning, validation, tooling life, setup scrap, and regulatory release requirements.

3.4 Standard work

Standard work documents the current best-known method for performing a task safely, consistently, and at the required pace. It usually includes:

• takt or cycle time;
• work sequence;
• standard in-process inventory;
• quality and safety checkpoints;
• known abnormal conditions and escalation rules.

Standard work is not intended to suppress professional judgment. It provides a baseline from which deviations can be detected and improvements tested. Without a standard, it is difficult to distinguish improvement from merely changing the process.

3.5 Mistake-proofing and quality at the source

Mistake-proofing, or poka-yoke, prevents an error, detects it immediately, or makes the error difficult to make. Examples include connectors that fit only one way, barcode validation, presence sensors, checklists for high-risk steps, and software rules that prevent incomplete submissions.

The hierarchy of controls matters. Preventing an error is generally stronger than relying on inspection after the error occurs. Yet automation can introduce new failure modes. A poka-yoke should therefore be validated, maintained, and periodically challenged to ensure it still detects the intended condition.

3.6 Kaizen and structured problem solving

Kaizen means continuous, incremental improvement involving the people who perform the work. Effective kaizen follows a disciplined cycle:

1. Define the problem in observable terms.
2. Establish a baseline using reliable data.
3. Observe the actual process.
4. Analyze causes rather than symptoms.
5. Test countermeasures on a small scale.
6. Check results against the baseline.
7. Standardize successful changes.
8. Continue monitoring and learning.

The Plan–Do–Check–Act cycle is useful, as are 5 Whys, cause-and-effect diagrams, process capability analysis, and error-frequency charts. “Five Whys” should not be used mechanically; complex failures may have multiple interacting causes and require systems analysis.

4. Theory of Constraints

4.1 Core logic

TOC begins with the proposition that every system has at least one constraint limiting its ability to achieve its goal. In a production system, the constraint may be a machine, skilled specialist, policy, market, supplier, or information bottleneck. Improving a non-constraint may create local gains but not increase total system throughput.

TOC commonly distinguishes three system measures:

• Throughput: the rate at which the system generates money through actual sales, not merely production.
• Inventory or investment: money tied up in things intended for sale, including materials and work-in-process.
• Operating expense: money spent to convert inventory into throughput.

The objective is generally to increase throughput while reducing inventory and operating expense, without damaging quality, safety, or long-term capability.

4.2 The five focusing steps

1. Identify the constraint. Use evidence such as persistent queues, missed shipments, workload exceeding capacity, or a policy that limits flow.
2. Exploit the constraint. Obtain more output from existing constraint capacity—for example, reduce downtime, ensure quality at the source, and reserve the constraint for valuable work.
3. Subordinate everything else. Align upstream release and downstream support with the constraint’s operating rhythm. Do not flood the constraint with excess work.
4. Elevate the constraint. Add capacity through overtime, cross-training, outsourcing, redesign, automation, or capital investment where justified.
5. Repeat. Once one constraint is broken, another becomes limiting. Avoid inertia and return to step one.

The associated Drum–Buffer–Rope system uses the constraint’s schedule as the drum, a protective time or material buffer before the constraint, and a controlled release mechanism or rope that prevents excessive work from entering the system.

4.3 A short numerical illustration

A process has three sequential resources with effective capacities of 50, 35, and 45 units per hour. Ignoring demand and other constraints, system capacity is the minimum capacity:

The second resource is the constraint. Improving the first resource from 50 to 60 units per hour does not increase system capacity. If the second resource is elevated to 48 units per hour, the third resource at 45 units per hour becomes the new constraint, and system capacity rises to 45 units per hour, assuming demand, quality, materials, and labor support the change.

This example is deliberately simplified. Real systems require consideration of setup losses, product mix, downtime, yield, blocking, starvation, and finite demand.

5. Integrating Lean and TOC

Lean and TOC can be integrated, but they emphasize different questions. Lean asks, “How can the value stream flow with less waste?” TOC asks, “What currently limits total system performance?” A lean initiative that reduces every buffer indiscriminately may expose the system to starvation and instability. A TOC initiative that protects a constraint with a large buffer may appear inconsistent with inventory reduction, but the buffer may be economically justified if it protects throughput.

A practical integration sequence is:

1. Define customer value, strategic objectives, and system boundaries.
2. Map the end-to-end value stream and quantify queues, lead time, quality, and capacity.
3. Identify the current constraint and distinguish it from ordinary inefficiencies.
4. Stabilize basic conditions through safety, quality, maintenance, standard work, and visual management.
5. Protect and improve the constraint while reducing waste that interferes with flow.
6. Use pull and Kanban where replenishment conditions are suitable.
7. Review performance at the system level and identify the next constraint.

The correct choice of metric depends on the improvement question. Takt time supports demand-paced design; cycle time supports process analysis; throughput supports system performance; first-pass yield supports quality; and lead time supports customer responsiveness. No single metric is sufficient.

6. Operational Excellence as a Management System

Operational excellence is broader than isolated process improvement. It requires alignment among strategy, process architecture, leadership behavior, workforce capability, technology, and governance. A mature operating system typically contains:

• a clearly defined customer and value proposition;
• stable and visible processes;
• daily performance management;
• problem-solving routines;
• standards that are actively maintained;
• escalation pathways for abnormal conditions;
• leadership presence at the place where work occurs;
• employee involvement and psychological safety;
• evidence-based capital and technology decisions.

A balanced performance architecture should include quality, delivery, cost, flexibility, safety, people, and sustainability. For example, reducing labor hours while increasing injuries is not operational excellence. Increasing output through excessive overtime may conceal a capacity or scheduling problem. Metrics should be reviewed for unintended consequences and gaming.

7. Implementation Barriers and Change Requirements

7.1 Common barriers

Implementation commonly fails for organizational rather than technical reasons. Barriers include:

• treating lean as a cost-cutting program;
• senior leaders delegating responsibility without changing their own behavior;
• inadequate process stability;
• conflicting departmental targets;
• fear that productivity improvement will eliminate jobs;
• insufficient time for training and experimentation;
• poor data quality;
• copying tools without understanding their operating conditions;
• ignoring suppliers, customers, or support functions;
• confusing visual activity with actual performance improvement.

7.2 Change leadership

Sustainable change requires a credible purpose, participation, capability development, reinforcement, and fair treatment. Employees need to understand how improvement affects customers, safety, workload, and employment. Leaders should distinguish accountability for standards from blame for systemic problems. A worker who reports an abnormality is contributing to control, not causing the problem.

Improvement teams should include people with process knowledge, technical expertise, customer understanding, and authority to test changes. Experiments should have explicit hypotheses, measures, time limits, and rollback criteria. Recognition systems should reward learning, reliable problem escalation, and team outcomes rather than only individual output.

7.3 Ethical and governance issues

Lean methods can be misused to intensify work, eliminate legitimate recovery time, or conceal workforce reductions. Ethical implementation requires compliance with labor, health and safety, data protection, accessibility, and sector-specific regulations. Monitoring technology and AI-based workflow systems raise additional concerns about surveillance, bias, explainability, data ownership, and due process.

Automation should not simply transfer error detection to workers or make jobs more precarious without consultation. Managers should assess ergonomic effects, algorithmic decision quality, cybersecurity, and the possibility that an automated control fails silently. In regulated settings, process changes may require validation, documentation, traceability, and formal approval.

8. Technology, Digital Lean, and AI

Digital tools can strengthen lean practices when they improve visibility and decision quality. Examples include real-time equipment monitoring, electronic Kanban, digital work instructions, process mining, predictive maintenance, simulation, and computer vision for quality inspection.

Technology should follow a clearly defined problem. Installing sensors before identifying the decision they will support can create data abundance without operational learning. AI may help detect patterns in downtime, forecast demand, classify defects, or recommend maintenance priorities. However, AI predictions are not automatically causal explanations. Models require representative data, monitoring for drift, human oversight, cybersecurity controls, and clear escalation when predictions conflict with safety or professional judgment.

Digitalization can also accelerate waste. Automatic scheduling may generate excessive changeovers, dashboards may encourage local optimization, and electronic workflows may reproduce unnecessary approvals. A useful test is whether the technology improves customer value, flow, quality, safety, learning, or constraint performance.

9. Illustrative Case: Improving Flow in a Medical-Device Assembly Operation

Background

The following is a fictional illustrative case. A medical-device assembly plant produces three related products for hospitals. Customer demand is stable overall but varies by product. The plant has experienced late deliveries, overtime, and rising work-in-process. Management initially proposes purchasing another assembly machine.

Problem

A value-stream review shows that final testing is completed by a specialized team. Upstream assembly averages 62 units per hour, final testing can process only 40 units per hour, and packaging can process 55 units per hour. Work accumulates before testing. Although the assembly department reports high utilization, customer lead time is increasing. First-pass yield at testing is 92%, so defective units also consume scarce testing capacity.

Analysis

The testing team is the current constraint. The plant’s immediate problem is not a shortage of assembly capacity. Further increasing assembly output would enlarge the queue. Observation identifies four hours of testing downtime per week caused by missing calibration materials, repeated paperwork, and changeover searches. Testing also performs avoidable rework because upstream assembly errors are detected late.

The team calculates a target based on available weekly demand and working time. It introduces standard work for test preparation, a small visual buffer before testing, and a Kanban signal for calibration materials. A mistake-proof connector check is added at assembly. The team also separates external preparation from internal changeover activities and prepares fixtures before the test station stops.

Approach and solution

The five focusing steps are applied:

1. Identify: final testing is the constraint.
2. Exploit: eliminate preparation delays, protect testing from defective inputs, and schedule the highest-value mix first.
3. Subordinate: cap assembly release using a controlled signal and prevent unnecessary upstream overproduction.
4. Elevate: cross-train a technician and add a second test fixture after verifying that lower-cost actions are insufficient.
5. Repeat: after testing capacity improves, packaging becomes the next constraint and receives a new improvement cycle.

5S is applied to test fixtures, standard work is posted at the station, and a daily management board tracks throughput, first-pass yield, downtime, and buffer status. Importantly, the plant does not use the board to rank individuals; it uses it to trigger team problem solving.

Outcome

After eight weeks, testing downtime falls, first-pass yield improves, and the queue before testing declines. The plant delays the purchase of an additional assembly machine. Customer lead time improves because release is governed by the constraint rather than by assembly utilization. The case does not imply that every problem can be solved without investment. Once lower-cost improvements are exhausted, capacity investment may be appropriate.

Learning points

The case demonstrates that:

• system capacity is governed by the constraint, not by the fastest department;
• quality at the source protects scarce capacity;
• pull controls can prevent overproduction;
• lean tools are most effective when connected to a system diagnosis;
• operational excellence requires both technical redesign and changed management behavior.

10. Best-Practice Implementation Roadmap

A graduate-level implementation plan should be sequenced rather than tool-driven:

Stage 1: Diagnose. Clarify customer requirements, define the value stream, establish a baseline, and identify risks and constraints.

Stage 2: Stabilize. Address safety, quality, equipment reliability, staffing, data definitions, and basic standard work.

Stage 3: Improve flow. Reduce major sources of waiting, movement, defects, and changeover loss. Introduce visual management and appropriate pull signals.

Stage 4: Manage the constraint. Apply the five focusing steps, protect constraint capacity, and align release to system requirements.

Stage 5: Develop capability. Train leaders and operators in observation, experimentation, root-cause analysis, and standardization.

Stage 6: Sustain and renew. Audit adherence, review outcomes, learn from deviations, and repeat the constraint-identification cycle.

The roadmap should include owners, resources, decision rights, baseline and target measures, review frequency, and criteria for stopping or redesigning an intervention. Improvements must be embedded in budgeting, performance appraisal, maintenance, procurement, product design, and leadership routines.

Chapter Summary

Lean operations seeks to maximize customer value while eliminating waste, unevenness, and overburden. Its central principles are value, value-stream understanding, flow, pull, and continuous pursuit of perfection. Important methods include takt-time analysis, Kanban, 5S, SMED, standard work, mistake-proofing, and kaizen. These methods work best when processes are stable, employees are involved, and improvements are assessed across the entire value stream.

The Theory of Constraints identifies the factor limiting total system performance and directs improvement through the five focusing steps: identify, exploit, subordinate, elevate, and repeat. Lean and TOC are not mutually exclusive. Lean improves flow and reduces waste, while TOC prioritizes system-wide attention. Operational excellence integrates both with strategy, leadership, capability development, ethical governance, reliable measurement, and continuous learning.

Successful implementation requires more than tools. It requires leadership behavior, psychological safety, meaningful employee participation, suitable metrics, respect for people, and protection against local optimization. Digital technologies and AI can improve visibility and prediction, but they should address real operational problems and remain subject to human, ethical, safety, and regulatory controls.

Key Terms

Lean operations: A system for creating customer value with minimum waste and reliable flow.

Value: A product or service attribute that fulfills a customer requirement.

Value stream: The complete sequence of material, information, and work activities required to deliver value.

Muda: Wasteful activity that consumes resources without creating customer value.

Mura: Unevenness or variability in demand, work, or process performance.

Muri: Overburden placed on people, equipment, or systems.

Takt time: Available production time divided by customer demand for the same period.

Cycle time: The elapsed time between completed units at a process.

Pull system: A system in which downstream consumption authorizes upstream replenishment.

Kanban: A visual or electronic signal that controls replenishment or work release.

5S: Sort, Set in order, Shine, Standardize, and Sustain.

SMED: A method for reducing equipment changeover time by separating and simplifying setup activities.

Standard work: The current best-known method for performing work safely and consistently.

Poka-yoke: Mistake-proofing that prevents or immediately detects errors.

Kaizen: Continuous, participative improvement.

Constraint: A factor that limits the system’s ability to achieve its goal.

Throughput: The rate at which a system generates money through actual sales or completed service.

Drum–Buffer–Rope: A TOC scheduling logic based on the constraint schedule, protective buffer, and controlled release.

Operational excellence: Sustained, system-wide performance achieved through aligned processes, people, leadership, and learning.

Review Questions

Short Answer Questions

1. Distinguish muda, mura, and muri.
2. What is the difference between takt time and cycle time?
3. State the five focusing steps of the Theory of Constraints.
4. What is the purpose of a Kanban signal?
5. Why is standard work necessary for continuous improvement?

Long Answer Questions

1. Explain the five principles of lean operations and discuss how they reinforce one another.
2. Compare lean operations and the Theory of Constraints in terms of objectives, methods, and performance logic.
3. Explain how 5S, SMED, and mistake-proofing can improve flow and quality.
4. Discuss the organizational and ethical barriers to implementing lean operations.
5. Design an operational-excellence roadmap for a service or manufacturing organization.

Analytical / Application Questions

1. A process has 360 available minutes per shift and customer demand of 90 units. Calculate takt time and explain how it should influence line design.
2. Three sequential resources have capacities of 70, 48, and 60 units per hour. Identify the constraint and explain which improvement would increase system capacity most directly.
3. A department proposes reducing every buffer to zero to demonstrate lean performance. Critically evaluate this proposal using Little’s Law, flow stability, and the Theory of Constraints.

Multiple Choice Questions with Answers

Question 1

Which statement best defines takt time?

A. The time required to complete a changeover

B. The average time a unit spends in the entire value stream

C. The customer-required pace based on available time and demand

D. The time needed to inspect one finished unit

Correct Answer: C. The customer-required pace based on available time and demand

Question 2

A process completes 50 units per day and average work-in-process is 150 units. Under stable conditions, what is the average flow time?

A. 2 days

B. 3 days

C. 50 days

D. 200 days

Correct Answer: B. 3 days

Question 3

Which activity is the primary purpose of a pull system?

A. To authorize production from forecasted utilization targets

B. To authorize replenishment in response to downstream consumption

C. To maximize inventory at every workstation

D. To eliminate all process buffers regardless of variability

Correct Answer: B. To authorize replenishment in response to downstream consumption

Question 4

A line has available time of 420 minutes per day and demand of 105 units per day. What is takt time?

A. 2 minutes per unit

B. 4 minutes per unit

C. 105 minutes per unit

D. 525 minutes per unit

Correct Answer: B. 4 minutes per unit

Question 5

Which of the following is an example of mistake-proofing?

A. Producing a larger batch to reduce perceived unit cost

B. Adding inventory before a process

C. Using a connector that can fit only in the correct orientation

D. Increasing inspection paperwork after defects occur

Correct Answer: C. Using a connector that can fit only in the correct orientation

Question 6

In the Theory of Constraints, what should management do immediately after identifying the constraint?

A. Subordinate all other activities before studying the constraint

B. Exploit the constraint using existing capacity effectively

C. Purchase new equipment automatically

D. Remove all buffers from the system

Correct Answer: B. Exploit the constraint using existing capacity effectively

Question 7

A system has sequential capacities of 80, 45, and 65 units per hour. What is its capacity before other factors are considered?

A. 45 units per hour

B. 65 units per hour

C. 80 units per hour

D. 190 units per hour

Correct Answer: A. 45 units per hour

Question 8

Which statement about standard work is most accurate?

A. It permanently prevents employees from suggesting improvements

B. It documents the current best-known method and provides a baseline for improvement

C. It applies only to automated equipment

D. It replaces the need for quality measurement

Correct Answer: B. It documents the current best-known method and provides a baseline for improvement

Question 9

What is the main purpose of SMED?

A. To increase finished-goods inventory

B. To reduce setup or changeover time

C. To calculate customer demand

D. To identify all forms of organizational waste

Correct Answer: B. To reduce setup or changeover time

Question 10

Which condition most directly supports sustainable operational excellence?

A. Optimizing each department independently

B. Using output alone as the performance measure

C. Combining stable processes, employee involvement, system-level metrics, and continuous learning

D. Implementing every lean tool simultaneously

Correct Answer: C. Combining stable processes, employee involvement, system-level metrics, and continuous learning