Change Management in Digital Transformation Projects

Change Management in Digital Transformation Projects: A Guide for Managers

An organisation buys a good system, trains staff for one day, then discovers months later that much of the work is still in notebooks and Excel files. Change management is what prevents this familiar scenario.

Skills and change management 6 min read

By Nour Aldein Tleti. Updated 7 October 2026.

What is change management in digital transformation projects?

Change management is the organised planning of how people move from the old way of working to the new one. It is not just installing a system. It covers explaining why the change is happening, involving users early, training them by role, supporting them after launch, and retiring the old alternatives at the right time.

Why do projects stall without change management?

Treating the project as purely technical: An IT department or vendor is tasked with the installation, and nobody takes responsibility for changing how departments work.
No convincing reason: When an employee does not understand the problem the system solves, they see it as nothing more than extra work.
The old alternative stays: If paper reports and Excel files are still accepted, everyone will go back to them at the first difficulty.
Short, generic training: One presentation for all staff does not answer the questions of the storekeeper, the accountant or the receptionist.
Nobody follows up after launch: The vendor leaves after handover, and no one in the organisation is left to answer questions or notice that usage is falling.

The elements of change management

A sponsor from senior management: Someone with real authority who settles disagreements and shows their commitment in front of the team.
Impact analysis: For each role: what will change in their daily work? What will become easier, and what will be harder for a while?
A communication plan: Clear, repeated messages about the reason, the timeline and what is expected of each person.
A training plan: Hands-on training by role, close to the launch date, with materials people can refer back to later.
Post-launch support: Daily follow-up in the first weeks, quick problem-solving, and measurement of actual usage.

In the Syrian context

Mixed experience in the same department: One employee may be fluent with computers while another has relied on a notebook for years, and training must cater for both.
Outages disrupt the launch: Define a fallback procedure for working during power or internet cuts, so an outage does not become an excuse to return to the old way.
The weight of personal relationships: The influential person in a department, even if not a manager, can speed up adoption or block it, so involve them from the start.
Currency and prices in the system: Exchange-rate swings mean staff need clear rules for entering both currencies and updating prices, or they will go back to their own calculations on paper.

A short change management plan

01
Name the sponsor and the team
A responsible manager, a project coordinator and a representative from each affected department.
02
Explain the problem before the solution
Bring staff together and talk about the current problem with examples they know, then present the system as the answer to it.
03
Involve users in testing
Let department representatives try the system on real cases and suggest changes.
04
Train, then launch
Role-based training just before launch, then a launch with close on-site support.
05
Retire the old alternatives
Set a date after which paper reports or parallel spreadsheets are no longer accepted.
06
Measure and adjust
Monitor usage, errors and feedback, and adjust the system or the training as needed.

A purely technical project or one with change management?

Aspect	Technical project only	Project with change management
Starting point	Choosing and installing the software	Understanding the problem and involving departments in defining it
Training	One general presentation before launch	Hands-on training for each role, with internal go-to people
The old way	Remains available with no end date	Retired on an announced date after a transition period
After launch	The vendor leaves and problems are left to staff	Daily follow-up, usage measurement and continuous adjustments

Read also

Skills and change management

Frequently asked questions

When does change management start?

Before choosing the system, because involving staff in defining the problems and requirements makes them partners in the solution rather than people it is imposed on.

Does a small company need change management?

Yes, but in a simpler form: an honest conversation with the team, hands-on training, follow-up in the first weeks, and a clear decision to stop the old way.

Who leads the change, management or the vendor?

The vendor supports and trains, but leading the change is the organisation’s management’s responsibility, because only management can decide to change how work is done.

How do we know the change has succeeded?

When the system becomes the only source of information, decisions are made from its reports, and staff no longer need to go back to notebooks or spreadsheets.

Do we need an outside party to manage the change?

Not always, as leadership stays with management. But an experienced partner such as ONE DIGITAL’s branch in Hama can help plan the launch, the training and communication with the team, alongside the technical side.