What it means
Organisations change constantly: new software, mergers, restructurings, new products, new regulations, new leaders. Each change asks people to stop doing something familiar and start doing something unfamiliar, and people resist that for good reasons: they do not understand why, they doubt it will work, they fear for their position, they lack the skills, or they have seen previous changes fail.
Change management is the discipline of anticipating and working through that resistance so that the change takes hold. The established models share a sequence.
First, establish why the change is needed and make the case compelling enough that people prefer the change to the status quo. Second, build a coalition of leaders who visibly sponsor the change and a network of people across the organisation who champion it.
Third, describe the future state clearly: what will be different, for whom, and what will not change. Fourth, communicate repeatedly through every channel, answering the question everyone asks first, which is what it means for them.
Fifth, remove obstacles: policies, systems, incentives and managers that block the change. Sixth, equip people with the skills and support to work in the new way, through training, coaching and time.
Seventh, produce and celebrate early wins that prove the change works. Eighth, embed the change in structures, measures and rewards so that it does not revert when attention moves on.
The models differ in emphasis. Some focus on the individual (awareness, desire, knowledge, ability, reinforcement), some on the organisation (unfreeze, change, refreeze), some on leadership.
All agree on the central findings: sponsorship from the top is the strongest predictor of success; communication is never enough; middle managers make or break adoption; and changes that alter incentives and measures stick while those that rely on goodwill fade. For finance, change management appears in three places.
As a cost: every system implementation, restructuring or process redesign should budget for communication, training, temporary productivity loss and the time of the people driving the change, which typically adds 10% to 20% to the technical cost and is the item most often omitted. As a risk: the business case for a project assumes adoption, and the benefits (efficiency, accuracy, speed) arrive only if the new way is actually used; finance should ask how adoption will be achieved and measured.
As a subject: finance functions themselves are changed repeatedly (new systems, shared services, automation, new standards) and are often the worst-managed changes in the organisation, because their leaders assume competent people will simply adapt. Measures of change management include adoption rates (proportion of users on the new system or process), proficiency (error rates, time per task), benefit realisation (savings or improvements achieved against the business case), and, on the human side, survey measures of understanding and commitment.
A change that scores well on these is delivering; one that has been "implemented" without them may be a fiction.
In practice
Real-world examples.
Example
A bank merging two branch networks runs a two-year change programme covering systems, roles, branding and culture, with a change team of forty.
Example
A finance function moving to a shared service centre manages the change with early communication about roles, retention bonuses for key staff through transition, and parallel running for two month-ends.
Example
A manufacturer introducing lean production trains every shift supervisor as a change champion before touching the line.
Think of it
“Change management is helping people adapt to new ways-managing the human side of transitions.
Formula
Calculation
Change management is a process, not a formula, but its financial logic can be expressed:
Realised Benefit = Planned benefit x Adoption rate x Proficiency factor
Change Management Cost = Communication + Training + Change team time + Productivity dip during transition
Return on Change Investment = (Realised benefit minus Total project cost) / Total project cost
Worked example. A distribution company implements a new warehouse management system to replace paper picking. Technical cost (software, hardware, integration) $1,200,000. Business case: picking productivity up 30%, errors down 60%, worth $900,000 a year in labour and returns handling.
Scenario A, no change management budget. The system goes live on schedule. Warehouse staff, given a two-hour demonstration, distrust the handheld devices, keep paper lists as a backup, and enter data at the end of shifts. Adoption after six months: 55% of picks through the system as designed. Proficiency: errors initially rise as staff learn, then settle at 30% below the old rate rather than 60%. Realised benefit = $900,000 x 0.55 x about 0.6 = about $300,000 a year. Productivity fell 15% for three months during transition (cost about $190,000). Return in year one: ($300,000 minus $190,000 minus $1,200,000) / $1,200,000 = minus 91%; steady state: $300,000 a year against a $1,200,000 investment, a four-year payback for a project sold on eighteen months.
Scenario B, change management budgeted at $180,000 (15% of technical cost): a change lead seconded from operations for six months ($45,000); supervisor workshops before design so the workflows reflect how the warehouse actually works ($20,000); structured training with practice time on the floor, not in a classroom ($60,000); floor walkers for the first four weeks after go-live ($30,000); a weekly adoption dashboard shown to every shift, with the first team to reach 95% system picks recognised publicly ($5,000); and the removal of paper lists on a fixed date, announced in advance, with a supervisor sign-off process for exceptions ($20,000 of process design). Adoption after six months: 96%. Errors down 55%. Productivity dipped 8% for five weeks (cost about $50,000). Realised benefit = $900,000 x 0.96 x 0.92 = about $795,000 a year. Return in year one: ($795,000 minus $50,000 minus $1,380,000) / $1,380,000 = minus 46%; steady state $795,000 a year, payback about twenty months.
The $180,000 of change management produced about $495,000 a year of additional benefit and cut the transition cost by $140,000: a return on the change budget itself of more than three times in the first year.Case study
Seen in the real world.
A professional services firm replaced its time recording and billing system, a $2,000,000 project, on the assumption that professionals would use the new system because they had to. The old system was switched off on a Friday; the new one went live on Monday with an online tutorial. Within a month, time recording compliance had fallen from 92% to 61%, partners were approving bills late because they could not find the new approval screen, billing for the month fell $3,000,000 short, and the firm drew on its overdraft.
Three partners threatened to leave over "the system". The managing partner appointed a change lead, who found that the system worked but that nobody had told the professionals why it had been chosen, what would change for them, or how to do the six things they did every day. The recovery took four months: a partner from each practice group became a sponsor; every professional received a one-page guide to their six tasks and a fifteen-minute session with a floor walker; the finance team ran a daily compliance report by group, shown to the group heads; and time recording was linked to the bonus scheme's eligibility for the year.
Compliance recovered to 94% and the billing backlog cleared. The firm's post-mortem estimated the cost of the missing change management at $600,000 in lost billing and remediation, against a change budget of $150,000 that had been cut from the project to hit the approved figure.
Watch out
Common mistakes.
- Treating change as a technical implementation with a training session at the end, rather than as a programme that starts before design and continues after go-live.
- Cutting the change management budget to fit the project into an approved figure, which saves 10% of the cost and loses half the benefit.
- Declaring the change complete at go-live. Adoption, proficiency and benefit realisation are measured for months afterwards, and the change is embedded only when measures and incentives depend on the new way.
Questions
People also ask.
How much should a project budget for change management?
Commonly 10% to 20% of the technical cost, more for changes that alter roles, culture or many people's daily work.
What is the single biggest predictor of success?
Visible, active sponsorship from leaders who explain why, model the change and hold people accountable for adopting it.
How is change management measured?
Adoption rate, proficiency (errors, speed), benefit realisation against the business case, and survey measures of understanding and commitment among those affected.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%