Lean Manufacturing

Chapter 15
Lean Transformation Strategy and Future Directions

Bachelors Program in Machine Technology
Lean Manufacturing   •   Bachelor

Lean Transformation Strategy and Future Directions

Introduction

Lean manufacturing is often introduced through tools such as 5S, kanban, standard work, value-stream mapping, and total productive maintenance. These tools are valuable, but enterprise transformation is not achieved by implementing tools in isolation. It requires a coherent strategy that connects purpose, policy, operating systems, leadership behavior, employee capability, technology, and measurable business results.

A lean transformation is therefore a long-term organizational change program. It must translate strategic intent into daily work, coordinate improvement portfolios, assess maturity, verify performance through audits, and ensure that gains continue after the initial project ends. At the same time, contemporary manufacturers must respond to environmental limits, supply disruption, customized demand, digital technologies, and the human-centered expectations associated with Industry 5.0.

This chapter presents an enterprise approach to lean transformation. It explains hoshin kanri and catchball, maturity assessment, portfolio governance, audits, benefit sustainment, and the relationship between lean thinking and green, circular, customized, resilient, and human-centric manufacturing.

Learning Objectives

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

  1. Explain how hoshin kanri aligns enterprise strategy with daily improvement activity.
  2. Apply catchball to create realistic, two-way policy deployment.
  3. Design a lean maturity assessment and interpret its limitations.
  4. Establish governance for a portfolio of lean initiatives.
  5. Plan audits, performance reviews, and benefit-sustainment mechanisms.
  6. Evaluate the strategic relationship between lean manufacturing and green lean, circular manufacturing, mass customization, resilient operations, and Industry 5.0.
  7. Recommend an integrated transformation roadmap for a manufacturing enterprise.

1. From Lean Projects to Enterprise Transformation

A lean project normally has a defined process, team, problem, and completion date. Transformation is broader. It changes how the enterprise chooses priorities, designs work, allocates resources, develops people, manages suppliers, and learns from performance.

Three levels should be distinguished:

LevelMain questionTypical output
Local improvementHow can this process perform better?Kaizen event, standard work, reduced waste
System improvementHow should connected processes work together?Flow redesign, production-control system, cross-functional process
Enterprise transformationHow should the organization compete and learn?Strategic deployment, capability system, governance model

The most common failure is local optimization. A department may reduce its labor hours by producing larger batches, while total inventory, lead time, and customer response worsen. Enterprise lean requires a systems view in which customer value, material flow, information flow, people, assets, suppliers, and financial performance are considered together.

Transformation also has a temporal dimension. Initial improvements often produce visible gains, but performance may return to its former level when attention shifts. Sustainable lean therefore depends on management routines, capability development, standard work for leaders, and an operating system that makes abnormal conditions visible.

2. Hoshin Kanri: Strategy into Action

Hoshin kanri, often translated as policy deployment or strategy deployment, is a disciplined method for converting a small number of strategic priorities into coordinated objectives and improvement work. It is not simply annual target setting. It combines strategic choice, dialogue, measurement, review, and organizational learning.

A typical deployment sequence is:

  1. Clarify purpose, customer needs, and long-term direction.
  2. Analyze the current condition and significant performance gaps.
  3. Select a limited number of breakthrough objectives.
  4. Define annual objectives and measurable targets.
  5. Develop improvement strategies and responsible owners.
  6. Deploy objectives through successive organizational levels.
  7. Review progress frequently and adjust based on evidence.
  8. Reflect on learning at the end of the cycle.

A useful hoshin plan links the following elements:

ElementMeaning
True northLong-term direction and enduring purpose
Breakthrough objectiveSignificant change needed over several years
Annual objectiveResult expected during the current cycle
MeasureIndicator used to assess performance
Improvement initiativeCoordinated work intended to close the gap
OwnerPerson accountable for progress and learning
Review cadenceFrequency and method of checking progress

Good objectives describe an outcome rather than an activity. “Train operators in problem solving” is an activity. “Reduce repeat quality escapes by 50% while maintaining delivery performance” is an outcome. Training may be one means of achieving it, but the objective remains connected to customer and process performance.

