13. Organizational Change, Development and Digital Transformation

Introduction: Change as a Leadership and Organizational Problem

Organizational change is not merely the implementation of a new structure, technology, policy, or strategy. It is a process through which patterns of meaning, authority, work, identity, and resource allocation are altered. Because organizations are social systems, change affects both formal arrangements and the informal relationships through which work is actually accomplished. A new enterprise platform may alter reporting routines; a merger may challenge professional identities; a sustainability strategy may redistribute power among functions; and an agile operating model may redefine managerial authority. Each is therefore simultaneously a technical, political, cultural, and psychological event.

For leaders, the central challenge is not simply to identify what should change. It is to understand how change can become legitimate, practically workable, and sufficiently owned by those expected to enact it. Doctoral study requires attention to competing theories of change, the quality of evidence supporting intervention, the role of context, and the ethical consequences of managerial action. No single model explains all change. Planned change is useful when objectives and pathways are relatively clear; emergent perspectives are more appropriate when outcomes develop through interaction and learning; dialogic approaches emphasize the narratives and conversations through which organizational realities are reconstructed.

Digital transformation intensifies these issues. It involves the strategic and organizational use of digital technologies to redesign value creation, operating processes, decision systems, customer relationships, and organizational capabilities. Transformation is therefore broader than digitization, which converts analogue information into digital form, and digitalization, which uses digital tools to improve existing processes. Successful transformation requires changes in leadership, governance, skills, culture, incentives, and stakeholder relationships.

Learning Objectives

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

1. Distinguish planned, emergent, and dialogic approaches to organizational change.

2. Diagnose organizational readiness, change capacity, and sources of resistance.

3. Apply organization development principles and intervention methods.

4. Design leadership approaches for digital transformation and agile change.

5. Analyze stakeholder adoption, ethical risks, governance requirements, and implementation outcomes.

6. Critically evaluate change models in relation to context, evidence, power, and organizational consequences.

The Nature of Organizational Change

Organizational change may be classified according to scale, speed, intentionality, and impact. Incremental change modifies existing routines, whereas transformational change alters the organization’s identity, strategy, or dominant operating logic. Episodic change occurs as a relatively bounded intervention, while continuous change is embedded in ongoing adaptation. Some change is deliberate and sponsored by leaders; other change emerges from experimentation, competition, crises, professional practice, or technological development.

A useful distinction is between first-order and second-order change. First-order change improves an existing system without challenging its basic assumptions. Revising a workflow or upgrading software may be first-order change. Second-order change questions the assumptions that define the system itself—for example, replacing a functional hierarchy with a networked product model. The distinction matters because a second-order problem cannot be solved reliably through first-order tools alone.

Change also has a temporal dimension. Organizations may experience a sequence of preparation, transition, and stabilization, but actual change rarely follows a perfectly linear path. Formal milestones can coexist with uncertainty, reversals, local adaptations, and unintended consequences. Leaders must therefore combine direction with inquiry: they provide a compelling orientation while remaining willing to revise methods in response to evidence.

Several concepts are central to diagnosis. Change readiness refers to the extent to which individuals and collective units are psychologically and behaviorally prepared to implement change. Change capacity is the organization’s ability to absorb, coordinate, and sustain multiple changes. Change efficacy concerns confidence in the organization’s ability to execute the required actions. Change valence concerns whether stakeholders perceive the change as worthwhile. These dimensions can diverge: employees may value a transformation but doubt the organization’s capability to deliver it.

Resistance should not be treated automatically as irrational opposition. It may indicate fear of loss, inadequate information, incompatible incentives, low trust, previous experiences of failed change, perceived injustice, or valid concerns about safety and feasibility. Resistance can also be productive when it exposes hidden assumptions or operational weaknesses. The leadership task is to distinguish defensive resistance from informed dissent and to respond proportionately rather than suppressing disagreement.

Three Ways of Understanding Change

Planned Change

