11. Lean Strategy, Hoshin Kanri and Transformation Governance

Introduction and Context

Lean management is often introduced through operational practices such as value-stream mapping, standardized work, visual management, pull systems, and problem solving. These practices are essential, but they do not by themselves constitute a strategy. An organization may conduct many improvement events and still fail to improve its competitive position because local projects are disconnected from customer value, financial performance, risk, and long-term direction.

Lean strategy addresses this gap. It connects organizational purpose with a limited number of breakthrough priorities and translates those priorities into coordinated action at every level. Hoshin Kanri is one of the most influential approaches for achieving this alignment. Commonly translated as “policy deployment,” Hoshin Kanri combines strategic planning, dialogue, measurement, review, and learning. Its distinctive feature is not merely the existence of strategic objectives, but the disciplined process through which objectives are negotiated, deployed, executed, and revised.

Transformation governance provides the organizational infrastructure for this work. It defines who decides, who is accountable, how resources are allocated, how progress is reviewed, and how risks are managed. Without governance, lean transformation can become dependent on enthusiastic individuals or isolated improvement teams. With excessive governance, it can become bureaucratic and slow. The central managerial challenge is therefore to create sufficient alignment and control while preserving learning, initiative, and problem-solving capability.

Learning Objectives

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

1. Explain the relationship between lean strategy, Hoshin Kanri, catchball, and tiered management.

2. Distinguish annual priorities from breakthrough objectives and routine improvement work.

3. Construct a practical Hoshin Kanri deployment process with measures, owners, and review cycles.

4. Design a transformation portfolio and governance structure appropriate to organizational scale and risk.

5. Use maturity assessment to diagnose the current state of lean capability.

6. Develop change-management responses to resistance, overload, and transformation failure.

7. Evaluate lean transformation through operational, strategic, cultural, and customer-oriented measures.

From Operational Improvement to Strategic Deployment

Lean strategy begins with a question: what must the organization become capable of doing better in order to create superior value for customers and stakeholders? The answer should not be expressed only as an activity, such as “implement 5S” or “train employees in lean.” Activities are means. Strategic objectives describe desired changes in performance or capability, such as reducing order-to-delivery time, improving reliability, developing flexible capacity, or creating a problem-solving culture.

A useful hierarchy separates four levels of intention. At the highest level is purpose or strategic direction: why the organization exists and what position it seeks to achieve. The next level consists of breakthrough objectives, which represent significant changes required over several years. Annual priorities convert these objectives into achievable results for the current planning period. Daily management sustains standards, detects abnormalities, and improves routine performance.

These levels must be connected. A breakthrough objective without daily management remains aspirational; daily management without strategic direction produces local optimization. Lean strategy therefore requires both vertical alignment and horizontal integration. Vertical alignment links corporate intent to team-level action. Horizontal integration coordinates functions such as sales, operations, procurement, finance, information technology, and human resources so that one department does not improve its own metric by damaging the total value stream.

Strategic deployment also requires a distinction between lagging and leading indicators. Revenue, cost, delivery performance, defects, and customer retention are generally lagging outcomes. Training completion, adherence to problem-solving routines, supplier development activity, process capability, and the closure rate of verified countermeasures are leading indicators. Neither category is sufficient alone. A dashboard containing only outcomes may identify failure too late, while one containing only activity measures may reward motion without results.

Hoshin Kanri: Logic and Architecture

Hoshin Kanri is a cyclical management system for translating strategic intent into coordinated improvement. Although organizations use different formats, a robust system normally includes the following elements:

• a clearly stated organizational direction;
• a small number of breakthrough objectives;
• annual objectives and target conditions;
• owners, measures, milestones, and resources;
• dialogue across organizational levels;
• regular review and corrective action; and
• reflection and learning at the end of the cycle.

The word “breakthrough” should be interpreted carefully. It does not necessarily mean a dramatic innovation. It means a result that cannot be achieved through ordinary incremental improvement alone. For example, reducing lead time by a modest percentage may be an annual improvement target, whereas redesigning the end-to-end order process to support same-day response may be a breakthrough challenge.

The Hoshin Planning Cycle

The cycle commonly begins with a review of the organization’s purpose, environment, customer expectations, performance trends, and major constraints. Strategic leaders then identify a few priorities. Limiting the number is important because every priority consumes attention, management time, and organizational capacity. A long list of “critical” objectives is usually evidence that prioritization has not occurred.

