3. Value Stream Analysis and Waste Diagnosis

Introduction and Context

Lean manufacturing is concerned not merely with reducing isolated operating costs, but with improving the complete system through which customer value is created. A production department may report high machine utilisation, a purchasing department may achieve low material prices, and a warehouse may maintain accurate records, yet the organisation may still suffer from long delivery times, excessive inventory, poor quality, and unreliable schedules. These outcomes occur because local efficiency does not necessarily produce flow across the entire value-creation system.

Value stream analysis provides a way to see that system. It follows a product family from the receipt of customer demand through planning, material movement, processing, inspection, storage, and delivery. The analysis includes both the physical flow of materials and the information flow that directs production. Its purpose is to distinguish activities that create value from those that consume resources without increasing the product’s value to the customer. It also reveals queues, interruptions, constraints, rework loops, and failures in coordination that are often invisible when departments are studied separately.

For production managers, value stream analysis is an important bridge between lean philosophy and operational decision-making. It supports the construction of a current-state map, the diagnosis of the eight wastes, the calculation of lead time and process-cycle efficiency, and the design of a future-state system. The method is analytical, but it is also managerial: it requires choices about priorities, policies, technology, capacity, supplier relationships, and employee involvement.

Learning Objectives

After studying this chapter, the learner should be able to:

1. Define a value stream and explain the relationship between material flow and information flow.

2. Construct and interpret current-state and future-state value stream maps.

3. Identify the eight forms of waste and distinguish waste from necessary non-value-adding work.

4. Diagnose constraints, bottlenecks, queues, batch effects, and information-flow failures.

5. Calculate lead time, process-cycle efficiency, value-added ratio, takt time, and related measures.

6. Prioritise improvement opportunities using evidence-based criteria.

7. Evaluate the managerial, technological, ethical, and organisational implications of value-stream improvement.

Seeing the Whole Value Stream

A value stream is the complete set of activities required to transform raw material, information, or a customer requirement into a delivered product or service. In manufacturing, it commonly extends from suppliers through the plant to the customer. It includes activities that directly transform the product, such as machining and assembly, as well as activities that determine or support production, such as order entry, scheduling, purchasing, inspection, maintenance, and dispatch.

The value stream should be analysed by product family rather than by every individual stock-keeping unit. A product family consists of products that pass through broadly similar processing steps and equipment. If products with entirely different routings are mapped together, the result becomes difficult to interpret. Conversely, if every part number is mapped separately, the organisation may lose sight of systemic patterns. Product-family selection therefore requires judgement based on routing data, demand characteristics, volumes, and managerial purpose.

Lean analysis uses three broad categories of activity:

• Value-adding activity changes the form, fit, function, or quality of the product in a way the customer is willing to pay for and that is performed correctly the first time.
• Necessary but non-value-adding activity consumes resources without directly adding customer value, but may currently be required by regulation, technology, safety, or the existing operating system.
• Pure waste consumes resources and can be removed without reducing the product’s required function, quality, safety, or legal compliance.

This distinction prevents a simplistic interpretation of lean. For example, final inspection may not add value from the customer’s perspective, but eliminating inspection without improving process capability would create risk. The immediate objective may therefore be to reduce inspection effort while preventing defects at source.

The Architecture of a Value Stream Map

A value stream map is a visual representation of the flow of material and information. It is not simply a process flowchart. A conventional map shows customer demand, supplier interaction, production-control signals, process boxes, inventory triangles, transportation, data boxes, and a timeline. The symbols are less important than the discipline of representing actual system behaviour.

A current-state map should be based on direct observation, often called going to the gemba. The mapping team follows the physical route from shipping back toward receiving, records actual quantities and times, and then traces how information authorises and sequences work. Standard data normally include customer demand, available working time, takt time, cycle time, changeover time, uptime, number of operators, batch size, inventory quantity, defect or rework information, and the frequency and method of scheduling.