Planned change assumes that an organization can identify a problem, define a desired state, design interventions, and guide movement from the current condition toward the desired condition. The classical action-research tradition associated with Kurt Lewin treats change as a cycle of diagnosis, action, evaluation, and learning. Lewin’s unfreezing–changing–refreezing metaphor highlights the need to loosen established patterns, introduce new ways of working, and stabilize useful practices. It is best understood as a heuristic rather than a rigid sequence.

Contemporary planned approaches often use stages such as establishing urgency, forming a guiding coalition, articulating a vision, communicating it, enabling action, generating short-term wins, consolidating progress, and embedding new practices. Such models help leaders coordinate complex programs and make dependencies visible. They are particularly valuable when the organization faces regulatory requirements, a known performance gap, or a major system implementation with defined deliverables.

The limitation of planned change is the assumption that the future can be specified in advance and that implementation is primarily a matter of managerial control. Plans can become symbolic documents detached from local realities. They may also privilege senior perspectives and underestimate informal power. A plan should therefore function as a learning hypothesis, not as a substitute for inquiry.

Emergent Change

Emergent perspectives view change as an ongoing outcome of interactions among people, technologies, institutions, markets, and local experiments. The organization is not moved mechanically from one state to another; rather, new patterns develop through sensemaking, improvisation, negotiation, and adaptation. Managers may influence conditions, but they do not fully control outcomes.

Emergent change is especially relevant in uncertain environments where customer needs, technologies, or competitive conditions are changing faster than formal planning cycles. Small experiments, iterative feedback, distributed decision-making, and rapid learning become more important than detailed prediction. The leader’s role shifts from commander to architect of conditions: clarifying boundaries, protecting experimentation, removing obstacles, and helping participants interpret evidence.

Emergence does not mean absence of leadership or strategy. Without priorities, resources, and decision rights, experimentation may produce fragmentation. Effective emergent change combines strategic intent with local autonomy and disciplined reflection. Leaders must ask which experiments deserve scaling, which should be stopped, and how learning will be transferred across organizational boundaries.

Dialogic Change

Dialogic change emphasizes the role of language, identity, narratives, and collective meaning. Organizations are sustained through conversations about what is real, valuable, possible, and legitimate. Change occurs when dominant narratives are questioned and new accounts of the organization become sufficiently credible to guide action.

Appreciative inquiry illustrates a dialogic approach by inviting participants to identify moments of organizational excellence, imagine desirable possibilities, design new arrangements, and commit to action. Other dialogic practices include open-space meetings, future search, large-group interventions, storytelling, and structured dialogue across stakeholder groups. These methods are not simply communication techniques. They seek to alter the interpretive frames through which organizational members understand their work.

Dialogic change is powerful where identity, trust, and meaning are central—for example, during mergers, cultural renewal, professional transformation, or the development of a new organizational purpose. Its limitation is that dialogue can become superficial if power differences are ignored. A meeting in which all voices are formally invited may still reproduce hierarchy if some participants control resources, agenda setting, or the consequences of speaking.

Comparing the Approaches

The three approaches should not be treated as mutually exclusive. A digital transformation may require planned governance and architecture, emergent experimentation with users, and dialogic work to redefine professional identity. The appropriate combination depends on the degree of uncertainty, the nature of the problem, the distribution of expertise, and the consequences of failure.

| Dimension | Planned | Emergent | Dialogic |

|---|---|---|---|

| View of change | Designed movement toward an intended state | Ongoing adaptation and pattern formation | Reconstruction of meaning and identity |

| Leadership emphasis | Direction, coordination, implementation | Enabling, experimentation, learning | Conversation, inclusion, sensemaking |

| Best suited to | Clear requirements and defined outcomes | High uncertainty and complex interdependence | Identity, culture, and contested meaning |

| Major risk | Overcontrol and false certainty | Fragmentation and lack of coherence | Symbolic participation without power sharing |

A doctoral analysis should ask not which model is universally superior, but what each model makes visible and what it conceals.