Each priority is expressed through a result, a target condition, a time horizon, and an accountable owner. The target condition should describe what will be different in the process, not merely the numerical result. For example, “reduce claim resolution time from ten days to three” is stronger when accompanied by a description of the future process: standardized triage, clear decision rights, visible queue status, and rapid escalation of exceptional cases.

The next step is deployment. Senior priorities are translated into contributions required from functions and operating units. The contributions should be negotiated rather than mechanically cascaded. A manufacturing unit may contribute through changeover reduction, procurement through supplier responsiveness, and product engineering through design-for-manufacturability. The objective remains shared, but the means reflect local knowledge.

Execution takes place through projects, daily management, leader standard work, and cross-functional coordination. Reviews should examine both results and the quality of the management process. When a target is missed, the question is not simply who failed. Leaders should ask what was learned, whether the assumption was valid, whether resources were adequate, and whether the countermeasure addressed the system rather than its symptoms.

The cycle ends with reflection. Annual reviews should identify which assumptions held, which experiments generated evidence, what capabilities were developed, and what should be stopped. This reflection prevents the next planning cycle from becoming a repetition of the previous one.

Catchball: Strategy as Dialogue

Catchball is the dialogue through which objectives, measures, methods, and resources move between levels of the organization. The metaphor suggests that a proposal is passed back and forth until it is understood, feasible, and owned by the participants. It is not a ceremonial approval process and should not be confused with simple downward communication.

Effective catchball tests several questions. Is the target meaningful to the customer and the organization? Can the responsible unit influence it? Are definitions and baselines consistent? What support is needed from other functions? Which conflicts among objectives must be resolved? What unintended consequences could the measure create?

Catchball improves strategy in two ways. First, it reveals implementation knowledge that senior leaders may not possess. Second, it builds commitment because people participate in shaping the work. However, participation does not mean that every target is negotiable without limits. Leadership retains responsibility for direction and resource trade-offs. The quality of catchball depends on openness combined with decision discipline.

A common failure is pseudo-catchball: leaders announce fixed targets, invite comments, and then proceed unchanged. Another failure is endless negotiation, in which dialogue becomes a means of avoiding commitment. A mature process establishes deadlines for negotiation, records assumptions, and makes unresolved decisions visible.

X-Matrix and Related Planning Tools

The X-matrix is a visual planning device often used in Hoshin Kanri. It links long-term breakthroughs, annual objectives, improvement initiatives, measures, and responsible individuals. Its value lies in showing relationships and potential overload. It can reveal, for example, that five projects depend on the same technical specialist or that an annual target has no supporting initiative.

The X-matrix is not a substitute for strategic thinking. Poorly chosen objectives remain poor when placed in a sophisticated diagram. Nor should the matrix become an administrative document updated only before executive reviews. It is most useful when treated as a living representation of choices, dependencies, and accountability.

Other useful tools include a strategy deployment table, an A3 for each major objective, a portfolio kanban for initiatives, a policy deployment calendar, and a benefits-realization register. The tool should follow the management need. A small organization may require only a one-page deployment sheet and a weekly review board; a multinational enterprise may need integrated digital planning and dependency management.

Tiered Management and the Connection to Daily Work

Tiered management creates linked review levels. A team may review safety, quality, delivery, cost, and people issues each shift. Departmental leaders may review cross-team constraints daily. Site or business-unit leaders may review strategic initiatives weekly or monthly. Senior executives may review enterprise priorities and resource conflicts at longer intervals.

The purpose of tiers is not to multiply meetings. It is to ensure that information and decisions travel at the speed required by the problem. Issues should be solved at the lowest competent level, while unresolved barriers are escalated with facts and a clear request. Each tier needs a defined purpose, standard agenda, visual information, decision rights, and escalation rules.

Tiered management is effective when it connects three forms of work:

1. Daily management, which keeps current processes stable and exposes abnormalities.

2. Improvement management, which develops countermeasures and experiments.

3. Strategic management, which directs resources toward future capability and performance.

A tiered system fails when meetings focus only on reporting. Reports should lead to decisions, problem solving, or learning. It also fails when indicators are disconnected across levels. A team may be praised for maximizing utilization while the value stream suffers from excess inventory and delayed customer response. Measures must therefore be linked to flow and customer outcomes rather than isolated departmental efficiency.

Designing a Lean Transformation Portfolio

Lean transformation is rarely one project. It is a portfolio of related interventions involving processes, technology, capability, leadership behavior, organization design, and supplier or customer relationships. Portfolio thinking helps leaders manage interactions among initiatives and avoid treating each one as an independent project.

