Organizational Change, Learning, and Innovation

Introduction and Context

Organizations operate in environments characterized by technological disruption, demographic change, global competition, regulatory pressure, shifting customer expectations, and ecological uncertainty. Change is therefore not an exceptional event but a continuing condition of organizational life. Yet change does not automatically produce improvement. A new structure may create confusion, a digital system may intensify work rather than improve it, and an innovation program may generate ideas without commercial value.

Organizational behavior examines change as a social, psychological, political, and strategic process. Effective change requires more than announcing a new strategy. Managers must understand how people interpret change, how power and interests shape implementation, how organizational routines support or obstruct learning, and how creativity can be converted into innovation. This chapter integrates planned and emergent change, stakeholder and force-field analysis, readiness assessment, resistance management, organizational development, learning organizations, knowledge management, creativity, and innovation.

Learning Objectives

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

1. Distinguish planned, emergent, transformational, and continuous change.
2. Apply Lewin’s three-stage model, Kotter’s process, and emergent-change perspectives critically.
3. Analyze stakeholders, driving forces, restraining forces, and organizational readiness.
4. Diagnose and manage resistance ethically.
5. Explain organizational development and learning-organization principles.
6. Design knowledge-management, creativity, and innovation practices.
7. Evaluate technology and artificial intelligence as enablers and sources of change.
8. Develop an integrated change intervention using evidence, participation, and governance.

The Nature of Organizational Change

Organizational change is a difference over time in an organization’s strategy, structure, technology, processes, culture, people, or relationships with its environment. Change may be intentional or unintentional, episodic or continuous, incremental or transformational.

A central distinction is between first-order change, which modifies existing practices without altering underlying assumptions, and second-order change, which challenges assumptions, identities, and patterns of power. Replacing a paper form with an electronic form may be first-order. Redesigning decision rights so that customers and frontline employees shape service design may be second-order.

Change also has an emotional dimension. Employees may experience uncertainty, loss of competence, reduced status, workload disruption, or threats to professional identity. Resistance is therefore not simply irrational opposition. It may provide information about risks, poor design, unfairness, or inadequate participation. The managerial task is to distinguish legitimate concerns from defensive behavior while preserving the organization’s capacity to act.

Planned and Emergent Change Models

Lewin’s Three-Stage Model

Kurt Lewin conceptualized change as movement among relatively stable patterns of behavior. His model contains three broad stages:

1. Unfreezing: creating awareness that existing practices are inadequate and loosening attachment to them.
2. Changing or moving: introducing, testing, and learning new behaviors, processes, or structures.
3. Refreezing: reinforcing effective new patterns through systems, rewards, training, leadership, and culture.

The model is valuable because it emphasizes preparation and stabilization. However, “refreezing” can be misleading in volatile environments. Organizations may need a new equilibrium that remains adaptable rather than a permanent fixed state.

Kotter’s Change Process

Kotter’s widely used process translates planned change into a leadership sequence: establish urgency; build a guiding coalition; form a strategic vision; enlist broad participation; remove barriers; create short-term wins; sustain acceleration; and institutionalize new approaches. The sequence is not a mechanical checklist. Political support, experimentation, and feedback may require stages to overlap or recur.

The model is particularly useful when leaders must coordinate large-scale change across functions. Its limitations include a tendency toward top-down leadership and an assumption that change follows a broadly linear path. In practice, urgency may be contested, coalitions may evolve, and short-term wins may encourage superficial compliance rather than deep learning.

Emergent Change

Emergent perspectives treat change as an ongoing process produced by local adaptation, sensemaking, conversations, routines, and environmental interaction. Strategy may develop through experiments rather than preceding them. Managers act less as architects who specify every detail and more as designers of conditions: clear purpose, psychological safety, information access, decision boundaries, and rapid feedback.

An emergent approach is appropriate when the problem is complex, the solution is uncertain, and knowledge is distributed among employees, customers, suppliers, or communities. It does not mean abandoning direction. Leaders still define strategic intent, ethical boundaries, resource constraints, and measures of progress. They then permit multiple pathways to generate evidence about what works.

A Contingency Perspective

No single change model is universally superior. A planned approach is useful when the destination is relatively clear, dependencies are known, and coordinated implementation is essential. An emergent approach is more appropriate when uncertainty is high and local knowledge is crucial. Many effective programs combine both: planned intent and governance with emergent experimentation.

Diagnosing the Need for Change

Change should begin with diagnosis rather than enthusiasm for a fashionable intervention. A useful diagnosis examines four questions:

• What performance, environmental, or ethical problem requires attention?
• What are the underlying causes rather than visible symptoms?
• Which organizational elements must change together?
• What unintended consequences might the intervention produce?

The congruence model associated with Nadler and Tushman examines the fit among work, people, formal organization, and informal organization. Misalignment may explain why a technically sound initiative fails. For example, a firm may introduce customer-centric software while retaining sales incentives based solely on individual product volume. The technology and stated strategy then conflict with rewards and behavior.

A diagnostic process should combine quantitative and qualitative evidence: performance indicators, process data, employee surveys, interviews, observation, customer feedback, and document analysis. Data should be disaggregated where appropriate because an organizational average can hide unequal effects on occupational groups, locations, or demographic communities.

Stakeholder and Force-Field Analysis

Stakeholder Analysis

Stakeholders are individuals or groups that affect, are affected by, or perceive themselves to be affected by change. They may include employees, managers, owners, customers, regulators, suppliers, unions, professional bodies, communities, and technology partners.

A practical stakeholder analysis identifies each stakeholder’s interests, influence, likely response, information needs, and ethical claims. Influence is not identical to formal authority. A technically expert employee, trusted union representative, or influential customer may shape outcomes without holding a senior title.

Stakeholder mapping should not be used merely to manipulate people. Ethical engagement requires accurate information, meaningful voice, respect for privacy, and honest disclosure of constraints. Consultation without any possibility of influence can increase cynicism.

Force-Field Analysis

Lewin’s force-field analysis represents change as the interaction between driving forces and restraining forces. Driving forces may include customer demand, regulatory requirements, executive sponsorship, cost pressure, or employee aspirations. Restraining forces may include skills gaps, fear of job loss, incompatible systems, resource scarcity, or conflicting incentives.

A simple qualitative procedure is to list the forces, assess their relative strength, examine interactions, and identify interventions. Managers often focus only on increasing pressure for change. Reducing restraining forces is frequently more sustainable: provide training, redesign work, clarify roles, protect speaking-up, or remove contradictory metrics.

Force-field analysis is a heuristic, not a precise prediction model. Numerical scores can create false confidence unless the assumptions behind them are made explicit. Its value lies in making assumptions visible and encouraging discussion.

Readiness for Change

Readiness refers to the extent to which organizational members see change as necessary, appropriate, feasible, supported, and personally meaningful. It exists at individual, team, organizational, and system levels.

Important readiness dimensions include:

• Discrepancy: recognition that current performance or conditions are inadequate.
• Change appropriateness: belief that the proposed intervention addresses the problem.
• Efficacy: confidence that people can implement the change.
• Leadership support: visible and credible commitment from influential leaders.
• Valence: perceived personal and organizational benefit.
• Resources: time, skills, budget, data, and infrastructure.

Readiness assessment may use surveys, interviews, workshops, pilot results, and operational data. A survey score should not be treated as an objective fact detached from context. Low readiness may indicate poor communication, historical distrust, genuine design flaws, or a rational assessment of insufficient resources.

A useful readiness conversation asks: What must be true for this change to succeed? Who possesses the knowledge to answer that question? Which assumptions can be tested through a low-risk pilot? What evidence would cause the organization to revise the proposal?

Resistance, Participation, and Ethical Implementation

Resistance can be active, passive, cognitive, emotional, political, or procedural. Examples include open disagreement, delay, selective compliance, silence, absenteeism, workarounds, and withdrawal of discretionary effort. Leaders should avoid labeling all resistance as a character defect. Resistance may reveal inadequate consultation, distributive injustice, unclear accountability, or threats to safety and identity.

Common responses include communication, participation, facilitation, training, negotiation, coaching, and—in limited circumstances—formal authority. Communication is necessary but insufficient when employees face material losses. Participation is most credible when participants can influence design, sequencing, or safeguards.

Ethical change management requires:

• truthful communication about benefits, risks, uncertainty, and job implications;
• procedural fairness in decision-making;
• protection against retaliation for good-faith criticism;
• reasonable support for reskilling and transition;
• attention to accessibility and unequal effects;
• confidentiality and lawful handling of employee data; and
• monitoring for unintended harm.

Coercion may produce short-term compliance but often damages trust and learning. Manipulating metrics or manufacturing urgency is especially problematic because it undermines informed participation.

Organizational Development

Organizational development (OD) is a planned, values-based, organization-wide effort to increase effectiveness and human capability through behavioral-science knowledge. OD traditionally emphasizes participation, diagnosis, feedback, action research, and respect for human dignity.

