15. Enterprise Application and Operational Excellence Capstone

Introduction and Context

Operational excellence is not achieved by improving isolated processes, installing a dashboard, or conducting a short improvement event. It is achieved when an organisation consistently converts customer requirements into reliable value through capable processes, disciplined management, effective leadership, and financially sound decisions. The enterprise application of Lean Manufacturing therefore requires more than knowledge of individual tools such as value-stream mapping, 5S, kanban, standard work, statistical process control, or total productive maintenance. It requires the ability to integrate operational evidence, financial evidence, strategic priorities, human considerations, risk management, and governance into one coherent improvement programme.

This chapter serves as a capstone for Lean Manufacturing and Operational Excellence. It presents an end-to-end method for diagnosing an enterprise, benchmarking its performance, designing a future state, quantifying benefits, evaluating risks and stakeholder effects, and establishing a governed implementation and control system. The method can be applied to a real organisation, a plant-level problem, or a simulated case.

A capstone analysis should not begin with the question, “Which Lean tool should be used?” It should begin with questions such as: What value does the customer expect? Where is value delayed, distorted, or destroyed? Which operational conditions create financial consequences? What evidence supports the diagnosis? What future state is strategically desirable and operationally feasible? How will the organisation know that improvement has been sustained?

The central idea is that operational excellence is a system of mutually reinforcing capabilities. Flow improvement without quality control may increase the speed of producing defects. Cost reduction without regard to reliability may increase downtime and customer dissatisfaction. Automation without process stability may make waste more expensive. A credible capstone therefore links diagnosis, design, economics, implementation, people, and control.

Learning Objectives

After completing this chapter, students should be able to:

1. Conduct an enterprise-level diagnostic using operational, customer, and financial evidence.

2. Distinguish symptoms from root causes and construct an evidence-based problem statement.

3. Benchmark performance using appropriate internal, external, and target comparisons.

4. Design a future-state operating model that integrates Lean principles and business strategy.

5. Quantify benefits, investment requirements, payback, and sensitivity to assumptions.

6. Assess implementation risks, stakeholder impacts, ethical concerns, and organisational readiness.

7. Develop a governed implementation roadmap with ownership, decision gates, and control measures.

8. Present a defensible operational excellence proposal to senior management.

From Local Improvement to Enterprise Performance

A local process is embedded in a larger system. A machining cell may improve its cycle time, yet the factory may experience no improvement in customer delivery because finished goods remain in a constrained inspection area. A purchasing department may obtain a lower unit price while larger order quantities increase inventory and obsolescence. These examples illustrate the difference between local efficiency and enterprise effectiveness.

Lean thinking defines value from the customer’s perspective and seeks to establish smooth, demand-driven flow with minimal waste. Operational excellence extends this logic by asking whether the entire management system reliably produces the intended business outcomes. These outcomes may include on-time delivery, first-pass yield, cash conversion, asset productivity, employee safety, regulatory compliance, and profitable growth.

An enterprise capstone should examine at least five interrelated dimensions:

• Customer and market performance: delivery reliability, lead time, responsiveness, quality, and customer experience.
• Process performance: flow, capacity, variation, bottlenecks, changeovers, defects, downtime, and work-in-process.
• Financial performance: revenue at risk, cost of poor quality, labour productivity, inventory investment, working capital, and return on improvement investment.
• People and organisation: skills, leadership behaviour, decision rights, engagement, workload, and readiness for change.
• Governance and risk: compliance, safety, cybersecurity where relevant, resilience, escalation, and control of benefits.

The five dimensions should not be treated as separate chapters of an investigation. Their relationships are the substance of the diagnosis. For example, unstable equipment may create schedule changes, which increase overtime, expedite fees, inventory buffers, employee fatigue, and customer complaints. A high-quality analysis traces this chain rather than reporting each measure independently.

Building an Evidence-Based Diagnostic

Framing the business problem

A useful problem statement specifies the process, population, period, performance gap, consequence, and strategic importance. “Production is inefficient” is too vague. A stronger statement might be: “During the last two quarters, the assembly family achieved 78 percent on-time shipment against a 95 percent requirement; schedule changes and premium freight increased, while work-in-process rose by 31 percent. The principal business concern is unreliable customer fulfilment rather than isolated labour utilisation.”

The statement should identify what is known and what remains uncertain. Early assumptions must be labelled as hypotheses. This prevents the project team from presenting opinions as facts and encourages targeted data collection.

Selecting and validating evidence