A transformation portfolio normally contains four categories. First are performance initiatives that address measurable customer or operational problems. Second are capability-building initiatives, such as leader development, problem-solving education, coaching systems, and standardized work for management. Third are enabling initiatives involving data, equipment, information systems, or facility design. Fourth are governance and culture initiatives that establish review, accountability, recognition, and learning mechanisms.

Prioritization should consider strategic contribution, customer impact, urgency, feasibility, risk reduction, interdependence, and resource demand. A financially attractive project may be unsuitable if it consumes scarce capability needed for a more urgent safety or reliability problem. Similarly, a low-visibility capability initiative may be essential because it enables several performance projects.

Portfolio governance should distinguish three decisions: whether an initiative should begin, how it should be resourced and sequenced, and whether it should continue, change, pause, or stop. Continuing every initiative creates congestion and disguises failure. Stop criteria should be agreed in advance, especially for experiments with uncertain outcomes.

Benefits should be defined carefully. A reduction in labor hours is not automatically a cash saving if staffing remains unchanged. Benefits may include released capacity, improved service, avoided risk, lower working capital, better quality, or increased employee capability. Finance and operational leaders should agree on benefit definitions before results are reported.

Maturity Assessment as a Strategic Diagnostic

Maturity assessment helps an organization understand its current capability and select an appropriate transformation path. It should be used diagnostically, not as a ranking device. A high score can create complacency, while a low score can encourage cosmetic compliance if the assessment is treated as an inspection.

A practical maturity model may examine five dimensions:

• Purpose and alignment: whether lean priorities are connected to customer value and strategy.
• Process control and flow: stability, standard work, visual management, and abnormality response.
• Problem-solving capability: use of evidence, root-cause analysis, experimentation, and learning.
• Leadership system: leader standard work, coaching, gemba engagement, and decision behavior.
• People and culture: psychological safety, involvement, skill development, and respect for people.

Levels might range from fragmented activity, through managed practice and integrated deployment, to adaptive capability. Evidence should include observation, interviews, performance trends, problem-solving records, and employee experience—not merely the presence of posters or completed forms.

Assessment results should lead to a small number of development priorities. If leaders score poorly on coaching, adding more technical tools may produce little benefit. If processes are unstable, launching advanced flow experiments may be premature. Maturity is contextual: a highly capable laboratory may require a different system from a high-volume factory or a public-service organization.

Transformation Governance and Leadership Responsibilities

Governance is the system through which authority, accountability, information, and escalation are organized. A lean transformation governance structure commonly includes an executive sponsor, a transformation steering group, value-stream or business-unit owners, initiative leaders, improvement coaches, and frontline teams.

The executive sponsor protects the purpose of the transformation, resolves major trade-offs, and ensures that the effort is not treated as a temporary campaign. The steering group manages the portfolio, dependencies, risks, and resource conflicts. Value-stream owners are accountable for end-to-end performance rather than a single functional metric. Initiative leaders manage experiments and benefits. Coaches develop capability rather than permanently solving problems for the organization.

Governance should clarify the difference between accountability and responsibility. A senior leader may be accountable for an enterprise objective, while several teams are responsible for specific contributions. Decision rights should specify who can alter scope, approve resources, accept risk, and stop an initiative.

Leader behavior is especially important. Leaders who demand results but punish the discovery of problems create concealment. Leaders who ask for evidence, go to the workplace, challenge assumptions respectfully, and follow up on countermeasures reinforce a learning system. Governance is therefore cultural as well as structural.

Digital tools can support governance through integrated dashboards, workflow systems, electronic A3s, process mining, and automated alerts. These tools are valuable when they improve visibility and reduce administrative work. They are harmful when they encourage surveillance, metric gaming, or the belief that a dashboard represents reality without direct observation. Data definitions, access rights, cybersecurity, privacy, and model transparency require explicit attention, particularly when artificial intelligence is used to prioritize cases or predict process risk.

Change Management, Resistance, and the Human System

Lean transformation changes routines, authority, expertise, workload, and sometimes employment expectations. Resistance is therefore not simply irrational opposition. It may signal fear of job loss, previous failed programs, unclear priorities, excessive workload, loss of professional autonomy, or legitimate concern about customer and safety risks.

