A new job management system goes live, and six months later the old spreadsheet is still open on several desks. A contracts manager role is created, and pricing decisions still go to the managing director. Neither is a fault in the system or the role. Both are what happens when a change is installed but not managed.
Organisational change management is the work that sits between deciding on a change and that change becoming the normal way the business runs. This guide covers what it is, how it relates to organisational design, what makes operational change different, the main models, the steps in a change, how to tell whether a change has stuck, what a change strategy includes, and what guidance and the law say when a change touches employees’ terms.
What is organisational change management?
Organisational change management is the structured approach a business uses to move people, teams and processes from the way work is done now to a defined new way of working, and to keep it there.
It helps to separate two things that are often run together:
- The change itself: a new structure, system, process, role or way of pricing work.
- The management of the change: the communication, capability building, support and reinforcement that get people working the new way and stop them drifting back.
A business can get the first right and still fail on the second. A well-chosen system that nobody uses has not changed how the business runs.
Change management also differs from business transformation. Transformation is a deliberate redesign of how a business creates value, touching several parts of the operating model at once. Change management is one discipline within a transformation, but it applies equally to much smaller changes, such as a new handover between sales and operations or a new way of logging variations.
How do organisational design and change management work together?
The two disciplines answer different questions.
| Organisational design | Change management | |
|---|---|---|
| Question it answers | What should the structure, roles and decision rights be? | How do people move into that structure and keep working in it? |
| Main outputs | Structure, role definitions, reporting lines, decision rights, core processes | Communication, training, support, feedback, reinforcement |
| What goes wrong without the other | A new organisation chart that people work around | Energy and goodwill, but no clear roles to move into |
The organisational design process decides who owns what. Change management makes that ownership real. In practice the two meet at four points:
- Before announcing: roles and decision rights are defined before the change is communicated, so the first question from the team (“who do I go to now?”) has an answer.
- When communicating: the reasons behind the design are explained, not just the new chart.
- When building capability: training covers the new role as well as any new system, including the decisions the role now makes.
- After launch: feedback from people working in the new design is used to adjust it, rather than treated as resistance.
What is operational change management?
Operational change management is change management applied to how day-to-day work runs: processes, systems, scheduling, quoting, job costing, handovers between teams, and the reporting rhythm managers use to run the business.
It overlaps with structural change (who reports to whom) and strategic change (which markets and services the business pursues), but it has three features of its own:
- The business keeps trading. Operational change happens alongside live work. Jobs still have to be scheduled, installed, invoiced and paid while the new way is being introduced.
- The people asked to change are the people running the work. The planners, supervisors and engineers who need to learn the new process are the same people keeping current jobs on track.
- Old and new often run side by side. For a period, both the old and new way of working are available. A fallback that is always available is easy to keep using, so the point at which the old way is switched off needs to be decided, not left to happen.
Examples across Heating, Ventilation and Air Conditioning (HVAC), electrical contracting and renewables businesses include moving job scheduling from a whiteboard into a single system, introducing a standard handover pack from sales to operations, changing how labour and materials are costed on each job, or moving from owner-approved purchase orders to set approval limits.
When several of these change together (structure, decision rights, processes and systems at once), the work becomes operating model transformation, and change management becomes one strand of a larger programme.
Check your business: how change is set up
- Were the roles and decision rights for your last change settled before it was announced?
- Are decisions now made where the new structure says they should be?
- When a new system or process went live, was there a set date for switching off the old way?
What are the main change management models?
Several published models describe how change is led. Two of them look at change from different levels.
Kotter’s 8 steps describe how to lead change across an organisation. As set out by Kotter, the steps are: create a sense of urgency; build a guiding coalition; form a strategic vision; enlist a volunteer army; enable action by removing barriers; generate short-term wins; sustain acceleration; and institute change.
Prosci’s ADKAR Model looks at change at individual level. Prosci describes ADKAR as “a model for individual change”, which breaks change into five observable elements: Awareness, Desire, Knowledge, Ability and Reinforcement.
The two can be used together. Kotter’s steps shape the overall sequence of a change. ADKAR helps explain why one person or team is behind the rest: a supervisor who understands why a change is happening (awareness) but has not been trained in the new process (knowledge) needs something different from one who has been trained but does not see the point (desire).
Neither model is a guarantee. Both are frameworks for thinking through what a change needs, not checklists that make a change succeed on their own. The guide to change management frameworks compares these with other published models.
How do you implement organisational change?
The steps below draw the main models into one practical sequence. The order matters more than the names.
Define the change and the outcome. State what will be different and how anyone will know. “Move scheduling into the job management system” is an activity. “Every job scheduled in one place, visible to the whole operations team” is an outcome. Take a baseline measure before starting.
Map who is affected and how. List the roles whose tasks, decisions, tools or terms will change. A change that looks small at director level can alter most of a planner’s day.
Design before announcing. Settle roles, decision rights, process steps and system set-up before the change is communicated widely, so questions can be answered when they are asked.
Explain the reasons before the detail. Setting out the reasons first gives the detail context. Set out the problem the change solves, what will change, when, and what other options were considered.
Equip people to work the new way. Training, documented standard operating procedures, and someone to ask in the first weeks. Procedures written down before launch also give new starters the same version as everyone else. Managers who ask what is getting in the way before offering an answer can help the new way settle; how to create a coaching culture in a small organisation covers how to build that habit.
Run old and new deliberately, then retire the old. If a period of parallel running is needed, give it an end date and remove access to the old way when it arrives.
Gather feedback and adjust. Ask the people doing the work what is getting in the way, and change the process or the design where the feedback shows a real problem. People are more willing to raise those problems where reporting them is safe, which is part of building trust in a healthy company culture.
Reinforce and hand over ownership. Recognise the teams using the new way, build it into reviews and reporting, and hand ownership from whoever led the change to the line managers who will run it. How those line managers behave, for example whether they lead by example and hold people to the new way, has a large effect on whether it sticks; see leadership behaviours that improve performance.
How do you know a change has stuck?
A change has stuck when the new way is the default and the old way has gone, not when the launch date has passed. Four kinds of evidence help show the difference. If a redesign has not stuck, why a target operating model fails and how to fix it sets out the usual causes.
| Evidence | What it shows | Examples |
|---|---|---|
| Adoption | Whether the new way is being used | Share of jobs scheduled in the new system; share of quotes on the new template |
| Workarounds | Whether the old way is still in use alongside the new | Spreadsheets still being updated; approvals still going to the owner by phone |
| Decision level | Whether decisions are made where the design says | Purchase orders approved within limits without escalation |
| Outcomes | Whether the business is performing differently | Time from enquiry to quote; jobs invoiced on completion; rework |
Adoption and workarounds can be measured sooner than outcomes, and financial results take longer still. Tracking only the lagging measures means a stalled change may not be noticed until it is expensive to correct. The guide to business performance management covers how performance is measured and reviewed more broadly.
Ownership is the other test. If the person who led the change is still the only one checking whether it is being followed, the change depends on them rather than on the way the business runs.
Check your business: whether change sticks
- Can the outcome of your last change be stated in one sentence, with a measure taken before it started?
- Is there a measure that shows whether the new way of working is being used, not only whether it was launched?
- Does a named line manager own the change now that the project has finished?
What should an organisational change strategy include?
A change plan sets out the steps for one change. A change strategy decides which changes the business takes on, in what order, and at what pace. When several related changes are managed together, they become an organisational change programme.
A change strategy typically covers:
- The link to the business’s objectives. Each change should trace back to something the business is trying to achieve, such as growth without adding proportionate overhead, preparing for investment, or reducing dependence on a few people.
- Sequence and capacity. The same managers and teams absorb every change. Running fewer changes at once, in a deliberate order, can reduce the load on the day job and gives each change time to settle.
- Sponsorship. A named sponsor with time set aside, who attends reviews and makes trade-off decisions, not a title on a slide.
- Capability. The skills managers need to lead change, and how they will build them.
- Governance and measures. Who reviews progress, how often, which measures they look at, and who can remove blockers.
Change strategy sits alongside organisational development, the longer-term work on capability, culture and how the organisation learns, which determines how well the business absorbs change in future.
What does guidance say about consulting on changes to employees’ terms?
A change to how existing duties are carried out, such as a new way of logging jobs, is a different matter from a change to the terms of employment themselves, such as hours, pay, place of work or the duties set out in a contract. Which side of that line a change falls on depends on the employee’s terms, including any that are not written down.
Where a change does alter contractual terms, Acas guidance on changing employees’ contracts says employers should inform and consult all affected workers and their representatives. Acas lists what they should be told about:
- what the proposed changes are
- who might be affected
- why the changes may be needed
- the timeframe for the proposed changes
- any other options that have been considered
Acas also notes a risk of discrimination if anyone is excluded or accidentally overlooked, for example someone who is absent through sickness, or who needs information in a particular format because of a disability or because English is not their first language.
Where an employer seeking to change contracts envisages that it might dismiss employees who do not agree and re-engage them on new terms, the statutory Dismissal and re-engagement: code of practice applies. It does not apply where redundancy is the only reason for a possible dismissal. GOV.UK says the code sets out employers’ responsibilities when seeking to change contractual terms and conditions, and seeks to ensure dismissal and re-engagement is only used as a last resort. The code says that in certain tribunal claims, a tribunal can increase an award by up to 25% where an employer has unreasonably failed to comply with it, or reduce it by up to 25% where the employee has. Acas notes the code applies only to those with the legal status of employee, but advises following the same fair procedure for workers.
The law on fire and rehire is changing. The government’s Employment Rights Act timeline update lists new fire and rehire protections among the measures due to take effect in January 2027, and notes that all future dates remain subject to parliamentary processes and may change.
Where a business, or part of one, moves to a new employer, for example through an asset purchase or a change of service provider, Acas explains that workers might be protected by TUPE when an organisation is transferred from one employer to another. Acas also sets out when contracts can be changed after a TUPE transfer.
Frequently asked questions
The terms can be used to mean the same thing. “Organisational” makes clear the change concerns how the business is structured and run (its roles, processes and ways of working) rather than change control on IT systems, which is also called change management.
It is change management applied to day-to-day operations: processes, systems, scheduling, quoting, job costing and handovers between teams. Its main distinguishing features are that the business keeps trading while the change happens, and that new and old ways of working often run side by side for a period.
Two published models are Kotter’s 8 steps, which describe how to lead change across an organisation, and Prosci’s ADKAR Model, which looks at change at individual level through Awareness, Desire, Knowledge, Ability and Reinforcement.
It is a set of related changes managed together under one sponsor and one review rhythm, so that their sequence, the capacity they need and their combined effect on the business are planned as a whole rather than change by change.
There is no fixed timescale. Adoption measures can be tracked sooner than changes to outcomes, and financial results take longer still. The size of the change, the number of people affected and how many other changes are running at the same time all affect the timescale.
Acas guidance says employers should inform and consult all affected workers and their representatives about what the changes are, who might be affected, why they may be needed, the timeframe and other options considered. Where an employer envisages dismissal and re-engagement, the statutory code of practice also applies, and the government’s timeline lists new fire and rehire protections for January 2027, subject to parliamentary processes.
Sources
- Acas, Treating all workers fairly – Changing your employees’ contracts (last updated 10 August 2026)
- Acas, TUPE transfers
- Acas, Changing a contract after TUPE
- GOV.UK, Dismissal and re-engagement: code of practice
- GOV.UK, Plan to Make Work Pay and Employment Rights Act: timeline update (last updated 14 October 2026)
- Kotter, The 8 Steps for Leading Change
- Prosci, The Prosci ADKAR Model
Figures last checked: October 2026




