Why change management comes too late
In many projects, change management is a line in the schedule placed between acceptance testing and go-live. It boils down to a communication campaign and training sessions. Its budget is often the first to be cut when the project drifts, because its effects only become visible afterwards.
The result is well known. On go-live day, users discover a tool designed without them. They look for their usual cases and do not find all of them. Their manager knows no more than they do. After a few weeks, personal spreadsheets reappear, the old system stays open “as a fallback”, and the project, officially completed, has not produced what it was funded for.
The mistake is not having communicated badly. It is having treated adoption as an end-of-project step, when it is decided in the project’s design. Knowing who will be affected, and in what way, changes what is built and the order in which it is deployed.
What “change” covers: four kinds of impact
Not all changes require the same effort. We distinguish four kinds of impact, which often combine for the same population.
| Kind of impact | What changes for the person | Appropriate response |
|---|---|---|
| Tool | Screens and actions, for identical work | Familiarisation, online help, start-up support |
| Process | The sequence of tasks, controls, lead times | Training on real cases, updating procedures |
| Role | Responsibilities, decisions, contacts | Clarification by management, individual support |
| Job | The skills expected, sometimes the position itself | Upskilling paths, social dialogue, a long time frame |
A project that only affects the tool is handled through training. A project that changes roles or jobs is not handled through training alone: it involves the management line and, depending on the case, human resources and employee representatives.
Models such as ADKAR or Kotter’s eight steps provide useful checklists so that nothing is forgotten. We use them as reminders, not as methods to be rolled out. Finally, a point of vocabulary: in the ITIL framework, change management refers to controlling modifications made to IT services. It is a different, technical discipline, which does not deal with adoption by people.
Our approach to change management in five workstreams
Our consultants work within your project teams; decisions remain yours.
Analysing impacts
We start from populations, not features. For each one, we describe with people from the field what stops, what starts and what continues. This analysis goes back to the project team: a heavy impact may justify modifying the solution or deploying in several stages.
Engaging stakeholders
We identify who can champion the change and who can block it. The sponsor has a visible and repeated role, which we prepare with them. A network of change agents, chosen for their credibility with their colleagues more than for their enthusiasm, circulates information in both directions.
Communicating
Each population receives the messages that concern it, from the sender it listens to. For matters affecting daily work, that sender is the direct manager, not the project team. We help them acquire the means to respond: talking points, timetable, answers to foreseeable questions.
Training
Training covers work situations, not menus. It takes place shortly before go-live, and continues with enhanced support during the first days.
Measuring and embedding
After go-live, our consultants help track actual use and deal with gaps: additional training, fixing an irritant, intervention by management. The approach ends when the new practice has become the normal practice, and the old one is no longer available.
On a programme, these workstreams are included in the overall plan and tracked by programme management in the same way as technical deliveries.
The mistakes that jeopardise adoption
- Announcing instead of listening. A communication plan without a feedback channel detects none of the problems that will cause the deployment to fail.
- Training too early, or too broadly. Training attended long before first use is forgotten. Identical training for everyone bores some and loses others.
- Bypassing line managers. If they learn about the change at the same time as their teams, they can neither explain it nor require it.
- Keeping the old system alive. As long as the old way of doing things remains possible, some users go back to it at the first difficulty.
- Ignoring saturation. Several projects targeting the same teams at the same time cancel each other out. This effect is seen and settled at the level of project portfolio management.
Measuring adoption, not participation
The number of people trained and the number of messages sent measure the activity of the approach. They say nothing about its result. Together with you, we choose indicators that describe what users actually do.
- Usage. The share of the target population using the key functions, not the mere number of logins.
- Abandonment of the old. The disappearance of parallel spreadsheets and workarounds.
- Autonomy. The volume and nature of support requests, which should decrease and shift from basic questions to special cases.
- Quality. Input errors, rejections and rework observed in the new process.
- Perception. What users and their managers say about their ability to do their job.
These indicators are defined before go-live, with the baseline value where it can be measured. They are tracked by the business departments concerned, which report on them to the steering committee: adoption is their result before it is the project’s.