A change plan should address four questions: why is change necessary, what will change, how will people participate, and what support will be provided? Communication must be continuous and two-way. Training should be linked to actual work and followed by coaching. Early initiatives should produce credible evidence without creating unrealistic promises. Recognition should reward learning, teamwork, and problem exposure—not only numerical target achievement.

Several predictable failure modes deserve attention. “Tool-first” transformation introduces lean methods without clarifying the problem. “Event-driven” transformation conducts workshops but does not change management routines. “Cascade-only” deployment imposes targets without catchball. “Metric substitution” rewards local indicators that damage total flow. “Project overload” launches more initiatives than the organization can absorb. “Leadership exemption” asks employees to follow standards while managers ignore their own. “Permanent pilot” demonstrates success in one area without building replication capability.

Countermeasures include limiting priorities, sequencing change, protecting improvement time, establishing psychological safety, involving affected employees in design, and conducting regular checks of adoption and unintended consequences. Resistance should be analyzed using facts: where does it occur, what behavior is observed, what interests are threatened, and what evidence would alter the position?

Illustrative Case: Meridian Medical Devices

Background

Meridian Medical Devices, a fictional mid-sized manufacturer, produces sterile diagnostic components for hospitals. Its stated strategy was to become the most reliable regional supplier. Sales growth had increased product variety, but delivery reliability had fallen, expediting costs had risen, and employees were experiencing frequent schedule changes.

Situation and Problem

The executive team initially proposed twelve improvement projects, including automation, supplier reduction, warehouse redesign, visual management, and a new planning system. Departments selected projects independently. After six months, activity was high but performance had not improved. Production maximized batch efficiency, purchasing negotiated larger order quantities, and customer service promised dates without visibility of capacity. No single leader owned the end-to-end order process.

Analysis

A value-stream review showed that the main constraint was not machine speed but unstable order prioritization and lengthy release decisions. The organization also lacked a common definition of on-time delivery. The maturity assessment indicated reasonable technical problem-solving skills but weak strategic alignment, cross-functional ownership, and tiered escalation. Interviews revealed that employees avoided raising risks because previous reviews focused on blame.

Approach

The executive team reduced the transformation portfolio to three priorities: improve on-time delivery, reduce quality escapes, and build a reliable daily management system. Through catchball, the on-time objective was translated into contributions from sales, planning, production, quality, and purchasing. A value-stream owner received authority to resolve cross-functional sequencing conflicts.

A tiered review system was introduced. Frontline teams reviewed abnormalities at the start of each shift; the value-stream team reviewed constraints daily; the steering group reviewed trends, dependencies, and resource decisions weekly. A target condition described a stable order-release process, a visible priority rule, and rapid escalation of material and quality risks.

The portfolio used a simple A3 for each priority and a visual board showing initiative status, expected benefits, dependencies, and stop decisions. Finance agreed that released capacity and avoided expediting would be tracked separately from cash savings. Leaders received coaching in asking process-focused questions and conducting gemba reviews.

Outcome

After the first planning cycle, Meridian had not solved every delivery problem, but the organization had clearer priorities, fewer competing projects, faster escalation, and more consistent definitions. Some experiments were stopped when they failed to address the constraint. Employees reported that problems were more visible and that cross-functional decisions were less dependent on informal relationships. The case demonstrates that governance and alignment can improve before all outcome measures reach their final targets.

Learning Points

The case illustrates five lessons. First, strategic focus is more valuable than a large project inventory. Second, end-to-end ownership is necessary when customer outcomes cross functions. Third, catchball improves feasibility and commitment. Fourth, leading indicators such as escalation quality and adherence to release rules help manage transformation before lagging results appear. Finally, governance should support learning and stopping, not merely authorize continuation.

Ethical, Professional, and Governance Considerations

Lean strategy must respect people as participants in value creation, not merely as variable costs. Workforce reductions presented as the primary purpose of lean can destroy trust and discourage problem reporting. If productivity releases capacity, leaders should consider redeployment, service improvement, reduced overtime, skill development, or natural attrition before treating job elimination as the default outcome.

Metrics must be transparent and contestable. Employees should understand how measures are defined and how they will be used. Data collected through digital systems should be proportionate, secure, and consistent with privacy obligations. Automated recommendations should be reviewed for bias and should not replace professional judgment in safety-critical decisions.

Governance also requires attention to regulatory and quality requirements. In medical, aerospace, financial, food, and public-service settings, a rapid improvement cannot bypass validation, traceability, segregation of duties, or statutory controls. Lean thinking seeks to remove waste, not necessary control. The correct question is whether a control protects value and risk effectively, not whether it adds an administrative step.