The information flow may be formal, such as an enterprise resource planning system, production schedule, purchase order, or electronic kanban signal. It may also be informal, such as telephone calls, spreadsheets, handwritten notes, expediting messages, or supervisor intervention. Informal mechanisms are especially important because they often compensate for weaknesses in the formal system. A map that records only the ERP transaction but ignores daily expediting gives an inaccurate account of how production is actually controlled.

A practical mapping sequence is as follows:

1. Select a product family and define the boundaries of the study.

2. Establish customer demand, available time, delivery frequency, and service expectations.

3. Walk the process in the reverse direction, from customer dispatch to raw-material receipt.

4. Record process data and inventory at each point.

5. Draw the material flow, including transport, queues, rework, and storage.

6. Draw the information flow from customer and production control to suppliers and processes.

7. Add the timeline showing processing time and waiting or inventory time.

8. Validate the map with operators, supervisors, planners, quality personnel, and logistics staff.

9. Identify the dominant sources of delay and instability before proposing solutions.

The map should describe normal operating conditions as well as significant exceptions. If a process frequently waits for approval, lacks material, or requires schedule changes, those conditions are part of the current state. Averaging them away can make a system appear healthier than it is.

Quantifying Flow Performance

Quantitative measures help convert a visual diagnosis into an improvement case. They should be interpreted together rather than used as isolated performance targets.

Takt time expresses the rate at which production must be completed to meet customer demand:

Takt time = Available production time / Customer demand

If a plant has 420 available minutes in a shift and demand is 140 units, takt time is 3 minutes per unit. Takt is a demand-based requirement; it is not the same as cycle time. Cycle time is the actual time required by a process to complete one unit or one defined batch. A process with a cycle time below takt may still fail to meet demand if it is unreliable, starved, blocked, or frequently changed over.

Lead time is the elapsed time from the beginning of the value stream to delivery. It includes processing, transport, inspection, waiting, storage, queueing, and delays. In a production map, inventory time may be estimated by dividing inventory quantity by the relevant daily demand rate:

Inventory days = Inventory quantity / Daily demand

This calculation is an approximation. Demand variability, safety stock policies, product mix, and replenishment rules may require a more detailed analysis.

Process-cycle efficiency (PCE) measures the proportion of total lead time represented by value-adding processing:

PCE = Value-adding processing time / Total lead time × 100

A related measure, the value-added ratio, is often expressed in the same way. Some organisations use “value-added ratio” to include only customer-defined value-adding work, while others include a broader set of processing activities. The definition must therefore be stated explicitly.

Consider a product with 18 minutes of value-adding processing time and a total lead time of 4.5 days. If the plant operates 480 minutes per day, total elapsed operating time is 2,160 minutes. PCE is:

18 / 2,160 × 100 = 0.83 percent.

The very low result is not evidence that the operators are unproductive. It indicates that most elapsed time is associated with waiting, inventory, movement, inspection, scheduling, or other non-value-adding conditions. The improvement question is not simply how to make the 18 minutes faster; it is how to reduce the 2,142 minutes surrounding it without damaging quality or flexibility.

Other useful measures include first-pass yield, on-time delivery, changeover time, queue time, work-in-process turnover, schedule adherence, overall equipment effectiveness, and the percentage of orders requiring expediting. These metrics should be connected to customer outcomes. Increasing machine utilisation by producing large batches may reduce the number of setups per unit while increasing lead time and inventory. A local metric can therefore encourage behaviour that harms the value stream.

Diagnosing the Eight Wastes

The traditional lean framework identifies seven wastes; many contemporary applications add an eighth, underutilised human capability. The mnemonic DOWNTIME is commonly used:

Defects include errors, scrap, rework, incorrect documentation, and failures that require correction or replacement. Defects create direct cost and often generate hidden waste through investigation, rescheduling, additional inspection, and customer dissatisfaction. A defect should be traced to its process cause rather than treated only at the point of detection.

