Organizational Change Management
1. Overview
A. Definition
Organizational Change Management (OCM) is a people-side management activity that systematically prepares, supports, and embeds the behavioral transition of employees triggered by the introduction of new information systems, processes, organizational structures, or culture, so that the change is realized as the intended business performance and Value. If changing technology and processes is the "supply of change," change management owns the "demand of change" — making people actually adopt (Adoption) and use proficiently (Proficiency) that change.
The essence of organizational change management lies in recognizing that "turning the system on (go-live)" and "the system delivering results (value realization)" are entirely different events. No matter how excellent an ERP, groupware, or AI platform is built, if business users cling to old ways or resist, the return on investment (ROI) is not realized. In other words, change management is not an ancillary activity of a technical project but a Critical Success Factor (CSF) that determines investment performance. From a professional engineer's perspective, change management is the bridge spanning the gap between "system construction (development)" and "operational embedding," and can be seen as the domain that handles a fourth constraint — "Acceptance" — beyond the triple constraint of scope, schedule, and cost in project management.
Note that ITIL/ITSM's "Change Management/Change Enablement" differs from the "change management (OCM)" of this topic. ITSM change management is an activity that controls Change Requests (RFC) for IT services in operation through CAB, approval, and release procedures to preserve service stability, whereas organizational change management deals with the psychological, behavioral, and capability transition of people. If the former is technical control of "what and how may be changed," the latter is closer to the organizational psychology of "how do we get people to accept it."
B. Background and Necessity
Behind change management's rise as an independent discipline lies the failure rate of Digital Transformation. Many industry surveys report that a large share of large-scale change and DX programs fail to achieve their originally expected outcomes, and the core cause has been pointed to not as technical defects but as people problems such as employee resistance, leadership vacuum, and lack of communication. In other words, the bottleneck of failure has shifted from "technology" to "acceptance." The turmoil that arises immediately after the opening of next-generation systems in the public and financial sectors also stems in large part from the field's lack of proficiency and change fatigue.
Another driver is the increase in the frequency and scale of change. What used to be a large system replacement once every several years has turned, amid Agile, DevOps, and cloud transformation, into constant and continuous change. Employees are exposed to incessant change and experience "Change Fatigue." In such an environment, change management cannot rely on one-off training and announcements; the demand has grown to internalize change as the organization's sustained capability (Change Capability). This is why structured methodologies such as Prosci, Kotter, and ADKAR are widely adopted.
2. The Overall Structure of Change Management and Its Representative Models
Change management works through the interaction of the "change subject (leaders/sponsors)," the "change target (employees)," and the "change facilitator (Change Agent/CM team)." The structure diagram below shows the overall flow in which change is divided into supply (technology/process) and demand (people's acceptance), and change management bridges that gap to convert it into value.
flowchart TD
SPON["Sponsor/Leadership(Sponsor)"]
TECH["Technology/Process Change(supply side)"]
CM["Change Management(communication·training·resistance)"]
PEOPLE["Employee Acceptance(demand side)"]
AGENT["Change Facilitator(Change Agent)"]
ADOPT["Adoption·Proficiency(Adoption/Proficiency)"]
VALUE["Performance·Value Realization(ROI)"]
SPON -->|"visible sponsorship"| CM
TECH --> CM
AGENT --> CM
CM --> PEOPLE
PEOPLE --> ADOPT
ADOPT --> VALUE
SPON -->|"resistance adjustment"| PEOPLE
Change management methodologies are broadly organized into three representative models. These models are not mutually exclusive, and in practice they are often combined — Kotter's execution steps and ADKAR's individual-transition measurement layered on top of Lewin's macro framework.
A. Lewin's 3-Stage Model — The Macro Dynamics of Change
Kurt Lewin's model explains change in three stages: Unfreeze → Change/Move → Refreeze. Unfreeze is the stage of creating dissatisfaction with the current state and a sense of crisis to imprint the necessity of change; its purpose is to melt existing inertia (ice) into a state where change is possible. The Change stage is a transitional period in which new ways and systems are actually introduced and go through learning and trial and error, during which the "J-curve" phenomenon — a temporary drop in productivity — commonly appears.
Refreeze is the stage of solidifying change into an irreversible "New Normal." By reflecting the new process in institutions, KPIs, and reward systems and making successes visible, it locks people out of reverting to old ways. For example, when a manufacturer converts paper approval to electronic approval, merely leaving the system open is insufficient; refreeze is only completed when paper forms are physically withdrawn and the electronic-approval usage rate is incorporated into department evaluation metrics. Lewin's model is simple, yet it most clearly captures the essence of change as a state transition of "melting, changing, and solidifying."
B. Kotter's 8-Step Model — The Execution Roadmap of Change
John Kotter's 8-step model is an execution-centric roadmap designed by inverting the typical errors that make change fail. From Step 1, Create Urgency, to Step 8, Anchor in Culture, each step is arranged in an order such that "skipping it inevitably exacts a price." In particular, Kotter emphasizes creating urgency early and forming a strong Guiding Coalition, because many changes start without a shared understanding of "why we must change" and founder.
The practical strength of Kotter's model lies in the deliberate design of Short-term Wins. Large-scale change produces results late, so employees easily tire; in Step 6, deliberately creating fast, visible success cases maintains the momentum of change. For example, in an enterprise-wide cloud transformation, converting the single most responsive team first as a pilot and announcing early figures such as "30% cost reduction" serves as priming water that draws in the participation of other departments that had been watching. However, the 8 steps carry a strong top-down and sequential premise, so in a rapidly iterating Agile environment they need to be flexibly tailored.
C. The ADKAR Model — A Measurement Lens for Individual Transition
Prosci's ADKAR model starts from the insight that organizational change is ultimately the aggregated result of individual transitions. ADKAR is the acronym for the five sequential states an individual must pass through to succeed at change: Awareness → Desire → Knowledge → Ability → Reinforcement. The core principle is that this order cannot be skipped. Teaching how to use something (Knowledge) to someone who has not recognized the necessity of change is hollow, and building only Ability when there is no Desire leaves it unused.
The practical value of ADKAR lies in being a lens that diagnoses the cause of resistance. When a user does not use a new system, inspecting "why they do not use it" stage by stage from the ADKAR perspective allows the barrier point to be pinpointed. If they do not know the necessity, prescribe communication; if there is aversion, incentives and leader persuasion; if they do not know how, training; if they are not accustomed, coaching and a help desk; if they revert to old ways, reinforcement measures. The table below compares the focus and application phase of the three models.
| Category | Lewin 3-Stage | Kotter 8-Step | ADKAR |
|---|---|---|---|
| Focus | Macro state transition of change | Organization-level execution order | Individual transition state |
| Nature | Conceptual framework (What) | Execution roadmap (How, org) | Diagnosis·measurement (How, individual) |
| Strength | Simple·intuitive | Clear momentum·order | Can pinpoint resistance cause |
| Limitation | Lacks execution guidance | Top-down·sequential premise | No macro strategy |
| Application phase | Entire change design | Enterprise-wide change drive | User embedding·coaching |
3. The Change Management Process and Resistance Management
Practical change management is carried out as a lifecycle of "prepare → execute → embed." The process diagram below shows the cyclical flow that starts from change impact analysis, continuously monitors resistance, and reaches embedding.
flowchart LR
A["Change Impact Analysis(Impact)"] --> B["Stakeholder Analysis(Stakeholder)"]
B --> C["Communication·Training Plan(Plan)"]
C --> D["Execute: communication·training·coaching"]
D --> E["Resistance Monitoring(Resistance)"]
E -->|"resistance found"| F["Resistance Response·Adjustment"]
F --> D
E -->|"stable"| G["Embed·Reinforce(Reinforce)"]
G --> H["Performance Measurement·Internalization"]
A. Preparation Stage — Impact Analysis and Stakeholder Analysis
The starting point of change management is change impact analysis, which grasps quantitatively and qualitatively "whose, what, and how much this change alters." It identifies the gap of change by role, process, tool, and organizational structure, and assesses the magnitude of change and the organization's readiness to accept it. Then, in stakeholder analysis, groups are classified along the axes of impact and influence (e.g., high-impact·high-authority groups receive intensive management), and each group's expectations and concerns are mapped.
The deliverable of this stage, the "change readiness assessment," is directly linked to project risk management. For example, if a department with low acceptance readiness handles core operations, this must be registered as an operational risk at go-live and a mitigation plan established. Opening the system alone while skipping preparation leads, like the next-generation system opening turmoil mentioned earlier, to a flood of call-center calls and operational paralysis.
B. Execution Stage — Communication, Training, Sponsorship
The three major levers of execution are Communication, Training, and Sponsorship. The key to communication is delivering the "why" repeatedly and across multiple channels; in particular, early in the change, it must answer the "what does this change mean to me (WIIFM, What's In It For Me)" that employees wonder about. Training fills Knowledge and Ability, but it leads to proficiency when practice in the actual work context, microlearning, and on-site coaching are combined rather than one-off classroom training.
The most important factor is visible and active Sponsorship. In Prosci's repeated surveys, the greatest contributing factor to change success is cited as leaders' visible sponsorship. If a leader delegates the change with a single email and disappears, employees interpret it as "not sincere." Only when the leader personally visits the field, uses the new system first themselves, and clearly sets the priority of change does the organization move.
C. Resistance Management — Prevention Is Cheaper Than Cure
Resistance is a natural reaction to change and is not necessarily negative. Resistance is often an early warning about "a risk we missed." The principle of resistance management is a proactive approach. Predicting resistance at the impact-analysis stage and responding preemptively with communication and participation is far cheaper than firefighting after resistance has surfaced. "Reducing resistance through participation," which involves employees in the design of change, is the most proven technique.
The types of resistance should be distinguished and prescribed differently as "not knowing (lack of awareness)," "not liking (conflict of interest)," and "not able (lack of capability)." Middle managers in particular are the decisive group that determines the success or failure of change. Caught in a "sandwich" position between top-down change directives and field resistance, if they are not converted into allies of change (Change Agents), even the best strategy is diluted on the ground.
The cost structure of resistance response also matters. The cost of absorbing resistance preemptively by involving business representatives at the change-design stage is relatively small, whereas the cost of cleaning up after full-scale rejection has erupted post-go-live — adding retraining, system reconfiguration, and schedule delay — grows several-fold. Therefore, it is reasonable to budget change management as "upfront prevention investment" rather than "post-hoc firefighting cost." Indeed, for groups predicted to resist strongly, a strategy of deliberately creating a virtuous cycle of "pilot participation → feedback reflection → sharing success experience" from the early change-design phase to convert resistance into support is effective.
4. Comparison — Change Management vs. Project Management, and Integration
Change management and project management are easily confused but differ in focus. Project Management (PM) deals with the "technical side of designing, building, and delivering a solution," while Change Management (CM) deals with the "people side of people adopting and utilizing that solution." The two are not competitors but complements, and successful change is achieved when the two disciplines mesh into a single integrated plan.
| Perspective | Project Management (PM) | Change Management (CM) |
|---|---|---|
| Purpose | Build·deliver solution | Adopt·embed solution |
| Success criterion | Compliance with scope·schedule·budget (QCD) | Usage rate·proficiency·performance realization |
| Main target | Deliverables·tasks·schedule | Employees·behavior·culture |
| Risk | Technical·schedule delay | Resistance·acceptance failure |
| Representative tools | WBS·Gantt·EVM | ADKAR·communication plan·readiness assessment |
A concrete case showing the integration of the two is a financial firm's next-generation core-banking transformation. From the PM perspective, hundreds of development tasks and data migration schedules were managed, but simultaneously from the CM perspective, phased training and a "best-practice champion" system were operated for thousands of branch employees nationwide. In particular, placing on-site support staff at each branch for two weeks right after go-live — a "Hypercare" period — became a buffer that absorbed the initial turmoil. Had a perfectly built system been opened without training and support, counter delays and customer complaints would have exploded.
5. Deep Dive — Change Management and Measurement in the Era of Digital Transformation and Agile
The recent theme of change management is adaptation to a Continuous Change environment. As Agile and DevOps spread, change has shifted from quarterly large events into a continuous flow that occurs every two-week sprint. Accordingly, the linear model of "change management after project completion" revealed its limits, and Agile Change Management, which embeds change management within each iteration cycle, has emerged. It is an approach that continuously communicates small, frequent changes and manages the total amount of "change fatigue" at the change-portfolio level.
In addition, change management is evolving from what used to be dismissed as a "qualitative and subjective" domain into data-based measurement. Actual usage rates extracted from system logs, adoption rates by feature, changes in task processing time, survey-based readiness and satisfaction indices, and help-desk inquiry trends are taken as change-management KPIs to quantitatively track the degree of embedding. For example, if the "Weekly Active User (WAU) ratio" after introducing a new collaboration tool falls short of target, ADKAR diagnosis is used to find the bottleneck stage and intervene further. The capability to thus convert change into measurable performance is becoming a core competitiveness of modern change management.
As a concrete example of the measurement-based approach, there is a case where a public institution, while replacing its electronic-document system, tracked "electronic-approval processing rate," "average approval time," and "rejection-rewrite count" on a weekly dashboard. When, in the fourth week of introduction, the processing rate of a certain headquarters stagnated in the 50% range, diagnosing the cause with an ADKAR survey confirmed that a deficit at the "Knowledge" stage (unfamiliarity with writing new forms) was the bottleneck. When "two-minute feature-by-feature video guides" and on-site coaching were added instead of classroom training, the processing rate exceeded 90% within two weeks. This shows that change management is evolving into an engineering activity that finds bottlenecks and intervenes precisely with data rather than gut feeling.
At the organizational level, there is a strong movement to build change not as a project started anew each time but as a sustainable organizational capability (Change Capability/Change Muscle). This means establishing the change-management methodology as an enterprise-wide standard, making the change-facilitator network permanent, and training leaders in change leadership. Because organizations that absorb change well convert new technologies into performance faster than competitors, change capability itself becomes a sustained competitive advantage in the digital era.
6. Considerations and Implications
The strategies, trade-offs, and outlook to consider from a professional engineer's perspective when applying organizational change management to information-system projects are as follows.
Early-start strategy: Change management is not an activity of cramming training in right before go-live but must run in parallel with PM from the project's initiation point. Involving the business from the requirements-analysis stage raises acceptance and requirement quality simultaneously. The moment change management is deferred to a late-stage add-on activity, the risk to realizing investment performance surges.
Sponsorship vs. middle-manager trade-off: Where to invest limited change-management resources is a strategic choice. Rather than dispersing resources across enterprise-wide promotion, it is effective to concentrate on the visible sponsorship of top executives — the highest contributor to success — and on winning over middle managers who move the field. The balance between "broad shallow communication" and "narrow deep leader persuasion" is the crux.
Change fatigue and change-saturation management: In a constant-change environment, beyond managing individual changes well, one must coordinate the total amount of change (Change Saturation) that employees can bear at the portfolio level. When multiple change projects converge at once, employees burn out even if each is successful. Pacing and prioritizing the change schedule are necessary.
Measurement and ROI linkage: One must quantitatively measure the effect of change management with usage rate, proficiency, and performance indicators, and link this to the project's ROI and BSC to make it visible to executives, securing the justification for continued investment. Change management that is not measured easily becomes the first activity to have its budget cut.
Linked technologies·methodologies: Change management is closely linked with project management (the Stakeholder·Team performance domains of PMBOK 7th Edition), service transition (Change Enablement·Service Transition of ITIL 4), organizational culture·leadership, and educational technology. Especially in DX·AI adoption projects, it is desirable to specify change management as a separate Work Breakdown Structure (WBS) item and budget — no less than technology construction — to formalize responsibility and resources.
References
- Prosci, "The Prosci ADKAR Model", https://www.prosci.com/methodology/adkar
- John Kotter, "The 8-Step Process for Leading Change", https://www.kotterinc.com/methodology/8-steps/
- MindTools, "Lewin's Change Management Model", https://www.mindtools.com/ajm9l1e/lewins-change-management-model
In one line: Organizational change management is a people-side management activity that leads people to actually adopt and master technology/process change and converts it into investment performance; it succeeds only by combining Lewin (macro state transition), Kotter (execution roadmap), and ADKAR (individual-transition diagnosis) and integrating with project management around the axes of sponsorship, communication, resistance management, and measurement.