Emerging Directions

Several developments are shaping lean strategic management. Organizations are increasingly combining Hoshin Kanri with agile portfolio practices, using shorter planning cycles while preserving long-term direction. Process mining and real-time operational data can reveal delays and variation, but interpretation still requires process knowledge. Digital twins and simulation can test capacity and flow alternatives before physical changes are made. Artificial intelligence may support anomaly detection, forecasting, and prioritization, yet its use should remain transparent and subject to human review.

Sustainability is also becoming a strategic deployment concern. Energy use, carbon emissions, material circularity, water consumption, and social impact can be incorporated into value-stream objectives rather than treated as separate reporting exercises. Resilience has gained importance as well: organizations increasingly evaluate supplier concentration, recovery time, information visibility, and the ability to reconfigure processes under disruption.

These developments do not replace lean principles. They increase the need for clear purpose, sound problem definition, disciplined experimentation, and responsible governance.

Best Practices for Lean Strategic Deployment

Effective organizations generally follow several practices:

• limit breakthrough priorities and make trade-offs explicit;
• define customer-centered outcomes and credible target conditions;
• use catchball to test assumptions, capacity, dependencies, and ownership;
• connect strategic priorities with daily management and leader standard work;
• govern a portfolio rather than approving disconnected projects;
• combine lagging results with leading measures of capability and behavior;
• assess maturity through evidence, observation, and employee experience;
• establish stop, escalate, and revise decisions in advance;
• protect psychological safety and treat resistance as information;
• validate benefits with operational and financial owners; and
• reflect formally so that each planning cycle produces organizational learning.

Chapter Summary

Lean strategy connects organizational purpose with customer value, breakthrough objectives, annual priorities, and daily management. Hoshin Kanri provides a cyclical system for making this connection through strategic choice, catchball, deployment, execution, review, and reflection. The X-matrix and related tools can clarify relationships, but they cannot replace judgment or dialogue.

Tiered management links frontline abnormalities to higher-level decisions and prevents strategy from becoming detached from work. Transformation portfolios integrate performance improvement, capability development, enabling technology, and governance initiatives. Maturity assessment identifies the capabilities that must be developed before additional tools or projects are introduced. Governance defines accountability, decision rights, resource allocation, escalation, and learning.

Successful transformation recognizes the human system. Resistance may reveal legitimate risks, overload, or distrust. Ethical lean leadership protects dignity, transparency, safety, privacy, and professional judgment. Digital technologies, sustainability, resilience, and agile planning are emerging applications, but they remain effective only when grounded in clear purpose and disciplined problem solving.

Key Terms

Purpose: The fundamental reason an organization exists and the value it seeks to create.

Breakthrough objective: A significant strategic result requiring more than routine incremental improvement.

Annual priority: A time-bound objective selected for achievement during a planning cycle.

Hoshin Kanri: A management system for deploying, executing, reviewing, and learning from strategic priorities.

Policy deployment: The translation of strategic intent into coordinated objectives, actions, measures, and accountability.

Catchball: Two-way dialogue through which objectives, methods, resources, and measures are negotiated across organizational levels.

Target condition: A description of the desired future process state and performance.

X-matrix: A visual tool linking strategic objectives, annual priorities, initiatives, measures, and owners.

Tiered management: Linked review levels that enable escalation, coordination, and decision making at appropriate organizational layers.

Daily management: Routine management of standards, abnormalities, performance, and immediate corrective action.

Leader standard work: Defined leadership routines that sustain alignment, observation, coaching, and follow-up.

Transformation portfolio: A coordinated collection of improvement, capability, enabling, and governance initiatives.

Maturity assessment: A structured diagnosis of an organization’s current capability and development needs.

Value-stream owner: A person accountable for end-to-end performance across functional boundaries.

Leading indicator: A measure of activity, capability, or behavior that influences future outcomes.

Lagging indicator: A measure of performance results observed after processes have operated.

Benefits realization: The disciplined confirmation that intended operational, financial, customer, or risk benefits have occurred.

Psychological safety: A shared belief that people can raise concerns, questions, and mistakes without inappropriate punishment.

Governance: The structures and processes through which authority, accountability, decisions, resources, and risks are managed.

Review Questions

Short Answer Questions

1. What is the relationship between breakthrough objectives and annual priorities?

2. Define catchball and explain why it is more than downward communication.

3. What is the purpose of tiered management?