Overproduction occurs when products are made earlier, faster, or in greater quantity than demanded. It is frequently regarded as the most serious waste because it conceals other problems and creates inventory, storage, handling, obsolescence, and cash-flow burdens. Large batches may hide unreliable equipment, long changeovers, or poor supplier performance.

Waiting occurs when people, materials, information, equipment, or decisions are idle. A machine waiting for material and an operator waiting for quality approval are both examples. Waiting is often a symptom of unbalanced capacity, batch release, poor prioritisation, or an information delay.

Non-utilised talent arises when employees’ knowledge, creativity, problem-solving ability, or judgement is ignored. It appears when operators are excluded from process design, when suggestions are not acted upon, or when people spend their time compensating for administrative failures rather than improving the system.

Transportation is unnecessary movement of materials, components, tools, documents, or products. Transportation does not transform the product and may cause damage, loss, misidentification, or delay. Not all movement can be eliminated, but the need for it can often be reduced through layout, point-of-use storage, and better flow design.

Inventory includes raw material, work in process, finished goods, spare parts, and information held in queues. Inventory can protect customers from variation, but excessive inventory conceals defects, consumes space, ties up capital, and weakens urgency to solve process problems. Inventory reduction should follow improvements in stability and replenishment logic, not precede them recklessly.

Motion refers to unnecessary movement by people, including reaching, walking, searching, bending, repeated scanning, and retrieving tools. Motion is distinct from transportation because it concerns the movement of people or their actions at the workstation. Ergonomic risk and fatigue make this waste a safety and quality issue as well as a productivity issue.

Extra-processing consists of work beyond what the customer, technical specification, or regulatory requirement demands. Examples include duplicate data entry, excessive polishing, repeated inspections, unnecessary approvals, and producing reports that are not used. The correct remedy is to verify requirements, not to remove controls indiscriminately.

Waste categories frequently overlap. A poorly designed information system may cause waiting, extra-processing, overproduction, and non-utilised talent simultaneously. Improvement teams should therefore look for causal relationships rather than assigning each observation to only one category.

Constraints, Bottlenecks, and Flow Disruptions

A constraint is any factor that limits the ability of a system to achieve its purpose. A bottleneck is a capacity constraint at a particular process or resource. The bottleneck may be a machine, skilled employee, inspection station, supplier, approval process, or policy. The slowest process is not always the effective constraint: a nominally fast process may become restrictive when it has high downtime, long changeovers, or severe quality losses.

Constraint analysis asks several questions. Where does work accumulate? Which process has the longest effective cycle time? Where are shortages or expediting most frequent? Which resource determines the release of work? Does a capacity increase at one point merely move the queue elsewhere? These questions shift attention from visible busyness to system throughput.

The Theory of Constraints provides a useful logic: identify the constraint, exploit it by protecting and using its capacity effectively, subordinate other activities to it, elevate its capacity when justified, and repeat the process when the constraint moves. In a lean context, this logic must be combined with quality at source, standard work, pull control, and respect for people. Running a constraint continuously to produce defective or unwanted output is not exploitation; it is the creation of more waste.

Common flow disruptions include uneven demand, large transfer batches, unreliable equipment, shared resources, functional layouts, long approval chains, poor changeover practices, inaccurate bills of material, and conflicting performance indicators. These conditions often interact. For instance, a planner may issue large batches to protect utilisation because changeovers are long; the resulting inventory then increases congestion, which lengthens lead time and makes schedules less reliable.

From Current State to Future State

The current-state map is a diagnostic representation, not a target. A future-state map describes how the value stream should operate after selected improvements. It should be designed around customer demand, stable flow, controlled work-in-process, reliable information, and clear responsibility.

Important future-state questions include:

• Where can continuous flow be established?
• Where is a supermarket or controlled inventory point necessary because continuous flow is impractical?
• How will production be triggered: a customer order, kanban, scheduled replenishment, or another pull signal?
• At what point will the schedule be introduced, and how will upstream processes respond?
• What is the pacemaker process that sets the rhythm of the value stream?
• How will changeovers, maintenance, quality checks, and material replenishment support takt?
• What information will be visual, standardised, and available at the point of use?

