Enterprise Deployment, Leadership and Governance

Introduction and Context

Lean Management and Six Sigma are often introduced as methods for improving an individual process, department, or project. Their strategic value, however, appears only when improvement becomes an enterprise capability. Enterprise deployment means selecting, prioritising, funding, executing, and sustaining improvement work across the organisation in alignment with its purpose and strategy.

At enterprise level, improvement is not simply a collection of projects. It is a management system involving strategy deployment, leadership behaviour, governance, measurement, capability development, risk management, ethical conduct, and organisational learning. A technically successful project can still fail strategically if it optimises a local process while damaging customer value, safety, employee wellbeing, regulatory compliance, or end-to-end flow.

This chapter examines how organisations can build a coherent improvement portfolio, establish a continuous-improvement culture, manage resistance, develop competence, and govern standards, audits, ethics, safety, sustainability, and compliance. It also considers the relationship between Lean Six Sigma and relevant ISO management-system requirements.

Learning Objectives

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

1. Align Lean Six Sigma portfolios with organisational strategy and stakeholder requirements.
2. Explain the leadership responsibilities required for enterprise improvement.
3. Design governance arrangements for selecting, controlling, and sustaining improvement work.
4. Diagnose resistance to change and select appropriate responses.
5. Construct a capability-development architecture for continuous improvement.
6. Integrate standards, audits, risk, ethics, safety, sustainability, and compliance into improvement governance.
7. Evaluate the opportunities and limitations of digital technologies and artificial intelligence in enterprise improvement.
8. Apply these principles to a realistic organisational case.

1. From Projects to an Enterprise Improvement System

An improvement project has a defined problem, sponsor, team, scope, measures, and completion point. An enterprise improvement system is broader. It connects four levels of activity:

A mature system prevents three common failures. First, projects are not selected merely because a manager is enthusiastic about them. Second, local optimisation is tested against end-to-end customer and stakeholder outcomes. Third, project closure does not mean that attention to performance ends; ownership is transferred into normal management and daily control.

Enterprise deployment should therefore be understood as a socio-technical system. The technical elements include process analysis, statistical methods, visual management, standard work, data systems, and control plans. The social elements include leadership, trust, participation, psychological safety, learning, incentives, and power relationships. Either dimension can undermine the other. For example, a sophisticated dashboard will not create improvement if employees fear that reporting defects will lead to blame.

2. Strategic Alignment and Improvement Portfolios

2.1 Translating strategy into improvement themes

Organisational strategy normally expresses desired outcomes such as profitable growth, dependable service, resilience, regulatory assurance, innovation, safety, or environmental performance. These broad intentions must be translated into measurable improvement themes. Examples include:

• reducing order-to-delivery lead time;
• improving first-time-right performance;
• reducing serious safety risks;
• increasing equipment availability;
• improving cash conversion through inventory reduction;
• reducing energy and material intensity; and
• strengthening data integrity and regulatory control.

A useful deployment logic is:

Purpose → strategic objectives → critical stakeholder requirements → value streams → improvement themes → projects and daily management.

The logic should work in both directions. Strategic objectives guide project selection, while evidence from processes and customers can reveal that the strategy or its assumptions require revision.

2.2 Critical-to-quality and broader critical requirements

Six Sigma traditionally uses the concept of a critical-to-quality characteristic (CTQ): a measurable feature that strongly influences customer satisfaction or fitness for use. At enterprise level, related requirements should also be identified:

• Critical to delivery (CTD): time, availability, and reliability requirements.
• Critical to cost (CTC): cost, productivity, and resource requirements.
• Critical to safety (CTS): controls that prevent injury or unacceptable exposure.
• Critical to compliance (CTC): legal, contractual, and standard-based obligations.
• Critical to sustainability (CTS): environmental and social performance requirements.

The same output may be critical in several dimensions. A medical device, for example, must be delivered on time, manufactured consistently, documented correctly, and demonstrated to be safe. A portfolio that considers only financial savings is incomplete.

2.3 Portfolio selection

Portfolio selection balances value, risk, urgency, feasibility, and strategic contribution. A simple prioritisation model can support discussion, but it should not replace judgement. One possible weighted score is:

