Organizational change affects people, processes, technology, responsibilities, and measures of success. A change management process provides a structured way to define the case for change, assess impacts, engage stakeholders, prepare affected groups, implement the transition, measure adoption and outcomes, and sustain the new way of working.
This guide explains eight practical change management steps, four commonly used models, the roles involved, and visual templates for planning and communication. No framework guarantees adoption or project success; the approach should be adapted to the scope, risk, culture, and people affected by the change.
What is the Change Management Process?
The change management process is a structured approach to preparing, supporting, and enabling people and organizations through a defined transition. It complements project management: project activities deliver a solution, while change management addresses stakeholder impacts, communication, readiness, learning, adoption, and reinforcement.
A practical process identifies the reason for change, defines the target outcome, assesses affected roles and workflows, engages stakeholders, plans communication and training, implements the transition, gathers evidence and feedback, and reinforces the adopted behaviors. Outcomes depend on leadership, participation, implementation quality, and context—not the framework alone.
Change Management Process Steps
The following eight-step sequence is a practical synthesis rather than a universal standard. Adapt the activities, governance, and review cadence to the initiative:
1. Identify the need for change
Define the problem or opportunity using evidence rather than assumption. State the business outcome, what happens if no change is made, who is affected, the initial scope, and the executive sponsor or accountable owner. Separate the need for change from a preferred solution so alternatives can be evaluated.
2. Planning and analysis
Assess organizational readiness and the impact on people, roles, processes, systems, customers, controls, and partners. Define objectives and measures, governance, resources, dependencies, risks, communication, learning, support, and rollout approach. Establish a baseline so adoption and business outcomes can be evaluated later.
3. Stakeholder engagement
Identify stakeholders by influence, impact, role, location, and information need. Engage affected groups early enough to test assumptions, understand practical barriers, and improve the design. Participation does not eliminate resistance, but it can reveal concerns and create more credible communication and support plans.
4. Design the change
Translate the case for change into a clear future state. Document changes to workflows, ownership, handoffs, systems, skills, policies, measures, and behaviors. Compare the current and future states to identify transition requirements, affected groups, control changes, and implementation risks.
5. Implementation
Execute the approved rollout using the appropriate project and operational controls. Communicate what is changing and why, prepare managers, provide role-specific learning and support, update procedures and systems, and make escalation paths clear. A pilot or phased rollout may reduce risk when the context allows it.
6. Monitoring and evaluation
Track both delivery and adoption. Useful measures may include readiness, training completion, proficiency, usage, process adherence, support demand, employee or customer feedback, and the business outcomes defined in the case for change. Interpret measures in context and investigate causes before taking corrective action.
7. Feedback and adaptation
Collect feedback through manager check-ins, support channels, observation, surveys, performance data, and a retrospective meeting where appropriate. Record the issue, evidence, owner, decision, and follow-through. Adapt communication, learning, support, or the solution itself when evidence shows a change is needed.
8. Sustain and institutionalize
Transfer accountability from the change initiative to operational owners. Update policies, procedures, onboarding, measures, role expectations, and supporting systems. Continue measuring adoption and outcomes, recognize desired behaviors, address barriers, and maintain the current process documentation as the operating model evolves.
Why is the Change Management Process Important?
Creates a shared direction: A documented case for change, target outcome, scope, and measures gives sponsors, managers, and affected groups a common reference.
Makes impacts visible: Impact analysis identifies changes to roles, workflows, systems, skills, controls, customers, and cross-functional handoffs.
Improves communication planning: Stakeholder analysis helps teams tailor messages, channels, timing, and feedback mechanisms to different audiences.
Supports readiness and adoption: Role-specific learning, manager preparation, support, and reinforcement address the people side of implementation.
Enables evidence-based adaptation: Adoption and outcome measures help teams identify barriers and adjust the intervention instead of assuming the rollout is working.
Supports sustained operation: Clear operational ownership, updated documentation, measures, and reinforcement reduce the risk that the organization reverts unintentionally.
These are potential benefits, not guarantees. Change outcomes depend on the initiative, leadership, solution quality, organizational context, and the participation of affected people.
Change Management Process Models
Change management models provide different lenses for planning and supporting change. They are not interchangeable checklists or guarantees. Choose and adapt a model based on whether the initiative needs an individual-adoption lens, an organizational sequence, a transition concept, or an alignment diagnostic.
To learn more about these models in detail, refer to our post on change management tools.
- Prosci ADKAR model: ADKAR stands for Awareness, Desire, Knowledge, Ability, and Reinforcement. Prosci describes these as outcomes an individual needs to achieve through a change. Use it to diagnose barriers to individual adoption; combine it with organizational planning and project governance.
- Kotter’s 8-step change model: Kotter’s framework moves from creating urgency and a guiding coalition through forming and communicating a vision, enabling action, generating short-term wins, sustaining acceleration, and instituting change. Treat it as guidance to adapt rather than proof that an initiative will succeed.
- Lewin’s change management model: Commonly summarized as unfreeze, change, and refreeze, this model emphasizes preparing the current state, moving through a transition, and stabilizing new practices. In continuously changing environments, “refreeze” is better understood as reinforcing the adopted state while retaining the ability to learn and adapt.
- The McKinsey 7-S framework: The framework examines strategy, structure, systems, shared values, style, staff, and skills as interrelated organizational factors. McKinsey presents it as a way to understand coordination and organizational complexity; it can reveal alignment questions but does not prescribe a complete change process.
Who is Responsible for Change Management Process
Responsibility is distributed, but accountability should be explicit. Typical roles include an executive sponsor who authorizes and champions the change; a change lead who plans adoption activities; a project or program manager who coordinates delivery; people managers who translate the change for their teams; process and system owners who maintain the future operating model; subject-matter experts who validate impacts; and affected employees, customers, suppliers, or partners who provide practical feedback.
Use a responsibility model such as RACI where helpful, but define decision rights and escalation paths—not only participation. Avoid describing “everyone” as jointly accountable, because shared participation does not replace a named owner.
How to Use Creately to Successfully Lead Your Change Management Process
Creately Process helps change teams document current- and future-state workflows, clarify owners and handoffs, and keep supporting notes, links, and files connected to relevant process steps. Real-time editing and contextual comments let stakeholders discuss the map together. The accountable process owner can incorporate agreed updates and maintain it as living documentation; this does not imply formal approval states or automatic synchronization with operational systems.
Initiation and planning
Create a workspace for the initiative and organize relevant visuals for the case for change, readiness, objectives, stakeholder analysis, impact assessment, communication, and learning. Apply appropriate sharing permissions and invite the stakeholders who need to contribute or review.
Collaborative ideation and design
Use brainstorming templates or sticky notes to collect options and concerns, then evaluate them against evidence, constraints, stakeholder impact, and the target outcome. Separate ideation from the decision record so participants can see which proposal was selected and why.
Documentation and resource management
Add notes, links, and files to relevant process shapes so change plans, training guidance, risk information, and reference material remain connected to the workflow they explain. This helps people find context without claiming that the canvas replaces every document repository or governed system of record.
Task management and progress tracking
Use the Kanban template as a visual planning aid for work items, owners, and stages where that fits the team’s operating practice. Keep formal task execution, approvals, notifications, and audit records in the organization’s authorized work-management or governance system when required. The process map remains the reference for how work and handoffs should operate.
Collaborative meetings and workshops
Use Creately’s integration with Microsoft Teams to bring the relevant visual workspace into a Teams collaboration context. Participants can review maps and workshop visuals together; Microsoft Teams provides the meeting environment, while Creately provides the shared visual content.
Effective change management connects a clear reason for change with accountable sponsorship, stakeholder participation, practical support, and evidence of adoption and outcomes. Visual tools can make impacts, handoffs, decisions, and documentation easier to review, but sustained change depends on operational follow-through and continued ownership.