A classic OD cycle is:

1. Entry and contracting: clarify the issue, roles, expectations, and boundaries.
2. Diagnosis: gather and interpret data with relevant stakeholders.
3. Feedback: return findings in a form that supports shared understanding.
4. Joint action planning: select interventions and define responsibilities.
5. Implementation: act, monitor, and adapt.
6. Evaluation and institutionalization: assess effects and embed learning.

OD interventions may operate at the individual level, such as coaching; group level, such as team development and conflict intervention; or organizational level, such as structural redesign, culture work, survey feedback, and strategic change. Contemporary OD increasingly addresses power, inclusion, digital work, sustainability, and institutional systems rather than treating organizations as closed systems.

Action research is particularly relevant because it links knowledge generation with practical intervention. However, participation must be designed carefully. Employees may censor themselves if leaders control access to data or if confidentiality is not credible.

Learning Organizations and Organizational Learning

Organizational learning is the process by which organizations acquire, interpret, distribute, retain, and apply knowledge. It is not equivalent to sending employees to training. Learning occurs when experience changes shared understanding, routines, decisions, or capabilities.

Peter Senge’s learning-organization perspective emphasizes systems thinking, personal mastery, mental models, shared vision, and team learning. Chris Argyris distinguished single-loop learning, which corrects errors without questioning governing assumptions, from double-loop learning, which examines and revises those assumptions. A firm that repeatedly trains staff to sell harder is using single-loop learning if it never questions whether its product or sales model fits customer needs.

Learning requires both exploration and exploitation. Exploration involves experimentation, search, variation, and risk; exploitation involves refining, standardizing, and scaling what already works. Excessive exploitation produces rigidity, while excessive exploration produces unimplemented ideas. Ambidextrous organizations separate or integrate these activities so that both can occur.

Psychological safety, a concept associated with Amy Edmondson, supports learning by enabling people to report errors, ask questions, and challenge assumptions without fear of humiliation or retaliation. Psychological safety is not permissiveness. High standards and accountability can coexist with interpersonal safety.

Knowledge Management

Knowledge management (KM) coordinates the creation, capture, sharing, retrieval, and application of knowledge. Knowledge may be explicit, such as procedures and databases, or tacit, such as judgment developed through experience.

Effective KM combines people, processes, technology, and culture. A repository is not a knowledge-management strategy if employees cannot find, trust, update, or apply its content. Communities of practice, mentoring, after-action reviews, expert directories, storytelling, and job rotation help transfer tacit knowledge.

A practical KM architecture includes:

1. Identify strategically important knowledge.
2. Map where knowledge resides and where it is vulnerable to loss.
3. Create mechanisms for capture and sharing.
4. Establish ownership, quality standards, and retention rules.
5. Make knowledge accessible within security and privacy constraints.
6. Measure use and organizational impact.

Metrics should go beyond document counts. Useful indicators include search success, reuse, time to competence, reduction in recurring errors, and contribution to customer or operational outcomes. Knowledge hoarding may reflect reward systems, professional identity, or distrust; technology alone cannot solve these causes.

Creativity and Innovation

Creativity is the generation of ideas that are novel and potentially useful. Innovation is the implementation and realization of value from new or significantly improved products, services, processes, methods, or business models. A creative idea is not necessarily an innovation until it is adopted, implemented, or converted into meaningful value.

The creative process is often described as preparation, incubation, illumination, evaluation, and implementation. In practice, these stages may overlap. Useful techniques include divergent brainstorming, design thinking, analogy, customer observation, TRIZ-inspired contradiction analysis, scenario development, and structured experimentation.

Design thinking commonly emphasizes empathizing with users, defining a problem, ideating, prototyping, and testing. Its strength is attention to user experience and iterative learning. Its limitation is that it may understate implementation politics, regulatory constraints, economics, and system-level effects.

Innovation can be classified by locus and degree:

Innovation portfolios should balance core improvements, adjacent opportunities, and uncertain transformational bets. Evaluation criteria may include customer value, strategic fit, feasibility, learning potential, ethical risk, and scalability. Financial projections are useful but unreliable when uncertainty is high; staged investment and explicit learning milestones reduce exposure.

Leading Innovation and Managing Failure

Innovation requires leadership that establishes direction while allowing experimentation. Managers should define the problem and constraints, not prescribe every solution. Cross-functional teams improve innovation because they combine technical, customer, operational, and commercial knowledge.

