13. Enterprise Deployment, Leadership and Governance

Introduction and Context

Lean Six Sigma is often introduced through process mapping, statistical analysis, waste reduction and variation control. At enterprise level, however, its central challenge is not the availability of tools. The challenge is creating an operating system through which improvement becomes a normal way of managing strategy, work and performance. A successful deployment connects strategic priorities with a disciplined portfolio of improvement projects, develops capable people, allocates resources, verifies benefits and sustains changed processes.

Enterprise deployment therefore differs from a collection of isolated projects. A local project may reduce defects in one process, whereas an enterprise system must decide which problems deserve attention, how improvement capability will be distributed, who owns the results and how financial and strategic consequences will be governed. It must also address the human side of change. Employees may resist because they fear job loss, additional workload, loss of autonomy or exposure of performance problems. Leaders must create conditions in which evidence-based improvement is both expected and safe.

This chapter examines the design and leadership of Lean Six Sigma operating systems. It considers maturity models, belt structures, project selection, portfolio governance, change leadership, coaching, conflict management and the connection between improvement benefits, managerial accounting and strategy execution. The underlying proposition is that Lean Six Sigma becomes strategically valuable when it is integrated with the organization’s management system rather than operated as a separate improvement programme.

Learning Objectives

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

1. Explain the characteristics of an enterprise Lean Six Sigma operating system.

2. Design an appropriate governance structure and belt deployment model.

3. Assess organizational maturity and identify suitable development priorities.

4. Select and prioritize projects using strategic, customer, operational and financial criteria.

5. Establish portfolio controls for resources, risks, benefits and sustainability.

6. Apply leadership, coaching and change-management approaches in improvement work.

7. Diagnose resistance and resolve conflicts among stakeholders.

8. Link project benefits to managerial accounting and strategy execution.

9. Evaluate digital and analytical technologies supporting enterprise deployment.

10. Recognize ethical risks, common deployment failures and emerging developments.

From Improvement Projects to an Operating System

An operating system is the set of routines, roles, information flows, decision rights and performance reviews through which an organization converts purpose into action. In Lean Six Sigma, this system should make improvement visible in everyday management. It includes strategic deployment, project selection, capability development, process ownership, performance review, problem escalation and benefit verification.

A mature operating system has five connected characteristics. First, improvement is linked to organizational purpose and customer requirements. Second, leaders actively sponsor and review improvement rather than delegating it entirely to specialists. Third, projects are selected as a portfolio, not as unrelated requests. Fourth, process owners remain accountable after project closure. Fifth, results are measured through operational and financial indicators and incorporated into normal management routines.

The distinction between a project and a system is important. A project has a defined problem, scope, team, method and completion date. A system determines whether the project should exist, how it competes for resources, how its gains are validated and what learning is transferred to other processes. Without the system, organizations commonly experience project proliferation, weak ownership, duplicated effort, benefits that cannot be verified and temporary improvements that disappear after the team leaves.

Lean Six Sigma deployment is also a matter of organizational design. Centralized deployment can provide consistency, expert support and standard methods. Decentralized deployment can improve responsiveness and local ownership. Most large organizations require a hybrid arrangement: enterprise standards and governance combined with business-unit ownership of problems and results.

Architecture of Enterprise Governance

Governance defines who makes which decisions, using what information, at what frequency and with what accountability. It should enable improvement without creating excessive bureaucracy. A typical governance architecture includes the following roles.

The executive sponsor establishes the strategic direction, removes major barriers and ensures that improvement receives appropriate resources. A deployment or steering council translates strategic priorities into an improvement portfolio and reviews progress, risk and benefits. Business-unit leaders own the performance of their value streams and sponsor projects within their areas. Master Black Belts or deployment leaders develop capability, coach teams and maintain methodological standards. Black Belts lead complex cross-functional projects, while Green Belts lead smaller projects alongside their normal responsibilities. Process owners sustain the redesigned process and monitor control measures. Finance, human resources, information technology, procurement and compliance functions provide specialist support.