Organization Development as a Change Discipline

Organization development (OD) is a planned, values-based, and evidence-informed effort to improve organizational effectiveness, health, and capacity through interventions in processes, relationships, structures, and culture. OD traditionally emphasizes participation, human dignity, inquiry, collaboration, and the alignment of organizational performance with the experience of members.

The OD process commonly begins with entry and contracting. The practitioner and sponsoring group clarify the presenting issue, authority, expectations, confidentiality, access to data, and criteria for success. Diagnosis follows, using interviews, surveys, observations, documents, network analysis, or performance data. Diagnosis should examine multiple levels: individual experience, team dynamics, intergroup relations, organizational systems, and institutional context.

Feedback and joint sensemaking are crucial. Data are not self-interpreting; participants must examine what findings mean, whose perspective is absent, and how the diagnosis relates to action. Interventions may include team development, process consultation, conflict facilitation, coaching, restructuring, work redesign, leadership development, culture work, or strategic dialogue. Evaluation should assess both outcomes and process: what changed, for whom, through which mechanisms, and with what unintended effects.

OD differs from simplistic culture change programs that attempt to impose preferred values through slogans or workshops. Culture is reproduced through recruitment, promotion, incentives, routines, technology, stories, and leadership behavior. If leaders demand collaboration while rewarding individual competition, formal messaging will have limited credibility.

Diagnosing Readiness and Resistance

A practical diagnosis begins by mapping the change system. The leader should identify sponsors, affected groups, implementers, opinion leaders, vulnerable stakeholders, external regulators, suppliers, customers, and parties with veto power. A stakeholder map should assess influence, interest, likely benefits, likely losses, current attitude, and required behavior.

Readiness can be examined through five questions:

• Do stakeholders understand why change is necessary?
• Do they believe the proposed future is desirable and legitimate?
• Do they trust the sponsor and implementation process?
• Do they possess the skills, time, resources, and authority required?
• Are systems of reward, measurement, and accountability aligned with the new behavior?

These questions prevent leaders from interpreting non-adoption as a motivation problem when it may actually be a design or capability problem. Resistance analysis should distinguish cognitive resistance, emotional resistance, behavioral resistance, and structural resistance. For instance, a team may agree intellectually with automation but delay adoption because performance metrics still reward the old manual process.

Readiness assessment should use mixed evidence. Surveys can identify broad patterns, interviews can reveal ambiguity and fear, process data can expose bottlenecks, and network analysis can show who actually influences adoption. Ethical practice requires transparency about how data will be used. Anonymous feedback loses credibility if employees suspect that responses will be used for individual surveillance.

Digital Transformation and the Reconfiguration of Work

Digital transformation changes more than tools. It may alter value propositions, customer access, organizational boundaries, roles, decision rights, and the location of expertise. Cloud platforms can enable scalable collaboration; data analytics can shift decisions from intuition toward evidence; artificial intelligence can automate classification, prediction, or content production; robotic process automation can reduce repetitive work; and digital twins can support simulation in industrial contexts.

The transformation challenge is socio-technical. Technology must fit work practices, skills, governance, and user expectations. A technically successful implementation may still fail if the system increases workload, undermines professional judgment, produces opaque recommendations, or does not integrate with existing processes. Leaders should therefore treat users as co-designers rather than passive recipients.

A transformation architecture normally includes several connected layers: strategic intent, customer or citizen value, operating model, process design, data and technology infrastructure, talent and capability, governance, and change adoption. Weakness in one layer can undermine the entire program. For example, a sophisticated analytics platform will not create value if data ownership is unclear or managers lack the authority to act on insights.

Digital transformation also creates ethical and governance questions. Organizations must consider privacy, cybersecurity, data quality, algorithmic bias, explainability, accessibility, intellectual property, labor displacement, and accountability for automated decisions. Compliance is a minimum requirement, not a complete ethical standard. A system may be lawful yet unfair, exclusionary, or inconsistent with professional responsibilities.