Failure should be interpreted carefully. A well-designed experiment that disproves an important assumption can generate valuable learning. Negligence, poor governance, or failure to act on known evidence should not be celebrated as constructive failure. Leaders should distinguish intelligent failure—limited, analyzed, and informative—from avoidable failure.

A disciplined experiment specifies a hypothesis, intervention, evidence, decision rule, and ethical safeguards. For example: “If customers receive a simplified onboarding process, completion rates will improve without increasing fraud.” The team can pilot the process, compare relevant outcomes, inspect unintended effects, and decide whether to adapt, scale, or stop.

Technology, Artificial Intelligence, and Change

Digital technologies alter coordination, work design, control, and knowledge flows. Artificial intelligence may support forecasting, document analysis, service personalization, decision support, and process automation. It can also introduce bias, surveillance, opacity, deskilling, cybersecurity risks, and accountability gaps.

Responsible implementation requires clear purpose, data governance, human oversight, validation, explainability appropriate to the use case, security, accessibility, and mechanisms for appeal. Employees should understand how AI affects evaluation, scheduling, promotion, or workload. Managers should assess whether automation removes burdens or merely transfers them to less visible forms of monitoring and exception handling.

Technology adoption is therefore a socio-technical change, not an information-systems installation. Work roles, incentives, skills, professional standards, and power relationships must be redesigned together. Regulatory obligations vary by jurisdiction and application; organizations should consult current legal and sector-specific requirements rather than relying on generic assurances.

An Integrated Change-Management Process

A robust managerial process can combine planned discipline with emergent learning:

1. Frame the case for change using evidence and stakeholder perspectives.
2. Diagnose the system—strategy, structure, work, people, technology, culture, and external context.
3. Map stakeholders and forces and identify ethical risks.
4. Assess readiness and capability, including resources and psychological safety.
5. Define a compelling direction while distinguishing non-negotiables from areas open to experimentation.
6. Build a guiding coalition that includes formal authority and credible local knowledge.
7. Co-design and pilot interventions with affected users.
8. Measure leading and lagging indicators and monitor distributional effects.
9. Learn and adapt, including revising the original theory of change.
10. Scale and institutionalize effective practices through systems, capability development, and governance.

Leading indicators may include participation, training completion, system use, experiment velocity, and reported concerns. Lagging indicators may include productivity, customer outcomes, quality, retention, safety, and financial performance. No single metric captures organizational change; a balanced evidence set is essential.

Illustrative Case: Northstar Medical Supplies

Background

Northstar Medical Supplies, a fictional regional distributor, had grown through acquisitions. Its order-processing system consisted of incompatible platforms, manual spreadsheets, and local workarounds. Customer complaints about delayed deliveries were increasing, while employees reported excessive rework.

Problem

The executive team proposed a single cloud-based platform and announced that all sites would adopt it within six months. Early communication emphasized efficiency but did not explain job impacts, data migration risks, or how local expertise would be retained. Warehouse supervisors feared loss of autonomy, and customer-service employees worried that automation would reduce staffing.

Analysis

A diagnostic team conducted interviews, observed order flows, and analyzed error data. Stakeholder analysis identified executives as high-influence sponsors, frontline employees as high-impact knowledge holders, customers as external evaluators, and regulators as important data-governance stakeholders. Force-field analysis showed that regulatory traceability and customer dissatisfaction drove change, while skills gaps, conflicting local incentives, and distrust restrained it.

Readiness was uneven. Employees agreed that the current system was inadequate but doubted that the proposed timetable was feasible. The team concluded that the problem was not resistance to technology itself; it was resistance to a poorly governed implementation.

Approach and Solution

Northstar retained a planned objective—integrated order visibility—but adopted an emergent implementation. A coalition included site managers, warehouse employees, customer-service representatives, IT specialists, and a data-protection officer. Two sites piloted the platform using representative orders. Employees participated in workflow redesign, and a protected channel collected concerns.

The organization created short-term wins by eliminating duplicate data entry in one high-volume process. It also preserved selected local practices where they improved safety or customer service. Training used simulations rather than one-time lectures. Managers revised performance measures so that employees were not penalized during the transition for reporting defects or assisting colleagues.

AI-based demand forecasting was tested separately rather than embedded immediately in the core rollout. Its recommendations required human review, and the firm documented data limitations and escalation procedures.

Outcome