A future-state design is not simply a picture with fewer inventory triangles. It must specify operating rules. These may include a FIFO lane with a defined maximum quantity, a supermarket with replenishment criteria, a heijunka or demand-levelling box, standard work, daily management, escalation rules, and a method for responding to abnormalities.

Implementation should be staged. The team may first stabilise the constraint, then reduce changeover time, establish standard work, connect processes through pull, and finally reduce buffers as reliability improves. Each step should have an owner, a measurable target, a review date, and a method for preventing regression. A map without an implementation plan is an analytical document rather than a management system.

Prioritising Improvement Opportunities

A current-state map may reveal dozens of problems. Attempting to solve all of them simultaneously disperses attention. Prioritisation should consider customer impact, lead-time reduction, constraint effect, financial significance, risk, implementation effort, and learning value.

A simple prioritisation matrix can classify opportunities by impact and difficulty. High-impact, low-difficulty actions are immediate candidates. High-impact, high-difficulty opportunities may require a structured project. Low-impact actions should not displace work on the constraint or on quality-critical issues. A weighted scoring model can make assumptions explicit. For example:

Priority score = customer impact + lead-time impact + constraint impact + quality impact − implementation effort − risk.

The numerical values are managerial judgements, not objective truths. They should be discussed with people who understand the process. Pareto analysis, cause-and-effect diagrams, five-whys analysis, process capability studies, and failure-mode analysis can then be applied to selected problems.

A sound improvement portfolio balances quick wins with foundational work. Moving a tool closer to an operator may produce an immediate ergonomic benefit, while correcting master data or redesigning supplier replenishment may take longer but deliver greater systemic value. Financial evaluation should include inventory carrying cost, released capacity, scrap, overtime, working capital, service performance, and the cost of implementation.

Illustrative Case: The Valve Assembly Value Stream

Background

The following is a fictional illustrative case. Meridian Flow Systems produces industrial control valves for equipment manufacturers. A product family of medium-sized valves is assembled, tested, and packed in one plant. Customer demand averages 240 units per day, and the plant operates one 480-minute shift with 30 minutes of planned breaks and meetings. Thus, available production time is 450 minutes per day.

Situation and Problem

The plant reports 92 percent machine utilisation in machining and maintains high finished-goods inventory to protect delivery performance. Nevertheless, average customer lead time is 8.2 days, on-time delivery is inconsistent, and supervisors frequently expedite orders. Operators report that schedules change several times per shift. Management initially proposes purchasing a faster machining centre.

A cross-functional team selects the valve family and observes the complete route. The main findings are:

• Customer demand is 240 units per day, giving a takt time of 1.875 minutes per unit.
• Machining cycle time is 1.6 minutes per unit, but changeovers take 110 minutes and occur four times weekly.
• Assembly cycle time is 2.4 minutes per unit, making assembly slower than takt.
• Testing takes 1.2 minutes per unit, but only one test station is available and it experiences frequent waiting for quality decisions.
• Inventory averages 1,200 units before assembly and 720 units before testing.
• A production schedule is released weekly, but supervisors alter it through messages and spreadsheets.
• Approximately 7 percent of assembled units require rework after testing.

Analysis

The inventory before assembly represents approximately five days of demand. The inventory before testing represents three days of demand. Even without including finished goods and raw material, the mapped inventory accounts for eight days of demand, which is consistent with the reported lead time. The value-adding processing time is 1.6 + 2.4 + 1.2 = 5.2 minutes per unit, excluding any operation-specific definition of value. If total elapsed time is approximated as 8.2 days × 450 minutes, or 3,690 minutes, PCE is:

5.2 / 3,690 × 100 = 0.14 percent.