Here, P_i is the priority score for initiative i; S_i is strategic alignment; C_i is customer or stakeholder impact; R_i is risk reduction; F_i is feasibility; E_i is estimated effort or complexity; and w_s, w_c, w_r, w_f, and w_e are non-negative weights. Scores must be defined on consistent scales, such as 0 to 5, and the weights should sum to 1 if the terms are normalised comparably. The equation is a decision aid, not an objective measure of value.

For example, suppose an organisation assigns weights of 0.30, 0.25, 0.20, 0.15, and 0.10 to the five terms. An initiative scored 5, 4, 3, 4, and 2 respectively has:

P = 0.30(5) + 0.25(4) + 0.20(3) + 0.15(4) − 0.10(2) = 2.35

The result is meaningful only in comparison with other initiatives evaluated using the same definitions. Mandatory legal or safety actions should not be rejected because they receive a low financial score; they may require a separate mandatory category.

Portfolio governance should examine dependencies and capacity. Ten high-value projects launched simultaneously may produce less benefit than five projects supported by available subject-matter experts, data analysts, process owners, and change leaders. WIP limits, stage gates, and explicit sequencing protect the organisation from improvement overload.

2.4 Hoshin Kanri and strategy deployment

Hoshin Kanri, or policy deployment, provides a disciplined way to translate breakthrough objectives into aligned annual priorities and local action. Its characteristic features include:

1. a small number of strategically important objectives;
2. measurable targets and owners;
3. vertical and horizontal alignment through dialogue, often called catchball;
4. deployment to functions and value streams; and
5. regular review of both results and learning.

Hoshin should not become a mechanical cascade of targets. Dialogue is essential because local teams possess knowledge about process constraints, trade-offs, and unintended consequences. A target imposed without capacity or method can encourage gaming, concealment, or unsafe behaviour.

3. Leadership for Enterprise Improvement

3.1 Leadership as system design

Senior leaders shape improvement less through speeches than through the systems they design. Their decisions determine whether people have time to solve problems, whether bad news is welcomed, whether incentives encourage end-to-end performance, and whether resources remain available after initial enthusiasm fades.

Effective leaders:

• establish a compelling purpose connected to customers and stakeholders;
• select a limited number of strategic priorities;
• visit processes and ask evidence-based questions;
• distinguish a performance problem from a system problem;
• protect psychological safety and fair treatment;
• remove barriers that local teams cannot remove;
• review leading indicators as well as financial outcomes; and
• hold process owners accountable for sustaining gains.

A leader who demands daily output while removing time for problem solving creates a contradiction. Similarly, a leader who rewards only quarterly cost reduction may unintentionally encourage inventory depletion, deferred maintenance, excessive overtime, or quality deterioration.

3.2 Leadership roles

An enterprise deployment normally requires several complementary roles:

Titles vary across organisations. The essential principle is that improvement expertise must complement, not replace, line ownership. A specialist may facilitate a project, but the operating manager remains responsible for the process and its results.

3.3 Management routines and leader standard work

Leader standard work converts desired leadership behaviour into observable routines. Examples include daily review of abnormal conditions, weekly review of project barriers, monthly portfolio review, periodic process observation, and verification that corrective actions remain effective. The purpose is not bureaucracy; it is to make learning and escalation reliable.

A robust review asks four questions:

1. What was expected?
2. What actually occurred?
3. What was learned about the process or system?
4. What action, owner, and due date follow?

The review should avoid replacing problem solving with status reporting. Red, amber, and green labels are useful only when they trigger appropriate inquiry and support.

4. Building a Continuous-Improvement Culture

Culture is not a slogan or a set of posters. It is the pattern of behaviours that an organisation repeatedly rewards, tolerates, and corrects. A continuous-improvement culture is characterised by respect for people, evidence-based problem solving, visible standards, rapid escalation of abnormal conditions, and learning from both success and failure.

4.1 Psychological safety and just culture

Employees must be able to report defects, near misses, unsafe conditions, and weak controls without unreasonable fear. This does not mean that all conduct is excused. A just culture distinguishes among:

• human error, which calls for redesign, coaching, or improved safeguards;
• at-risk behaviour, which calls for understanding incentives and clarifying expectations; and
• reckless or intentional violation, which may require disciplinary action.

