Portfolio Management, Finance and Change Leadership

Introduction

Six Sigma creates value through disciplined improvement, but individual projects do not automatically form a coherent improvement strategy. An organization may complete many technically successful projects while failing to improve its most important customer outcomes, financial results, or strategic capabilities. Portfolio management addresses this problem by selecting, sequencing, funding, governing, and reviewing projects as an interconnected set of investments.

In a mature Six Sigma system, project selection is not based solely on ease of execution or the enthusiasm of a local sponsor. Projects are evaluated through a balanced view of strategic value, customer impact, operational risk, financial return, organizational capacity, regulatory obligations, and the probability of sustainable adoption. Finance provides a common language for comparing alternatives, while change leadership converts technical recommendations into new organizational behavior.

This chapter examines the integration of Six Sigma portfolio management, financial analysis, resource governance, benefits realization, cross-functional leadership, resistance management, and institutionalization. The central argument is that improvement is both a technical and a social system: data may identify the opportunity, but leadership determines whether the improvement survives.

Learning Objectives

After studying this chapter, students should be able to:

1. Explain the purpose and structure of a Six Sigma project portfolio.
2. Prioritize projects using strategic, financial, risk, customer, and feasibility criteria.
3. Apply basic financial measures, including savings, ROI, payback, and NPV, while recognizing their limitations.
4. Design portfolio governance, resource-allocation, and benefits-realization processes.
5. Lead cross-functional Six Sigma teams and manage stakeholder expectations.
6. Diagnose and address individual, group, and systemic resistance to change.
7. Evaluate how improvement becomes embedded in management systems and organizational culture.

1. From Projects to Portfolios

A project is a temporary effort designed to achieve a defined improvement objective. A program coordinates related projects to obtain benefits that would be difficult to achieve separately. A portfolio is the organization’s collection of projects and programs, managed together to support strategic objectives and balance investment, risk, capacity, and expected benefits.

Six Sigma portfolio management therefore asks five linked questions:

• Are the right problems being selected?
• Is the organization investing at an appropriate level?
• Can the available people and capabilities execute the work?
• Are benefits actually being realized and sustained?
• Should projects be accelerated, redesigned, paused, or stopped?

A portfolio is not simply a list of projects. It is a decision system. Projects compete for scarce Black Belts, process owners, engineering support, information-technology capacity, operational access, and management attention. Without portfolio discipline, the organization experiences project overload, delayed implementation, weak sponsorship, and benefit dilution.

Strategic alignment

Strategic alignment means that a project contributes to an explicit organizational priority. Examples include reducing order-to-delivery time, improving patient safety, increasing first-pass yield, protecting regulatory compliance, or reducing cost-to-serve. Alignment should be demonstrated rather than asserted. A project charter should identify the strategic objective, the relevant customer or stakeholder, the process affected, and the measurable result expected.

A useful distinction is between strategic necessity and discretionary opportunity. A compliance project may have a modest financial return but be essential because failure creates legal or safety exposure. Conversely, a cost-reduction project may have a high projected return but be strategically harmful if it damages service quality or employee capability.

Portfolio balance

A balanced portfolio commonly contains several categories:

A portfolio dominated by short-term savings may weaken innovation. A portfolio dominated by exploratory initiatives may fail to deliver current performance. Senior leaders must therefore manage both the mix of projects and the timing of benefits.

2. Project Prioritization and Selection

Stage-gate selection

A robust selection process uses staged decisions rather than approving every idea immediately. A typical sequence is:

1. Idea capture: collect opportunities from strategy, customers, employees, audits, process data, and risk assessments.
2. Initial screening: remove ideas with unclear problems, negligible impact, or unsuitable scope.
3. Concept assessment: define the problem, baseline, customer requirement, likely benefits, risks, and sponsor.
4. Business-case review: estimate resources, timing, cost, benefits, and dependencies.
5. Portfolio approval: compare the proposal with alternatives and capacity constraints.
6. Periodic review: continue, redirect, pause, or terminate according to evidence.

The last stage is important. Approval is not a permanent entitlement. A project that fails to validate its problem or cannot obtain process-owner commitment should be reconsidered.

Weighted scoring model

A weighted scoring model makes assumptions visible. Let project score j be:

where wᵢ is the weight assigned to criterion i, rᵢⱼ is project j’s rating on criterion i, and the weights sum to 1. Ratings may use a defined scale, such as 1 to 5. The model assumes that criteria are sufficiently well defined and that the ratings are comparable. It produces a decision aid, not an objective truth.

