1. Foundations and Language of Change Management

Introduction: Why Change Requires a Common Language

Organizations exist in environments that rarely remain stable. Customers revise their expectations, technologies alter operating models, regulators introduce new requirements, competitors redesign value propositions, and employees seek different forms of work and participation. Yet organizational change is not simply the introduction of a new system, policy, structure, or strategy. It is a process through which an organization moves from an existing state toward a desired future state, while people interpret, experience, support, resist, and institutionalize that movement.

For students of Total Quality Management (TQM), change management is especially important. Quality improvement depends on changing processes, behaviours, measurements, decision rights, and organizational assumptions. A technically superior improvement may fail if employees do not understand its purpose, managers do not reinforce it, or the organization lacks the capability to sustain it. Change management therefore complements quality methods such as continuous improvement, statistical process control, Lean, Six Sigma, and business-process redesign.

The language used to describe change matters. Transformation, transition, innovation, reform, adaptation, development, and turnaround are often used as though they were interchangeable. They are related, but they describe different dimensions of organizational movement. A clear vocabulary improves diagnosis, leadership, communication, governance, and evaluation.

Learning Objectives

After studying this chapter, students should be able to:

1. Define organizational change and distinguish it from transformation, transition, and related concepts.

2. Explain the individual, group, organizational, and interorganizational levels of change.

3. Classify change according to pace, scope, intentionality, continuity, and origin.

4. Analyse internal and external drivers of change and their interaction.

5. Distinguish change management, change leadership, and change agency.

6. Apply major change frameworks critically rather than mechanically.

7. Evaluate likely outcomes, risks, ethical issues, and sustainability requirements in change initiatives.

8. Use change concepts in quality improvement and managerial decision-making.

The Core Meaning of Organizational Change

Organizational change is a significant alteration in an organization’s strategy, structure, technology, processes, culture, people, or relationships. The word “significant” is contextual. A modification that is minor for a multinational corporation may be substantial for a small hospital department. Change may be deliberate, such as implementing a new quality-management system, or emergent, such as adapting gradually to changing customer behaviour.

Change involves both observable and less visible dimensions. Observable changes include a new reporting structure, software platform, production method, or service process. Less visible changes include altered identities, power relationships, assumptions, routines, and expectations. Many initiatives fail because leaders manage the visible design while neglecting the social and psychological consequences.

A useful distinction is between the content, context, and process of change. Content concerns what is changing: for example, a production process or organizational structure. Context concerns the conditions surrounding the change, including history, culture, resources, regulation, competition, and power. Process concerns how the change is planned, communicated, implemented, interpreted, and sustained. The same intervention can produce different results in different contexts because change is not a purely technical event.

Change should also be distinguished from normal variation. In quality management, routine process variation is expected and analysed through appropriate measures. Organizational change, by contrast, alters the conditions under which work is performed. A new workflow may initially increase variation because employees are learning, systems are being configured, and responsibilities are being renegotiated. Managers should not confuse temporary implementation instability with evidence that the intended change is inherently defective.

A Vocabulary for Understanding Change

Change, transformation, and transition

Change refers broadly to movement from one condition to another. It may be incremental or radical, planned or emergent. Transformation is a deeper form of change involving a fundamental shift in organizational identity, operating logic, capabilities, or value creation. Moving from selling physical products to providing integrated digital services may be transformational because it changes customer relationships, revenue logic, skills, and organizational culture.

Transition describes the human and psychological process of letting go of an established way of working, navigating an uncertain intermediate period, and accepting a new way of operating. Change is often external and observable; transition is internal and experienced by people. An organization can install new software in a week, but employees may require months to develop confidence and new work habits.

Adaptation, development, innovation, and turnaround

Adaptation is adjustment to changing conditions in order to preserve or improve organizational fit. Organizational development generally refers to planned, systematic efforts to improve organizational effectiveness and human capability through behavioural and social-science knowledge. Innovation involves introducing or applying a new idea, product, service, process, or business model. Innovation creates a need for change, but not every change is innovative.

A turnaround is a change effort designed to reverse serious decline, often under intense time and resource pressure. Turnarounds may involve cost reduction, leadership replacement, restructuring, or strategic repositioning. Unlike developmental change, turnaround conditions may leave limited opportunity for gradual experimentation.

Change management, leadership, and agency

Change management is the structured planning, enabling, monitoring, and institutionalizing of change so that intended organizational and human outcomes are achieved. It includes stakeholder analysis, readiness assessment, communication, training, implementation planning, resistance management, measurement, and reinforcement.