This distinction improves reporting quality and prevents the common error of treating every failure as an individual attitude problem.

4.2 Daily management

Daily management connects strategy with work. Its components may include visual performance boards, standard work, escalation rules, layered process confirmation, short team meetings, skills matrices, and structured response to abnormalities. Indicators should be balanced. A useful set can include quality, delivery, cost, safety, people, and sustainability measures.

Lagging indicators, such as monthly complaints, show outcomes after they occur. Leading indicators, such as completion of preventive maintenance, adherence to critical controls, or response time to abnormalities, provide earlier information. Neither category is sufficient alone.

4.3 Standard work and improvement

Standard work is the current best-known safe method for performing a task under specified conditions. It is not a permanent restriction on creativity. It provides a baseline from which variation can be recognised and improvements tested. After a validated improvement, the standard must be revised, communicated, trained, and audited.

Without standardisation, organisations often experience improvement regression: performance returns to its previous state because the new method was not embedded in training, visual controls, information systems, staffing, or management routines.

5. Resistance, Change and Capability Development

5.1 Understanding resistance

Resistance is frequently described as an employee defect, but it may be a rational response to uncertainty, workload, loss of autonomy, previous failed initiatives, unfair measurement, or a threat to status and employment. Leaders should diagnose the source before selecting an intervention.

Common sources include:

• inadequate understanding of the reason for change;
• lack of confidence or skill;
• conflicting goals and incentives;
• insufficient time, equipment, data, or authority;
• concern about job security or professional identity;
• poor consultation and low trust; and
• fatigue from repeated, poorly sustained programmes.

A practical diagnostic separates willingness, capability, and opportunity. A person may support a change but lack training; possess the skill but lack authority; or have authority but distrust the programme.

5.2 A structured response to change

A credible change approach includes:

1. Case for change: explain the problem using evidence and stakeholder consequences.
2. Participation: involve those who perform and receive the process.
3. Impact assessment: identify effects on roles, workload, risk, technology, and measures.
4. Capability building: provide training, coaching, and practice.
5. Piloting: test assumptions on a controlled scale where risk permits.
6. Feedback and adaptation: treat objections as information, while distinguishing valid constraints from unsupported claims.
7. Reinforcement: align recognition, performance management, standards, and leadership routines.

Communication should be two-way. Repeatedly broadcasting a decision is not the same as engaging people in its implementation.

5.3 Capability architecture

A deployment needs differentiated capability rather than indiscriminate certification. A possible architecture is:

Training should be linked to real work. Competence is demonstrated through application, not attendance alone. A capability system should define learning outcomes, supervised practice, assessment, coaching, recertification where appropriate, and a skills matrix showing organisational coverage.

6. Governance Architecture

Governance is the system by which authority, accountability, decision rights, assurance, and escalation are established. It is distinct from management: management operates processes and projects; governance sets direction, monitors performance, and assures that decisions are responsible and controlled.

6.1 Portfolio stage gates

A typical improvement initiative passes through gates such as:

1. Idea and triage: Is there a real problem, and is it aligned with strategy?
2. Charter approval: Are scope, customer, baseline, sponsor, risks, and measures clear?
3. Define and measure review: Is the problem supported by reliable evidence?
4. Analysis review: Are causes demonstrated rather than assumed?
5. Solution and pilot review: Are risks, costs, human factors, and unintended effects addressed?
6. Implementation review: Are process ownership, training, controls, and benefits credible?
7. Closure and sustainment review: Is performance stable and responsibility transferred?

Gates should be proportionate. A small local improvement does not need the same documentation as a safety-critical enterprise change. However, proportionality must never be used to bypass mandatory legal, safety, or quality controls.

6.2 Benefits and measurement governance

Benefits should be defined before implementation. Financial benefits require agreement on baseline, timing, ownership, and whether the benefit is a hard saving, cost avoidance, released capacity, revenue protection, or working-capital improvement. Non-financial benefits—such as risk reduction, improved safety, or customer trust—should also be measured where feasible.

Measures must have operational definitions. For a defect rate:

The numerator and denominator must refer to the same population and time period, and the counting rule must specify whether one unit can contain multiple defects. A defect rate should not be compared across periods if inspection criteria, product mix, or sampling conditions have changed without adjustment.

For process capability, a common short-term index is:

Here, USL and LSL are upper and lower specification limits, and σ is the within-process standard deviation. The index assumes a stable process and an approximately appropriate distributional model; it does not account for centring. A related index is:

where μ is the process mean. These indices describe capability relative to specifications; they do not prove that the process is stable or that the specifications represent customer needs.

6.3 Three lines of organisational control

A practical governance model separates responsibilities:

• First line: operational managers own risks and controls in daily work.
• Second line: specialist functions such as quality, risk, compliance, safety, and sustainability set frameworks and provide monitoring.
• Third line: internal audit provides independent, risk-based assurance to the governing body.

Independence is important. A person should not provide supposedly independent assurance over controls they personally designed and operate without appropriate safeguards.

7. Standards, Audits and ISO-Related Requirements

Lean Six Sigma and ISO management systems are complementary. Lean Six Sigma supplies structured improvement methods and process discipline. ISO-based systems provide requirements or guidance for management-system structure, risk, documented information, competence, monitoring, corrective action, and continual improvement.

Relevant standards may include:

• ISO 9001: quality management systems and customer-focused, process-based management;
• ISO 19011: guidance for auditing management systems;
• ISO 45001: occupational health and safety management systems;
• ISO 14001: environmental management systems;
• ISO 31000: risk-management principles and guidelines; and
• sector-specific standards, regulations, contractual requirements, and accreditation rules.

Organisations must verify the current edition, applicable jurisdiction, scope, and sector requirements rather than relying on informal summaries. Certification to a standard is not identical to excellent performance, and an audit certificate does not transfer operational accountability.

7.1 Risk-based thinking

Risk-based thinking asks what could prevent intended outcomes, what opportunities exist, how significant the consequences are, and whether controls are effective. A simple risk-priority product can be useful for screening:

where S is severity, O is occurrence likelihood, and D is difficulty of detection, each scored using an agreed ordinal scale. Because ordinal scores are not necessarily interval measurements, the product should not be interpreted as a precise probability or monetary risk. High-severity hazards may require action regardless of the total score.

A stronger approach combines hazard analysis, legal requirements, process knowledge, incident and near-miss data, and expert judgement. Controls should follow the hierarchy of controls in safety contexts: eliminate the hazard where possible, substitute, use engineering controls, apply administrative controls, and use personal protective equipment as the last line rather than the primary solution.

7.2 Auditing for learning and assurance

An effective audit tests whether arrangements are suitable, implemented, effective, and improving. It uses objective evidence such as records, observation, interviews, data, and sampling. Auditors should distinguish:

• conformity: the requirement is met;
• nonconformity: a requirement is not met;
• observation or opportunity: improvement may be possible without a demonstrated requirement breach; and
• good practice: an approach that may be transferable.

Audits fail when they become checklist rituals, focus on document presence rather than operational effectiveness, or punish honest reporting. Corrective action should address both immediate containment and systemic cause. Effectiveness must be verified after sufficient time has passed.

8. Ethics, Safety, Sustainability and Compliance

Enterprise improvement can create ethical hazards. Pressure for savings may encourage manipulation of baselines, suppression of defects, unsafe staffing, excessive surveillance, or transfer of environmental harm to suppliers. Governance must therefore make ethical boundaries explicit.

8.1 Ethical improvement principles

Important principles include:

• truthfulness in data, reporting, and benefit claims;
• informed and respectful participation by employees;
• privacy protection and data minimisation;
• non-discrimination in performance measurement and automation;
• protection of whistleblowers and those reporting hazards;
• fair treatment during redesign, redeployment, or redundancy; and
• refusal to trade safety, legality, or human dignity for speed or cost.

An improvement project should include an ethical-impact question: who benefits, who bears the cost, whose voice is absent, and what safeguards are required?

8.2 Sustainability and systems boundaries

Lean and sustainability can reinforce each other by reducing defects, transport, waiting, energy use, and material consumption. They can also conflict if a narrow local improvement increases total environmental impact—for example, by reducing on-site inventory through frequent emergency deliveries.