Possible criteria include strategic alignment, customer impact, financial value, risk reduction, urgency, feasibility, data readiness, and capability development. A compliance project can receive a high risk-reduction rating even when its direct savings are low.

#### Illustrative prioritization

Suppose a governance board uses the following weights: strategic alignment 0.25, customer impact 0.20, financial value 0.25, risk reduction 0.15, and feasibility 0.15. Project A receives ratings of 5, 4, 3, 2, and 4 respectively. Its score is:

The result is 3.65 on a five-point scale. The arithmetic does not prove that Project A is superior; it indicates its relative attractiveness under the selected criteria and weights. Sensitivity analysis should test whether a modest change in weights changes the ranking.

Risk-adjusted prioritization

Expected value can incorporate uncertainty. If an outcome k has probability pₖ and monetary value Vₖ, expected monetary value is:

where probabilities sum to 1. For example, if a project has a 0.60 probability of producing a benefit of $200,000 and a 0.40 probability of producing $80,000, its expected benefit is:

This calculation assumes that the possible outcomes are mutually exclusive and collectively exhaustive, and that the values are measured on a consistent basis. Expected value does not eliminate risk; it makes uncertainty explicit. Decision makers should also consider downside exposure, variance, strategic irreversibility, and risk appetite.

Interdependencies and constraints

A project may depend on another project’s data architecture, supplier agreement, process redesign, or technology release. Portfolio analysis should identify:

• precedence dependencies;
• shared resources;
• capacity bottlenecks;
• common process owners;
• cumulative change burden;
• conflicts between benefits;
• timing of cash flows and operational disruption.

A project with a high score may be deferred if it competes for a scarce specialist needed by a higher-risk initiative. Conversely, a lower-scoring enabling project may be funded because it unlocks several strategic projects.

3. Financial Analysis of Six Sigma Projects

Financial analysis creates accountability, but it must not reduce quality management to short-term cost cutting. The financial case should distinguish cash savings, cost avoidance, capacity release, revenue effects, working-capital effects, and non-financial benefits.

Benefit classification

Hard savings are reductions that can be observed in the financial accounts, such as eliminated external expenditure, reduced overtime, or lower material consumption. Soft savings are operational benefits that may not immediately reduce the budget, such as released employee capacity or avoided future cost. Cost avoidance prevents a projected increase but may not reduce current expenditure. Revenue benefits may arise from increased sales, retention, or price realization, but they should be estimated conservatively and separated from cost savings.

A benefit statement should identify the mechanism, baseline, owner, timing, accounting treatment, and evidence required for verification.

Basic financial measures

The net benefit over a selected period is:

Return on investment is commonly expressed as:

Costs and benefits must use the same time period and currency basis. ROI is useful for communication, but it can favor projects with short lives and ignores the timing of cash flows.

The simple payback period is the time required for cumulative cash benefits to recover the initial investment. If annual net cash inflow is constant:

This special-case formula assumes constant annual inflows and excludes the time value of money. If inflows vary, cumulative cash flow must be calculated period by period.

For discounted cash-flow analysis, net present value is:

where C₀ is the initial investment at time 0, CFₜ is net cash flow in period t, r is the discount rate per period, and t is the period number. NPV assumes that cash flows and the discount rate use consistent periods and that the estimated rate reflects the relevant opportunity cost or hurdle rate. A positive NPV indicates value creation relative to that discount rate, subject to the quality of the forecasts.

#### Worked financial example

An improvement requires $60,000 initially and is expected to generate net cash benefits of $30,000 at the end of each of the next three years. At a discount rate of 10%:

The present values are approximately $27,273, $24,793, and $22,539. Therefore:

The project has a positive estimated NPV of approximately $14,605. Its undiscounted payback is two years because cumulative benefits reach $60,000 after two years. The two measures answer different questions: payback concerns recovery time, whereas NPV considers the value and timing of all cash flows.

Avoiding financial overstatement

Common errors include counting the same benefit in multiple projects, treating capacity release as cash savings without a capacity decision, using an unverified baseline, ignoring implementation costs, and claiming benefits before process performance is stable. Finance should validate the calculation, while the process owner should accept responsibility for realization.

Benefits should be tracked through a benefits register containing the project, metric, baseline, target, owner, realization date, evidence, accounting treatment, and status. A project is not financially successful merely because its report predicts savings.

