Change management in digital transformation: a practical guide

In short: Change management in digital transformation is the work of helping staff understand why the way of working must change, accept it and actually use the new tools. When it is missing, the symptom is easy to spot: the software is live, yet people keep their own spreadsheets on the side. The core of it is leadership explaining the reason in person, a champion in every team, training built around real daily tasks, and measuring actual use rather than accounts created.

What is change management?

Change management is the deliberate process of moving people from an old way of working to a new one: preparing them, supporting them through the switch and making sure the new way sticks. In digital transformation, what changes is how employees work with processes, data and software.

Picture a hypothetical company that buys a CRM (customer relationship management system) for a 15-person sales team. Three months later the system runs and everyone has a login, but most reps still keep customer numbers on their phones and update the CRM just before the weekly meeting. Reports are incomplete and late, so the director goes back to asking each person. Nothing is wrong with the software. What's missing is change management.

It is also different from project management. Project management gets the software installed on time and on budget. Change management makes sure people actually work the new way after go-live.

Why people decide whether transformation succeeds

Software only creates value when it is used every day, so real adoption matters more than feature lists. According to BCG (2020), 70% of digital transformations fall short of their objectives, and two of BCG's six success factors are about people: leadership commitment from the CEO through middle management, and a governance approach that drives broader adoption.

Prosci, a change management research firm, reports that projects with excellent change management are about seven times more likely to meet objectives than those with poor change management. The figure comes from its Best Practices in Change Management study of more than 2,600 practitioners, so it is a survey correlation, not a controlled experiment. Still, it matches what implementers see: projects fail because of people more often than because of software.

In smaller companies the effect is sharper. One senior salesperson who won't enter data can spoil the whole team's reports, and colleagues notice.

Why staff resist change

Resistance usually has a real cause. Understanding the cause is how you pick the fix.

Concern	Typical behaviour	What helps
Fear of losing their job to automation or AI	Silence, slow progress, hunting for software faults	Leadership states which tasks get automated and what those people will do next
Fear of being monitored	Partial, late or token data entry	Explain what the data is for and who sees it; don't use new data to punish right away
Double work	Keeping the old spreadsheet going	Retire the old file, have one place to enter data
Low confidence with new tools	Asking colleagues to do it, avoiding the system	Task-based training, a helper sitting in the team
No personal benefit	"The old way works fine"	Show which of their own chores gets lighter, such as month-end reporting
Losing status as keeper of information	Delaying the move of "master" files	Make that person the data owner in the new system

Fears about AI need to be addressed early. When a business brings in AI for everyday work or AI agents that look things up and draft documents, people wonder whether their job is safe. If leadership says nothing, rumours fill the gap.

Two models worth knowing

The two most widely used models are ADKAR and Kotter's eight steps. Small businesses don't need to apply them to the letter, but both make useful checklists.

Prosci's ADKAR model looks at change one person at a time, through five stages: Awareness (why change?), Desire (what's in it for me?), Knowledge (how do I do it?), Ability (can I actually do it?) and Reinforcement (does anyone notice?). When someone is stuck, find the stage and work on that.

Kotter's eight steps look at the organisation: create a sense of urgency, build a guiding coalition, form a strategic vision, enlist volunteers, remove barriers, generate short-term wins, sustain acceleration and institute the change. For SMEs, the two most useful are removing barriers and generating short-term wins.

Six steps to manage change

These steps run alongside your digital transformation roadmap, not after the software is finished.

Step 1: Leadership explains the reason and commits

The director speaks to staff directly rather than delegating it to IT or the vendor. Cover the current problem with numbers, what will change, what stays the same, whether there will be job cuts, and who answers questions. A company meeting plus short talks with each team beats a long email.

Step 2: Choose a champion in each team

Pick someone colleagues trust, who likes learning new things and gets time for the project. Champions try things first, feed into the design, then coach and support colleagues. People ask the person at the next desk far more readily than a helpdesk.

Step 3: Involve users in designing the new process

The people doing the work know the detours their managers don't see. When they shape the new process, they have a reason to defend it. Our guide to business process automation explains how to map processes with users.

Step 4: Train on tasks, not features

Feature-by-feature training is forgotten within a week. Train on the jobs people actually do, such as "creating a quote for a new customer" or "handling a returned order". Give each task a one-page guide or short video, and have a helper on hand during the first week.

Step 5: Create early wins and talk about them

Pick a result visible within the first few weeks, such as a sales report that is ready every morning instead of compiled by hand, and share it at a company meeting, naming the people involved. A visible win answers "what do we get?" better than any presentation.

Step 6: Switch off the old way and manage by the new one

Set a date to stop accepting Excel reports and approvals by chat message. From then on, weekly meetings use only system data. When the director looks only at system numbers, staff enter data fully and on time without constant reminders.

Department heads make or break it

Staff hear the director once but work with their manager every day. If the department head still assigns work by chat and asks for figures in Excel, staff conclude the old way is the real one. Department heads therefore need to be the first users of the new system.

They are also under the most pressure, protecting monthly results while persuading their teams. Give them a clear adoption target and accept a small dip in productivity for the first few weeks rather than demanding every number holds. Otherwise the safe choice for them is to allow parallel working, and the old way never gets switched off.

How to measure real adoption

Measure behaviour, not accounts or training sessions held.

Measure	How to track it	Warning sign
Share of transactions in the system	Orders and quotes in the system vs. actual totals	Much lower in one team or for one person
Entry delay	Time between an event and its entry	Data entered in bulk before meetings
Shadow files	Old spreadsheets still being updated	Old files alive after the switch-off date
Support requests	Weekly count and topics	The same question again and again
Business KPIs	Processing time, error rate vs. baseline	High usage but no KPI improvement

Review these weekly in the first month, then monthly. Low use in one team is rarely laziness; more often the new process doesn't fit their real work and needs fixing.

FAQ

What is change management? The deliberate process of moving people from an old way of working to a new one: preparing them, supporting the switch and making the change stick. In digital transformation it is what gets staff to actually use new processes and software.

Who is responsible for change management? A director or leadership team member owns it; department heads and champions carry it out in each team. Advisers and vendors support but can't replace leadership's voice.

How do we get older staff to use new software? Train them on the tasks they actually do, at a slower pace, with someone beside them in the first week. Show which of their chores gets lighter, and ask for their input on the process since they often know the business best.

Should using the new system be mandatory? Yes, once training is done and pilot issues are fixed. The most effective mandate is leadership using only system data and switching off the old way on an announced date.

How long does change management take? It starts at the announcement and lasts until the new way is a habit, well beyond go-live. Keep tracking adoption until the numbers have been stable for several months.

---

HAT Solutions delivers digital transformation together with the change management behind it: preparing leadership's message, task-based training and measuring real adoption after go-live. Contact us for advice. Read more: What is digital transformation?