Change leadership is the process of creating direction, meaning, commitment, and collective action in conditions of uncertainty. Change leadership is not restricted to senior executives. A manager, professional, team leader, or respected peer may lead change by helping others understand why it matters and how it can be achieved.

A change agent is an individual or group that facilitates, sponsors, implements, or advocates change. Change agents may be internal, such as quality managers and supervisors, or external, such as consultants and implementation partners. A change sponsor is a person with sufficient authority and legitimacy to authorize the change, allocate resources, remove barriers, and demonstrate visible commitment. Sponsors and change agents have different roles, although one person may sometimes perform both.

Resistance, readiness, and commitment

Resistance to change is opposition, hesitation, avoidance, or non-compliance arising from perceived threats, loss, lack of trust, low capability, poor timing, or disagreement with the proposed direction. Resistance is not always irrational or malicious. It can reveal operational risks, hidden dependencies, ethical concerns, or inadequate consultation.

Readiness for change is the extent to which individuals or an organization are willing and able to implement a proposed change. Readiness includes perceived need, belief in the proposed solution, leadership support, resource availability, and confidence in implementation capability. Commitment is stronger than awareness: it involves intention, participation, persistence, and willingness to invest effort.

Dimensions and Types of Organizational Change

No single classification captures all change. Managers should classify a change along several dimensions because the classification affects the appropriate leadership and implementation approach.

Incremental and transformational change

Incremental change improves existing systems without altering the organization’s fundamental identity or operating logic. Examples include reducing process cycle time, revising a quality checklist, or adjusting a service script. Incremental change is often compatible with continuous improvement and can be tested through pilots.

Transformational change alters core assumptions, structures, capabilities, or relationships. Examples include a merger that creates a new organizational identity, a hospital shifting from volume-based to value-based care, or a manufacturer becoming a digitally integrated service provider. Transformation normally requires broader stakeholder engagement, significant capability development, and attention to culture and identity.

Planned and emergent change

Planned change begins with an intended future state and a designed intervention. It is common in strategy execution, certification programmes, facility relocation, and enterprise-system implementation. Planned change provides direction, but plans may need revision as new information emerges.

Emergent change develops through local experimentation, learning, negotiation, and adaptation rather than through a fully specified master plan. Frontline employees may discover better methods through problem-solving, and successful practices may spread across the organization. Emergent change can be highly responsive, but it requires boundaries, learning mechanisms, and governance to prevent fragmentation.

Planned and emergent change should not be treated as opposites. A large programme may have a planned purpose and architecture while allowing emergent solutions at operational levels.

Episodic and continuous change

Episodic change occurs as a distinct intervention separated from periods of relative stability. Restructuring and major system replacement are typical examples. Continuous change consists of ongoing adjustments, learning, and refinement. TQM generally emphasizes continuous change through sustained process improvement, though periodic strategic interventions may still be necessary.

Reactive and proactive change

Reactive change responds to an existing problem or external pressure, such as declining quality, a regulatory finding, or loss of market share. Proactive change anticipates future conditions and acts before a crisis becomes evident. Proactive change can create strategic advantage, but it may face greater difficulty in demonstrating urgency because the threat is not yet visible.

First-order and second-order change

First-order change modifies practices within an existing frame of reference. Second-order change challenges the frame itself. For example, improving inspection accuracy is first-order change if the organization continues to define quality as detection of defects. Replacing inspection-based thinking with a system of prevention, process capability, and customer value may represent second-order change.

Levels of Change

Change operates simultaneously at several levels. Problems arise when leaders focus on one level while ignoring the others.

At the individual level, change affects knowledge, skills, motivation, identity, perceptions of fairness, and work habits. Individuals may move through awareness, understanding, experimentation, competence, and reinforcement, although the sequence is not always linear.

At the team or group level, change affects norms, trust, roles, coordination, conflict, and informal influence. A new process may fail because team members continue to reward old behaviours or because responsibilities between departments remain ambiguous.

At the organizational level, change affects strategy, structure, culture, technology, processes, resources, and governance. Organizational change requires alignment among these elements. A company cannot successfully demand customer-centred behaviour while maintaining performance measures that reward only internal efficiency.

At the interorganizational or ecosystem level, change involves suppliers, customers, regulators, professional bodies, alliances, communities, and technology platforms. Quality outcomes frequently depend on this wider network. A manufacturer’s process improvement may be constrained by supplier capability or logistics partners.