Assessment should consider the full value stream and relevant life-cycle effects. Measures can include energy per unit, water consumption, material yield, waste intensity, carbon emissions, injury rates, supplier labour risks, and product end-of-life impacts. The exact boundary, data quality, and calculation method must be stated; otherwise, sustainability claims may become misleading.

8.3 Compliance as a design requirement

Compliance should be built into process design rather than inspected in at the end. Critical requirements should appear in process maps, standard work, training, approval rules, system controls, supplier requirements, and audit plans. Compliance obligations should have owners, evidence requirements, review frequency, escalation thresholds, and change-control mechanisms.

9. Technology, Data and Artificial Intelligence

Digital technologies can support enterprise deployment through real-time process monitoring, electronic work instructions, workflow management, process mining, predictive maintenance, and integrated audit evidence. Artificial intelligence may assist with classification, anomaly detection, document analysis, forecasting, and generation of improvement hypotheses.

However, technology does not eliminate the need for process understanding. Risks include biased training data, false alarms, automation bias, cybersecurity threats, privacy breaches, model drift, opaque decisions, and inaccurate generated content. AI-generated recommendations should be treated as decision support unless validated for the specific use. Human accountability remains essential, particularly in safety-critical, employment, healthcare, financial, and regulated decisions.

Good practice includes data ownership, access control, version management, validation, monitoring, explainability appropriate to risk, human override, incident response, and periodic review of model performance. A digital dashboard should expose problems and enable action; it should not become a substitute for observing the work.

10. Illustrative Case: Northstar Medical Components

Background

Northstar Medical Components, a fictional manufacturer, supplies sterile tubing assemblies to hospitals. Its strategy emphasises patient safety, dependable delivery, regulatory compliance, and profitable growth. Customer complaints have increased, late deliveries are common, and employees report that production targets sometimes conflict with inspection requirements.

Problem

The executive team initially proposed a single project to reduce final-inspection failures. Analysis showed that defects originated across supplier preparation, cutting, assembly, cleaning, packaging, and documentation. The final inspection detected problems but did not create them. A local project could have improved inspection speed while leaving the value-stream causes untouched.

Analysis

A cross-functional team mapped the value stream and stratified defects by type and process step. It found three major patterns:

1. variation in incoming tubing dimensions;
2. inconsistent assembly settings across shifts; and
3. incomplete electronic records during changeovers.

The team also found a governance problem: production, quality, and supply-chain managers had conflicting measures. Production was rewarded for volume, quality for rejection detection, and supply chain for purchase price. No single process owner was accountable for end-to-end delivery and conformity.

Approach and solution

The steering committee created an enterprise portfolio with four linked initiatives:

• supplier capability improvement for critical dimensions;
• standardised assembly parameters and error-proofing;
• electronic changeover controls with mandatory fields; and
• a leadership and daily-management programme for the value stream.

A process owner was appointed. The initiatives were subject to risk review because changes could affect validated production conditions. Operators participated in experiments, and quality engineers verified that proposed changes maintained product requirements. The team used DMAIC: the charter and customer requirements were defined; defect and delay data were measured; causes were analysed; controlled changes were piloted; and control plans, training, and audit checks were implemented.

The organisation changed its review measures to include first-pass yield, on-time-in-full delivery, critical-control adherence, near-miss reporting, supplier capability, and employee improvement participation. Financial benefits were reported separately from capacity release and risk reduction to avoid overstating savings.

Outcome

After six months, first-pass yield improved, late deliveries declined, and changeover-record omissions were reduced. More importantly, the organisation had created a process-owner role, aligned measures, and a governance routine for validating changes. The gains were not attributed to one tool; they resulted from strategic alignment, cross-functional ownership, controlled experimentation, and sustained management attention.

Learning points

1. Final inspection is not a substitute for process capability and quality at source.
2. Conflicting measures can create defects even when individual departments perform well locally.
3. Regulated changes require technical validation and documented control.
4. Improvement benefits include safety, compliance, reliability, and learning—not only financial savings.
5. Sustainability depends on leadership routines and ownership after project closure.

11. Challenges and Limitations