After the pilot, Northstar delayed full deployment by two months, corrected data-migration problems, and redesigned role boundaries. Adoption improved because employees could see how their knowledge shaped the system. The organization reported fewer duplicate entries and better order visibility, while continuing to monitor workload, customer outcomes, and data quality. The most important outcome was not merely technical implementation; it was the development of a repeatable capability for participative experimentation.

Learning Points

The case demonstrates that urgency does not eliminate the need for diagnosis. Stakeholders may resist the method, timetable, or distributional consequences rather than the strategic goal. Planned direction and emergent learning can coexist. Finally, innovation and technology adoption require governance, participation, and attention to work identity—not only investment in software.

Challenges and Limitations

Change models simplify reality. Lewin’s stages can imply stability where organizations experience continuous movement. Kotter’s sequence may privilege executive agency. Force-field scores can disguise subjective judgments as measurement. Readiness surveys may reflect temporary mood, fear of disclosure, or survey design. OD can become symbolic if leaders request participation but retain all meaningful decisions.

Learning organizations may romanticize openness while neglecting power, workload, and accountability. Knowledge repositories can become bureaucratic archives. Innovation programs may reward novelty rather than value, overuse brainstorming, or ignore implementation capacity. Digital transformation can intensify inequality if training, accessibility, or voice is distributed unevenly.

Managers should therefore treat frameworks as diagnostic lenses, not universal recipes. They should make assumptions explicit, triangulate evidence, invite dissent, and evaluate both intended and unintended consequences.

Best-Practice Principles

• Start with a meaningful problem, not a preferred solution.
• Combine strategic clarity with local experimentation.
• Engage affected stakeholders early and honestly.
• Treat resistance as data as well as a potential obstacle.
• Protect psychological safety and procedural fairness.
• Align structures, incentives, skills, technology, and culture.
• Use pilots to test assumptions before scaling.
• Measure adoption, outcomes, learning, and unequal effects.
• Preserve valuable knowledge while changing obsolete routines.
• Govern AI and data according to risk, accountability, and human impact.
• Institutionalize learning without eliminating constructive challenge.

Chapter Summary

Organizational change is a social and strategic process involving behavior, identity, power, technology, learning, and performance. Planned models such as Lewin’s stages and Kotter’s process help managers create direction, coordination, and reinforcement. Emergent perspectives emphasize adaptation, distributed knowledge, experimentation, and sensemaking. Effective practice combines planned intent with emergent implementation where uncertainty is substantial.

Stakeholder analysis identifies interests, influence, impact, and engagement requirements. Force-field analysis examines driving and restraining forces, while readiness assessment considers discrepancy, appropriateness, efficacy, leadership support, valence, and resources. Resistance can reveal legitimate concerns and should be managed through evidence, participation, support, fairness, and ethical communication.

Organizational development uses diagnosis, feedback, action, and evaluation to improve both effectiveness and human capability. Learning organizations cultivate systems thinking, psychological safety, double-loop learning, and a balance between exploration and exploitation. Knowledge management links people, processes, technology, and governance to the creation and application of knowledge.

Creativity produces novel and useful ideas; innovation implements them to create value. Design thinking, prototyping, experimentation, portfolio management, and cross-functional collaboration can support innovation, but implementation, economics, ethics, and power must not be ignored. Technology and AI are socio-technical changes requiring human oversight, data governance, security, transparency, and attention to work design. The capable change leader integrates diagnosis, participation, experimentation, measurement, ethical governance, and institutional learning.

Key Terms

Organizational change: A difference over time in organizational strategy, structure, technology, processes, culture, people, or relationships.

Planned change: Deliberately designed and coordinated change directed toward an intended outcome.

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

Transformational change: Fundamental change to organizational identity, strategy, structure, or operating logic.

First-order change: Modification within existing assumptions and systems.

Second-order change: Change that challenges underlying assumptions, identities, or power arrangements.

Unfreezing: Preparing people and systems to question and move beyond existing patterns.

Refreezing: Reinforcing effective new patterns through systems, rewards, skills, and culture.

Stakeholder: A person or group that affects, is affected by, or perceives itself to be affected by change.

Force-field analysis: A method for examining forces that drive or restrain change.

Readiness for change: The extent to which people and systems are willing and able to implement change.

Resistance: Behaviors, attitudes, or processes that oppose, delay, question, or complicate change.

Organizational development: A planned, values-based effort using behavioral-science knowledge to improve organizational effectiveness and human capability.

Organizational learning: The acquisition, interpretation, sharing, retention, and application of knowledge.

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

Knowledge management: The coordinated creation, capture, sharing, retrieval, and application of knowledge.