The levels are interdependent. An enterprise-wide digital initiative may require individual training, team redesign, organizational governance, and supplier integration. An intervention at one level can create unintended effects at another.

Drivers of Change

Drivers are forces that create pressure or opportunity for movement. They may be external, internal, or jointly produced.

External drivers include technological development, customer expectations, competitive pressure, demographic change, economic conditions, environmental concerns, labour-market shifts, geopolitical events, and legal or regulatory requirements. For quality-oriented organizations, external drivers may include revised standards, product-safety expectations, data-protection obligations, and changes in accreditation requirements.

Internal drivers include poor performance, quality failures, excessive cost, employee dissatisfaction, leadership transitions, strategic ambition, capability gaps, cultural problems, and the need to integrate acquisitions. Internal data such as defect rates, complaints, rework, employee turnover, process delays, and audit findings can reveal a case for change.

Drivers do not automatically justify a particular solution. A fall in customer satisfaction may be caused by process complexity, inadequate training, product design, unrealistic promises, or a mismatch between customer segments and service standards. Effective diagnosis precedes intervention. Treating symptoms without understanding the system can produce expensive but ineffective change.

A useful strategic distinction is between push and pull drivers. Push drivers create pressure away from the current state, such as rising costs or compliance risk. Pull drivers attract the organization toward a desired future, such as a new market opportunity or a stronger quality reputation. Sustainable change often requires both: people need to understand what is unsatisfactory about the present and what is valuable about the future.

Frameworks for Making Sense of Change

Lewin’s three-stage model

Kurt Lewin’s model describes change as a movement through unfreezing, changing, and refreezing. Unfreezing involves challenging existing assumptions, creating awareness of the need for change, and reducing attachment to current routines. Changing involves experimenting with and adopting new behaviours, processes, or structures. Refreezing involves stabilizing the new state through systems, norms, measures, rewards, and leadership attention.

The model is useful because it highlights the need to prepare people and institutionalize results. However, the metaphor of refreezing may appear less suitable in turbulent environments where organizations must remain continuously adaptive. It is therefore better interpreted as establishing sufficient stability and reinforcement rather than achieving permanent finality.

Kotter’s process perspective

Kotter’s widely used framework emphasizes creating urgency, building a guiding coalition, developing a vision and strategic initiatives, communicating the vision, enabling broad action, generating short-term wins, sustaining acceleration, and anchoring new approaches in the culture. Its strength is its attention to sponsorship, coalition-building, communication, and reinforcement. Its limitation is that change rarely follows a perfectly linear sequence; organizations may revisit earlier activities as conditions develop.

ADKAR and the individual experience

The ADKAR framework focuses on individual adoption through Awareness, Desire, Knowledge, Ability, and Reinforcement. It is particularly helpful when managers need to diagnose why an individual or group is not adopting a new practice. For example, an employee may understand the reason for a new quality-control method but lack the ability to perform it; another may have the knowledge but no desire because performance incentives remain inconsistent.

ADKAR should not be used to reduce organizational change to individual attitude. Structural constraints, workload, technology, leadership behaviour, and resource availability strongly influence individual adoption.

The change equation

A diagnostic change equation proposes that change becomes more likely when dissatisfaction with the current state, a clear vision of the future, and practical first steps together exceed the costs or resistance to change. In symbolic form:

D × V × F > R

where D is dissatisfaction, V is vision, F is first steps, and R is resistance. The multiplicative form suggests that if any one of the first three elements is absent or very weak, overall momentum may be insufficient. This is not a predictive mathematical law; it is a managerial thinking tool. It reminds leaders that urgency without direction creates anxiety, vision without action creates frustration, and action without a compelling reason creates compliance without commitment.

Change Outcomes and Measures of Success

Change outcomes should be defined before implementation. An initiative may produce immediate outputs, intermediate adoption, and longer-term outcomes. Outputs include training completed, systems configured, or procedures published. Adoption concerns whether people actually use the new methods. Outcomes include improved quality, lower cost, faster service, stronger safety, better employee experience, or enhanced organizational resilience.

A balanced evaluation may include:

• operational measures such as defects, cycle time, productivity, and reliability;
• customer measures such as satisfaction, complaints, retention, and perceived value;
• people measures such as capability, engagement, workload, turnover, and psychological safety;
• financial measures such as cost of poor quality, revenue, margin, and return on investment; and
• sustainability measures such as durability of new behaviours, audit results, process ownership, and continued improvement.