The calculation highlights an important issue: the product spends almost all of its time waiting or being held. Assembly is above takt and is therefore a capacity concern. However, the proposed machining centre would not solve the primary system problem. The map indicates overproduction in machining, inventory used to conceal imbalance, schedule instability, testing delays, and defects generated upstream or during assembly.

The team identifies information-flow failure as a major cause. The official schedule is not the schedule used by the shop floor. Frequent changes create extra movement, priority confusion, and incomplete kits. The testing queue is also amplified by rework, while large machining batches are justified by long changeovers.

Approach and Solution

The future-state design uses assembly as the pacemaker because it is closest to customer configuration and is the effective capacity constraint. The team first documents standard work and balances assembly tasks to a target cycle time below takt. It introduces a small FIFO lane between machining and assembly with a maximum quantity. Machining replenishes this lane only when downstream consumption creates space.

A supermarket is retained for selected purchased components whose supply lead times make direct flow impractical. Replenishment is triggered by kanban cards rather than by weekly forecasts alone. The weekly schedule is converted into a controlled daily sequence at the pacemaker, while unauthorised schedule changes require an escalation decision.

A rapid-changeover project reduces external preparation, standardises fixtures, and separates internal from external setup activities. Testing receives a defined response standard for quality decisions, and a first-piece approval procedure is introduced after relevant changes. The team also establishes daily review of rework causes and uses operator suggestions to redesign the assembly fixture.

Outcome

In the illustrative scenario, after three months the team reports that pre-assembly inventory has been reduced from 1,200 to 360 units and pre-test inventory from 720 to 240 units. Changeover time falls from 110 to 45 minutes. Assembly cycle time falls to 1.75 minutes, below the 1.875-minute takt. Rework falls from 7 percent to 3 percent. The plant postpones the purchase of the faster machining centre because available capacity is released by smaller batches, improved changeovers, and reduced rework.

The outcome is not attributed to one tool. It results from connecting demand, pacemaker control, standard work, pull replenishment, quality at source, and employee involvement. The map made the relationships visible and helped management avoid an expensive local optimisation.

Learning Points

First, high utilisation is not equivalent to high flow. Second, inventory may be a symptom of instability rather than a solution to it. Third, information flow deserves the same analytical attention as material flow. Fourth, the constraint should guide improvement priorities. Finally, future-state mapping is effective only when it is translated into operating rules and reviewed through actual performance.

Common Errors, Risks, and Limitations

Value stream mapping can fail when the team maps an idealised process rather than the real one. Estimates copied from standard times or information systems may differ substantially from observed conditions. Another error is treating every non-value-adding activity as immediately removable. Safety checks, legal records, traceability, and essential maintenance cannot be eliminated merely because they do not transform the product.

A map may also encourage excessive focus on cycle time while ignoring quality, flexibility, employee wellbeing, or resilience. Reducing inventory too aggressively can expose suppliers and processes to variation before the underlying causes are controlled. Similarly, concentrating production around one constraint without contingency planning may increase vulnerability to breakdowns or supply disruption.

Organisational resistance is common. Departments may protect local metrics, fear loss of authority, or interpret transparency as criticism. Managers should frame the map as a representation of the system, not a device for blaming individuals. Data ownership, confidentiality, and fair performance evaluation are important governance issues. Employees should not be pressured to conceal abnormalities or work at unsafe speeds to meet takt. Lean improvement must respect occupational health, legal requirements, product safety, and the right to raise concerns.

Digital systems create additional risks. Automated dashboards may provide precise-looking measures based on incomplete or delayed data. Artificial intelligence can help detect patterns in downtime, defects, and demand, but its recommendations require process knowledge, data validation, and human accountability. A digital map is useful only when it reflects the actual process and supports decisions at the appropriate organisational level.

Contemporary Developments and Best Practice

Modern value-stream analysis increasingly combines traditional observation with event-log analysis, Internet of Things data, real-time location systems, digital twins, and process mining. These technologies can reveal variation by shift, product mix, machine state, or order type. They should complement, not replace, direct observation and employee experience. Quantitative data show what happened; people often explain why it happened.