2.1 Strategic diagnosis

Before targets are selected, the organization should establish a current condition. Useful evidence includes customer complaints, safety events, delivery reliability, inventory, productivity, quality losses, equipment performance, employee capability, and environmental impacts. The diagnosis should distinguish symptoms from causes. For example, late delivery may result from unreliable equipment, excessive product variety, poor scheduling rules, supplier shortages, or inaccurate master data.

A strategy deployment matrix can connect objectives to indicators and initiatives. However, a matrix is not a substitute for reasoning. Measures should be few enough to receive attention and balanced enough to prevent harmful behavior. A productivity target without safety and quality constraints can encourage overproduction or unsafe shortcuts.

2.2 Catchball

Catchball is the two-way dialogue through which objectives, methods, resources, and risks are negotiated between organizational levels. Senior leaders “throw” a strategic challenge to a function or site. The receiving group examines feasibility, identifies constraints, proposes methods, and returns a revised commitment. This process continues until alignment is achieved.

Catchball has four purposes:

  • test whether strategic goals are technically and operationally credible;
  • reveal interdependencies between departments;
  • secure ownership rather than passive compliance;
  • identify resources, capability gaps, and unintended consequences.

Catchball is not bargaining designed to make targets easier. Nor is it a one-way cascade in which lower levels merely receive instructions. Effective dialogue preserves strategic ambition while allowing those closest to the work to shape the method and expose facts that senior management cannot see.

2.3 The Plan–Do–Check–Act cycle

Hoshin kanri is commonly operated through PDCA. Planning establishes direction and countermeasures; doing implements experiments; checking compares actual results with the target; acting standardizes successful learning or revises the hypothesis. A review should ask not only “Did we achieve the target?” but also “What did we learn about the cause-and-effect relationship?”

A useful performance-gap expression is:

Gap = Target − Actual

The sign and interpretation depend on the measure. For a defect rate, a positive target-minus-actual value may indicate underperformance if the target is a lower number; therefore organizations should explicitly define whether “higher” or “lower” is better. The formula is a simple difference, not a causal model.

3. Lean Transformation Maturity

Maturity assessment helps an organization understand its present capability and select an appropriate next step. It should not be treated as a league table or certification score. Maturity is multidimensional: an organization may have advanced digital systems but weak problem-solving discipline, or excellent shop-floor standards but poor enterprise alignment.

A practical assessment can examine six dimensions:

  1. Leadership and purpose – visible commitment, strategic clarity, and leader standard work.
  2. Customer and value – understanding of customer value, quality at the source, and service performance.
  3. Process and flow – stable processes, pull, takt-based planning where appropriate, and short lead time.
  4. People and capability – psychological safety, training, problem solving, and participation.
  5. Management system – visual management, daily accountability, escalation, and PDCA.
  6. Extended enterprise and sustainability – supplier integration, environmental performance, resilience, and lifecycle thinking.

An illustrative five-stage scale is shown below.

StageGeneral characteristics
1. ReactiveProblems are managed through urgent intervention; standards are weak.
2. ControlledBasic standards and measures exist in selected areas.
3. SystematicLean practices are integrated across value streams.
4. IntegratedStrategy, operations, suppliers, and improvement are aligned.
5. Learning enterpriseImprovement is embedded in culture, governance, innovation, and adaptation.

Assessment evidence should combine observation, interviews, records, performance data, and direct confirmation at the process. A self-assessment alone is vulnerable to optimism and managerial bias. Conversely, an external audit may miss local knowledge and create defensive behavior.

A numerical score can support comparison if used carefully. For example, if each of six dimensions receives a rating from 1 to 5, an unweighted average may be calculated as:

M = (r₁ + r₂ + r₃ + r₄ + r₅ + r₆) ÷ 6

Here, M is the average maturity score and rᵢ is the rating for dimension i. The calculation assumes that dimensions use the same scale and are considered equally important. In practice, a low score in safety, quality, or leadership may be more consequential than a moderate score in another dimension; therefore the average must not conceal critical weaknesses.