A successful change is not necessarily one that reaches every original target. It may be successful if it produces valuable learning, avoids serious harm, or creates capabilities that support future adaptation. Conversely, a project delivered on time and within budget may still fail if expected benefits are not realized or if employees create workarounds.

Applying Change Management in Total Quality Management

TQM views quality as an organization-wide responsibility rather than the sole function of an inspection department. This perspective inherently requires change in leadership assumptions, process ownership, supplier relationships, customer listening, measurement, and employee involvement.

A quality manager acting as a change agent should begin with diagnosis. Process data, voice-of-customer information, employee knowledge, audit findings, and root-cause analysis can establish the case for change. The manager should then identify sponsors, affected stakeholders, capability requirements, risks, and measures of adoption. Pilot testing can generate evidence and short-term wins, while standard operating procedures, dashboards, training, audits, and recognition help sustain the improvement.

Resistance should be explored rather than automatically suppressed. A production employee who questions a new inspection step may be identifying an impractical sequence that will delay delivery. A supplier objecting to a new specification may reveal an untested design assumption. Listening does not mean accepting every objection; it means using evidence to distinguish legitimate risk from preference for the status quo.

Illustrative Case: From Inspection Dependence to Process Ownership

Background

The following is a fictional illustrative case. Meridian Components, a medium-sized manufacturer of industrial valves, had historically relied on final inspection to identify defects. Its quality department was respected for technical expertise, but production supervisors viewed quality as the responsibility of inspectors.

Situation and problem

Customer complaints increased after Meridian introduced a new product family. Internal data showed that most defects originated in machining and assembly, but they were discovered only at final inspection. Rework increased, delivery performance deteriorated, and employees experienced conflict between production targets and quality requirements. Senior management announced a project to introduce prevention-oriented quality management.

Analysis

The problem was not simply inadequate inspection. The existing system rewarded output volume, separated quality staff from process owners, and provided limited feedback at the point where errors occurred. Employees understood that defects mattered but did not share a clear model of process capability or ownership. The proposed change was therefore organizational and cultural as well as technical.

Stakeholder analysis identified the plant manager as sponsor, the quality manager as programme lead, production supervisors as critical middle-level leaders, operators as process experts, and key suppliers as external stakeholders. Readiness was uneven: senior managers supported the project, while some supervisors feared that visible defect data would be used for blame.

Approach

The organization created a cross-functional guiding team. It mapped the critical production process, established process measures, trained operators and supervisors in basic problem-solving, and introduced quality-at-source checks. A pilot line used visual standards, rapid feedback, and daily review of defects. Leaders changed performance measures so that production volume was not considered independently of first-pass yield and customer requirements.

Communication focused on the purpose of the change: preventing defects earlier rather than increasing inspection or assigning blame. Operators participated in designing work instructions. Early results from the pilot were shared, including problems that remained unresolved. Supervisors received coaching on how to conduct learning-oriented reviews.

Outcome

The pilot reduced rework and improved visibility of process causes. More importantly, employees began escalating problems earlier and treating quality data as a basis for improvement rather than punishment. The organization then extended the approach to other lines. Some benefits were initially lost when a supervisor was transferred, demonstrating the need to institutionalize the new practices through role descriptions, training, management review, and standard work.

Learning points

The case illustrates several principles. First, a technical quality tool cannot substitute for changes in ownership and incentives. Second, middle managers are central translators of change. Third, participation improves the practical quality of solutions and strengthens commitment. Fourth, short-term improvement is not the same as sustainability. Finally, change should be evaluated through both performance results and evidence that new behaviours have become part of normal work.

Challenges, Risks, and Common Errors

Change initiatives commonly fail through poor diagnosis, vague objectives, insufficient sponsorship, inconsistent leadership behaviour, inadequate resources, weak communication, or failure to engage those affected. Treating communication as a one-time announcement is particularly damaging. People need opportunities to ask questions, interpret implications, and provide feedback.

Another error is overreliance on universal recipes. Frameworks provide useful lenses, but organizational context determines how they should be applied. A crisis turnaround, a participative quality-improvement programme, and a global technology implementation require different balances of speed, consultation, experimentation, and control.

Change fatigue is a further risk. When multiple initiatives compete for attention, employees may become cynical or prioritize short-term survival. Leaders should sequence initiatives, clarify interdependencies, remove obsolete projects, and protect time for learning. Psychological safety is also important: people must be able to report problems and unintended consequences without fear of disproportionate punishment.