Operational evidence may include demand history, production schedules, standard times, actual cycle times, queue time, downtime records, changeover duration, scrap, rework, first-pass yield, inventory levels, supplier performance, and customer complaints. Financial evidence may include material cost, conversion cost, overtime, premium freight, inventory carrying cost, warranty cost, lost contribution margin, and cash tied up in stock.

Data should be tested for definition, completeness, consistency, timing, and ownership. A reported “utilisation” figure may include planned downtime in one department and exclude it in another. A defect percentage may use units as its denominator in one report and opportunities as its denominator in another. Before calculating conclusions, the analyst should define the measure, source, period, frequency, and responsible owner.

A practical evidence register records the claim being tested, the required data, its source, quality concerns, and the decision affected by the result. Direct observation, interviews, system records, and transaction-level analysis should be triangulated. No single source is automatically authoritative.

Seeing the system

A current-state value-stream map provides a useful high-level view of material and information flow, but an enterprise diagnostic often requires additional views. A process map clarifies activities and decision points; a spaghetti diagram reveals movement; a swim-lane map shows hand-offs; a capacity analysis identifies constraints; and a cost-of-quality analysis translates defects into economic consequences.

A useful analytical sequence is:

1. Define the customer requirement and product or service family.

2. Map the end-to-end flow from demand signal to delivery.

3. Measure process time, queue time, variation, quality, and capacity.

4. Locate the constraint and the points at which information or material is delayed.

5. Link operational losses to financial and customer consequences.

6. Test root-cause hypotheses using stratification, observation, and targeted analysis.

7. Confirm the diagnosis with process owners and affected stakeholders.

Root-cause analysis should move beyond labels such as “poor discipline” or “operator error.” Five Whys, cause-and-effect diagrams, fault-tree analysis, Pareto analysis, and statistical comparisons may be used, depending on the problem. A root cause is not merely a factor associated with poor performance; it is a controllable condition whose removal or treatment changes the outcome.

Measures, Benchmarks, and Interpretation

A balanced performance architecture prevents overreliance on one metric. Typical measures include:

• Lead time: elapsed time from customer order or demand signal to delivery.
• Process cycle efficiency: value-adding process time divided by total elapsed lead time.
• Overall equipment effectiveness: a combined view of availability, performance, and quality; it is useful only when its components and losses are defined consistently.
• First-pass yield: the proportion of units completing a process without rework.
• On-time-in-full delivery: the extent to which the customer receives the correct order when promised.
• Inventory turns: the relationship between annual consumption or cost of goods sold and average inventory.
• Cost of poor quality: internal and external failure costs, including scrap, rework, returns, complaints, and warranty consequences.
• Schedule adherence: actual production compared with the agreed production plan.
• Safety and people measures: incidents, near misses, training completion, absenteeism, and improvement participation.

Benchmarking involves comparison against a reference. Internal benchmarking compares plants, lines, shifts, or products. External benchmarking compares competitors, industry data, or recognised performance standards. Target benchmarking compares current performance with a strategically required future level. Benchmarking is meaningful only when context is considered: product mix, technology, demand volatility, regulatory requirements, and accounting conventions may differ.

A benchmark should prompt inquiry, not imitation. A plant with lower labour cost may have higher automation investment, different product complexity, or hidden quality costs. Managers should distinguish a performance gap from an opportunity gap. The first describes what is observed; the second estimates what may be attainable after considering capability, investment, and constraints.

Designing the Future State

The future state should describe how the organisation will operate, not merely list improvement projects. It should answer five questions: How will demand be translated into production? How will work flow? How will quality be assured? How will abnormal conditions be managed? How will leaders know whether the system is healthy?

Future-state design commonly incorporates the following principles:

• Establish a clear pacemaker process linked to customer demand.
• Reduce batch size and create controlled flow where product and process conditions permit.
• Use pull signals and defined replenishment rules rather than uncoordinated production.
• Separate normal work from abnormal response and make abnormalities visible.
• Build quality into the process through error-proofing, standard work, and rapid containment.
• Reduce changeover time so that the system can respond economically to demand variation.
• Protect the constraint and align upstream and downstream release with its capacity.
• Develop people capable of operating, improving, and sustaining the new system.

A future-state map must be tested against capacity and economics. If takt time is derived from available time divided by customer demand, the calculation must account for breaks, planned maintenance, changeovers, and realistic utilisation. A line designed to meet takt under ideal conditions may fail in practice. Similarly, a kanban quantity should reflect demand, replenishment time, container size, and an explicitly justified safety factor; it should not be selected solely because it resembles another department’s practice.