4. Portfolio Governance for Lean Initiatives

Large organizations often run dozens of improvement projects. Without governance, projects compete for the same engineers, operators, data analysts, and capital. Some projects duplicate one another, while others optimize a local process at the expense of an end-to-end value stream.

Portfolio governance provides a decision system for selecting, sequencing, funding, monitoring, and terminating initiatives. A portfolio board should include operations, engineering, quality, finance, supply chain, human resources, information technology, environmental specialists, and appropriate employee representatives.

Projects should be evaluated against explicit criteria, such as:

  • strategic relevance;
  • customer and quality impact;
  • safety and regulatory importance;
  • expected financial or capacity benefit;
  • environmental and social impact;
  • feasibility and resource demand;
  • dependency on other projects;
  • risk of disrupting current operations;
  • contribution to organizational capability.

A simple weighted score may be used:

P = ∑(wᵢsᵢ), where ∑wᵢ = 1

P is the portfolio priority score, wᵢ is the weight assigned to criterion i, and sᵢ is the normalized project score for that criterion. Scores must use a defined scale, such as 0 to 5. The method assumes that criteria can be meaningfully compared and that weights reflect strategic priorities. It is a decision aid, not an objective truth. Safety or legal requirements should normally be treated as gates rather than traded away through a weighted average.

Portfolio governance should distinguish three types of work:

  • mandatory work, such as safety, legal compliance, or urgent containment;
  • strategic transformation, such as redesigning a value stream or building problem-solving capability;
  • continuous improvement, such as small local kaizen activities.

Each initiative should have a charter stating the problem, customer, baseline, target, scope, owner, sponsor, expected benefits, risks, resources, and review dates. Charters should avoid claiming benefits that cannot be measured or attributed.

5. Audits, Reviews, and Benefit Sustainment

Audits in a lean system are learning mechanisms, not merely policing activities. A useful audit verifies whether the management system is being practiced and whether it is producing the intended conditions. It should examine the process at the workplace, speak with employees, review records, and test whether abnormalities lead to action.

Important audit types include:

  • process audits, which verify standard work and process controls;
  • layered process audits, conducted by different management levels at different frequencies;
  • system audits, which examine the connection between policy, routines, measures, and governance;
  • benefit audits, which verify whether claimed improvements remain real after project closure;
  • supplier audits, where external process capability affects customer performance.

Audits should be risk-based. A high-risk special process requires more attention than a stable low-risk activity. Findings should be classified according to severity, containment, root cause, corrective action, owner, and due date.

5.1 Benefit realization

A project benefit is not automatically equal to a financial saving. Reduced processing time may create capacity rather than immediate cost reduction. Lower inventory may release cash but could increase shortage risk if the system is unstable. Finance and operations should agree on definitions before implementation.

A basic benefit calculation is:

Benefit = Baseline performance − Current performance

This expression is valid only when the direction of improvement is defined and the measurement basis is consistent. For a cost reduction, a monetary benefit might be estimated as:

Annualized benefit = (Baseline cost per unit − New cost per unit) × Annual volume

The formula assumes that volume, product mix, cost boundaries, and measurement periods are comparable. It does not automatically represent cash released or profit improvement. Fixed costs, labor redeployment, investment, implementation expense, and demand changes must be considered separately.

Sustainment mechanisms include:

  1. documented standard work and visual controls;
  2. process ownership after project closure;
  3. leader standard work and regular confirmation;
  4. operator training and competency verification;
  5. reaction plans for abnormal conditions;
  6. trend monitoring rather than one-time measurement;
  7. integration into budgeting, appraisal, and operating reviews;
  8. periodic benefit audits;
  9. replication of proven practices only after checking local conditions.

A control plan should specify the characteristic to monitor, measurement method, frequency, responsible person, reaction limit, and escalation route. Control limits derived from statistical process control should not be confused with customer specifications: control limits describe process behavior, whereas specifications describe acceptable product or service requirements.

6. Green Lean and Environmental Performance

