how-to
The Change Management Process: 7 Steps That Work
A practical change management process for UK teams: seven steps, a ready-to-use plan, tools and KPIs to prove change delivers.
Editorial Team
·
·
16 min read
Last Updated: October 13, 2026
Why a Change Management Process Beats Heroic Effort
A change management process is the repeatable set of steps an organisation follows to move from a current state to a future state: diagnosis, planning, execution and reinforcement.
Heroic effort burns out: a project lead works weekends, chases approvals by email and holds it together through sheer will.
A defined change management process replaces that fragility with something repeatable. Below: the seven steps, the prerequisites, and the templates that make it stick.
Watch Out The most common failure we see is treating change management as a communications exercise. Communication matters, but it is one step of seven. Skip diagnosis and readiness, and you will spend the rest of the project fighting resistance you could have seen coming.
Prerequisites: What You Need Before You Start
Before the first step, you need a named sponsor, a way to record changes, and a baseline of your current state.
The sponsor has authority to approve or reject the change; without it, your initiative stalls at the first difficult decision.
The record matters just as much. Spreadsheets and email chains undermine control because nobody can say with certainty what changed, who approved it and why.
What you need before step one:
An executive sponsor with decision rights
A change register or platform to log every change
A documented current state to measure against
Get these wrong and every later step costs more.
The 7 Change Management Steps, Phase by Phase
The seven steps below form a full lifecycle, from identifying the need through to reviewing outcomes and feeding lessons into the next change.
Each phase has a clear output. If you cannot name it, the phase is not finished.
Phase 1: Identify the Need and Diagnose Root Causes
Start with the performance gap, not the solution. Ask what is underperforming and why.
Look for root causes, not symptoms. A missed delivery target might trace back to a system nobody was trained on, not lazy staff. Diagnose before you prescribe.
Phase 2: Assess Readiness and Map Stakeholders
Assess organisational readiness honestly. Which teams have the capacity, skills and appetite for this change? Which do not?
Map stakeholders by influence and impact: the most affected need the most support, the most influential the earliest briefing.
Phase 3: Set the Vision, Strategy and Governance
Define the desired state in one paragraph anyone can repeat. Then set governance: who approves, who is consulted, who is informed.
The approval rule that matters most is separation of duties. No change should be approved by the person who raised it.
Phase 4: Build the Implementation Plan and Communicate It
Turn the strategy into a change plan with owners, dates and dependencies. Then communicate it through the channels your teams actually read.
Phase 5: Execute, Monitor and Adjust
Run the plan, but watch the signals. Track adoption, not just completion. Adjust when the data tells you the plan is wrong.
Phase 6: Reinforce, Embed and Sustain the Change
Reinforcement is where most change management steps get dropped. Update processes, training and job aids so the new way becomes the default.
Phase 7: Review Outcomes and Feed Lessons Back
Review against the original business outcomes, document what worked and what failed, then feed those lessons into the next change initiative.
What Belongs in a Change Management Plan
A change management plan turns the seven steps into assigned tasks with dates, owners and evidence. Most plans fail not because they are wrong but because they are unreadable. Keep the core plan to two pages and push detail into appendices.
5 Steps in the Change Management Process | Business: Explained
HBS Online
Every plan should cover:
The current state and the desired future state
The reason for the change and the business outcomes expected
Named owners for each workstream
A Ready-to-Use Plan Template
Rather than starting from a blank page, adapt a fixed structure. The template below is the one we see work most often. Copy it into your document tool and fill the brackets.
Section | What to write | Owner |
|---|---|---|
1. Case for change | One paragraph: the performance gap, the cost of inaction, the outcome if the change lands | Sponsor |
2. Scope and boundaries | What is in, what is explicitly out, which sites or teams are affected | Change lead |
3. Current and future state | A short before/after description, plus a process map if the change alters workflow | Change lead |
4. Stakeholder map | Names, influence, impact, stance (supporter, neutral, sceptic) | Change lead |
5. Impact assessment | Which roles, systems, processes and customers are affected and how | Workstream owners |
6. Governance and decision rights | Who approves, who is consulted, who is informed, escalation path | Sponsor |
7. Plan and milestones | Tasks, owners, dates, dependencies, critical path | Project manager |
8. Communications plan | Audience, message, channel, timing, sender | Comms lead |
9. Training and support | Who needs what training, by when, and how competency is confirmed | L&D lead |
10. Risk and resistance register | Risk, likelihood, impact, mitigation, owner | Change lead |
11. KPIs and measurement | Adoption, proficiency, sentiment, business outcome, review cadence | Sponsor |
12. Reinforcement and embed | Process updates, job aids, performance measures, review date | Workstream owners |
The Three Templates That Do the Heavy Lifting
Three of those sections deserve their own artefact because teams most often skip them.
Change impact assessment. For each affected group, record what changes, the size of the change (minor, moderate, major), the effort to adopt it, and the support needed.
Stakeholder map. Plot stakeholders on two axes: influence (how much they can block or accelerate the change) and impact (how much the change affects them). The four quadrants drive different actions:
High influence, high impact: co-design with them, brief earliest, give them a named contact.
High influence, low impact: keep informed and use as sponsors or advocates.
Low influence, high impact: support heavily, listen for early resistance signals.
Communications plan. One row per message, with columns for audience, key message, channel, sender, timing and feedback route.
Measuring the Plan With Specific KPIs
A plan without measurement is a schedule. Track four categories, each with a named owner and review cadence.
Category | Example KPI | How to measure | Typical cadence |
|---|---|---|---|
Adoption | Percentage of affected staff using the new process or system | System logs or process audit | Weekly during rollout |
Proficiency | Time to competency for new users | Time from first use to passing a competency check | Monthly |
Sentiment | Employee confidence in the change | Short pulse survey, three to five questions | Fortnightly |
Business outcome | The original performance gap, e.g. cycle time, error rate, cost per transaction | Operational reporting | Monthly |
Adoption without proficiency is compliance theatre: people click the button but do not change how they work. Proficiency without adoption means training landed but the process did not. Track both, and review sentiment alongside them to catch quiet resistance before it shows in the numbers.
Key Takeaway A plan without named owners is a wish list. A plan without KPIs is a schedule. A plan without a reinforcement section is a project that will quietly revert six months after go-live.
Change Management Process Examples: IT, ERP and Operational Change
Different change types need different weightings of the same seven steps. The table below shows where risk concentrates and which control matters most.
Change type | Heaviest phase | Typical risk | Key control |
|---|---|---|---|
IT change | Phase 5 (execute and monitor) | Service downtime | Change control and rollback plan |
ERP implementation | Phase 4 (plan and communicate) | Workflow misalignment | Business and IT sign-off |
Operational change | Phase 2 (readiness and stakeholders) | Resistance to change | Early employee involvement |
Compliance-driven change | Phase 3 (vision and governance) | Audit findings | Evidence and approval records |
Restructure or redundancy | Phase 2 (readiness and stakeholders) | Loss of key staff and morale | Consultation and clear decision rights |
For IT change, risk sits in execution. For an ERP rollout, it sits in planning, because IT and business workflows must align before go-live. For operational change, it sits in readiness, because the people affected decide whether it works.
How the Approach Changes With Organisation Size
The same seven steps apply whether you have forty staff or four thousand, but the mechanics differ.
Mid-sized organisations (250 to 2,500 staff). Process discipline starts to matter here.
Large organisations (2,500+ staff). Governance dominates. You need a change advisory board or equivalent, formal decision rights, and visibility of every change in flight across the portfolio.
A Worked Example: Rolling Out a New Finance System
A mid-sized organisation replaces its finance system across three sites:
Phase 1. The performance gap is month-end close taking nine days against a target of five. Root cause is manual reconciliation, not staff capability.
Phase 2. Readiness assessment shows Manchester has a capable finance lead and Bristol does not. The stakeholder map flags the Bristol finance manager as high influence, high impact, currently sceptical.
Phase 3. Vision: close in five days with a single source of financial truth. Governance: finance director approves, IT and finance both sign off on workflow changes.
The Bristol manager, brought in early, becomes the strongest advocate at the other two sites. The sceptic you involve in Phase 2 is the ally you rely on in Phase 6.
Pro Tip When you map change types, ask which phase would hurt most if it were skipped. That is the phase to resource most heavily, regardless of what the template says.
Change Management Tools: What to Look For (and What to Ignore)
The right change management tools give you one governed lifecycle for business, operational and IT change, plus evidence you can hand to an auditor without rebuilding it by hand.
What to look for:
A single record of what changed, who approved it and why
Risk assessment built into the workflow, not bolted on
Separation of duties enforced by the system
What to ignore:
Features that only track IT changes
Tools that require manual evidence assembly
Anything your teams will work around
This is where ChangeGate fits. It unifies business, operational and IT change in one governed lifecycle, generates audit-ready evidence automatically, and gives IT and operations a shared record.
Pro Tip When you evaluate tools, ask the vendor to show you a real audit export for ISO 27001. If they cannot produce one in the demo, the "audit-ready" claim is marketing, not a feature.
Common Mistakes, Risks and How to Respond
The same mistakes sink change initiatives repeatedly.
Skipping diagnosis. You solve the wrong problem. Fix: complete Phase 1 before planning.
No named sponsor. Decisions stall. Fix: secure the sponsor before kick-off.
Communication after the fact. Teams feel done to rather than involved. Fix: brief affected staff early.
Resistance is the one people misread most. Treat it as data, not defiance. Find out whether it is fear of lost status, unclear benefit or genuine workload concern, then respond to the actual cause.
Conclusion: Make the Process the Default
The organisations that handle organisational change well are not the ones with the most heroic managers. They are the ones where the process is the default, and heroics are unnecessary.
That is the shift ChangeGate exists to make. Our platform brings change governance, risk management and benefits tracking into one place, generates audit-ready evidence automatically for ISO 27001, SOC 2 and TISAX, and aligns IT and operational change so nothing falls between them.
Frequently Asked Questions
What are the 5 steps of change management?
A common five-step version of the change management process runs: identify the need for change and diagnose the cause; assess organisational readiness and map stakeholders; set the vision, strategy and governance; build the implementation plan and communicate it; then execute, monitor and reinforce until the change is embedded. Some teams split execution and reinforcement into separate steps, which gives the seven-step version. The steps are the same logic either way, so pick the number that matches how your organisation actually approves and reviews work rather than forcing a fixed count.
What should a change management process include?
At minimum it should include a clear trigger for raising a change, an impact assessment covering people, process and technology, named roles with decision rights, an approval route where the person who raised the change cannot approve it, a communication plan, a rollback or contingency option, and a post-implementation review. For regulated teams, it also needs to produce audit-ready evidence automatically, since ISO 27001, SOC 2 and TISAX auditors expect a traceable record of what changed, who approved it and why.
What is the difference between change management and change control?
Change control is the gate: the approval, impact assessment and record-keeping that stops unplanned changes reaching production. Change management is the wider discipline of helping people adopt the change and making sure the business outcome is realised. In practice you need both. A process with strong change control but no adoption work produces technically successful changes that nobody uses, while adoption work without change control produces enthusiasm that gets undone by an unapproved configuration change three weeks later.
How do you measure whether a change management process is working?
Track a small set of KPIs: percentage of changes approved through the formal route, average time from request to approval, failed or rolled-back change rate, adoption against the target, and benefit realisation against the business case. Add an audit measure such as the number of findings raised on change records. Review these monthly with the change sponsor, not annually. If approval times fall while failed changes also fall, the process is doing its job; if approvals speed up but rollbacks rise, you have weakened control rather than improved it.
See what governed change looks like.
Book a demo
© 2026 Tenax Imperium. All rights reserved.