Roles should be distinguished from titles. An individual may perform more than one role in a small organization, but accountability must remain explicit. For example, a Black Belt may facilitate a project, but should not become the permanent owner of the process. Similarly, finance may validate the financial effect, but operational management must own the process changes that generate the effect.

Governance forums should have clear purposes. A project review asks whether a specific project has demonstrated a valid problem, sound analysis and sustained results. A portfolio review asks whether the collection of projects is balanced, strategically relevant and adequately resourced. An operating review asks whether process performance is improving and whether problems are being escalated appropriately. Combining all three purposes in one meeting often produces superficial discussion.

A useful governance calendar may include weekly team reviews, monthly project tollgates, quarterly portfolio reviews and periodic maturity assessments. Tollgates are decision points at which a project is approved, redirected, paused or closed. They should not be ceremonial presentations. Evidence at each stage should determine whether further investment is justified.

Capability Architecture and Belt Structures

The belt structure is a capability architecture, not merely a hierarchy of certificates. Its purpose is to place appropriate problem-solving skill close to the work while retaining access to advanced expertise.

Executives and sponsors need enough knowledge to select meaningful projects, ask effective questions and remove organizational barriers. They do not necessarily need advanced statistical training. Yellow Belts or equivalent participants usually understand basic Lean Six Sigma concepts and support local improvement. Green Belts lead bounded projects, often part-time, using process analysis, basic data methods and structured problem solving. Black Belts lead complex or cross-functional projects and coach Green Belts. Master Black Belts develop methods, coach leaders and teams, manage difficult analyses and support deployment design.

A belt model fails when certification becomes the objective. Training completion is an input to capability, not proof of business value. Certification should normally require evidence of application, such as a completed project, verified results, demonstrated use of appropriate methods and an effective control plan. Competence includes facilitation, communication, ethical judgment and the ability to work with process owners, not only statistical technique.

Deployment leaders must determine the right balance between dedicated and part-time roles. Dedicated Black Belts are appropriate where the organization has a substantial portfolio of complex work. Part-time Green Belts can be effective for localized improvements but may struggle when operational priorities are intense. If managers assign projects without protecting time, the programme creates hidden overload and unreliable completion.

Capability development should be staged. Initial training should be followed by coaching during project execution, peer learning, communities of practice and periodic assessment of actual application. The organization should track not only the number of trained people but also project cycle time, benefit realization, sustainability, quality of problem definitions and the spread of improvement practices.

Assessing Maturity and Choosing the Next Step

A maturity model helps leaders distinguish between current capability and desired capability. It should be used as a diagnostic device, not as a label for ranking departments. A practical five-level model is as follows:

At the reactive level, improvement is driven by crises, individual effort and informal problem solving. Data may be incomplete and solutions are often implemented before causes are understood. At the developing level, selected teams use standard methods, but sponsorship and process ownership are inconsistent. At the managed level, projects are linked to priorities, tollgates are used and benefits are reviewed. At the integrated level, Lean Six Sigma is embedded in strategy deployment, daily management and cross-functional process ownership. At the adaptive level, the organization continuously learns, rapidly reallocates improvement capacity and combines Lean Six Sigma with digital, innovation and organizational-development practices.

Assessment should examine several dimensions: leadership behavior, strategic alignment, project selection, process ownership, data capability, training, benefit management, change leadership, daily management and sustainability. A high score in training with a low score in process ownership indicates that more courses are unlikely to solve the main problem. The appropriate intervention may instead be clarification of accountability and integration with performance reviews.

Maturity is not uniform across an enterprise. A regulated production site may have strong control discipline, while a service function may have stronger customer analytics but weaker process definition. Consequently, deployment should be differentiated. The goal is not to make every unit identical but to establish minimum governance standards and develop capability where it creates the greatest strategic value.

Selecting Projects as a Strategic Portfolio

Project selection is one of the most consequential leadership decisions in Lean Six Sigma. A technically elegant project can be strategically irrelevant, while a strategically important issue can fail if its scope or ownership is poorly defined.