Creativity: The generation of ideas that are novel and potentially useful.

Innovation: The implementation of new or significantly improved offerings, processes, methods, or business models.

Exploration: Experimentation, search, variation, and discovery of new possibilities.

Exploitation: Refinement, standardization, and scaling of established capabilities.

Review Questions

Short Answer Questions

1. What is the difference between planned and emergent change?
2. Identify the three stages in Lewin’s change model.
3. Why should resistance not automatically be treated as irrational behavior?
4. Distinguish creativity from innovation.
5. What is psychological safety, and why does it support organizational learning?

Long Answer Questions

1. Critically compare Lewin’s three-stage model with an emergent-change perspective.
2. Explain how stakeholder analysis and force-field analysis can be integrated in a change program.
3. Discuss the role of organizational development in implementing complex organizational change.
4. Explain how exploration and exploitation can be balanced in an innovation portfolio.
5. Evaluate the ethical and organizational implications of introducing AI into employee work processes.

Analytical / Application Questions

1. A bank has strong executive support for digital transformation, but frontline employees report low trust and insufficient training. Diagnose the readiness problem and recommend an ethically appropriate intervention.
2. A manufacturing firm has generated hundreds of innovation ideas but implemented very few. Use creativity and innovation concepts to design a portfolio and experimentation process.
3. Apply stakeholder analysis and force-field analysis to a proposed restructuring in an organization of your choice. Identify likely unintended consequences and specify measures for learning and adaptation.

Multiple Choice Questions with Answers

Question 1

Which situation best illustrates emergent change?

A. A detailed five-year implementation plan is executed without modification.

B. A pilot team adapts a service through repeated feedback from users and employees.

C. A leader freezes all procedures until a final design is approved.

D. An organization copies a competitor’s structure exactly.

Correct Answer: B. A pilot team adapts a service through repeated feedback from users and employees.

Question 2

In Lewin’s model, unfreezing primarily involves:

A. Embedding new practices in reward systems

B. Creating awareness that existing patterns are inadequate

C. Selecting a final technology vendor

D. Measuring long-term financial performance

Correct Answer: B. Creating awareness that existing patterns are inadequate

Question 3

Which is a restraining force in a force-field analysis?

A. Regulatory pressure for improved safety

B. Customer demand for faster service

C. A skills gap that limits implementation

D. Visible executive sponsorship

Correct Answer: C. A skills gap that limits implementation

Question 4

Which readiness dimension concerns belief that the proposed intervention is suitable for the problem?

A. Change appropriateness

B. Valence

C. Refreezing

D. Exploitation

Correct Answer: A. Change appropriateness

Question 5

Why can resistance provide useful information?

A. It always indicates poor employee motivation.

B. It may reveal design flaws, unfairness, or implementation risks.

C. It eliminates the need for stakeholder analysis.

D. It proves that change should be abandoned.

Correct Answer: B. It may reveal design flaws, unfairness, or implementation risks.

Question 6

Double-loop learning occurs when an organization:

A. Corrects an error without questioning its assumptions

B. Repeats a successful routine more quickly

C. Examines and revises the assumptions governing its actions

D. Stores documents in a database

Correct Answer: C. Examines and revises the assumptions governing its actions

Question 7

Which statement best distinguishes knowledge management from document storage?

A. Knowledge management focuses only on software acquisition.

B. Knowledge management includes creating, sharing, retrieving, and applying knowledge.

C. Knowledge management prevents tacit knowledge from being used.

D. Knowledge management measures only the number of uploaded files.

Correct Answer: B. Knowledge management includes creating, sharing, retrieving, and applying knowledge.

Question 8

An innovation is best distinguished from a creative idea because innovation:

A. Must always be radical.

B. Is implemented or converted into value.

C. Can be generated only by senior managers.

D. Never involves experimentation.

Correct Answer: B. Is implemented or converted into value.

Question 9

What is a principal purpose of a pilot in an uncertain change program?

A. To guarantee that the final solution will succeed

B. To test assumptions and generate evidence at limited scale

C. To eliminate the need for governance

D. To prevent users from influencing design

Correct Answer: B. To test assumptions and generate evidence at limited scale

Question 10

Responsible use of AI in organizational change requires:

A. Removing all human oversight

B. Using opaque systems whenever they are cheaper

C. Attention to data governance, accountability, validation, and human impact

D. Treating technology adoption as separate from work design

Correct Answer: C. Attention to data governance, accountability, validation, and human impact