Agile Change and Stakeholder Adoption

Agile change applies iterative delivery, short learning cycles, cross-functional collaboration, and frequent user feedback to organizational transformation. Agile methods can reduce the risk of building an elaborate solution that fails to meet real needs. Product backlogs, minimum viable solutions, sprint reviews, retrospectives, and user testing create mechanisms for continuous learning.

Agility should not be confused with speed alone. An organization can accelerate poor decisions. Agile change requires clarity about the problem, empowered teams, rapid access to evidence, psychological safety, and governance that distinguishes reversible from irreversible decisions. It also requires integration with legal, security, risk, procurement, and operational requirements.

Adoption is the process through which stakeholders begin, continue, and institutionalize use of a new practice or technology. Communication is necessary but insufficient. Adoption depends on perceived usefulness, ease of use, social influence, trust, local leadership, compatibility with identity and workflow, and visible reinforcement. A useful adoption pathway moves from awareness to understanding, trial, competence, routine use, and institutionalization.

Leaders can improve adoption by involving representative users early, designing role-specific learning, providing accessible support, identifying local champions, measuring actual use rather than attendance at training, and removing contradictory procedures. The objective is not to secure ceremonial compliance but to create reliable capability and meaningful value.

Leadership, Power, and the Ethics of Change

Change leadership involves direction, interpretation, relationship management, resource allocation, and moral judgment. Leaders must explain why action is necessary without manufacturing crisis, acknowledge uncertainty without creating paralysis, and maintain accountability without punishing reasonable experimentation.

Power is present in every transformation. Change redistributes status, information, autonomy, workload, and career opportunity. A new data system may centralize knowledge previously held by specialists; a restructuring may eliminate managerial roles; automation may benefit customers while increasing surveillance of workers. Leaders who ignore these effects may describe legitimate concerns as resistance.

Ethical change requires procedural fairness, voice, transparency, proportionality, and attention to those who bear disproportionate costs. Where job displacement is likely, responsible organizations should consider reskilling, redeployment, transition support, and honest consultation. In digital systems, governance should define who is accountable when an automated recommendation causes harm. Employees should not be expected to accept opaque systems merely because they are presented as technically advanced.

Common mistakes include announcing a solution before diagnosing the problem, treating communication as persuasion rather than dialogue, launching too many initiatives simultaneously, measuring activity instead of outcomes, underestimating middle managers, ignoring informal networks, and declaring victory after implementation rather than sustained use. Another error is importing fashionable methods without adapting them to organizational context.

An Integrated Framework for Leading Transformation

An integrated approach can be organized around six linked questions:

1. Purpose: What problem or opportunity justifies change, and whose value is being pursued?

2. Context: What history, culture, institutional pressures, and power relations shape the situation?

3. Design: What must change in strategy, structure, processes, technology, roles, and capabilities?

4. Participation: Who must understand, influence, enact, and govern the change?

5. Learning: What evidence will indicate progress, failure, unintended consequences, or the need to adapt?

6. Institutionalization: How will new practices be reinforced through systems, leadership, incentives, and identity?

The framework combines planned clarity, emergent learning, and dialogic meaning-making. It can be used as a diagnostic sequence, but not as a rigid recipe. In uncertain settings, purpose and governance may be clear while design evolves. In identity-sensitive change, participation and dialogue may need to precede final design. In regulated environments, non-negotiable controls may constrain experimentation.

Evaluation should include leading and lagging indicators. Leading indicators include participation quality, capability development, system usability, adoption rates, experiment cycle time, and issue resolution. Lagging indicators include productivity, service quality, customer outcomes, financial performance, employee experience, safety, equity, and resilience. Metrics should be interpreted rather than worshipped: an increase in system logins may indicate adoption, or it may indicate that the new system creates unnecessary work.

Illustrative Case: Meridian Health Network’s Digital Transformation

Background