Project opportunities may arise from strategic objectives, customer complaints, audit findings, cost trends, employee suggestions, process-performance data, risk assessments or technology changes. The initial opportunity should be expressed in terms of a measurable performance gap, affected customers or stakeholders, business consequences and an accountable process owner. Statements such as “improve communication” are inadequate unless converted into measurable conditions, such as reducing order-status inquiries or preventing incomplete handoffs.

A project-selection framework should consider at least:

• strategic contribution and alignment with policy deployment;
• customer or stakeholder impact;
• financial or capacity opportunity;
• risk reduction and regulatory significance;
• feasibility, data availability and scope clarity;
• urgency and interdependence with other initiatives;
• readiness of the sponsor, process owner and team.

A weighted scoring model can support comparison. For example, a steering council may assign weights to strategic alignment, customer impact, financial value, risk reduction and feasibility. Each candidate is scored against agreed criteria. The score does not replace judgment; it makes assumptions visible and reduces the influence of personal advocacy.

Portfolio balance is as important as individual ranking. A portfolio may contain short-cycle improvements that release capacity, larger transformational projects, compliance-related work and capability-building initiatives. If every project is high risk and long term, benefits may be delayed. If every project is small and local, strategic transformation may never occur. Leaders must also identify dependencies: a data-standardization project may enable several later projects, and a process redesign may depend on an information-system change.

A project should be rejected, deferred or reframed when the problem is not measurable, the process owner is absent, the proposed solution is already predetermined, the scope is too broad or the expected value is too small relative to effort. Saying “not now” is an important governance function because organizational capacity is limited.

Portfolio Governance and Benefit Realization

Portfolio governance extends beyond approving projects. It manages capacity, sequencing, risk, interdependencies and benefits across the enterprise. A portfolio dashboard should distinguish activity measures from outcome measures. Number of trained belts, meetings held and projects launched are activity measures. Defect reduction, cycle-time improvement, released capacity, customer retention, risk reduction and verified financial benefits are outcome measures.

Benefits should be defined before implementation. A benefit profile normally identifies the baseline, target, measurement formula, timing, owner, financial treatment and assumptions. For example, a reduction in processing time may create additional capacity, but it does not automatically create cash savings. If staffing is unchanged and demand does not increase, the immediate effect may be capacity release rather than a reduction in expenditure.

Managerial accounting is essential for credible benefit claims. Finance and operational leaders should agree on whether a benefit is a hard saving, cost avoidance, revenue enhancement, working-capital improvement, capacity release or nonfinancial value. A hard saving generally affects the budget or actual expenditure. Cost avoidance prevents a forecast increase but may not reduce current spending. Capacity release creates potential for additional volume or redeployment, but its value depends on management action. Nonfinancial benefits may include improved safety, compliance, reliability or customer experience.

Baseline discipline is critical. The baseline should reflect a suitable period and account for seasonality, mix, volume, unusual events and changes in accounting treatment. Benefits should be validated after implementation and monitored during the control period. Double counting occurs when two projects claim the same saving or when a local improvement is counted both as a unit benefit and an enterprise benefit.

Strategy execution requires more than financial measurement. A balanced portfolio links projects to strategic themes such as customer trust, operational resilience, innovation, employee capability or responsible growth. Strategy maps and policy-deployment matrices can show how improvement outcomes support strategic objectives. The connection should be causal and explicit: reducing first-pass errors may improve delivery reliability, which supports customer retention and strategic growth.

Leadership, Change and the Human System

Lean Six Sigma changes how work is designed, measured and managed. It therefore creates emotional and political consequences. Resistance should not be treated automatically as irrationality. It may reveal legitimate concerns about workload, competence, job security, fairness or the practicality of a proposed solution.

Effective leaders establish a compelling case for change without exaggeration. They explain why the current condition matters, what evidence supports action, what will change and what will not change. They involve affected employees in understanding the process and testing solutions. Participation is not a substitute for decision-making, but it improves local knowledge and commitment.

Several leadership behaviors are particularly important. Leaders must model data-based inquiry rather than blame, protect time for improvement, respond quickly to barriers, recognize learning and hold process owners accountable for sustainment. They should ask questions such as: What is the customer requirement? What does the data show? Where is the process owner? What assumption is being tested? How will the gain be sustained?