Scenario analysis is valuable when demand, mix, or supplier performance is uncertain. At minimum, the design should be tested under expected, high-demand, low-demand, and disruption conditions. The future state may need alternative modes, such as a normal flow mode and a controlled surge mode.

Quantifying the Business Case

Operational improvement becomes an executive decision when its consequences are expressed in financial and strategic terms. The business case should distinguish hard savings, cost avoidance, capacity release, working-capital reduction, revenue protection, and intangible benefits. These categories should not be combined without explanation.

A simplified annual benefit model may be expressed as:

Net annual benefit = labour benefit + material benefit + quality benefit + logistics benefit + capacity or revenue benefit − recurring implementation cost.

Working-capital release can be estimated by comparing current and future inventory at an agreed valuation basis. However, inventory reduction is not automatically a cash benefit. It becomes cash only when purchasing, production, or financing requirements actually fall. Likewise, released labour capacity is not a labour saving unless staffing or overtime changes; otherwise it may support additional output or resilience.

Common investment measures include:

• Payback period: initial investment divided by expected periodic net cash benefit.
• Return on investment: net benefit divided by investment, using clearly stated time boundaries.
• Net present value: discounted value of future cash flows less initial investment.
• Sensitivity analysis: examination of outcomes when key assumptions change.

A credible business case states assumptions, ownership, timing, and confidence level. It should show optimistic, expected, and conservative scenarios where uncertainty is material. Double counting must be avoided. For example, the same defect reduction should not be counted separately as both full labour saving and full capacity release unless the organisation can realise both.

Governance, Stakeholders, and Change

Operational excellence programmes alter routines, authority, measures, and sometimes jobs. Stakeholder analysis should therefore begin before implementation. Operators may fear job loss or increased surveillance; supervisors may perceive standard work as a challenge to autonomy; finance may question benefit calculations; maintenance may resist production targets that undermine equipment care; customers may be affected by trials or changed delivery patterns.

A stakeholder assessment considers influence, impact, concerns, desired behaviour, and engagement method. Participation is not merely a communication exercise. People who perform the work often possess essential knowledge about variation, workarounds, safety, and failure modes. Excluding them creates technical and ethical risk.

Governance defines who sponsors the programme, who owns each benefit, who approves changes, who resolves cross-functional conflicts, and how escalation occurs. A steering committee may review strategic alignment, investment, risk, and benefit realisation. A project team manages design and implementation. Process owners remain accountable after project closure. A RACI matrix can clarify responsibility, but it should not replace active leadership.

Ethical governance requires accurate reporting of benefits, respect for worker safety and dignity, protection of confidential information, and avoidance of targets that encourage unsafe or deceptive behaviour. Productivity measures should not reward bypassing quality checks or suppressing incident reporting. If digital monitoring is introduced, its purpose, access rules, retention, and appropriate use should be transparent and compliant with applicable law and organisational policy.

The Implementation and Control Architecture

A capstone proposal should convert the future state into a sequence of manageable releases. A typical roadmap includes stabilisation, pilot, scale-up, and institutionalisation. Stabilisation may address safety, data integrity, standard work, equipment condition, and immediate bottlenecks. The pilot tests the future-state design in a bounded area. Scale-up extends proven practices while adapting them to local conditions. Institutionalisation embeds ownership, audits, training, budgeting, and management routines.

Each initiative should have a charter containing its objective, scope, baseline, target, owner, resources, dependencies, risks, and benefit logic. Decision gates should be used to determine whether to continue, modify, pause, or stop. A project that fails to demonstrate process capability or safe operation should not be scaled merely because money has already been spent.

Control plans translate improvement into daily management. They specify the critical process measures, target and warning limits, data frequency, responsible role, reaction plan, and escalation path. Visual management is effective when it supports decisions rather than displaying excessive data. A board showing output but not quality, abnormality, or action ownership may create the appearance of control without control itself.

Management standard work may include daily tier meetings, leader process confirmation, review of abnormalities, coaching, layered audits, and periodic benefit verification. Control charts or other statistical methods are appropriate where the underlying data and process assumptions support them. Audit questions should test whether the process is capable and understood, not whether forms have been completed.

Illustrative Capstone Case: Meridian Components

Background

Meridian Components is an illustrative manufacturer of precision brackets supplied to industrial equipment producers. Its plant operates machining, surface treatment, inspection, and assembly processes. Demand is moderately variable, and customers increasingly require shorter and more reliable delivery. The plant has invested in modern equipment but continues to experience late shipments and high inventory.