Green lean integrates waste elimination with reduced environmental impact. Traditional lean waste categories—defects, overproduction, waiting, transport, excess processing, inventory, motion, and underused talent—often have environmental consequences. For example, defects consume materials and energy, while unnecessary transport increases fuel use and emissions.

However, green lean is not simply conventional lean with an environmental label. Some lean actions can create environmental trade-offs. More frequent deliveries may reduce inventory but increase transport emissions. A faster machine may reduce lead time but increase energy consumption or maintenance demand. Environmental objectives must therefore be included in value-stream and investment decisions.

Useful environmental indicators include energy per good unit, water use, material yield, waste intensity, hazardous waste, greenhouse-gas emissions, and transport distance. A generic intensity measure is:

Environmental intensity = Environmental impact ÷ Functional output

The functional output must be defined, such as kilograms of saleable product or customer orders fulfilled. Comparisons require consistent boundaries and data quality. Greenhouse-gas accounting should specify the relevant organizational and operational boundaries and avoid claiming reductions that result only from shifting impacts elsewhere.

7. Circular Manufacturing

Circular manufacturing seeks to preserve product, component, and material value through durability, repair, reuse, remanufacturing, refurbishment, and recycling. Lean contributes by exposing material losses, stabilizing processes, reducing damage, and improving flow. Circularity adds lifecycle responsibility: the organization considers what happens before production and after the customer’s use.

Circular strategies may include:

  • design for disassembly and repair;
  • modular components and upgradeability;
  • reverse logistics and return systems;
  • remanufacturing standards;
  • recycled or renewable material selection;
  • industrial symbiosis and by-product exchange;
  • product-service models that reward durability.

Circular systems introduce additional flow complexity. Demand for returned products may be uncertain, product condition varies, and inspection and traceability become important. A lean pull system must therefore be adapted to two-way flows and variable recovery yields.

Ethical and regulatory questions include responsibility for product safety after refurbishment, truthful environmental claims, data privacy in connected products, and avoidance of exporting waste to jurisdictions with weaker controls.

8. Mass Customization and Lean Flow

Mass customization aims to provide variety approaching individual customer preference while retaining near mass-production efficiency. Lean principles support this goal through late customization, modular design, flexible equipment, quick changeover, mixed-model production, postponement, and reliable information flow.

The strategic challenge is to separate common operations from differentiating operations. Standard modules can flow in a stable system, while final configuration occurs closer to the customer once demand information is available. This reduces finished-goods variety but requires accurate bills of material, disciplined configuration management, capable suppliers, and error-proof information systems.

Customization can also increase cognitive load and quality risk. Operators need clear digital or visual instructions, appropriate training, and the authority to stop when a configuration is ambiguous. Artificial intelligence may assist demand sensing, scheduling, or configuration support, but its recommendations require validation, explainability, cybersecurity, and human accountability.

9. Resilient Lean Operations

Lean and resilience are sometimes portrayed as opposites. Excessively lean systems may appear vulnerable if they remove all buffers, suppliers, and capacity redundancy. This is an incomplete interpretation. Lean seeks the removal of unnecessary resources, not the removal of all protection against known risk. Resilience requires deliberate, risk-based buffers and the capability to recover.

Resilient operations combine:

  • supplier visibility and qualification;
  • multi-sourcing where justified;
  • strategic inventory for critical or long-lead items;
  • flexible workforce and equipment capability;
  • cross-training;
  • scenario planning and business continuity;
  • modular product and process designs;
  • rapid problem escalation;
  • transparent information sharing.

A buffer should be justified by risk rather than habit. A simple risk priority logic can consider likelihood, consequence, and detectability, but numerical risk scores can create false precision. Critical single points of failure should receive attention even when their estimated frequency is low.

Resilience should also be measured beyond recovery speed. Relevant questions include how long the enterprise can continue during disruption, how quickly it can restore acceptable service, and whether it learns sufficiently to reduce recurrence.

10. Human-Centric Industry 5.0

Industry 4.0 emphasizes connected equipment, automation, data, and cyber-physical systems. Industry 5.0 extends the discussion toward human-centricity, sustainability, and resilience. It does not necessarily replace Industry 4.0 technologies; it changes the purpose and governance of their use.