Coaching differs from directing. A directive leader supplies answers; a coach helps the team frame the problem, examine evidence and develop its own capability. Coaching is especially valuable when teams are tempted to jump to solutions or when interpersonal tensions obscure process facts. The coach must know when to teach, when to question and when to intervene decisively.

Resistance can be addressed through diagnosis. Lack of awareness requires communication; lack of skill requires training and practice; lack of resources requires managerial action; disagreement about the solution requires experimentation and evidence; distrust requires consistent behavior over time. Treating every form of resistance with more communication is ineffective.

Conflict is not necessarily harmful. Task conflict can expose weak assumptions, whereas relationship conflict can damage collaboration. Leaders should separate people from problems, clarify interests, establish decision criteria and use process evidence where possible. When conflict involves power, ethics or employment consequences, it may require escalation to a senior sponsor or appropriate professional function.

Sustaining Change Through Management Routines

The final phase of a project is not the end of leadership responsibility. A redesigned process becomes stable when ownership, measurement, standard work, training, escalation and audit routines are established.

A control plan should identify critical process measures, acceptable limits, data sources, review frequency, responsible persons and required responses to abnormal conditions. Visual management and daily huddles can make emerging problems visible. Standard work should be updated, and affected employees should be trained and given opportunities to confirm understanding.

Layered process audits may be used where risk justifies them. These audits should examine adherence to critical controls and the effectiveness of the management system, not merely search for individual blame. Internal audit, risk management and compliance functions should be coordinated with Lean Six Sigma rather than treated as unrelated systems.

Sustainability also depends on organizational changes. If performance targets reward speed while the project depends on accuracy, the old behavior will return. If supervisors are not trained in the redesigned process, turnover will erode the gain. If information systems continue to reinforce the old workflow, workarounds will reappear. Control therefore includes incentives, technology, staffing, training and leadership routines.

Digital Enablement and Emerging Practice

Digital tools can strengthen enterprise deployment when they improve visibility, analysis and decision speed. Portfolio platforms can connect project charters, milestones, risks, owners and benefits. Process mining can reveal actual process paths, rework loops and variation in transaction-based work. Statistical dashboards can provide near-real-time signals, while collaboration tools support distributed teams.

Artificial intelligence can assist with document classification, anomaly detection, text analysis of complaints and identification of patterns across large datasets. Generative AI may help draft process descriptions, summarize meeting evidence or suggest analytical questions. However, AI-generated outputs require human validation, especially where data quality is uncertain or decisions affect employees, customers, safety or compliance.

Digital deployment introduces risks. Poor master data can produce precise-looking but misleading analysis. Automated dashboards may encourage metric fixation. Algorithms can reproduce historical bias. Sensitive operational or employee data require appropriate access control, privacy protection and retention rules. Technology should support a clear management purpose; digitizing an unstable process can simply accelerate waste.

Emerging practice increasingly combines Lean Six Sigma with agile delivery, process mining, sustainability management, resilience planning and enterprise architecture. The integration is useful when methods are selected according to the problem. Not every innovation challenge requires DMAIC, and not every process-control problem requires an agile sprint. Governance should preserve the discipline of evidence while allowing appropriate methodological flexibility.

Illustrative Case: Integrating Improvement with Strategy Execution

Background

The following is an illustrative case based on a composite industrial-service organization, Meridian Equipment Services. The organization maintains specialized equipment for commercial customers. Its strategic objective is to improve customer retention through more reliable service while controlling operating cost.

Situation and Problem

Customer complaints indicated that service appointments were frequently delayed and invoices were often corrected after issue. Several departments had proposed separate projects: scheduling software, technician training, invoice automation and customer-contact improvements. Senior leaders were concerned that the organization was launching more initiatives than it could execute. Reported savings also varied widely because no agreed baseline or benefit-verification method existed.

Analysis

A deployment council mapped the customer-facing value stream and identified three major performance gaps: schedule adherence, first-time completion and invoice accuracy. The council found that projects were being selected by functional managers, with limited attention to cross-functional effects. Finance could not validate many claimed savings because the proposals described reduced effort but not changes in budgeted cost or capacity use. Process ownership was divided among scheduling, field operations and finance.