Situation and problem

Management reports 82 percent on-time-in-full delivery against a target of 96 percent. Average order-to-ship lead time is 18 days, although processing time is estimated at less than one day. Work-in-process has increased, overtime is common, and premium freight is used during month-end recovery. First-pass yield in assembly is 91 percent. The plant’s overall equipment effectiveness report shows 74 percent in machining, but the reliability of this figure is questioned because downtime codes are inconsistently used.

The initial project statement is: “Meridian must improve delivery reliability and reduce lead time without compromising safety, quality, or financial performance.” The project team includes production, quality, maintenance, supply chain, finance, engineering, and operator representatives.

Analysis

A current-state map reveals that batches are released according to departmental schedules rather than customer demand. Machining runs large batches to maximise apparent utilisation, creating queues before surface treatment. Inspection is performed in batches twice daily, and defects discovered there return to machining or assembly. Changeovers average 68 minutes, but observation shows substantial searching and first-piece approval delay. Interviews also reveal that supervisors frequently alter priorities because the schedule does not reflect actual constraint capacity.

Data stratification identifies three major contributors to late orders: waiting for surface treatment slots, rework from assembly defects, and schedule changes caused by unplanned machining downtime. Financial analysis estimates that premium freight, overtime, scrap, and rework are significant recurring losses. Finance confirms that a reduction in inventory would improve cash only if release quantities and purchasing policies were changed; therefore, inventory benefit is classified separately from immediate cost saving.

The team validates three root causes: the absence of a demand-linked pacemaker and release rule, unstable changeovers and equipment availability at the machining constraint, and late detection of assembly defects. “Low operator commitment” is rejected as a root cause because operators had repeatedly identified these conditions but lacked authority and support to correct them.

Future-state approach

The proposed design establishes machining as the pacemaker because it constrains total flow. A heijunka-informed sequence is created for the principal product family, with a finite release schedule tied to available constraint capacity. A supermarket is positioned between machining and surface treatment with defined minimum and maximum levels. Assembly receives smaller, more frequent deliveries after quality is confirmed at source.

The first improvement package separates internal and external changeover activities, prepares tools before the change, and introduces a first-piece approval standard. Maintenance establishes a focused preventive and condition-based routine for the constraint equipment. Assembly introduces error-proofing for the two most frequent defect modes and moves selected checks closer to the point of work. A daily tier meeting reviews safety, quality, delivery, cost, and people measures, with abnormality escalation within the same shift.

Business case and risk assessment

The business case includes expected reductions in overtime, premium freight, scrap, and rework; it also identifies capacity released by shorter changeovers. The team does not claim all released capacity as immediate labour savings. A conservative scenario assumes only a portion will produce additional saleable output during the first year. Investment is required for fixtures, training, maintenance support, and limited digital scheduling capability.

Key risks include overloading the pacemaker during demand peaks, using supermarket stock as a substitute for root-cause action, inaccurate downtime data, and resistance to changed supervisory routines. Mitigations include surge rules, replenishment limits, data validation, operator involvement, and a formal review after the pilot. Safety review is required before any layout or material-handling change.

Outcome and control plan

In the illustrative pilot, one product family is selected rather than the entire plant. Success criteria include improved schedule adherence, reduced changeover time, stable first-pass yield, lower queue time, and no adverse safety outcome. The pilot is governed by weekly steering reviews and daily team management. Benefits are verified by finance after the agreed measurement period. The design is scaled only when process performance is stable and owners are trained.

The case demonstrates that the most important intervention is not a single tool. It is the alignment of demand, constraint management, quality at source, maintenance, financial logic, and management behaviour. The future state is credible because it specifies operating rules, not just aspirations.

Common Failure Modes and Limitations

Capstone projects fail when teams begin with a fashionable solution, collect only convenient data, or confuse activity with progress. Other common failures include treating OEE as a universal productivity target, reducing inventory without stabilising replenishment, copying another plant’s benchmark, and declaring savings before benefits are realised.

A second limitation is model uncertainty. Forecasts, cost assumptions, and capacity estimates may be wrong. Sensitivity analysis and staged investment reduce exposure but do not eliminate it. A third limitation is organisational fatigue. Too many simultaneous initiatives can overload supervisors and operators, causing superficial compliance. Portfolio governance is therefore necessary.

Lean methods also have boundaries. They cannot compensate indefinitely for fundamentally uncompetitive product design, unreliable suppliers, inadequate technology, or an unsafe work system. In some environments, high variability, low volume, strict traceability, or regulatory requirements require hybrid solutions rather than a literal application of repetitive-flow methods.