A human-centric lean transformation treats employees as problem solvers and knowledge holders rather than variable costs. Technologies such as collaborative robots, wearable guidance, digital work instructions, predictive maintenance, and decision-support analytics should improve safety, capability, quality, and meaningful work.

Key principles include:

  • technology should augment human judgment where possible;
  • automation should not conceal abnormal conditions or deskill workers without safeguards;
  • workers should participate in system design;
  • data collection should be proportionate, transparent, and secure;
  • algorithmic recommendations should be monitored for bias and error;
  • reskilling should accompany technological change;
  • job quality, autonomy, inclusion, and safety should be treated as performance outcomes.

A digital dashboard can make performance visible, but visibility alone does not create improvement. Data must be accurate, timely, interpretable, and connected to a response process. Cybersecurity is also part of operational reliability: a connected factory can be disrupted by unauthorized access, ransomware, or compromised sensor data.

11. Integrated Transformation Roadmap

An enterprise can organize transformation into six overlapping phases:

Phase 1: Establish purpose and baseline

Define customer value, business purpose, safety commitments, environmental boundaries, and the current condition. Identify major value streams and critical risks.

Phase 2: Build leadership alignment

Select a small number of breakthrough objectives. Conduct catchball with sites, functions, suppliers, and employee representatives. Define measures and resource requirements.

Phase 3: Stabilize and learn

Improve safety, quality, standard work, equipment reliability, data integrity, and problem visibility. Do not scale unstable processes merely because a pilot appears successful.

Phase 4: Improve end-to-end flow

Coordinate production, logistics, engineering, procurement, and customer service. Use value-stream analysis to address systemic constraints rather than isolated departmental targets.

Phase 5: Scale capabilities and technology

Develop internal coaches, standardize management routines, and introduce digital tools where they solve a defined problem. Evaluate environmental and human consequences before deployment.

Phase 6: Institutionalize and renew

Audit the operating system, verify benefits, review strategic assumptions, and update the hoshin cycle. Mature organizations treat renewal—not the completion of a project—as the normal condition.

Illustrative Case: Northstar Components

Background

Northstar Components, a fictional manufacturer of precision brackets, supplied automotive and industrial customers from one plant. It had introduced 5S, visual boards, and several kaizen events. Despite local improvements, on-time delivery remained at 82%, finished-goods inventory was rising, and employees reported that improvement activities were disconnected from daily priorities.

Problem and analysis

A cross-functional team mapped the order-to-delivery value stream. It found frequent schedule changes, long changeovers, supplier variation, and departmental targets that encouraged large batches. Quality defects were low at final inspection but high in rework hours. The maturity assessment showed relatively strong workplace organization but weak strategic alignment, problem-solving capability, and supplier integration.

The leadership team selected two breakthrough objectives: improve dependable customer delivery and reduce material and energy losses per saleable unit. Through catchball, production proposed a mixed-model pilot, engineering proposed fixture standardization, procurement proposed supplier development, and employees requested training in first-response problem solving.

Approach

The portfolio board prioritized four linked initiatives rather than twelve independent projects:

  1. stabilize the highest-risk stamping process;
  2. reduce changeover through internal/external activity separation;
  3. redesign scheduling around demand and constraint visibility;
  4. establish supplier quality and delivery reviews.

Environmental measures were added to the project charters. The plant also introduced layered process audits and a benefit review at 30, 90, and 180 days after implementation.

Outcome

After nine months, the pilot value stream achieved 95% on-time delivery, reduced average changeover time, and lowered rework. Inventory declined, but the plant retained a defined protective buffer for a critical imported component. Energy intensity improved because fewer defective parts were processed. The most important result was not a single metric: supervisors began using daily abnormality management and operators participated in countermeasure design.

The plant did not immediately replicate the model everywhere. It first tested whether the causes and controls were comparable. This prevented the common error of copying a local solution without understanding its conditions.

Learning points