A maturity assessment placed the organization between the developing and managed levels. Training existed, but project selection, benefit governance and sustainment were weak. The council therefore paused several low-priority projects and selected one cross-functional project focused on reducing delayed and incomplete service visits. A senior operations manager became sponsor, and a process owner was appointed for the end-to-end service process.

Approach and Strategy

The project team used DMAIC. During Define, the team translated the strategic objective into a measurable problem and identified customers, technicians, schedulers and finance as key stakeholders. During Measure, it established baselines for schedule adherence, first-time completion and invoice corrections, controlling for service type and region. During Analyze, the team discovered that appointment promises were made without checking technician skill availability, while incomplete job information caused repeat visits.

The solution combined a revised scheduling rule, a standardized job-information checklist, visual escalation of at-risk appointments and a limited technology change. The team tested the changes in one region before wider deployment. Finance classified the expected result primarily as capacity release and cost avoidance rather than immediate hard savings. Operational leaders agreed how released capacity would be used and which measures would confirm the benefit.

The governance council reviewed the project at tollgates. It required evidence before authorizing expansion and ensured that the technology project did not proceed independently of the process redesign. The process owner accepted responsibility for the control plan, weekly performance review and training of supervisors.

Outcome

The pilot demonstrated improved schedule adherence and fewer repeat visits. The organization did not claim the entire operational improvement as a budget saving. Instead, it reported verified financial effects separately from customer and capacity benefits. The project was expanded after the pilot, and the council transferred several lessons to the invoice-accuracy portfolio. A quarterly portfolio review later removed two projects whose expected value had declined after the scheduling changes.

Learning Points

The case illustrates that enterprise deployment involves choices about sequencing, ownership and measurement, not simply the application of tools. A strategic objective became actionable only after it was translated into process measures. Portfolio governance prevented overlapping initiatives. Finance improved credibility by distinguishing capacity release from cash savings. Most importantly, sustainment was assigned to the process owner and embedded in operating reviews.

Risks, Limitations and Common Deployment Errors

Several recurring errors undermine enterprise Lean Six Sigma. One is treating belt numbers as the main indicator of success. This encourages training volume without capability or results. Another is selecting projects according to executive enthusiasm rather than evidence of customer or business need. A third is allowing projects to proceed without a process owner, making sustainment someone else’s problem.

Other risks include excessive bureaucracy, overuse of statistical tools, premature solution selection, weak data definitions, poorly controlled scope and failure to account for system constraints. A project may appear successful because a metric improves temporarily during special attention. Without a control plan and post-project review, the organization cannot distinguish durable improvement from short-term effort.

Cultural risks deserve particular attention. If project data are used to punish individuals, employees may hide problems or manipulate measures. If leaders demand rapid results while ignoring workload, teams may bypass analysis. If improvement is associated with headcount reduction without transparent workforce planning, resistance will become rational and persistent.

There are also limitations to Lean Six Sigma. It is less suitable as a stand-alone approach for problems dominated by unknown market demand, radical product discovery or fundamental political conflict. Its structured methods can be too slow when immediate containment is required, although rapid containment can be followed by disciplined analysis. Method selection should reflect the nature, urgency and uncertainty of the problem.

Ethical and Professional Governance

Improvement leaders have a duty to represent evidence honestly. Baselines should not be manipulated to exaggerate results, and financial benefits should not be claimed without agreed definitions. Data involving customers or employees must be collected and used lawfully and respectfully. Privacy, confidentiality, safety and non-discrimination requirements remain applicable during experiments and process redesign.

A project that improves cost while increasing unsafe work, unfair workload or service exclusion is not a quality success. Governance should therefore include relevant ethical and regulatory stakeholders. Where automation changes roles, leaders should consider consultation, retraining, redeployment and transparent communication. Professional credibility depends on balancing efficiency with customer welfare, employee dignity, compliance and long-term organizational health.

Best-Practice Principles for Enterprise Deployment

Effective deployment generally follows a small number of principles:

1. Begin with strategic and customer priorities, not with available tools or trained belts.

