Change management: driving adoption of a new business tool
Why business tools fail without change management, and the concrete steps that secure adoption by the teams.
You selected the right tool, the technical rollout went smoothly, but three months later nobody is using it. This scenario is common, and it has nothing to do with the quality of the software. The problem is almost always a human one.
Why tools fail
- The surprise effect: the teams discover the tool on the day it is rolled out.
- No sense of purpose: nobody explained why the old tool was being replaced.
- Insufficient training: a one-hour session is not enough to change working habits.
- No way to give feedback: users report problems, but nothing changes. They give up.
- No lead from the top: if management does not use the tool, neither will the teams.
The steps of effective change management
1. Communicate early
From the selection phase onwards, tell the teams about the project, its objectives and the timetable. Transparency reduces resistance.
2. Identify champions
Spot one or two motivated colleagues in each department who are comfortable with digital tools. Train them first so they become close-at-hand points of contact. They are not necessarily the managers: they are the people colleagues naturally go to when they have a problem.
3. Train around usage, not around features
Do not give a guided tour of every menu. Start from concrete business processes: “how do I enter an order?”, “how do I find a customer’s history?”. Adapt the materials to the level of each group of users.
4. Support the transition period
- Allow for a period of dual running if possible (the old and new tools side by side)
- Set up a dedicated support channel (a mailbox, a drop-in session)
- Accept the temporary drop in productivity and own it in front of management
5. Collect feedback and act on it
Hold feedback sessions 1 week, 1 month and 3 months after the rollout. Deal visibly with the irritants that come up. Nothing kills adoption faster than the feeling of not being listened to.
6. Measure adoption
Define simple indicators: the number of logins, the usage rate of key features, the volume of support tickets. Track those indicators over time and adjust the support you provide accordingly.
What to remember
The change management budget should represent 10 to 15% of the total project budget. It is an investment, not an optional expense.