Change Management Process
When parts of the change management process operate in isolation, the gaps often surface during implementation. Training can be developed before anyone fully understands what is changing for whom, communications can go out before the stakeholder landscape is clear, and adoption can be treated as something that will happen automatically after go-live.
The process below connects that work. Eight steps across four phases move an initiative from definition through sustained adoption, with each step providing information or direction for what comes next.
The sequence gives the work structure without making it rigid. Stakeholder feedback, readiness findings, implementation issues, and adoption results can all lead back to earlier decisions or adjustments to the Change Management Plan.
Establish the Change
People-side assessment needs something sufficiently clear to assess. Before that work begins, the change needs a defined case, scope, intended future state, expected outcomes, sponsor, ownership, and timing.
That does not mean waiting until every solution detail is complete. Most initiatives continue to evolve. It means there is enough clarity to understand the direction of the change, why it matters, and which parts of the organization are likely to be involved.
Sponsorship starts here, and it is more than a name attached to the initiative. The change needs leadership ownership that carries through planning, implementation, adoption, and reinforcement.
Assess Organizational Readiness
The first readiness question applies to the organization as a whole: is the organization in a position to take on this change?
This looks beyond individual Roles and Teams to the conditions surrounding the initiative, including leadership alignment, organizational capacity, change fatigue, available resources, change capability, culture, and other changes already competing for the same people’s attention.
An organization can have a strong business case and still face conditions that make implementation difficult. Identifying those conditions early allows leaders to account for them before they become larger barriers.
Readiness returns later in Step 6 with a narrower question, once the impacts on specific groups are understood.
Conduct Stakeholder Analysis
With the change defined and the organizational conditions understood, the focus moves to the people and groups who will experience or influence it. Stakeholder Analysis and Change Impact Assessment give two different views of the same change.
Stakeholder Analysis identifies the people and groups who are affected by the change, can influence it, or play an important role in its success. Influence, impact, current disposition, stakeholder-related risk, and ownership help show where attention and involvement matter most.
The value is not the stakeholder list itself. The analysis distinguishes a highly influential resistant stakeholder from a large employee group facing significant impact, and both from a supportive leader whose involvement could help move the change forward. Those situations require different responses.
Conduct Change Impact Assessment
Change Impact Assessment moves from the stakeholder landscape to the practical effects of the change. It documents how work will differ for each affected Role or Team in the future state and how significant those differences are.
Significance matters as much as volume. Several major changes concentrated in one Role can require very different support from a single process adjustment spread across the same number of people.
These findings become a direct input to planning. Communication, training, engagement, manager support, readiness, and implementation support should respond to the impacts people will actually experience rather than being designed as generic activities.
For a closer look at how the two assessments divide the work, see how Stakeholder Analysis and Change Impact Assessment differ.
Develop the Change Management Plan
The Change Management Plan is where understanding becomes coordinated action. Stakeholder and impact findings determine which workstreams the initiative needs and how much emphasis each one requires.
The plan brings the major change management workstreams together
- Leadership & sponsorship
- Stakeholder engagement
- Change agent network
- Communication
- Training & enablement
- Manager support
- Resistance management
- Readiness
- Adoption & reinforcement
For larger or more distributed changes, the plan may also include developing a change agent network. A well-designed network extends the reach of the central change team, brings local feedback back into the process, reinforces key messages, and helps surface emerging issues earlier.
Assessment findings shape what goes into the plan
The plan is not a generic checklist, and it is not written once and set aside. It starts from what is known about the change and is adjusted as engagement, readiness, implementation, and adoption produce new information.
The assessments matter because their findings shape the actions and decisions that follow.
Assess Change-Specific Readiness
Readiness appears twice in the process because the two assessments answer different questions at different points.
Change-specific readiness becomes meaningful once the impacts are clear enough to define what each group must be prepared to do and enough preparation has occurred to assess remaining gaps.
An organization can be well positioned to take on an initiative while particular Roles or Teams remain unprepared for implementation. Those gaps may involve understanding, capability, capacity, manager support, local conditions, processes, systems, or other requirements of the future state.
The findings act as a bridge into implementation. They can confirm that preparation is working or show where more communication, training, manager support, leadership action, process changes, or time are still needed.
Support Implementation and Adoption
Implementation moves the organization into the changed environment. Issues that could not be fully understood during design and preparation often become visible once people begin doing the work differently.
A process may work differently in practice than expected. Employees may develop workarounds. Managers may interpret requirements differently. A Team that appeared ready may still need additional support when the future state becomes real.
The Change Management Plan therefore continues through implementation. Manager coaching, change agents, targeted communication, additional training, job aids, local support, feedback channels, and issue escalation can all help people make the transition successfully.
Readiness findings help focus this support. Groups with significant impacts or unresolved gaps may need more attention than groups experiencing relatively minor change.
Go-live is not adoption. A system can launch, a process can officially change, or a new structure can take effect before people have fully adopted the behaviors and ways of working the change depends on.
Measure, Reinforce and Adapt
Implementation does not tell the organization whether the new way of working is taking hold or whether the change is producing the intended result. Those questions require different measures.
Implementation
Did the planned milestones and activities occur, such as go-live, communications, or training delivery?
Adoption
Are people actually using the new process, system, responsibilities, or behaviors as intended?
Outcomes
Is the change contributing to the operational or business results it was intended to support?
Those three views should not be confused. Training completion does not demonstrate proficiency, and a system launch does not show that employees are using it correctly.
When adoption is weaker than expected, the response should match the cause. The barrier may involve capability, manager reinforcement, leadership behavior, workload, process design, system usability, competing priorities, or another part of the change environment.
Reinforcement helps sustain what is working, while measurement shows where the approach needs to adapt.
How the Change Management Steps Work Together
The value of the process is not simply that it contains eight steps. Each part provides information or direction for what follows, while later findings can send the organization back to adjust earlier assumptions, plans, or interventions.
Clarify what the organization is changing, why it matters, and what the intended future state looks like.
Organizational readiness shows whether broader conditions are likely to support or hinder the initiative.
Stakeholder Analysis identifies who matters, who is affected, and where stakeholder attention is needed.
Change Impact Assessment explains what will actually change for affected Roles and Teams.
The Change Management Plan converts what has been learned into coordinated action.
Change-specific readiness shows whether affected groups are prepared and where additional action is needed.
Implementation reveals how the change works in practice and where people need additional support.
Adoption and outcome measures show whether the change is taking hold and what needs reinforcement or adjustment.
Later findings regularly change earlier work. That is expected in a connected process rather than a sign that the process has failed.
The steps provide continuity, but the information generated throughout the change continues to shape the work. That is what keeps the process structured without making it rigid.
The Process Scales With the Change
The same overall process can support many types of organizational change. What varies is the depth, scale, and intensity of the work.
Large, Complex Change
An enterprise ERP implementation may involve extensive Stakeholder Analysis, hundreds of documented impacts, multiple audiences, role-specific training, a change agent network, repeated readiness checks, and substantial implementation support.
Moderate Change
A cross-functional process or technology change may follow the same logic with fewer stakeholder groups, impacts, interventions, and measures.
Smaller Change
A focused policy or process change may require a lighter approach while still considering stakeholders, impacts, readiness, preparation, adoption, and reinforcement.
The point is not to perform every change management activity at maximum scale. The process provides a structure for understanding what the change requires and applying the level of support that fits the initiative.
Frequently Asked Questions
These questions address common distinctions about how the change management process is structured and when different parts of the work occur.
Who is responsible for the change management process?
Responsibility is shared. Leaders and sponsors provide direction, visibility, decisions, and reinforcement. Change practitioners coordinate the people-side assessment and planning. Project or initiative teams provide information about the future state and implementation. Managers help translate the change for their teams and support adoption in day-to-day work. The exact roles vary with the size and complexity of the change.
When should change management begin?
Change management should begin while the change is still being defined rather than shortly before implementation. Starting early leaves time for organizational readiness, stakeholder, and impact findings to influence how the initiative is planned and supported.
Is the change management process linear?
No. The steps follow a logical progression, but the process is iterative. Stakeholder feedback can reveal new impacts, readiness findings can require additional preparation, and implementation or adoption issues can lead to changes in the plan or in the change itself.
What is the difference between the change management process and a Change Management Plan?
The change management process is the broader sequence of work from establishing the change through adoption, measurement, and adaptation. The Change Management Plan is one part of that process. It coordinates the leadership, engagement, communication, training, manager support, resistance, readiness, implementation support, and adoption activities required for a particular change.
Why are there two Change Readiness Assessments in the process?
They answer different questions. Early organizational readiness examines whether the organization has the conditions and capacity to take on the initiative. Later change-specific readiness examines whether affected Roles and Teams are sufficiently prepared for the particular change as implementation approaches.
Find the Right Resource for Your Next Step
Whether you are analyzing stakeholders, assessing impacts, checking readiness, or building the broader change plan, explore Change Adaptive tools and resources designed to support the work.