2. Evolution and Theories of Organizational ChangeIntroduction and ContextOrganizational change is not a single event but a continuing feature of institutional life. Organizations alter their strategies, structures, technologies, processes, cultures, and relationships with stakeholders in response to internal aspirations and external pressures. In a total quality management (TQM) context, change is particularly significant because quality improvement requires more than installing procedures or measuring defects. It involves reshaping habits, leadership practices, decision rights, employee participation, supplier relationships, and assumptions about what constitutes value for the customer. Theories of organizational change have developed in response to changing views of organizations. Early approaches often treated change as a deliberate intervention designed and controlled by managers. Later perspectives emphasized organizational learning, political negotiation, culture, uncertainty, networks, and complexity. No single theory explains every change situation. A stable manufacturing plant introducing a documented quality system may benefit from a planned approach, whereas a digital platform operating in an unpredictable market may require experimentation and continuous adaptation. This chapter examines the evolution of major perspectives on organizational change. It compares planned and emergent change, episodic and continuous change, systems thinking, complexity perspectives, and organizational development (OD). It also evaluates influential models associated with Lewin, Kotter, ADKAR, McKinsey 7-S, Nadler–Tushman, Burke–Litwin, and related approaches. The central argument is that change models are not universal recipes. They are analytical and practical lenses whose usefulness depends on context, scale, pace, power relations, organizational maturity, and the nature of the desired outcome. Learning ObjectivesAfter studying this chapter, students should be able to: 1. Explain the historical development of organizational change theory. 2. Distinguish planned, emergent, episodic, continuous, systems, complexity, and organizational development perspectives. 3. Critically compare Lewin’s three-stage model, Kotter’s process, ADKAR, and related frameworks. 4. Select an appropriate change perspective for different organizational and TQM situations. 5. Identify the assumptions, strengths, limitations, and ethical implications of major change approaches. 6. Apply change theories to a complex organizational case and formulate a defensible intervention strategy. From Stability and Control to Adaptation and LearningClassical management theories generally assumed that organizations could be designed rationally. Structure, authority, specialization, standardization, and supervision were expected to produce predictable performance. Change was consequently viewed as an interruption to normal operations. Managers diagnosed a problem, selected a solution, communicated a plan, and expected employees to implement it. This view was useful where technologies, markets, and work processes were relatively stable. It also supported important quality practices such as standard operating procedures, statistical control, process documentation, and corrective action. However, it underestimated informal relationships, employee interpretation, professional identity, organizational politics, and the influence of the external environment. Human relations research shifted attention towards motivation, group norms, leadership, communication, and participation. The organization came to be viewed not merely as a technical arrangement but also as a social system. Later, open-systems thinking emphasized that organizations depend on customers, suppliers, regulators, labour markets, technologies, and communities. A change in one part of the system could produce unintended consequences elsewhere. By the late twentieth century, globalization, technological innovation, deregulation, knowledge work, and shorter product life cycles made continuous adaptation increasingly important. Change was no longer limited to occasional restructuring. Organizations were expected to learn, innovate, improve processes, collaborate across boundaries, and respond rapidly to new information. Contemporary approaches therefore combine deliberate direction with local experimentation and learning. Important Concepts and TerminologyOrganizational change refers to a significant alteration in an organization’s strategy, structure, processes, technology, culture, people, or relationships. Change may be intentional or unplanned, incremental or radical, temporary or enduring. A change agent is an individual or group that facilitates, sponsors, designs, or supports change. Change agents may be senior executives, line managers, internal consultants, quality professionals, project leaders, or external advisers. A change sponsor is a person with sufficient authority and legitimacy to authorize change, allocate resources, remove barriers, and demonstrate commitment. Sponsorship is different from project management: a project manager coordinates activities, whereas a sponsor establishes organizational ownership. Change readiness is the extent to which individuals and groups believe that change is necessary, appropriate, feasible, supported, and personally meaningful. Resistance to change is behaviour, communication, or inaction that delays, weakens, challenges, or prevents a change. Resistance may reflect fear, loss of status, workload concerns, ethical objections, inadequate evidence, or poor implementation rather than irrationality. A transformation is a substantial change in an organization’s identity, operating model, capabilities, or value proposition. Transformation generally has broader consequences than process improvement. Organizational learning is the development and use of knowledge that improves an organization’s capacity to act. It includes experimentation, reflection, knowledge sharing, and revision of assumptions. Organizational culture comprises shared assumptions, values, meanings, and patterns of behaviour that influence how work is understood and performed. A system is a set of interdependent elements whose relationships produce outcomes. Systems thinking examines patterns, interactions, feedback, boundaries, and consequences rather than isolated events. An emergent change is a change that develops through ongoing interactions, local adaptations, learning, and responses to circumstances rather than through a fully specified central plan. Planned Change and the Logic of Deliberate InterventionPlanned change assumes that an organization can identify a problem or opportunity, define a desired future state, design interventions, implement them, and evaluate results. The approach is associated with diagnosis, objectives, project governance, communication, training, milestones, and measurement. Planned change is especially appropriate when the desired outcome is reasonably clear and the organization has enough stability to coordinate action. Examples include implementing an ISO-based quality management system, redesigning a production line, introducing a standardized audit process, or replacing a legacy enterprise resource planning system. Its strengths include clarity of purpose, accountability, resource coordination, and the possibility of evaluating progress against explicit criteria. Its limitations arise when managers assume that the future can be predicted accurately, that people will respond mechanically to instructions, or that implementation is merely the final stage of design. A plan can become obsolete when conditions change. It can also create compliance without commitment if employees are excluded from diagnosis and decision-making. In TQM, planned change is valuable for defining quality objectives, establishing process ownership, setting control measures, and deploying improvement projects. Nevertheless, quality improvement cannot be sustained solely through plans. It requires learning at the point where work is performed and the capacity to adjust procedures when evidence reveals a better method. Emergent Change and Organizational LearningThe emergent perspective views change as an ongoing process arising from interaction among people, technologies, routines, power relationships, customers, and environmental conditions. Leaders may influence direction, but they cannot fully determine how change will unfold. Meaning is constructed through conversations and experience; solutions are often refined through experimentation. Emergent change does not imply the absence of leadership or structure. Rather, leadership creates conditions in which useful adaptation can occur. These conditions include psychological safety, access to information, rapid feedback, cross-functional collaboration, permission to test ideas, and mechanisms for scaling successful practices. This perspective is useful when the problem is ambiguous, the environment is uncertain, and local knowledge is essential. For example, a hospital seeking to reduce patient waiting time may establish a broad aim but allow departments to test different scheduling, triage, and information-sharing practices. Learning from these experiments may produce a solution that could not have been designed centrally in advance. The danger is that emergent change can become fragmented or directionless. Local adaptations may conflict, successful experiments may not spread, and employees may experience constant adjustment without a coherent strategic purpose. Effective organizations therefore combine a guiding intent with decentralized learning. Episodic and Continuous ChangeEpisodic change is discontinuous, intentional, and usually associated with a distinct event such as a merger, restructuring, crisis response, major technology implementation, or leadership transition. It often requires mobilization, concentrated resources, and visible decisions. Its risks include disruption, change fatigue, loss of knowledge, and insufficient attention to post-implementation stabilization. Continuous change is ongoing, cumulative, and embedded in everyday work. It includes incremental process improvements, routine problem solving, customer feedback, preventive actions, and adaptation of standards. Continuous change is central to Kaizen and many TQM practices. It does not mean that every activity changes constantly; rather, the organization maintains a capability for repeated, disciplined improvement. The distinction is analytical rather than absolute. An organization may undertake an episodic enterprise-wide digital transformation while simultaneously pursuing continuous improvement in operational processes. Indeed, major change is more likely to succeed when supported by continuous learning before, during, and after the formal project. Systems Thinking and the Whole OrganizationSystems thinking challenges narrow interventions that optimize one department while damaging overall performance. It directs attention to interdependence, feedback loops, delays, system boundaries, and unintended consequences. For example, a purchasing department may reduce unit cost by selecting a cheaper supplier. If the supplier has poor reliability, the organization may experience production stoppages, inspection costs, customer complaints, and increased rework. Local efficiency has produced global inefficiency. A systems perspective would examine total cost, process capability, lead time, quality risk, and customer impact. The systems approach is particularly relevant to TQM because quality is produced by a network of processes rather than by inspection alone. It encourages organizations to examine the relationship between leadership, supplier management, design, production, service delivery, measurement, and customer experience. Tools such as process mapping, causal-loop diagrams, stakeholder analysis, value-stream mapping, and the Plan–Do–Study–Act cycle support this perspective. Systems thinking does not remove the need for specialized analysis. Instead, it places specialist knowledge within a wider account of organizational purpose and performance. Its limitation is that broad analysis can delay decisions or become too abstract unless linked to specific action and measures. Complexity Perspectives on ChangeComplexity perspectives are appropriate when organizations operate as adaptive systems in conditions characterized by uncertainty, nonlinearity, diverse actors, and unpredictable outcomes. In a complex setting, a small intervention may have large consequences, while a substantial investment may produce little effect. Cause and effect become visible only retrospectively or remain contested. Complexity thinking differs from traditional planning in several ways. It emphasizes enabling conditions rather than complete control, patterns rather than isolated events, and experimentation rather than certainty. Leaders may use short learning cycles, safe-to-fail experiments, distributed decision-making, network analysis, and real-time sensing. Complexity does not mean that everything is unknowable. Some organizational situations are complicated but manageable through expertise and planning; others are complex because relationships and responses change as participants learn. The practical challenge is to distinguish between these conditions. Treating a complex cultural transformation as a technical installation can produce failure. Conversely, treating a well-understood compliance requirement as endlessly exploratory can waste resources. In quality management, complexity is evident in healthcare, public services, software ecosystems, and global supply chains. Quality outcomes depend on multiple actors whose goals and behaviours influence one another. Managers should therefore combine standards and controls with feedback, dialogue, and adaptation. Organizational Development: A Humanistic and Participative TraditionOrganizational development is a planned, organization-wide effort to increase organizational effectiveness and health through interventions informed by behavioural science. OD traditionally emphasizes participation, human dignity, open communication, inquiry, collaboration, and alignment between people and systems. Classic OD interventions include survey feedback, team development, process consultation, intergroup development, appreciative inquiry, coaching, role negotiation, and organization-wide meetings. The action-research cycle—diagnosis, action, evaluation, and further diagnosis—illustrates the OD commitment to learning through participation rather than imposing solutions on employees. OD is valuable because it recognizes that sustainable change depends on relationships, meaning, trust, leadership behaviour, and norms. It is particularly relevant when the change concerns culture, collaboration, employee engagement, leadership, or organizational capability. However, OD can be criticized when it underestimates power, structural inequality, economic constraints, or the need for rapid decisive action. Participation itself is not automatically ethical or effective; it must involve genuine influence rather than symbolic consultation. Lewin’s Three-Stage ModelKurt Lewin conceptualized change through the stages of unfreezing, changing, and refreezing. Unfreezing involves creating awareness that existing patterns are inadequate and preparing people to reconsider established assumptions. Changing, sometimes described as movement, involves learning and adopting new behaviours, processes, or ways of working. Refreezing involves stabilizing the new pattern through reinforcement, systems, leadership, and norms. The model’s enduring contribution is its attention to forces that maintain the status quo. A force-field analysis distinguishes driving forces that support change from restraining forces that impede it. Managers may strengthen drivers, reduce restraints, or redesign the situation so that new behaviour becomes easier. Lewin’s model is often criticized for implying that organizations can reach a stable endpoint. In environments characterized by continuous disruption, refreezing may be temporary or inappropriate. Nevertheless, the model remains useful as a conceptual framework for understanding readiness, transition, and institutionalization. In a TQM project, unfreezing might involve evidence of customer complaints and process variation; changing might involve pilot improvements and training; refreezing might involve revised standards, audits, recognition, and management review. Kotter’s Eight-Step ProcessJohn Kotter’s model translates planned change into an eight-step leadership process: establish a sense of urgency; build a guiding coalition; form a strategic vision and initiatives; enlist a volunteer army; enable action by removing barriers; generate short-term wins; sustain acceleration; and institute change. The model highlights leadership, coalition building, communication, empowerment, visible progress, and cultural embedding. It is useful for large-scale change where multiple stakeholders must align around a direction. Short-term wins can create credibility and demonstrate that effort is producing value. Institutionalization connects the change with recruitment, promotion, performance management, and leadership succession. Critics argue that the sequence may be too linear and that urgency can be manufactured in manipulative ways. The model may also appear top-down if the guiding coalition is limited to senior leaders. In practice, the steps often overlap and recur. A coalition may need to be rebuilt when the context changes, and learning from early implementation may alter the vision itself. ADKAR and the Individual Experience of ChangeThe ADKAR model focuses on the individual outcomes required for successful change: Awareness of the need for change, Desire to participate and support it, Knowledge of how to change, Ability to implement new skills and behaviours, and Reinforcement to sustain the change. Its main contribution is to distinguish organizational change from individual adoption. A well-designed system can fail if employees do not understand why it is necessary, lack motivation, have not been trained, cannot perform the new behaviour, or receive incentives to return to old habits. ADKAR is therefore useful for diagnosing adoption barriers and designing targeted interventions. The model’s individual focus is also its limitation. It can understate structural power, organizational politics, competing objectives, and system-level constraints. Employees may possess awareness and ability yet be unable to change because staffing, technology, authority, or workload makes the desired behaviour impractical. ADKAR should therefore complement, not replace, systems and organizational analysis. Other Integrative FrameworksThe McKinsey 7-S framework examines alignment among strategy, structure, systems, shared values, skills, style, and staff. It is useful for diagnosing whether a proposed change is supported by mutually consistent organizational elements. For example, a customer-centric strategy will be weak if performance systems reward only internal efficiency and leaders model command-and-control behaviour. The Nadler–Tushman congruence model views organizational performance as a product of the fit among inputs, transformational processes, and outputs. It draws attention to the alignment of tasks, people, formal arrangements, and informal organization. The Burke–Litwin model links external environment, leadership, mission, culture, management practices, work climate, motivation, and individual or organizational performance. It distinguishes transformational factors from more transactional factors. The Kübler-Ross change curve is frequently used to describe emotional responses such as shock, denial, frustration, exploration, and commitment. It may help managers discuss emotional transition, but it should not be treated as a universal or fixed sequence. Individuals do not necessarily experience every stage, and the model has limited explanatory power compared with evidence-based diagnosis. The Theory of Constraints, appreciative inquiry, design thinking, and agile approaches offer further perspectives. They focus respectively on system bottlenecks, strengths and possibilities, user-centred experimentation, and iterative delivery. These approaches can be integrated with TQM when their assumptions and measures are made explicit. Comparing the Major PerspectivesPlanned change asks, “What future state should be designed and implemented?” Emergent change asks, “How can the organization learn and adapt as the situation unfolds?” Episodic change emphasizes mobilization around a significant event, while continuous change emphasizes routines and ongoing capability. Systems thinking asks how elements interact across the organization; complexity thinking asks how adaptive interactions generate unpredictable patterns. OD asks how people can participate in improving organizational health and effectiveness. These perspectives differ in their assumptions about knowledge, control, leadership, and time. Planned models assume that important objectives can be specified. Emergent and complexity approaches accept that objectives may be refined through learning. Planned approaches often assign leadership a directing role; emergent approaches emphasize enabling, sense-making, and distributed leadership. Systems thinking broadens the unit of analysis, while ADKAR narrows attention to individual adoption. OD places greater emphasis on participation and human processes than many project-based models. A mature change strategy uses contingency rather than ideological loyalty. A regulated change may require formal planning and control. A culture change may require dialogue, participation, and experimentation. A crisis may require strong direction initially, followed by participative recovery. The choice should be based on the nature of the problem, the degree of uncertainty, the level of interdependence, the time available, and the consequences of error. Practical Application in Total Quality ManagementQuality professionals can use change theories in several connected ways. First, diagnosis should identify whether the issue concerns technical design, process capability, behaviour, culture, leadership, incentives, or system alignment. Second, the organization should define quality outcomes in terms meaningful to customers and other stakeholders. Third, leaders should determine which elements require standardization and which should remain open to local adaptation. A quality improvement initiative might combine Lewin’s force-field analysis, Kotter’s coalition-building, ADKAR’s adoption diagnosis, and PDSA experimentation. For example, a hospital introducing electronic medication verification could use evidence of medication errors to unfreeze current practice, establish a multidisciplinary coalition, pilot the system in one ward, train staff, monitor adoption and near misses, remove workflow barriers, and revise procedures based on learning. Sustaining the improvement would require audit feedback, leadership attention, equipment maintenance, and integration with orientation and performance systems. Measures should include both results and change-process indicators. Results may include defect rates, customer complaints, cycle time, safety events, or cost of poor quality. Process indicators may include training completion, use of standard work, participation in improvement meetings, response time to problems, and the number of implemented learning cycles. Measurement should support learning rather than punish employees for reporting problems. Illustrative Case: Meridian Components’ Quality TransformationBackgroundMeridian Components, a fictional medium-sized manufacturer of precision parts, supplied several large equipment producers. Its quality system was formally documented, but customer complaints were increasing. Internal data showed repeated rework, late corrective actions, and disagreement between production and quality departments about the causes of defects. Situation and ProblemThe chief executive initially proposed purchasing an automated inspection system. The quality manager argued that inspection would detect defects but would not address unstable processes, unclear work instructions, or pressure to meet production targets. Employees reported that improvement initiatives had previously been launched with enthusiasm and abandoned after several months. AnalysisA systems analysis identified interactions among production scheduling, machine maintenance, supplier variation, operator training, performance incentives, and the corrective-action process. A force-field analysis found strong drivers, including customer pressure and executive concern, but also restraints: distrust of management, fear that defect data would be used for blame, limited problem-solving skills, and departmental targets that encouraged local optimization. The change was both episodic and continuous. A formal quality transformation was needed, but its success depended on daily learning. The situation was sufficiently uncertain that a completely predetermined solution would be inappropriate. A hybrid approach was selected. Approach and StrategyThe executive formed a guiding coalition including production, quality, maintenance, procurement, engineering, and front-line operators. The coalition developed a clear objective: reduce repeat defects by improving process capability and learning speed, rather than merely increasing final inspection. Using ADKAR, managers assessed awareness, desire, knowledge, ability, and reinforcement among affected groups. Operators understood the customer problem but lacked confidence in statistical problem-solving. Supervisors desired improvement but feared production losses. Training therefore combined practical data analysis with protected time for improvement work. Two production cells conducted PDSA cycles. Teams mapped the process, identified variation sources, tested revised setup procedures, and used visual controls. Early wins included a reduction in setup-related defects and faster escalation of abnormal conditions. The organization then revised incentives so that supervisors were evaluated on first-pass yield and corrective-action quality as well as output volume. OutcomeThe pilot produced measurable improvement and increased confidence in cross-functional problem solving. The company did not assume that the pilot automatically constituted organizational transformation. It reviewed the evidence, adapted the standard work, and extended the approach to other cells. The new routines were reinforced through management reviews, operator involvement in audits, and recognition of useful problem reporting. Learning PointsThe case illustrates why no single model is sufficient. Lewin helped explain the need to challenge established routines and stabilize new practices. Kotter informed coalition building, communication, and short-term wins. ADKAR exposed individual adoption barriers. Systems thinking revealed that incentives and scheduling were contributing to quality problems. Emergent experimentation enabled the organization to discover workable solutions rather than impose an untested design. Challenges, Risks, and Common MistakesOne common mistake is treating a model as a universal sequence. Models simplify reality and may conceal feedback, politics, emotion, and competing interpretations. A second mistake is confusing communication with participation. Informing employees about a decision is not equivalent to involving them in diagnosis or design. Another risk is change overload. When too many initiatives compete for attention, employees may comply superficially, postpone implementation, or become cynical. Leaders should prioritize, retire obsolete projects, and make resource trade-offs explicit. Poor sponsorship is also damaging. Senior leaders may announce change but fail to model it, allocate resources, or remove barriers. Resistance should not automatically be labelled irrational. It may identify safety risks, unrealistic targets, inadequate consultation, or unintended effects on vulnerable groups. Suppressing dissent can produce silent failure. At the same time, consultation without decisions can create frustration. Ethical change management requires listening, explaining the basis of decisions, and providing fair avenues for challenge. Change can also produce unequal impacts. Automation may remove repetitive work but alter employment, skills, surveillance, and autonomy. Restructuring may improve efficiency while weakening psychological safety or increasing workload. Leaders should assess distributional effects, protect confidential information, comply with labour and safety requirements, and avoid using quality data as an instrument of unfair punishment. Digital Change, Analytics, and AIDigital technologies increasingly influence organizational change through workflow automation, collaboration platforms, process mining, predictive maintenance, dashboards, and artificial intelligence. These tools can reveal process variation, identify bottlenecks, and support faster feedback. Process-mining software, for example, can compare the actual sequence of transactions with the intended process and expose rework or delay. Technology does not eliminate the social dimensions of change. A dashboard may make performance visible, but employees may distrust its data, misunderstand its measures, or alter behaviour in undesirable ways. AI-based recommendations may reproduce historical bias, obscure accountability, or encourage overreliance on automated outputs. Governance should therefore include data quality controls, explainability appropriate to the decision, access security, human oversight, and clear responsibility for outcomes. Digital initiatives should be evaluated not only by installation or usage but by realized value: improved customer outcomes, reduced variation, safer work, better decisions, and sustainable capability. Pilot testing, user participation, privacy assessment, and post-implementation review are essential. Current Developments and Best PracticeContemporary change practice increasingly combines strategic direction with adaptive delivery. Agile methods, continuous improvement, employee experience design, hybrid work, resilience planning, and ecosystem collaboration have expanded the range of change capabilities required of managers. Organizations are also paying greater attention to psychological safety, inclusion, sustainability, and stakeholder trust. Best practice does not consist of following one model mechanically. It includes: - diagnosing the organization and its environment before selecting an intervention;
- connecting change to customer value, organizational purpose, and measurable outcomes;
- securing credible sponsorship while involving those closest to the work;
- combining formal governance with experimentation and feedback;
- addressing technical, behavioural, cultural, and structural conditions together;
- measuring adoption, performance, unintended consequences, and equity;
- treating resistance as information while maintaining decision clarity; and
- embedding learning through leadership routines, systems, incentives, and capability development.
Chapter SummaryOrganizational change theory has evolved from a predominantly planned and managerial view towards broader perspectives that recognize participation, systems, learning, uncertainty, and complexity. Planned change is valuable when objectives are clear and coordination is required; emergent change is useful when solutions must be discovered through adaptation. Episodic change concerns significant transitions, whereas continuous change is embedded in everyday improvement. Systems thinking emphasizes interdependence, complexity thinking emphasizes nonlinearity and adaptation, and organizational development emphasizes human participation and organizational health. Lewin provides a foundational account of preparing for, implementing, and stabilizing change. Kotter highlights urgency, coalition, communication, empowerment, short-term wins, and institutionalization. ADKAR focuses on individual adoption. McKinsey 7-S, Nadler–Tushman, Burke–Litwin, PDSA, appreciative inquiry, and related approaches provide additional diagnostic and implementation perspectives. Their value depends on context, and their limitations must be acknowledged. For TQM professionals, effective change requires alignment between customer needs, processes, people, technology, leadership, measures, and organizational culture. The most defensible approach is usually hybrid: provide strategic direction and governance while enabling local learning, ethical participation, and continuous improvement. Key TermsPlanned change: Deliberate alteration designed, guided, and evaluated against intended objectives. Emergent change: Change that develops through interaction, learning, and local adaptation. Episodic change: Discontinuous change associated with a distinct event or major intervention. Continuous change: Ongoing, incremental adaptation embedded in routine work. Systems thinking: Analysis of relationships, interdependence, feedback, and consequences across a whole system. Complexity perspective: A view of organizations as adaptive systems in which outcomes may be nonlinear and unpredictable. Organizational development: A planned, participative effort to improve organizational effectiveness and health using behavioural-science knowledge. Change readiness: The perceived necessity, appropriateness, feasibility, and support for a proposed change. Change sponsor: An authority figure who legitimizes, resources, and actively supports change. Change agent: A person or group that facilitates or implements organizational change. Organizational learning: The development and application of knowledge that improves collective action. Force-field analysis: A method for examining forces supporting and restraining a proposed change. Unfreezing: Preparation that loosens attachment to existing assumptions and routines. Refreezing: Reinforcement and institutionalization of a new pattern of behaviour. Guiding coalition: A group with sufficient influence and commitment to lead a change effort. ADKAR: A model involving Awareness, Desire, Knowledge, Ability, and Reinforcement. Congruence: The degree of fit among organizational tasks, people, structures, and informal arrangements. Psychological safety: A shared belief that people can speak up, question, and report problems without fear of humiliation or retaliation. Quality improvement: Systematic effort to improve process performance and customer or stakeholder outcomes. Review QuestionsShort Answer Questions1. What is meant by emergent change? 2. Distinguish episodic change from continuous change. 3. Identify the three stages in Lewin’s model. 4. What does ADKAR contribute to change analysis? 5. Define systems thinking in the context of TQM. Long Answer Questions1. Critically compare planned and emergent perspectives on organizational change. 2. Explain Lewin’s model and evaluate its relevance in an environment of continuous change. 3. Discuss Kotter’s eight-step process, including its principal strengths and limitations. 4. Explain how organizational development differs from a purely technical change approach. 5. Compare systems thinking and complexity thinking as approaches to quality transformation. Analytical / Application Questions1. A company introduces a new quality-information system, but employees continue using informal spreadsheets. Use ADKAR and systems thinking to diagnose the problem and recommend interventions. 2. A hospital wants to reduce waiting times but cannot identify a single cause. Which change perspective or combination of perspectives would you select, and why? 3. A manufacturing organization is achieving local productivity targets while customer complaints and rework increase. Apply at least two frameworks from this chapter to analyse the situation and design a change strategy. 22. Multiple Choice Questions with AnswersQuestion 1Which situation most strongly supports an emergent change approach? A. Implementing a legally specified reporting format with fixed requirements B. Introducing a well-tested standard operating procedure across identical facilities C. Improving service experience where causes are uncertain and solutions must be tested locally D. Replacing equipment according to a detailed approved specification Correct Answer: C. Improving service experience where causes are uncertain and solutions must be tested locally Question 2In Lewin’s model, unfreezing primarily involves: A. Embedding new behaviour in reward and control systems B. Creating readiness to question existing assumptions and routines C. Completing technical training after implementation D. Selecting a permanent organizational structure Correct Answer: B. Creating readiness to question existing assumptions and routines Question 3Which feature is most characteristic of Kotter’s approach? A. Individual adoption without attention to leadership B. A guiding coalition and generation of short-term wins C. Elimination of all formal planning D. Treating resistance as irrelevant to implementation Correct Answer: B. A guiding coalition and generation of short-term wins Question 4An employee understands why a new process is needed and wants to support it, but cannot perform it because training and practice are inadequate. Which ADKAR element is the primary gap? A. Awareness B. Desire C. Knowledge D. Reinforcement Correct Answer: C. Knowledge Question 5A purchasing department reduces unit prices, but production stoppages and customer complaints increase. Which concept best explains the problem? A. Local optimization within an interdependent system B. Successful refreezing C. Excessive psychological safety D. Individual awareness failure Correct Answer: A. Local optimization within an interdependent system Question 6Which statement best distinguishes complexity from merely complicated change? A. Complex situations always lack data B. Complex situations involve adaptive interactions and outcomes that cannot be predicted reliably from individual parts C. Complicated situations never require expertise D. Complexity means that planning and measurement are impossible Correct Answer: B. Complex situations involve adaptive interactions and outcomes that cannot be predicted reliably from individual parts Question 7A major limitation of using ADKAR alone is that it may: A. Ignore individual adoption completely B. Understate structural, political, and system-level constraints C. Reject training as an intervention D. Require organizational change to be continuous Correct Answer: B. Understate structural, political, and system-level constraints Question 8Which practice best reflects organizational development? A. Imposing a solution without employee involvement B. Using participation, behavioural inquiry, and feedback to improve organizational effectiveness C. Measuring only final product defects D. Replacing dialogue with automated dashboards Correct Answer: B. Using participation, behavioural inquiry, and feedback to improve organizational effectiveness Question 9Why are hybrid change strategies often appropriate in TQM? A. They eliminate the need for leadership decisions B. They combine direction and governance with experimentation and local learning C. They avoid the need to measure outcomes D. They assume that all change is unpredictable Correct Answer: B. They combine direction and governance with experimentation and local learning Question 10In the Meridian Components case, changing performance incentives was important because it: A. Removed the need for process analysis B. Aligned organizational systems with desired quality behaviours C. Guaranteed that resistance would disappear D. Converted continuous change into a purely technical project Correct Answer: B. Aligned organizational systems with desired quality behaviours
|