Sustainable value-stream mapping extends the analysis to energy, emissions, water, packaging, hazardous materials, and reverse logistics. Resilience-oriented mapping examines single-source suppliers, long replenishment times, cyber dependence, and recovery options. In service and administrative environments, the same logic applies to information queues, approvals, case handling, and customer response.

Good practice includes defining the customer and product family clearly, observing the gemba, validating data across functions, displaying both material and information flows, distinguishing demand from capacity, protecting quality and safety, involving employees, and linking every future-state feature to an implementation action. Maps should be revisited when demand, product design, technology, suppliers, or operating policies change.

Chapter Summary

Value stream analysis examines the complete system through which customer demand becomes delivered value. It integrates material flow with information flow and distinguishes value-adding work from necessary and pure waste. Current-state mapping documents actual conditions, including queues, inventory, defects, constraints, informal expediting, and schedule instability. Future-state mapping designs a more coherent system based on takt, flow, pull, controlled work-in-process, pacemaker control, standard work, and quality at source.

The eight wastes—defects, overproduction, waiting, non-utilised talent, transportation, inventory, motion, and extra-processing—often reinforce one another. Constraint analysis prevents managers from pursuing local improvements that do not increase system throughput. Measures such as takt time, lead time, process-cycle efficiency, and value-added ratio make delay and waste visible, while prioritisation methods help focus scarce improvement resources. Effective application requires direct observation, cross-functional participation, ethical safeguards, employee involvement, and disciplined implementation. Digital tools and sustainability perspectives can strengthen the analysis when used with sound process knowledge and validated data.

Key Terms

Value stream: The complete set of activities required to create and deliver a product or service.

Value stream map: A visual representation of material flow, information flow, inventories, processes, and time.

Product family: A group of products sharing sufficiently similar processing routes for joint analysis.

Value-adding activity: Work that transforms the product in a way required and valued by the customer.

Necessary non-value-adding activity: Work that does not add customer value but is currently required by regulation, technology, safety, or system conditions.

Pure waste: Resource-consuming activity that can be removed without reducing required value, quality, safety, or compliance.

Takt time: The available production time divided by customer demand.

Cycle time: The actual time required to complete a unit or defined production cycle.

Lead time: Total elapsed time from the beginning of a process or order to delivery.

Process-cycle efficiency: The percentage of total lead time represented by value-adding processing time.

Value-added ratio: A measure comparing customer-defined value-adding time with total elapsed time.

Current-state map: A documented representation of how the value stream operates now.

Future-state map: A proposed representation of how the value stream should operate after improvement.

Pacemaker process: The process selected to set the production rhythm and sequence for the value stream.

Supermarket: A controlled inventory point replenished according to downstream consumption.

FIFO lane: A first-in, first-out flow-control mechanism with defined limits.

Constraint: Any factor that limits the system’s ability to achieve its purpose.

Bottleneck: A resource or process whose effective capacity restricts system throughput.

Process mining: The analysis of event-log data to discover and evaluate actual process flows.

Review Questions

Short Answer Questions

1. What is the difference between a value stream map and a conventional process flowchart?

2. Define takt time and explain why it should not be confused with cycle time.

3. List the eight wastes represented by the DOWNTIME mnemonic.

4. What is the purpose of a pacemaker process in a future-state map?

5. Why can inventory be both a protection mechanism and a source of waste?

Long Answer Questions

1. Explain the procedure for constructing a current-state value stream map, including the data that should be collected.

2. Discuss how material flow and information flow interact to create or reduce operational waste.

3. Explain process-cycle efficiency and value-added ratio, including their uses and limitations.

4. Analyse the relationship between constraints, batch sizes, changeovers, and inventory in a production system.

5. Describe how a future-state map can be converted into a practical implementation plan.

Analytical / Application Questions