The case illustrates that strategy deployment connects improvement work to enterprise outcomes; catchball improves feasibility and ownership; portfolio governance prevents fragmentation; environmental and resilience criteria reveal trade-offs; and sustainment requires audits, ownership, and repeated learning.

Challenges and Limitations

Lean transformation can fail when leaders treat it as a cost-cutting program, when targets are excessive, or when employees fear that improvement will eliminate their jobs. It can also fail through tool worship, inadequate process stability, poor data, weak middle-management capability, or excessive reliance on consultants.

Maturity models may encourage score chasing. Weighted project rankings may hide ethical or safety obligations. Digital systems can automate a bad process and intensify surveillance. Green initiatives may shift rather than reduce environmental burden. Circular models may be uneconomic without appropriate product design and reverse logistics. Resilience investments may appear inefficient during stable periods even though they protect the enterprise against severe disruption.

Responsible governance requires transparent assumptions, worker participation, data protection, fair treatment, regulatory compliance, and honest communication about benefits and trade-offs. Transformation should improve the capability and dignity of work, not merely increase the speed of extraction from people and resources.

Best-Practice Checklist

  • Link every major initiative to customer, strategic, safety, environmental, or resilience needs.
  • Use catchball to test feasibility and expose interdependencies.
  • Limit breakthrough objectives and make ownership explicit.
  • Assess maturity through multiple evidence sources.
  • Govern initiatives as a portfolio, not as disconnected projects.
  • Define benefit measurement before implementation.
  • Audit actual practices at the workplace.
  • Distinguish specifications, control limits, targets, and financial benefits.
  • Preserve risk-based buffers where they protect continuity.
  • Use technology to augment people and strengthen problem solving.
  • Include lifecycle environmental impacts and circular opportunities.
  • Review, learn, and renew the transformation system continuously.

Chapter Summary

Enterprise lean transformation is a strategic management system rather than a collection of isolated tools. Hoshin kanri aligns long-term purpose, breakthrough objectives, annual targets, and improvement initiatives. Catchball makes deployment two-way by combining strategic ambition with operational knowledge. Maturity assessment helps identify capability gaps, but scores must be interpreted as evidence rather than treated as goals.

Portfolio governance coordinates resources, dependencies, risk, and benefit expectations. Audits should verify real process conditions and generate learning. Benefit sustainment requires ownership, standard work, leader routines, training, reaction plans, and post-project verification. Future-oriented lean strategy must integrate environmental performance, circularity, customization, resilience, and human-centered digital technology. The central principle is that operational excellence is sustainable only when it improves value for customers while developing people, protecting the environment, and strengthening the enterprise’s capacity to adapt.

Key Terms

Hoshin kanri: A method for deploying strategic priorities through coordinated objectives, measures, and improvement work.

Catchball: Two-way negotiation and learning between organizational levels during strategy deployment.

True north: The organization’s long-term purpose and desired direction.

Breakthrough objective: A major strategic change requiring coordinated effort over an extended period.

Lean transformation: Enterprise-wide change in strategy, processes, behaviors, capabilities, and management systems.

Maturity assessment: A structured evaluation of an organization’s capability in defined dimensions.

Portfolio governance: The system for selecting, prioritizing, funding, monitoring, and terminating initiatives.

Benefit realization: The process of confirming that intended operational or financial improvements actually occur.

Layered process audit: Auditing of process conditions by different organizational levels and at planned frequencies.

Green lean: Integration of lean improvement with environmental performance objectives.

Circular manufacturing: Production designed to preserve product, component, and material value across lifecycles.

Mass customization: Delivery of varied or individualized products with near mass-production efficiency.

Resilience: The ability to withstand disruption, recover acceptable performance, and learn from disturbance.

Industry 5.0: A human-centered, sustainable, and resilient development of advanced industrial systems.

Leader standard work: Defined management routines that support observation, coaching, escalation, and learning.

Value stream: The connected activities required to deliver a product or service to a customer.

Postponement: Delaying final product differentiation until demand information is more certain.

Control plan: A documented specification of what is monitored, how, by whom, and what response follows abnormality.