2. Make process ownership and decision rights explicit.

3. Select projects through transparent criteria and manage them as a portfolio.

4. Protect improvement capacity and sequence initiatives realistically.

5. Treat finance as a partner in defining and validating benefits.

6. Develop capability through coached application, not certification alone.

7. Use leaders as sponsors and coaches, not merely approvers.

8. Diagnose resistance and involve affected employees in solution design.

9. Embed control plans, standard work and review routines into normal management.

10. Use digital technology to strengthen evidence and learning, while controlling data and algorithmic risks.

11. Review whether projects remain relevant and stop those that no longer justify investment.

12. Measure organizational learning and sustainability as well as short-term results.

Chapter Summary

Enterprise Lean Six Sigma is an operating system for aligning strategy, process performance, people and benefits. Its effectiveness depends on governance that clarifies roles, selects projects transparently, balances a portfolio and verifies results. Belt structures should build applied capability rather than generate certificates, while maturity models should guide differentiated development.

Strategic project selection requires attention to customer value, risk, financial impact, feasibility and interdependence. Portfolio governance must distinguish activity from outcomes and must connect operational gains to managerial accounting. Capacity release, cost avoidance, hard savings and nonfinancial value should not be confused. Leadership is equally important: sponsors remove barriers, coaches develop problem-solving ability, and process owners sustain redesigned work.

Resistance and conflict should be diagnosed rather than dismissed. Sustainable change requires standard work, measurement, training, control plans and management routines. Digital technologies, process mining and AI can strengthen deployment but introduce data, privacy and bias risks. Ultimately, enterprise maturity is demonstrated when evidence-based improvement is integrated into strategy execution and everyday management.

Key Terms

Operating system: The roles, routines, information flows and decision rights through which an organization manages performance and improvement.

Deployment governance: The structures and processes used to direct, prioritize, review and control Lean Six Sigma activity.

Executive sponsor: A senior leader accountable for strategic support, resources and removal of major barriers.

Process owner: The person accountable for end-to-end process performance and sustainment after project completion.

Belt structure: A capability framework that differentiates Lean Six Sigma training, responsibilities and levels of expertise.

Master Black Belt: A senior improvement expert who develops capability, coaches complex work and supports deployment design.

Maturity model: A staged framework for assessing organizational capability and identifying development priorities.

Project portfolio: The collection of improvement initiatives managed together for strategic alignment, resource balance and benefit realization.

Tollgate: A formal decision point at which project evidence is reviewed and continuation, redirection or closure is determined.

Benefit realization: The process of defining, tracking, validating and sustaining expected project outcomes.

Hard saving: A verified financial improvement that affects expenditure, budget or realized cash flow.

Capacity release: Productive time made available through improvement, whose value depends on subsequent management action.

Policy deployment: A method for translating strategic priorities into measurable objectives, initiatives and accountability.

Process owner: The manager responsible for maintaining process performance and controls.

Change readiness: The extent to which people, systems and leadership conditions support adoption of a new way of working.

Resistance diagnosis: The identification of the underlying reason for opposition, such as lack of awareness, skill, resources or trust.

Control plan: A documented arrangement specifying critical measures, limits, responsibilities and responses for sustaining performance.

Process mining: The use of event-log data to discover, analyze and monitor actual process behavior.

Portfolio dashboard: A management display summarizing project status, risks, resources, dependencies and benefits.

Sustainability: The ability of an improved process to maintain intended performance over time.

Review Questions

Short Answer Questions

1. What distinguishes an enterprise Lean Six Sigma operating system from a collection of individual projects?

2. What is the purpose of a project tollgate?

3. Why should belt certification not be treated as the main measure of capability?

4. Distinguish between a hard saving and capacity release.

5. Identify two leadership behaviors that support sustainable change.

Long Answer Questions

1. Explain how governance, process ownership and portfolio management interact in enterprise Lean Six Sigma deployment.

2. Discuss the five-level maturity model and explain how an organization should use it diagnostically.

3. Describe a comprehensive project-selection mechanism incorporating strategic, customer, financial, risk and feasibility criteria.