Digital Applications and Emerging Developments

Digital tools can strengthen an operational excellence system when they improve visibility, decision speed, and learning. Manufacturing execution systems can connect orders, operations, quality records, and traceability. Sensors can support condition monitoring; process-mining tools can reveal actual transaction paths; advanced analytics can identify patterns in downtime or defects; and simulation can test alternative layouts, buffers, or release policies before physical change.

Artificial intelligence may assist with anomaly detection, demand analysis, maintenance prediction, and knowledge retrieval. However, predictive accuracy does not guarantee operational value. Data quality, explainability, cybersecurity, model drift, access rights, and human decision authority must be addressed. An algorithm that recommends production priorities without considering safety, customer commitments, or constraint logic can amplify system problems.

The emerging direction is the integration of Lean management with digital operating systems. The principle remains unchanged: technology should make value flow, abnormalities, and learning more visible. Digital complexity that creates more reports but no better decisions is not operational excellence.

Best-Practice Principles for the Capstone Presentation

A professional capstone presentation should tell a decision story. It should begin with the customer and business problem, show the evidence and diagnosis, explain the future state, quantify the economics, disclose assumptions and risks, and finish with governance and control. Charts should show trends, distributions, constraints, and relationships rather than merely display large quantities of data.

The presenter should distinguish fact, inference, and proposal. Every target should have a baseline and an owner. Financial claims should be reconciled with finance. Risks should include both probability and consequence, together with a practical response. The recommendation should make clear what management must decide, by when, with what resources, and under what conditions the proposal will be reconsidered.

Chapter Summary

Enterprise application of Lean Manufacturing requires an integrated diagnosis of customer performance, process behaviour, financial consequences, people, and risk. The capstone begins with a precise problem statement and validated evidence. Current-state mapping, operational measures, root-cause analysis, and benchmarking reveal where value is delayed or destroyed. Future-state design then aligns demand, flow, quality, capacity, maintenance, and management routines.

A financially credible proposal distinguishes realised savings, cost avoidance, capacity release, working-capital effects, and revenue protection. It tests assumptions through sensitivity analysis and avoids double counting. Implementation depends on stakeholder involvement, ethical governance, clear ownership, staged decision gates, and a control architecture that sustains performance after the project team leaves. Digital tools can strengthen this system, but they cannot replace process understanding or responsible leadership. The capstone is successful when it converts Lean principles into a governed, measurable, and strategically relevant operating system.

Key Terms

Operational excellence: An organisational capability to deliver customer and business outcomes through reliable, efficient, continuously improving processes.

Enterprise diagnostic: A structured examination of performance across processes, functions, finances, people, and risks.

Value-stream map: A visual representation of material and information flow from demand to delivery.

Pacemaker process: The process that sets the rhythm and sequencing for the broader value stream.

Constraint: A factor that limits the capacity or performance of a system.

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

Process cycle efficiency: Value-adding time divided by total elapsed lead time.

First-pass yield: The proportion of units completed correctly without rework.

On-time-in-full: A delivery measure combining promised timing and order completeness.

Cost of poor quality: Costs arising from defects, rework, scrap, returns, complaints, and related failures.

Benchmarking: Systematic comparison of performance with an internal, external, or target reference.

Future-state design: A planned description of how a process or enterprise should operate after improvement.

Benefit realisation: The process of verifying that planned improvements produce intended operational or financial outcomes.

Control plan: A documented arrangement of measures, owners, limits, and reaction actions used to sustain process performance.

Management standard work: Defined leadership routines for observing processes, responding to abnormalities, and supporting improvement.

Stakeholder analysis: Assessment of groups affected by or able to influence an initiative, including their concerns and required engagement.

Decision gate: A formal review point at which continuation, modification, or termination of an initiative is decided.

Sensitivity analysis: Examination of how changes in assumptions affect a projected result.

Process capability: The demonstrated ability of a stable process to meet specified requirements.

Review Questions

Short Answer Questions

1. Why must an enterprise Lean diagnostic combine operational and financial evidence?

2. What characteristics make a problem statement useful for a capstone project?

3. Define process cycle efficiency and explain what it reveals.

4. Why should released capacity not automatically be reported as labour saving?

5. What information should a control plan contain?

Long Answer Questions

1. Explain an end-to-end method for diagnosing an enterprise value stream, from problem framing to root-cause validation.