Ethical risks include concealing information, manipulating consultation, shifting costs unfairly to vulnerable employees or suppliers, monitoring workers without transparency, and presenting job reductions as purely technical necessities. Fair process requires honest communication, respect, attention to affected stakeholders, and opportunities for meaningful participation. Governance should specify decision rights, escalation routes, data protection responsibilities, benefit ownership, and criteria for stopping or revising a change.

Digital Change and Emerging Developments

Digital technologies increasingly shape both the content and process of change. Enterprise platforms, workflow automation, collaboration tools, process mining, dashboards, and artificial intelligence can reveal bottlenecks and support decision-making. Process-mining tools may identify the difference between documented procedures and actual work patterns. Analytics can help segment stakeholder sentiment, monitor adoption, and detect quality variation.

Technology does not eliminate the human dimensions of change. An AI-supported decision system may alter professional autonomy, introduce bias, create explainability concerns, or require new accountability arrangements. Automated monitoring can improve process visibility but may also undermine trust if employees do not know what is collected or how it is used. Responsible digital change therefore requires data governance, cybersecurity, accessibility, human oversight, and assessment of unintended consequences.

Emerging practice increasingly emphasizes adaptability as an organizational capability rather than change as a series of isolated projects. Organizations are developing product-oriented operating models, agile experimentation, continuous listening, networked leadership, and integrated transformation offices. These approaches can improve responsiveness, but they should not become excuses for weak prioritization or perpetual disruption. Sustainable adaptability combines experimentation with standards, learning with accountability, and local autonomy with strategic coherence.

Principles for Effective Change Practice

Effective change practice rests on several connected principles:

1. Diagnose the system before selecting an intervention.

2. Explain both the reason for change and the practical meaning for affected stakeholders.

3. Align sponsorship, structure, measures, resources, and rewards.

4. Treat employees and customers as sources of knowledge, not merely recipients of decisions.

5. Use pilots and evidence while remaining open to emergent learning.

6. Distinguish legitimate concerns from resistance based only on habit or preference.

7. Develop middle managers and frontline leaders as translators and facilitators.

8. Measure adoption and sustained outcomes, not only project completion.

9. Embed new practices in routines, systems, capabilities, and culture.

10. Govern change ethically, with transparency, fairness, accountability, and respect for human dignity.

Chapter Summary

Organizational change is movement from an existing condition toward a desired condition, involving technical, structural, behavioural, cultural, and relational dimensions. Transformation is deeper and more identity-shaping, while transition describes the human process of letting go, adapting, and adopting. Change management structures implementation; change leadership creates meaning, direction, and commitment; and change agents facilitate movement across organizational levels.

Change can be classified as incremental or transformational, planned or emergent, episodic or continuous, reactive or proactive, and first-order or second-order. It operates at individual, team, organizational, and ecosystem levels. Drivers may be external or internal and may push organizations away from the present or pull them toward a desired future. Frameworks such as Lewin, Kotter, ADKAR, and the change equation provide useful perspectives, but they must be adapted to context.

In TQM, change is essential for moving from inspection and blame toward prevention, process ownership, learning, and customer value. Successful change requires diagnosis, sponsorship, participation, capability development, measurement, ethical governance, and reinforcement. Digital tools can support analysis and adoption, but technology cannot replace human judgement, trust, or responsible leadership.

Key Terms

Organizational change: A significant alteration in an organization’s strategy, structure, technology, processes, people, culture, or relationships.

Transformation: Deep change that alters organizational identity, operating logic, capabilities, or value creation.

Transition: The psychological and human process of moving from an established way of working to a new one.

Change management: The structured planning, enabling, monitoring, and institutionalizing of organizational change.

Change leadership: Creating direction, meaning, commitment, and collective action during change.

Change agent: An individual or group that facilitates, advocates, implements, or supports change.

Change sponsor: An authorized leader who provides legitimacy, resources, decisions, and visible support.

Resistance: Opposition, hesitation, avoidance, or non-compliance related to a proposed change.

Readiness: The extent to which people or an organization are willing and able to implement change.

Commitment: Sustained intention and effort to support and enact a change.

Incremental change: Gradual improvement within an existing organizational framework.

Emergent change: Change that develops through local learning, experimentation, and adaptation.

Continuous change: Ongoing adjustment and improvement rather than isolated interventions.

First-order change: Modification of practices without challenging the underlying frame of reference.

Second-order change: Change that challenges fundamental assumptions, identities, or operating logic.

Organizational development: Planned improvement of organizational effectiveness and human capability using behavioural and social-science knowledge.