Psychological safety: A condition in which people can raise problems, questions, or concerns without fear of humiliation or retaliation.

Review Questions

Short Answer Questions

  1. What is the purpose of hoshin kanri?
  2. How does catchball differ from one-way target cascading?
  3. Why should maturity scores not be treated as transformation objectives?
  4. Name four mechanisms that help sustain lean benefits.
  5. What are the three central themes associated with Industry 5.0?

Long Answer Questions

  1. Explain how an enterprise can use hoshin kanri to connect strategic priorities with daily management.
  2. Discuss the role of portfolio governance in preventing local optimization and initiative overload.
  3. Compare green lean and circular manufacturing, including their different boundaries and challenges.
  4. Explain how lean systems can support resilience without removing all buffers.
  5. Evaluate the ethical and operational implications of human-centric digital transformation.

Analytical / Application Questions

  1. A plant has strong 5S scores but poor delivery reliability and weak problem-solving capability. Design a maturity-assessment follow-up and propose two hoshin objectives.
  2. An improvement project reduces inventory but increases expedited transport. Analyze the trade-off and recommend measures for an integrated decision.
  3. Develop a governance outline for a portfolio containing a changeover project, a supplier-resilience project, a collaborative-robot project, and a circular-product redesign project. Identify selection criteria, gates, owners, and sustainment reviews.

Multiple Choice Questions with Answers

Question 1

What is the primary purpose of hoshin kanri?

A. To replace all local improvement activities

B. To align strategic priorities with coordinated organizational action

C. To calculate equipment depreciation

D. To eliminate the need for performance measures

Correct Answer: B. To align strategic priorities with coordinated organizational action

Question 2

Catchball is best described as:

A. A one-way cascade of executive instructions

B. A method for ranking suppliers by price

C. Two-way dialogue to test and refine objectives and methods

D. A statistical sampling technique

Correct Answer: C. Two-way dialogue to test and refine objectives and methods

Question 3

Which item should normally be treated as a governance gate rather than traded freely in a weighted project score?

A. Safety or legal compliance

B. Office layout preference

C. Presentation quality

D. Meeting duration

Correct Answer: A. Safety or legal compliance

Question 4

A benefit audit primarily verifies whether:

A. A project team held enough meetings

B. A claimed improvement remains real after implementation

C. All employees received identical bonuses

D. The project used the newest software

Correct Answer: B. A claimed improvement remains real after implementation

Question 5

Which statement correctly distinguishes control limits from specifications?

A. Control limits describe process behavior; specifications describe acceptable requirements

B. Specifications describe process behavior; control limits are customer wishes

C. They are identical in every application

D. Neither requires a measurement basis

Correct Answer: A. Control limits describe process behavior; specifications describe acceptable requirements

Question 6

Green lean is concerned principally with:

A. Adding inventory to every process

B. Integrating waste reduction with environmental performance

C. Replacing all workers with robots

D. Maximizing product variety regardless of impact

Correct Answer: B. Integrating waste reduction with environmental performance

Question 7

Which practice most directly supports mass customization?

A. Large fixed batches of finished goods

B. Late customization and modular product design

C. Eliminating configuration control

D. Removing operator training

Correct Answer: B. Late customization and modular product design

Question 8

Why might a resilient lean system retain a buffer?

A. Because all inventory is automatically valuable

B. To protect against a justified critical risk or disruption

C. To conceal unstable processes permanently

D. To prevent customer responsiveness

Correct Answer: B. To protect against a justified critical risk or disruption

Question 9

Industry 5.0 places particular emphasis on:

A. Human-centricity, sustainability, and resilience

B. Maximum automation without human involvement

C. Removing cybersecurity controls

D. Measuring only machine speed

Correct Answer: A. Human-centricity, sustainability, and resilience

Question 10

If six maturity dimensions are rated 3, 4, 2, 5, 3, and 1 on an equal-weight scale, what is the average score?

A. 2.5

B. 3.0

C. 3.5

D. 4.0

Correct Answer: B. 3.0

Lean Manufacturing
Chapter 15 of 15