Meridian Health Network, a fictional regional healthcare organization, operated several hospitals and outpatient clinics. Its patient records were fragmented across legacy systems, appointment scheduling was inconsistent, and clinicians spent substantial time searching for information. The executive team proposed an integrated digital platform with electronic records, predictive scheduling, patient messaging, and an analytics dashboard.

Situation and Problem

The initial program was designed as a planned, technology-led implementation. A central project office selected the platform, established a twelve-month timetable, and prepared standardized training. Executives assumed that the clinical benefits would generate rapid acceptance. During pilot implementation, nurses reported that the interface added documentation time, physicians questioned the reliability of predictive alerts, and administrators feared that transparent performance data would be used for punitive comparisons. Several influential clinicians informally advised colleagues to delay adoption.

Analysis

The program had a strong strategic rationale but weak readiness. Leaders had diagnosed an information problem while neglecting workflow, identity, trust, and power. The proposed system changed professional routines and decision authority. Resistance was therefore not simply opposition to technology. It reflected concerns about patient safety, workload, professional autonomy, and evaluation.

The organization also lacked change capacity. Several other initiatives were competing for the same clinical time, and middle managers had no additional resources to support adoption. The planned model provided direction but insufficient local learning. A dialogic intervention was needed to surface concerns and reconstruct the transformation as a clinical improvement rather than an administrative surveillance project.

Approach

The executive team paused full-scale deployment and established cross-functional design groups involving clinicians, patients, information specialists, administrators, and cybersecurity staff. Each group mapped current workflows and identified high-risk points. A limited number of departments conducted short experiments with scheduling and patient messaging. Clinicians reviewed alert criteria and could recommend removal of low-value notifications.

The project office retained non-negotiable requirements for privacy, security, and data integrity, but allowed local teams to adapt training and workflow. Managers received coaching on responding to concerns and interpreting adoption data. The organization published a decision log showing which suggestions had been accepted, rejected, or deferred and why. Success measures included patient access, documentation time, alert usefulness, safety incidents, user confidence, and continuity of care rather than system activation alone.

Outcome

The revised approach extended the implementation period but increased sustained use. Some features were redesigned or abandoned after user testing. Clinicians reported greater confidence because they could see how decisions were made and how safety concerns were handled. The transformation did not eliminate disagreement; instead, it converted hidden resistance into visible design work. The organization also learned that local champions were effective only when they had protected time and genuine influence.

Learning Points

The case illustrates that planned governance, emergent experimentation, and dialogic engagement can operate together. It also demonstrates that adoption is an organizational outcome, not a communication event. Digital transformation requires attention to professional identity, workload, data governance, and ethical accountability alongside technical performance.

Current Developments and Emerging Questions

Several developments are reshaping change leadership. Generative artificial intelligence is accelerating experimentation but raises questions about reliability, authorship, privacy, employment, and human oversight. Platform-based work is challenging traditional organizational boundaries and complicating accountability. Hybrid work requires leaders to redesign coordination, inclusion, performance evaluation, and organizational culture rather than simply reproduce office routines online.

Organizations are also confronting continuous transformation fatigue. The accumulation of restructurings, system changes, and strategic initiatives can reduce trust and capacity. Sustainable change therefore requires portfolio governance: leaders must sequence initiatives, retire obsolete projects, protect attention, and assess the cumulative burden imposed on employees. Environmental and social pressures are similarly integrating change management with resilience, sustainability, and stakeholder accountability.

Research opportunities remain substantial. Scholars can investigate how algorithmic systems alter managerial authority, how psychological safety affects experimentation, how digital transformation influences inequality, and which forms of participation produce actual power sharing rather than symbolic inclusion. Future research should avoid treating technology as an independent cause and should examine the interaction among technology, institutions, leadership, and human agency.

Best-Practice Principles

Effective change leaders generally:

• diagnose before prescribing;
• distinguish technical problems from adaptive and political problems;
• combine strategic direction with local experimentation;
• involve those who possess operational and professional knowledge;
• make losses, trade-offs, and uncertainties discussable;
• align incentives, metrics, authority, and capabilities with the desired behavior;
• use evidence to learn rather than to punish prematurely;
• protect ethical standards, privacy, safety, and dignity;
• measure sustained outcomes and unintended consequences; and
• institutionalize learning instead of treating change as a project with a final date.

Chapter Summary

Organizational change is a socio-technical process involving strategy, structure, technology, relationships, identity, and power. Planned change offers direction and coordination when objectives are relatively clear. Emergent change emphasizes experimentation, adaptation, and the limits of prediction. Dialogic change focuses on language, narratives, participation, and the reconstruction of meaning. These approaches are complementary rather than universally competing.

Organization development provides an evidence-informed and values-based discipline for diagnosing systems, engaging stakeholders, intervening, and evaluating outcomes. Readiness depends on perceived need, desirability, trust, efficacy, capability, and alignment. Resistance may reveal legitimate risks and should be analyzed rather than automatically suppressed. Digital transformation extends beyond technology to include operating models, skills, governance, data, culture, and stakeholder adoption. Agile change supports iterative learning, but requires disciplined governance. Ethical leadership demands attention to fairness, privacy, accountability, professional autonomy, labor consequences, and unequal distributions of benefit and cost. Sustainable transformation results when new practices are learned, supported, measured, and embedded in organizational systems.

Key Terms

Organizational change: A modification in organizational structures, processes, strategies, technologies, relationships, or meanings.

Transformational change: Change that significantly alters organizational identity, operating logic, capabilities, or strategic direction.

Planned change: A deliberate process that uses diagnosis, intervention, coordination, and evaluation to pursue an intended future state.

Emergent change: Change that develops through interaction, experimentation, adaptation, and local sensemaking rather than complete prior design.

Dialogic change: Change produced through shifts in narratives, conversations, identity, and collective meaning.

Organization development: A values-based, planned, and evidence-informed effort to improve organizational effectiveness and health.

Change readiness: The extent to which individuals or groups are prepared and willing to enact a change.

Change capacity: The organizational ability to absorb, coordinate, and sustain change.

Change efficacy: Confidence that the organization can successfully implement the required change.

Change valence: The perceived desirability or value of a proposed change.

Resistance: Actions, beliefs, emotions, or structural conditions that delay, challenge, or redirect change.

Digital transformation: Strategic organizational change enabled by digital technologies and redesigned operating models.

Digitization: Conversion of analogue information into digital form.

Digitalization: Use of digital technologies to improve or redesign existing processes.

Agile change: An iterative approach based on short learning cycles, cross-functional work, experimentation, and feedback.

Stakeholder adoption: The process through which stakeholders begin, continue, and institutionalize use of a new practice or system.

Socio-technical system: A system in which social arrangements and technical elements jointly shape performance and outcomes.

Institutionalization: The embedding of new practices in routines, systems, incentives, identities, and norms.

Change fatigue: Reduced motivation or capacity resulting from excessive, poorly coordinated, or continuous change demands.

Review Questions

Short Answer Questions

1. Distinguish between digitization, digitalization, and digital transformation.

2. What is meant by change readiness, and how does it differ from change capacity?

3. Identify two characteristics of emergent change.

4. Why can resistance provide useful information to change leaders?

5. What is the purpose of entry and contracting in organization development?

Long Answer Questions

1. Compare planned, emergent, and dialogic change models, including the contexts in which each is most appropriate.

2. Explain how organization development combines diagnosis, participation, intervention, and evaluation.

3. Discuss the socio-technical nature of digital transformation and its implications for leadership.

4. Analyze the relationship between power, professional identity, and resistance during organizational change.

5. Explain how agile change can be governed without undermining experimentation and local autonomy.

Analytical / Application Questions

1. A university introduces an AI-supported student-advising system, but advisors rarely use it. Design a diagnosis of readiness, resistance, capability, and stakeholder adoption.