Change driver: An internal or external force creating pressure or opportunity for change.

Adoption: The extent to which affected people use and sustain the new practice or system.

Change fatigue: Reduced energy, trust, or engagement caused by excessive or poorly coordinated change.

Psychological safety: A shared belief that people can speak up, ask questions, and report problems without unfair punishment.

Review Questions

Short Answer Questions

1. Distinguish organizational change from organizational transition.

2. What is the difference between a change agent and a change sponsor?

3. Define emergent change and provide one organizational example.

4. Identify the four levels at which organizational change may operate.

5. What is meant by second-order change?

Long Answer Questions

1. Explain the relationship among change management, change leadership, and change agency.

2. Compare incremental change and transformational change, including their implications for TQM.

3. Discuss the internal and external drivers of organizational change and explain why diagnosis is necessary before intervention.

4. Explain Lewin’s model, Kotter’s process perspective, and ADKAR, including one strength and one limitation of each.

5. Discuss the ethical and governance responsibilities of managers leading a major organizational change.

Analytical / Application Questions

1. A hospital introduces an electronic quality-reporting system, but nurses continue using informal paper records. Analyse the problem using the ADKAR framework and recommend actions.

2. A manufacturer has excellent defect-detection data but persistent rework and blame between production and quality departments. Classify the change required and design an appropriate change-management approach.

3. An organization is implementing several digital initiatives simultaneously and employees report change fatigue. Using the concepts in this chapter, propose a prioritization, communication, and reinforcement strategy.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes change from transition?

A. Change is always planned, while transition is always emergent.

B. Change concerns observable movement, while transition concerns the human and psychological process of adapting.

C. Change occurs only at the organizational level, while transition occurs only at the individual level.

D. Change is incremental, while transition is transformational.

Correct Answer: B. Change concerns observable movement, while transition concerns the human and psychological process of adapting.

Question 2

A quality manager has authority to allocate resources, remove barriers, and demonstrate visible commitment to a new quality system. Which role is being described?

A. Change sponsor

B. External auditor

C. Process operator

D. Informal resistor

Correct Answer: A. Change sponsor

Question 3

Which situation is the clearest example of transformational change?

A. Revising a production checklist

B. Reducing approval time for purchase orders

C. Changing from a product-selling business to an integrated digital-services model

D. Updating a customer-service script

Correct Answer: C. Changing from a product-selling business to an integrated digital-services model

Question 4

In the change equation D × V × F > R, what does F represent?

A. Financial return

B. First practical steps

C. Formal authority

D. Future uncertainty

Correct Answer: B. First practical steps

Question 5

A company communicates the need for a new process, but employees lack the skills to perform it. Which ADKAR element is most directly deficient?

A. Awareness

B. Desire

C. Knowledge

D. Ability

Correct Answer: D. Ability

Question 6

Why should resistance to change not automatically be treated as irrational behaviour?

A. Resistance always guarantees project failure.

B. Resistance may reveal operational risks, ethical concerns, or inadequate consultation.

C. Resistance eliminates the need for sponsorship.

D. Resistance proves that the proposed change is transformational.

Correct Answer: B. Resistance may reveal operational risks, ethical concerns, or inadequate consultation.

Question 7

Which example best represents second-order change in quality management?

A. Adding another final inspection point

B. Increasing the inspection department’s staffing

C. Replacing inspection-based thinking with prevention and process ownership

D. Changing the colour of a defect tag

Correct Answer: C. Replacing inspection-based thinking with prevention and process ownership

Question 8

A planned enterprise programme allows local teams to experiment with implementation methods while pursuing a common strategic objective. This illustrates that:

A. Planned and emergent change can coexist.

B. Emergent change must always replace planned change.

C. Local experimentation prevents governance.

D. A strategic objective is unnecessary when teams experiment.

Correct Answer: A. Planned and emergent change can coexist.

Question 9

Which measure provides the strongest evidence that a change has been sustained?

A. The project team published a procedure.

B. All employees attended an introductory presentation.

C. The new practice is reflected in routines, performance measures, and daily behaviour over time.

D. The implementation budget was spent completely.

Correct Answer: C. The new practice is reflected in routines, performance measures, and daily behaviour over time.

Question 10

A digital monitoring system improves process visibility but collects employee data without explaining its use. Which consideration is most directly implicated?

A. Ethical data governance and transparency

B. Incremental product innovation

C. Refreezing as a technical activity only

D. External competitive benchmarking

Correct Answer: A. Ethical data governance and transparency