4. Portfolio Governance and Benefits Realization

Portfolio governance defines who decides, what evidence is required, how priorities are changed, and how accountability is maintained. A practical governance structure may include:

• Executive steering committee: sets strategic priorities, approves major investments, resolves conflicts, and removes barriers.
• Portfolio or transformation office: maintains the portfolio view, standards, dashboards, dependencies, and review calendar.
• Finance partner: validates business cases and realized benefits.
• Master Black Belt or improvement leader: assures methodology, coaching, and capability development.
• Process owner: accepts the redesigned process and owns sustained performance.
• Project sponsor: provides authority, resources, and organizational advocacy.
• Black Belt or project leader: manages analysis, delivery, risks, and team activity.

Governance should be proportionate. Excessive approval layers slow improvement, whereas weak governance creates uncontrolled scope and unreliable benefits.

Portfolio performance measures

A balanced dashboard can include:

Metrics must have clear definitions. For example, benefit realization rate may be defined as realized benefits divided by approved benefits, but the organization must specify whether the denominator includes only completed projects or the full approved portfolio.

Stop, continue, or pivot decisions

Evidence-based governance should permit termination. Warning signals include an invalidated problem, absent process ownership, inaccessible data, unacceptable risk, duplicated scope, or benefits that no longer justify investment. Stopping a project is not necessarily failure; it may represent successful portfolio learning and responsible resource management.

5. Leading Cross-Functional Six Sigma Teams

Six Sigma projects cross functional boundaries because defects often occur at interfaces rather than within a single department. A team may include operations, quality, finance, engineering, information technology, procurement, sales, compliance, and customer representatives.

Team design

Effective teams require a clear purpose, decision rights, defined roles, adequate time, relevant expertise, and psychological safety. The sponsor should identify what the team can decide and what requires escalation. A responsibility matrix such as RACI—responsible, accountable, consulted, and informed—can reduce ambiguity, although it should not become a substitute for real conversation.

A cross-functional leader must translate between professional languages. Operations may emphasize flow and workload; finance may emphasize controllability and evidence; technology may emphasize architecture; customers may emphasize reliability and usability. The leader’s role is not to make every decision personally but to create a disciplined process through which differences become useful analysis.

Team development and decision quality

Teams typically move through orientation, conflict, norm formation, productive work, and closure, although stages may recur when membership or scope changes. Conflict is not inherently dysfunctional. Task conflict can improve decisions when evidence-based and respectfully managed; relationship conflict usually damages trust and information sharing.

Useful practices include a team charter, explicit meeting decisions, visual problem statements, pre-reading, structured debate, and documented assumptions. When consensus is impossible, the decision owner should be identified in advance and the rationale recorded.

6. Change Leadership and Resistance

Technical improvement changes work methods, authority, measures, routines, and sometimes professional identity. Resistance is therefore not simply irrational opposition. It may signal loss of control, fear of job impact, distrust created by earlier initiatives, inadequate skills, workload pressure, or a legitimate concern about safety and service.

A systems view of resistance

Resistance can be analyzed at three levels:

1. Individual: knowledge, confidence, motivation, perceived threat, and personal benefit.
2. Group: norms, peer influence, local leadership, and professional identity.
3. System: incentives, workload, technology, policies, reporting structures, and resource constraints.

A training session cannot solve a system-level problem such as conflicting performance targets. Leaders should ask whether the desired behavior is understood, possible, reinforced, and safe.

Change frameworks

The ADKAR model emphasizes Awareness, Desire, Knowledge, Ability, and Reinforcement. It is useful for diagnosing individual adoption gaps. Kotter’s change framework emphasizes urgency, coalition, vision, communication, enabling action, short-term wins, consolidation, and anchoring change. Lewin’s unfreezing–changing–refreezing model offers a broad systems metaphor, although contemporary organizations often experience continuous rather than discrete change.

These frameworks are not competing statistical laws. They are managerial lenses. Their value depends on diagnosis, leadership behavior, and adaptation to context.

Practical response to resistance

A responsible sequence is:

• listen before persuading;
• distinguish facts, fears, and interests;
• involve affected employees in process observation and solution design;
• explain what will change and what will not;
• provide training, time, tools, and local support;
• pilot where risk is manageable;
• measure both outcomes and unintended effects;
• recognize adoption and address persistent non-compliance fairly.