Enterprise deployment is difficult for several reasons. Strategy may be vague or unstable, data may be incomplete, and benefits may be affected by external demand or product mix. Weighted scoring can create false precision. Certification can encourage documentary compliance rather than operational learning. Lean language may be misused to justify job cuts, damaging trust. Six Sigma tools may be applied mechanically when the main issue is political, ethical, or strategic.

There is also a danger of programme fatigue. Organisations that launch successive branded initiatives without closing old work create cynicism. A smaller number of well-supported priorities usually produces greater learning than a large catalogue of poorly resourced projects. Finally, not every problem requires a DMAIC project. Some issues need immediate containment, engineering design, policy clarification, maintenance, negotiation, or executive decision.

12. Best-Practice Principles

A credible enterprise system generally follows these principles:

1. Begin with purpose, stakeholder value, and risk—not with tools.
2. Select a limited portfolio aligned with strategy and organisational capacity.
3. Give process owners authority and accountability for end-to-end outcomes.
4. Make safety, ethics, compliance, and sustainability design constraints.
5. Use data rigorously, while recognising its limitations and human context.
6. Involve front-line employees as knowledge holders and improvement partners.
7. Build capability through coached application rather than certificates alone.
8. Use proportionate governance and independent assurance.
9. Verify benefits and sustainment after implementation.
10. Treat failures and resistance as sources of system learning, while maintaining clear accountability for reckless conduct.

Chapter Summary

Enterprise deployment transforms Lean Management and Six Sigma from isolated projects into an integrated management system. Strategic objectives must be translated into critical stakeholder requirements, value-stream priorities, and a carefully sequenced improvement portfolio. Portfolio decisions should consider strategic alignment, customer impact, risk, feasibility, capacity, and mandatory obligations.

Leadership establishes the conditions in which improvement can succeed. Leaders must model evidence-based inquiry, protect psychological safety, provide resources, align measures, and ensure that process owners sustain results. A continuous-improvement culture depends on daily management, standard work, employee participation, reliable escalation, and learning rather than blame.

Resistance should be diagnosed as a possible response to uncertainty, inadequate capability, conflicting incentives, or low trust. Capability development should be role-specific and demonstrated through application. Governance provides decision rights, stage gates, benefits control, risk management, audit, and independent assurance.

ISO-related management systems, Lean Six Sigma, safety management, sustainability, and ethical governance are mutually reinforcing when integrated around process performance and stakeholder protection. Digital tools and AI can strengthen visibility and analysis, but they introduce risks requiring validation, privacy protection, cybersecurity, human oversight, and accountability. Sustainable enterprise improvement is therefore both a technical and a leadership discipline.

Key Terms

Enterprise deployment: Coordinated organisation-wide application of improvement methods in alignment with strategy.

Improvement portfolio: The collection of improvement initiatives selected and managed as a group.

Hoshin Kanri: A strategy-deployment approach that aligns objectives, measures, actions, and review through organisational dialogue.

Critical-to-quality: A measurable characteristic that strongly affects customer requirements or fitness for use.

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

Leader standard work: Defined leadership routines that make effective management behaviours repeatable.

Psychological safety: A shared belief that people can raise concerns, questions, and errors without unreasonable interpersonal punishment.

Just culture: An approach that distinguishes human error, at-risk behaviour, and reckless conduct.

Daily management: Routine visual and structured control of performance, abnormalities, escalation, and learning.

Standard work: The current best-known safe and effective method for performing a task under specified conditions.

Stage gate: A formal decision point at which an initiative is reviewed before proceeding.

Benefits realisation: The disciplined verification that intended project outcomes have been achieved and sustained.

Risk-based thinking: Considering threats, opportunities, consequences, and controls when designing and managing processes.

Conformity: Fulfilment of a specified requirement.

Nonconformity: Failure to fulfil a requirement.

Corrective action: Action taken to eliminate the cause of a detected nonconformity and prevent recurrence.

Three lines model: Separation of operational ownership, specialist oversight, and independent assurance.

Process capability: The ability of a stable process to meet specified limits consistently.

Sustainment: Continued achievement of improvement results after implementation.

Improvement culture: Shared organisational behaviours and systems that support continual learning and performance improvement.

Review Questions

Short Answer Questions