4. Analyze the role of managerial accounting in validating Lean Six Sigma benefits.

5. Explain how leaders can diagnose resistance, coach teams and manage conflict during improvement initiatives.

Analytical / Application Questions

1. An organization has trained many Green Belts but has few completed projects and no reliable financial benefits. Diagnose the likely system weaknesses and recommend a deployment response.

2. Two departments propose separate projects addressing the same customer complaint, but their solutions depend on a common information-system change. Design a portfolio-governance approach for deciding whether and how to proceed.

3. A project reduces processing time but employees report increased workload and customers experience inconsistent service. Evaluate whether the project is successful and propose appropriate corrective actions.

22. Multiple Choice Questions with Answers

Question 1

Which feature most clearly distinguishes an enterprise Lean Six Sigma operating system from isolated improvement projects?

A. It requires every employee to become a Black Belt.

B. It links project selection, ownership, benefits and sustainment to management routines.

C. It uses more statistical tools in every project.

D. It eliminates the need for functional managers.

Correct Answer: B. It links project selection, ownership, benefits and sustainment to management routines.

Question 2

A project reports reduced labor hours, but staffing and the budget remain unchanged. How should the immediate benefit primarily be classified?

A. Hard saving

B. Revenue enhancement

C. Capacity release

D. Working-capital reduction

Correct Answer: C. Capacity release

Question 3

What is the most appropriate purpose of a project tollgate?

A. To celebrate project completion regardless of evidence

B. To determine whether evidence justifies continuation, redirection or closure

C. To transfer all project responsibility to Finance

D. To replace the project charter with a training record

Correct Answer: B. To determine whether evidence justifies continuation, redirection or closure

Question 4

An organization has extensive belt training but weak process ownership and poor sustainment. What is the most appropriate next intervention?

A. Increase the number of certification examinations

B. Clarify accountability and embed control routines with process owners

C. Launch more projects to demonstrate activity

D. Remove all operational performance measures

Correct Answer: B. Clarify accountability and embed control routines with process owners

Question 5

Which project is most suitable for selection through an enterprise portfolio?

A. A project chosen solely because a manager prefers its proposed solution

B. A project with a measurable customer problem, accountable owner and strategic relevance

C. A project with no baseline but a large claimed saving

D. A project whose scope includes every process in the organization

Correct Answer: B. A project with a measurable customer problem, accountable owner and strategic relevance

Question 6

Why should capacity release not automatically be reported as a hard financial saving?

A. Capacity release can never have economic value.

B. Released time creates value only when management converts it into savings, volume or redeployment.

C. Finance is not involved in improvement projects.

D. Hard savings apply only to quality metrics.

Correct Answer: B. Released time creates value only when management converts it into savings, volume or redeployment.

Question 7

A team resists a redesigned process because employees fear that automation will eliminate their roles. What is the most appropriate initial leadership response?

A. Dismiss the concern as irrational resistance.

B. Increase statistical analysis of the current process.

C. Diagnose the concern, communicate transparently and address workforce implications.

D. Close the project immediately without investigation.

Correct Answer: C. Diagnose the concern, communicate transparently and address workforce implications.

Question 8

Which statement best describes a mature Lean Six Sigma organization?

A. It launches the maximum number of projects each year.

B. It embeds improvement in strategy deployment, daily management and process ownership.

C. It measures success mainly through training attendance.

D. It centralizes every improvement decision in a specialist department.

Correct Answer: B. It embeds improvement in strategy deployment, daily management and process ownership.

Question 9

What is a principal governance risk when two projects claim the same operational saving?

A. Overtraining of Green Belts

B. Double counting of benefits

C. Excessive customer segmentation

D. Improved process visibility

Correct Answer: B. Double counting of benefits

Question 10

Which use of artificial intelligence is most consistent with responsible enterprise deployment?

A. Allowing an unvalidated algorithm to make employment decisions automatically

B. Using AI to identify complaint patterns while validating outputs and protecting sensitive data

C. Replacing process owners with an automated dashboard

D. Using generated analysis without checking data quality

Correct Answer: B. Using AI to identify complaint patterns while validating outputs and protecting sensitive data