Manipulation, concealed surveillance, and coercive communication may produce superficial compliance but undermine trust and continuous improvement.

7. Institutionalizing Improvement Culture

A culture of improvement is not created by slogans or isolated workshops. It is embedded in systems that repeatedly reinforce evidence-based problem solving. Institutionalization occurs when improvement is part of strategy deployment, daily management, performance review, budgeting, talent development, and process ownership.

Important mechanisms include:

• standard work and visual management;
• control plans and process audits;
• routine review of critical process measures;
• leader standard work and regular gemba observation;
• recognition of problem identification, not only successful outcomes;
• structured suggestion and rapid-improvement channels;
• training linked to real projects;
• succession planning for sponsors and improvement specialists;
• integration of lessons learned into procedures and technical standards.

The organization should avoid creating a separate “quality island.” If Six Sigma is owned only by a central improvement office, operational leaders may regard it as temporary or external. The improvement office should build capability and governance while process owners retain accountability for performance.

Psychological safety and learning

A mature culture allows employees to report defects, near misses, and weak signals without fear of unfair blame. This does not eliminate accountability. It distinguishes human error, risky system design, at-risk behavior, and deliberate violation. Such distinctions support learning while preserving ethical and operational standards.

Capability maturity

Organizational maturity can be viewed as a progression:

1. Reactive: problems are addressed after failure.
2. Project-based: selected problems receive structured improvement.
3. Managed: portfolios, governance, and benefits are coordinated.
4. Integrated: improvement is linked to strategy and daily management.
5. Adaptive: the organization learns continuously and redesigns its systems as conditions change.

Maturity is not a label to be claimed; it is demonstrated through consistent behavior and results.

8. Technology, Data, and Artificial Intelligence

Digital tools can improve portfolio visibility, automate data collection, identify process patterns, and support benefits tracking. Workflow platforms can connect charters, approvals, risks, actions, and outcomes. Process mining can reveal actual process paths and rework. Predictive models may help forecast demand, failure, or project delay.

However, technology does not replace problem definition, process ownership, or ethical judgment. AI-generated recommendations may reproduce biased historical decisions, expose confidential data, or create false confidence through opaque models. Governance should address data quality, access control, explainability, human review, cybersecurity, intellectual property, and accountability for decisions.

AI should augment—not obscure—the DMAIC logic. The organization must still define the customer and problem, measure the baseline, analyze causal evidence, improve the process, and control the result. A model’s prediction is not proof of causation.

9. Illustrative Case: Regional Medical Device Manufacturer

Background

This illustrative case concerns MedAxis, a fictional regional manufacturer of sterile medical devices. Its strategic priorities were regulatory reliability, on-time delivery, and cost competitiveness. The organization had 26 proposed Six Sigma projects but only four experienced Black Belts, two process engineers, and limited information-technology support.

Problem

Projects had been selected independently by departments. Several addressed similar production delays, while no project addressed a recurring sterilization documentation risk. Finance reported that projected benefits exceeded $4 million, but no common baseline or benefit owner existed. Employees complained of initiative fatigue and conflicting priorities.

Analysis

The portfolio team established five weighted criteria: regulatory and patient risk 0.30, strategic alignment 0.25, customer impact 0.20, validated financial opportunity 0.15, and feasibility 0.10. Projects were scored on a five-point scale. The team also mapped dependencies and identified that three projects required the same data-engineering resource.

A finance review separated hard savings from capacity release. One proposed project claimed $500,000 in savings by reducing operator time, but headcount and overtime budgets would not change. The benefit was reclassified as capacity release and assigned a process-owner decision: either use the capacity to increase output or remove overtime. This prevented double counting.

Approach and solution

The steering committee approved eight projects, deferred six, combined four overlapping projects, and rejected eight poorly defined proposals. The compliance-related project was prioritized despite a modest direct return because its risk reduction was strategically essential. A quarterly portfolio review was introduced, with stage gates at definition, validated baseline, approved solution, implementation, and benefits verification.

Each approved project received a sponsor, process owner, finance partner, and change-impact assessment. Operators participated in future-state design. Supervisors were trained in daily control checks, and the new documentation process was piloted on one production line before broader implementation.

Outcome

After nine months, the portfolio had completed five projects, with two still in implementation and one stopped after data analysis invalidated the original problem statement. Verified annualized financial benefits were $620,000 against an approved estimate of $700,000. The compliance project reduced documentation errors and improved audit readiness. On-time delivery improved, although the organization continued to monitor whether production gains increased downstream inspection workload.