2. A manufacturing firm wants to replace functional departments with cross-functional product teams. Recommend a blended planned, emergent, and dialogic change strategy and justify your choice.

3. Evaluate the Meridian Health Network case using an ethical and governance perspective. What additional indicators would you use to determine whether the transformation had genuinely succeeded?

22. Multiple Choice Questions with Answers

Question 1

Which situation most strongly supports the use of an emergent change approach?

A. A regulator has specified a deadline and exact compliance requirements.

B. An organization is exploring an uncertain market opportunity through experiments.

C. A company is implementing a standardized payroll system across all units.

D. A board has approved a fixed restructuring plan with defined positions.

Correct Answer: B. An organization is exploring an uncertain market opportunity through experiments.

Question 2

What is the central emphasis of dialogic change?

A. Strict adherence to a predetermined implementation sequence

B. Replacement of human judgment with automated decisions

C. Reconstruction of meaning through conversations, narratives, and participation

D. Reduction of change to financial performance indicators

Correct Answer: C. Reconstruction of meaning through conversations, narratives, and participation

Question 3

Employees value a proposed transformation but doubt that their organization can deliver it. Which diagnosis is most accurate?

A. High change valence and low change efficacy

B. Low change valence and high change efficacy

C. Low change capacity and low change valence only

D. High resistance caused exclusively by poor communication

Correct Answer: A. High change valence and low change efficacy

Question 4

Why should resistance not automatically be treated as irrational opposition?

A. All resistance guarantees successful implementation.

B. Resistance may reveal risks, workload problems, or perceived injustice.

C. Resistance eliminates the need for leadership sponsorship.

D. Resistance proves that the original strategy is correct.

Correct Answer: B. Resistance may reveal risks, workload problems, or perceived injustice.

Question 5

Which activity is most consistent with organization development?

A. Selecting a technology without consulting users

B. Using diagnosis, joint feedback, intervention, and evaluation to improve the system

C. Imposing cultural slogans without changing incentives

D. Measuring only whether employees attended training

Correct Answer: B. Using diagnosis, joint feedback, intervention, and evaluation to improve the system

Question 6

A digital platform is technically reliable but increases documentation time and is rarely used. What does this most clearly demonstrate?

A. Technical performance alone does not ensure stakeholder adoption.

B. User participation always reduces implementation speed.

C. Digital transformation is limited to hardware acquisition.

D. Resistance is necessarily evidence of poor employee motivation.

Correct Answer: A. Technical performance alone does not ensure stakeholder adoption.

Question 7

Which leadership practice best combines planned and emergent change?

A. Fixing every implementation detail before involving users

B. Providing strategic boundaries while allowing local experimentation and feedback

C. Allowing every team to pursue unrelated priorities

D. Avoiding evaluation until the transformation is complete

Correct Answer: B. Providing strategic boundaries while allowing local experimentation and feedback

Question 8

In the Meridian Health Network case, why did clinicians resist the initial implementation?

A. They rejected all forms of digital technology on principle.

B. They lacked any interest in patient outcomes.

C. They were concerned about workload, safety, autonomy, and surveillance.

D. They had been excluded from all communication about the project.

Correct Answer: C. They were concerned about workload, safety, autonomy, and surveillance.

Question 9

Which measure is most likely to indicate sustained adoption rather than ceremonial participation?

A. Number of employees attending an introductory workshop

B. Number of implementation announcements distributed

C. Regular, effective use of the system integrated into work routines

D. Amount of money spent on the technology

Correct Answer: C. Regular, effective use of the system integrated into work routines

Question 10

Which issue is an ethical governance concern in AI-enabled organizational change?

A. Whether the project has an attractive logo

B. Whether automated recommendations are explainable and accountable

C. Whether all experimentation can be eliminated

D. Whether leaders can avoid documenting decisions

Correct Answer: B. Whether automated recommendations are explainable and accountable