2. Discuss how a future-state design should integrate demand, flow, quality, maintenance, capacity, and management routines.

3. Explain the role of benchmarking in operational excellence and identify its principal limitations.

4. Describe how a Lean improvement business case should classify and quantify benefits.

5. Discuss the governance and stakeholder requirements for sustaining an enterprise operational excellence programme.

Analytical / Application Questions

1. A plant reports high equipment utilisation, increasing inventory, and declining on-time delivery. Using the frameworks in this chapter, determine what additional evidence should be collected and propose a diagnostic sequence.

2. A proposed automation project promises a 20 percent labour reduction but provides no evidence of process stability, quality improvement, or demand growth. Critically evaluate the proposal and specify the analyses and governance conditions required before approval.

3. Design a pilot and control plan for a product family experiencing long changeovers, high rework, and frequent schedule changes. Include measures, ownership, decision gates, risks, and benefit-verification rules.

22. Multiple Choice Questions with Answers

Question 1

Which statement best describes the purpose of an enterprise operational excellence capstone?

A. To select the largest possible number of Lean tools for immediate deployment

B. To connect operational evidence, financial consequences, future-state design, implementation, and control

C. To maximise local utilisation regardless of customer performance

D. To replace managerial judgement with automated dashboards

Correct Answer: B. To connect operational evidence, financial consequences, future-state design, implementation, and control

Question 2

Which problem statement is most suitable for an enterprise diagnostic?

A. The factory is inefficient

B. Employees need to work harder

C. On-time delivery has remained below the required level, with identifiable lead-time and quality consequences during a defined period

D. Lean practices should be introduced everywhere

Correct Answer: C. On-time delivery has remained below the required level, with identifiable lead-time and quality consequences during a defined period

Question 3

Why should a benchmark not be copied without contextual analysis?

A. Benchmarks are never useful

B. Different products, technologies, demand patterns, and accounting definitions may affect performance

C. Internal data is always superior to external data

D. Benchmarking applies only to financial measures

Correct Answer: B. Different products, technologies, demand patterns, and accounting definitions may affect performance

Question 4

In future-state design, the pacemaker process primarily:

A. Determines the rhythm and sequencing of the broader value stream

B. Stores all finished goods before shipment

C. Eliminates the need for maintenance

D. Sets employee compensation levels

Correct Answer: A. Determines the rhythm and sequencing of the broader value stream

Question 5

Which claim illustrates correct treatment of released capacity?

A. All time saved is automatically a labour cost saving

B. Released capacity may support additional output or resilience unless staffing or overtime is actually reduced

C. Capacity release should never be included in a business case

D. Capacity release is identical to inventory reduction

Correct Answer: B. Released capacity may support additional output or resilience unless staffing or overtime is actually reduced

Question 6

What is the main purpose of a decision gate in an improvement roadmap?

A. To ensure that a project continues after investment has begun

B. To provide a formal basis for continuing, modifying, pausing, or stopping an initiative

C. To transfer all accountability to the finance department

D. To replace pilot testing

Correct Answer: B. To provide a formal basis for continuing, modifying, pausing, or stopping an initiative

Question 7

Which response best addresses the ethical risk of productivity targets?

A. Reward output even when safety and quality checks are bypassed

B. Suppress incident reporting to protect performance statistics

C. Design measures so that productivity cannot be improved by unsafe or deceptive behaviour

D. Use only financial measures because they are objective

Correct Answer: C. Design measures so that productivity cannot be improved by unsafe or deceptive behaviour

Question 8

In the Meridian Components case, why was machining treated as the pacemaker?

A. It had the largest physical area

B. It constrained total flow and required demand-linked release and sequencing

C. It was the newest department

D. It had the lowest labour cost

Correct Answer: B. It constrained total flow and required demand-linked release and sequencing

Question 9

Which practice most directly prevents double counting in a Lean business case?

A. Reporting every operational improvement as a separate cash saving

B. Separating labour savings, capacity release, inventory effects, and revenue protection with explicit assumptions

C. Excluding finance from the project team

D. Using only optimistic estimates

Correct Answer: B. Separating labour savings, capacity release, inventory effects, and revenue protection with explicit assumptions

Question 10

What is the most appropriate view of digital tools in operational excellence?

A. They automatically create process capability

B. They should replace process observation and human accountability

C. They are useful when they improve visibility, decisions, and learning while risks and data quality are governed

D. They eliminate the need for standard work

Correct Answer: C. They are useful when they improve visibility, decisions, and learning while risks and data quality are governed