Learning points

The case demonstrates that portfolio value comes from selection, integration, and governance rather than project volume. Financial validation protected credibility. Stopping a weak project released scarce capacity. Involving operators improved adoption, while the pilot exposed an unintended workload transfer. Finally, risk and compliance projects should be assessed through strategic and exposure-based reasoning, not direct savings alone.

10. Challenges and Limitations

Portfolio models can create false precision. A score of 4.1 does not mean a project is exactly 10 percent better than one scoring 3.7. Ratings may be biased by powerful sponsors, optimistic forecasts, or incomplete data. Financial models are sensitive to assumptions about demand, adoption, implementation cost, and timing.

There is also a danger of metric gaming. Teams may redefine baselines, delay recognition of adverse results, or select measures that are easy to improve but weakly connected to customer value. Governance must therefore encourage challenge, independent validation, and transparent assumptions.

Another limitation is that culture cannot be engineered solely through dashboards. Trust, identity, leadership credibility, and perceived fairness develop through repeated interactions. Change leadership requires judgment and ethical consistency, particularly when improvement affects roles, workload, employment, or professional autonomy.

Best-Practice Checklist

• Link every project to a documented strategic, customer, risk, or capability need.
• Use transparent criteria and test ranking sensitivity.
• Separate hard savings, cost avoidance, capacity release, and revenue effects.
• Assign a process owner and finance validator before approval.
• Review dependencies, resource constraints, and cumulative change load.
• Use stage gates and permit evidence-based termination.
• Include affected employees in diagnosis and solution design.
• Measure adoption and unintended consequences, not only technical performance.
• Embed controls in daily management and standard work.
• Govern digital and AI tools through data, privacy, security, and human-accountability controls.

Chapter Summary

Six Sigma portfolio management converts isolated improvement ideas into a strategically governed investment system. Effective prioritization combines strategic alignment, customer value, financial return, risk reduction, feasibility, capacity, and project interdependencies. Weighted scoring and expected-value analysis make assumptions visible, while financial measures such as ROI, payback, and NPV support disciplined investment decisions. These measures must be based on consistent definitions, validated baselines, and careful separation of savings from cost avoidance or released capacity.

Portfolio governance assigns decision rights, controls resources, reviews progress, and verifies benefits. Cross-functional teams require clear purpose, decision authority, psychological safety, and process-owner accountability. Resistance should be diagnosed as an individual, group, and system phenomenon rather than dismissed as irrational behavior. Change frameworks provide useful lenses, but adoption depends on participation, capability, reinforcement, and credible leadership.

Improvement becomes institutionalized when it is integrated into strategy, budgeting, daily management, standard work, performance review, training, and recognition. Technology and AI can strengthen visibility and analysis, but they do not replace causal reasoning, ethical governance, or human accountability. Sustainable Six Sigma is therefore a portfolio, financial, leadership, and cultural discipline simultaneously.

Key Terms

Portfolio management: Coordinated selection and governance of projects and programs to achieve strategic objectives.

Project: A temporary effort undertaken to deliver a defined improvement or result.

Program: A coordinated group of related projects managed to obtain combined benefits.

Strategic alignment: The degree to which a project supports stated organizational priorities.

Weighted scoring model: A prioritization method that multiplies criterion weights by project ratings.

Expected monetary value: Probability-weighted value of possible outcomes.

Hard savings: Financial reductions verified in the organization’s accounts.

Soft savings: Operational benefits not immediately represented as budget reduction.

Cost avoidance: Prevention of an expected future cost increase.

Capacity release: Time or resources made available without necessarily reducing expenditure.

ROI: Return on investment, commonly calculated as net benefit divided by cost.

Payback period: Time required for cumulative cash benefits to recover initial investment.

NPV: Net present value of discounted future cash flows less initial investment.

Benefits realization: The process of confirming that approved project benefits actually occur.

Stage gate: A formal decision point at which a project is continued, changed, paused, or stopped.

Process owner: The person accountable for ongoing performance of the improved process.

Change resistance: Opposition or reluctance arising from perceived threat, lack of capability, or system conditions.

Psychological safety: A climate in which people can raise concerns and report problems without unfair interpersonal punishment.

Institutionalization: Embedding improvement practices into routine management systems and organizational culture.