1. What is the difference between an improvement project and an enterprise improvement system?
2. Define a process owner and explain why the role is important.
3. What is psychological safety, and why does it matter for quality improvement?
4. State two purposes of an improvement portfolio stage gate.
5. Distinguish between conformity and nonconformity in an audit.

Long Answer Questions

1. Explain how Hoshin Kanri can align strategy, value streams, projects, and daily management.
2. Discuss the leadership behaviours required to develop a continuous-improvement culture.
3. Evaluate the role of capability development in sustaining Lean Six Sigma deployment.
4. Explain how ISO-related management systems and Lean Six Sigma can be integrated without reducing either to documentation.
5. Discuss the ethical, safety, and sustainability risks of pursuing improvement through narrow cost reduction.

Analytical / Application Questions

1. An organisation has twelve proposed projects but enough specialist capacity for only five. Design a transparent portfolio-selection process, including strategic, risk, capacity, and compliance considerations.
2. A factory’s defect rate falls, but near-miss reporting also falls sharply. Analyse at least three possible explanations and recommend an investigation and governance response.
3. A predictive-maintenance AI system recommends delaying inspection of a safety-critical asset. Explain what validation, human oversight, risk assessment, and approval controls should be required before any decision is implemented.

Multiple Choice Questions with Answers

Question 1

Which sequence best represents enterprise improvement deployment?

A. Tools → training → slogans → audits

B. Purpose → objectives → stakeholder requirements → value streams → initiatives

C. Audits → certification → projects → strategy

D. Budgets → departments → individual targets → customer needs

Correct Answer: B. Purpose → objectives → stakeholder requirements → value streams → initiatives

Question 2

What is the primary responsibility of a process owner?

A. Conduct every improvement project personally

B. Approve all employee leave requests

C. Own end-to-end process performance and sustainment

D. Perform independent financial audits

Correct Answer: C. Own end-to-end process performance and sustainment

Question 3

A portfolio score uses strategic alignment, customer impact, risk reduction, feasibility, and effort. What is the main limitation of such a score?

A. It cannot support any comparison

B. It replaces the need for judgement and governance

C. It may create false precision if definitions and scales are weak

D. It is useful only for safety projects

Correct Answer: C. It may create false precision if definitions and scales are weak

Question 4

Which response is most consistent with a just culture?

A. Punishing every reported error identically

B. Ignoring intentional reckless violations

C. Distinguishing human error from at-risk and reckless behaviour

D. Discouraging near-miss reporting

Correct Answer: C. Distinguishing human error from at-risk and reckless behaviour

Question 5

What is the main purpose of standard work in continuous improvement?

A. To prevent all future changes

B. To establish a baseline for safe, consistent performance and learning

C. To replace employee judgement in every situation

D. To eliminate the need for process measurement

Correct Answer: B. To establish a baseline for safe, consistent performance and learning

Question 6

In the formula C_p = (USL − LSL) ÷ (6σ), what does σ represent?

A. The process mean

B. The upper specification limit

C. The within-process standard deviation

D. The defect percentage

Correct Answer: C. The within-process standard deviation

Question 7

Which line of control owns risks and controls in daily operations?

A. First line

B. Second line

C. Third line

D. External certification line

Correct Answer: A. First line

Question 8

Why should final inspection not be treated as a complete quality strategy?

A. Inspection always increases process speed

B. Inspection detects outcomes but does not necessarily remove process causes

C. Inspection is unrelated to customer requirements

D. Inspection eliminates the need for standard work

Correct Answer: B. Inspection detects outcomes but does not necessarily remove process causes

Question 9

Which is an appropriate governance concern when using AI in improvement?

A. Assuming generated recommendations are automatically valid

B. Removing human accountability from safety decisions

C. Validating performance, protecting data, and retaining appropriate human oversight

D. Using the model without monitoring for drift

Correct Answer: C. Validating performance, protecting data, and retaining appropriate human oversight

Question 10

What should happen after a corrective action is implemented?

A. The issue should be closed immediately without evidence

B. Effectiveness should be verified after adequate time and evidence

C. The original requirement should be deleted

D. The audit trail should be removed

Correct Answer: B. Effectiveness should be verified after adequate time and evidence