4. Distinguish a leading indicator from a lagging indicator, giving one example of each.

5. Why should a transformation portfolio include capability-building initiatives?

Long Answer Questions

1. Explain the Hoshin Kanri cycle from strategic review through reflection and learning.

2. Discuss how the X-matrix can support strategic alignment and identify its limitations.

3. Explain how governance structures should allocate accountability, responsibility, decision rights, and escalation.

4. Describe a maturity-assessment approach for evaluating lean leadership, process capability, problem solving, and culture.

5. Analyze the principal human and ethical risks associated with lean transformation and recommend management responses.

Analytical / Application Questions

1. An organization has fifteen active lean projects, declining delivery performance, and conflicting departmental metrics. Design a portfolio-prioritization and governance response using concepts from this chapter.

2. A senior team sets a demanding quality target, but frontline employees state that the target is impossible with current equipment and staffing. Show how catchball and target-condition thinking could be used to redesign the deployment process.

3. A digital dashboard reports excellent productivity while customers experience longer lead times. Diagnose the likely strategic and measurement failures and propose a tiered-management response.

22. Multiple Choice Questions with Answers

Question 1

Which statement best describes the strategic role of Hoshin Kanri?

A. It replaces daily management with annual strategic planning.

B. It translates strategic priorities into coordinated action, review, and learning.

C. It limits improvement activity to senior management.

D. It focuses primarily on implementing lean tools in production.

Correct Answer: B. It translates strategic priorities into coordinated action, review, and learning.

Question 2

What is the defining purpose of catchball?

A. To communicate fixed targets from executives to employees.

B. To rank employees according to improvement performance.

C. To negotiate objectives, methods, measures, and resources across levels.

D. To transfer all strategic decisions to frontline teams.

Correct Answer: C. To negotiate objectives, methods, measures, and resources across levels.

Question 3

Which is the strongest example of a breakthrough objective?

A. Conduct a weekly workplace audit.

B. Train supervisors in visual management.

C. Reduce one workstation’s changeover by five minutes.

D. Redesign the order process to provide reliable same-day response.

Correct Answer: D. Redesign the order process to provide reliable same-day response.

Question 4

A tiered-management system is functioning effectively when it:

A. requires every issue to be decided by executives.

B. uses linked reviews to solve issues at the lowest competent level and escalate barriers.

C. measures only financial performance.

D. increases the number of meetings without changing decisions.

Correct Answer: B. uses linked reviews to solve issues at the lowest competent level and escalate barriers.

Question 5

Which item is most appropriately treated as a leading indicator?

A. Annual revenue

B. Customer retention after a service failure

C. Verified closure of problem-solving countermeasures

D. Year-end operating margin

Correct Answer: C. Verified closure of problem-solving countermeasures

Question 6

Why should a transformation portfolio include stop criteria?

A. To ensure that every project ends before the planning cycle.

B. To allow evidence-based discontinuation of initiatives that no longer justify resources.

C. To prevent experimentation under uncertain conditions.

D. To transfer project accountability to finance.

Correct Answer: B. To allow evidence-based discontinuation of initiatives that no longer justify resources.

Question 7

An organization scores highly on lean tools but employees conceal problems from managers. Which maturity dimension is most clearly weak?

A. People and culture

B. Equipment utilization

C. Annual budgeting

D. Supplier concentration

Correct Answer: A. People and culture

Question 8

Which leadership behavior is most likely to support psychological safety during transformation?

A. Punishing teams whenever a target is missed

B. Avoiding workplace observation to preserve managerial authority

C. Asking process-focused questions and treating problems as learning opportunities

D. Rewarding only projects that produce immediate cash savings

Correct Answer: C. Asking process-focused questions and treating problems as learning opportunities

Question 9

A department improves utilization by producing large batches, but customer lead time increases. What failure does this most clearly illustrate?

A. Overuse of catchball

B. Local optimization caused by disconnected measures

C. Excessive maturity assessment

D. Appropriate portfolio sequencing

Correct Answer: B. Local optimization caused by disconnected measures

Question 10

Which is the most appropriate principle for using AI in lean governance?

A. Allow automated recommendations to replace professional judgment in all cases.

B. Use AI without documenting data definitions to preserve flexibility.

C. Use AI for visibility or prediction while maintaining transparency, human review, and data governance.

D. Exclude employees from decisions involving algorithmic prioritization.

Correct Answer: C. Use AI for visibility or prediction while maintaining transparency, human review, and data governance.