Benefits register: A controlled record of benefit definitions, baselines, owners, targets, evidence, and status.

Review Questions

Short Answer Questions

1. What distinguishes a portfolio from a project and a program?
2. Why should project prioritization include risk and regulatory exposure as well as financial return?
3. Define hard savings, soft savings, and capacity release.
4. What is the role of a process owner in benefits realization?
5. Name three mechanisms through which improvement can become institutionalized.

Long Answer Questions

1. Explain how a weighted scoring model can support Six Sigma portfolio selection, and discuss its limitations.
2. Compare ROI, payback period, and NPV as measures for evaluating improvement projects.
3. Discuss the responsibilities of the executive steering committee, portfolio office, sponsor, Black Belt, and process owner.
4. Explain how resistance to change can arise at individual, group, and system levels.
5. Evaluate the argument that sustainable Six Sigma requires cultural and management-system change in addition to technical analysis.

Analytical / Application Questions

1. An organization has twelve projects but enough Black Belt capacity for only five. Design a prioritization framework that balances strategic value, financial return, risk, feasibility, and resource dependencies.
2. A project claims $400,000 of annual savings by reducing staff processing time, but no staffing or overtime budget will change. How should the benefit be classified, validated, and governed?
3. A technically successful process redesign is not being used by supervisors. Diagnose possible causes using a change-leadership framework and propose an intervention plan.

Multiple Choice Questions with Answers

Question 1

What is the primary purpose of Six Sigma portfolio management?

A. To maximize the number of projects completed

B. To coordinate projects as strategic investments under resource and risk constraints

C. To eliminate the need for process owners

D. To replace financial evaluation with statistical analysis

Correct Answer: B. To coordinate projects as strategic investments under resource and risk constraints

Question 2

In a weighted scoring model, what does the project score represent?

A. The guaranteed financial return

B. The exact probability of project success

C. A relative decision aid based on weighted criteria and ratings

D. The project’s payback period

Correct Answer: C. A relative decision aid based on weighted criteria and ratings

Question 3

A project costs $50,000 and produces verified benefits of $80,000. Using ROI = (Benefits − Costs) ÷ Costs × 100%, what is the ROI?

A. 37.5%

B. 60%

C. 160%

D. 260%

Correct Answer: B. 60%

Question 4

Which statement best describes NPV?

A. It measures only the time until investment recovery

B. It discounts future cash flows and subtracts the initial investment

C. It is identical to undiscounted annual savings

D. It excludes the timing of cash flows

Correct Answer: B. It discounts future cash flows and subtracts the initial investment

Question 5

Which benefit is most accurately described as capacity release?

A. A reduction in an approved materials invoice

B. A reduction in legally required expenditure

C. Employee time made available without an immediate reduction in the budget

D. A confirmed increase in product selling price

Correct Answer: C. Employee time made available without an immediate reduction in the budget

Question 6

Who is primarily accountable for sustaining the performance of an improved process?

A. The external auditor

B. The process owner

C. The project team’s newest member

D. The portfolio administrator alone

Correct Answer: B. The process owner

Question 7

Which response is most appropriate when employees resist a process change?

A. Ignore concerns until compliance is mandatory

B. Remove affected employees from solution design

C. Diagnose the source of resistance and provide involvement, capability, and support

D. Report all disagreement as misconduct

Correct Answer: C. Diagnose the source of resistance and provide involvement, capability, and support

Question 8

Why might a compliance project be prioritized despite modest direct financial savings?

A. Compliance projects never require resources

B. Risk reduction and regulatory obligation may have high strategic value

C. Compliance benefits are always larger than productivity benefits

D. Financial analysis is prohibited for compliance projects

Correct Answer: B. Risk reduction and regulatory obligation may have high strategic value

Question 9

What is a key purpose of a portfolio stage gate?

A. To guarantee that every project continues to completion

B. To provide evidence-based decisions to continue, redirect, pause, or stop a project

C. To transfer all accountability to the Black Belt

D. To prevent changes to project scope under any circumstances

Correct Answer: B. To provide evidence-based decisions to continue, redirect, pause, or stop a project

Question 10

Which practice most strongly supports institutionalization of improvement?

A. Treating each project as separate from daily management

B. Embedding controls, standard work, review routines, and process ownership into operations

C. Measuring only the number of trained employees

D. Using AI outputs without human review

Correct Answer: B. Embedding controls, standard work, review routines, and process ownership into operations