1. A plant operates 450 minutes per day and receives demand for 180 units. Calculate takt time and explain what it implies for a process with a 2.8-minute cycle time.

2. A product has 24 minutes of value-adding time and a total lead time of six operating days at 420 minutes per day. Calculate process-cycle efficiency and interpret the result.

3. A factory has high machine utilisation but frequent expediting, large work-in-process queues, and schedule changes made through informal messages. Using value-stream analysis, identify likely causes and propose three prioritised improvement actions.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes takt time from cycle time?

A. Takt time is the actual time a machine takes, while cycle time is customer demand divided by available time.

B. Takt time is demand-based, while cycle time is the actual time required by a process.

C. Takt time includes inventory waiting, while cycle time excludes processing.

D. Takt time applies only to suppliers, while cycle time applies only to customers.

Correct Answer: B. Takt time is demand-based, while cycle time is the actual time required by a process.

Question 2

A product has 12 minutes of value-adding processing and a total lead time of 2,400 operating minutes. What is its process-cycle efficiency?

A. 0.5 percent

B. 2 percent

C. 5 percent

D. 20 percent

Correct Answer: A. 0.5 percent

Question 3

Which observation is the clearest example of overproduction?

A. An operator walks to obtain a tool.

B. A finished product is made before there is customer demand for it.

C. A component fails final inspection.

D. A machine waits for maintenance approval.

Correct Answer: B. A finished product is made before there is customer demand for it.

Question 4

Why should information flow be included in a value stream map?

A. Because information has no relationship to production performance.

B. Because material movement is always controlled directly by customers.

C. Because schedules, approvals, and signals determine how work is released and prioritised.

D. Because information flow measures only employee productivity.

Correct Answer: C. Because schedules, approvals, and signals determine how work is released and prioritised.

Question 5

A process has a cycle time below takt but still misses deliveries because it frequently breaks down and waits for materials. What does this demonstrate?

A. Cycle time alone does not guarantee effective flow.

B. Takt time is irrelevant to customer demand.

C. Inventory always improves delivery reliability.

D. The process is necessarily the system bottleneck.

Correct Answer: A. Cycle time alone does not guarantee effective flow.

Question 6

Which future-state feature is most appropriate when two processes cannot be connected by continuous flow but downstream consumption can trigger replenishment?

A. Uncontrolled batch production

B. A supermarket with a pull signal

C. A larger finished-goods inventory

D. A weekly schedule change by supervisors

Correct Answer: B. A supermarket with a pull signal

Question 7

In the illustrative valve case, why was purchasing a faster machining centre not the first priority?

A. Machining had no cycle time at all.

B. The main problems included assembly capacity, large batches, rework, and unstable information flow.

C. Customer demand was zero.

D. Testing was eliminated from the value stream.

Correct Answer: B. The main problems included assembly capacity, large batches, rework, and unstable information flow.

Question 8

Which action best reflects the Theory of Constraints?

A. Improve every department equally before studying throughput.

B. Increase output at non-constraints regardless of demand.

C. Identify, protect, and improve the resource limiting system throughput.

D. Remove all inventory immediately, including safety-critical stock.

Correct Answer: C. Identify, protect, and improve the resource limiting system throughput.

Question 9

Why can excessive inventory conceal operational problems?

A. It makes defects, unreliable processes, and poor scheduling less visible to downstream users.

B. It always reduces product variety.

C. It eliminates the need for material handling.

D. It guarantees that information is accurate.

Correct Answer: A. It makes defects, unreliable processes, and poor scheduling less visible to downstream users.

Question 10

What is an important governance principle when implementing lean improvements?

A. Employees should be required to work faster even when unsafe.

B. Performance data should be used to blame individuals for system defects.

C. Safety, legal compliance, product quality, and employee participation must be protected.

D. Digital dashboards should replace direct observation completely.

Correct Answer: C. Safety, legal compliance, product quality, and employee participation must be protected.