Key points in 30 seconds
- Resistance to change is a normal reaction to uncertainty, not a lack of goodwill.
- Explaining the why before the how greatly reduces resistance.
- Internal champions chosen from within the teams are more credible than management.
- Adoption can be measured: actual usage, quality, satisfaction.
Why teams resist
Faced with change, everyone asks three questions: what do I lose? (habits, mastered skills, status), what do I gain? and will I manage? As long as these questions go unanswered, caution wins. It is not bad will, but a rational reaction to uncertainty.
1. Explain the why before the how
A project announced through its rules ("from the 1st, every opportunity must be entered in the CRM") generates objections. The same project presented through its goal ("we are losing deals because of missed follow-ups, here is how we will fix it") generates questions. Start with the concrete problem the change solves, ideally with a figure.
2. Involve the people affected early
Involve users in the design: pipeline stages, required fields, follow-up rules. What has been co-built gets defended. What has been imposed gets worked around.
3. Rely on internal champions
In each team, identify one or two people respected by their colleagues, not necessarily managers. Train them first, give them an official role and time. With their peers, their opinion carries more weight than management's.
4. Train for the task, not the tool
Training that covers every feature is quickly forgotten. Training that shows how to perform the five daily actions of the role is applied the very next day. Plan short sessions, then a reference guide available at any time.
5. Retire the old solutions
If the old Excel file remains available, it will keep being used. Set a date when the old system becomes read-only, then archived.
6. Measure adoption
| Indicator | Example for a CRM project |
|---|---|
| Usage | Share of sales reps logged in every day |
| Quality | Share of opportunities with a dated next step |
| Outcome | Change in conversion rate |
| Sentiment | Short survey after one month, then after three months |
7. Celebrate early wins
A deal won thanks to an automated follow-up, an hour saved on reporting: share these wins in team meetings. They turn an imposed project into a useful one.
Typical timeline for an SME: one month of preparation and co-design, one month of rollout with the champions, then three months of adoption monitoring before considering the change embedded.
Frequently asked questions
What is change management?
It is the set of actions that help employees adopt a new organisation, tool or strategy: explanation, involvement, training, support and measurement of adoption.
How can you reduce resistance to change?
By explaining the problem the change solves, involving users in its design, relying on credible internal champions and training people on everyday tasks rather than every feature.
How long does change take in an SME?
For a project such as a CRM rollout, allow about five months: one month of preparation, one month of rollout and three months of adoption monitoring.