Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Project management and PMO

Change management: getting what the project delivers adopted

A project delivered and not used has spent its budget without producing anything. Our consultants help your teams prepare for adoption from the framing stage: who is affected, by what, and what they need to work differently.

Our principles

  • An impact analysis by population, not by tool
  • Line managers placed at the centre of the approach
  • Adoption measured by actual use
In brief

Change management brings together the actions that lead the people affected by a project to adopt new tools, new processes or a new organisation on a lasting basis. Management Square consultants support it alongside your project teams, from impact analysis to adoption measurement, building it into the project plan instead of reducing it to a communication plan.

Scope

How we contribute

  1. Impact analysis

    For each population concerned: what stops, what starts, what continues. The analysis covers tools, processes, roles and skills, and qualifies the scale of the effort required.

  2. Stakeholder mapping

    Identification of sponsors, change agents, opponents and exposed populations, with their degree of influence and their position, revised as the project progresses.

  3. Change agent network and support for managers

    Building a network of field correspondents and preparing line managers, the teams' first point of contact when questions arise.

  4. Communication plan

    Messages, senders, channels and timetable by population, with a channel for feeding questions and objections back to the project team.

  5. Training arrangements

    Role-based paths, built on real work situations and scheduled as close as possible to go-live, with the materials and support for the first days.

  6. Adoption measurement

    Usage, proficiency and perception indicators, tracked after go-live and accompanied by corrective actions until the target is reached.

Page contents

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.

Typical work

What our consultants contribute to

Impact matrix

Impacts by population and by nature (tool, process, role, skill), with the level of effort and the associated support actions.

Change management plan

Engagement, communication and training actions, aligned with the project milestones, with their owners.

Deployment kit

Training materials, role-based guides, talking points for managers and answers to frequently asked questions.

Adoption dashboard

Tracking of actual use, support requests and user perception, by population.

Insights

Further reading

All insights
Train whom, when and in what form? The choices in user training during a roll-out

User training is, during the roll-out of a tool, the workstream that prepares each role for the actions it will have to carry out in that tool. Management Square, whose change management assignments include this workstream, proposes here criteria for settling its audiences, timing, format, design, delivery and the check on its effect, and for seeing what training does not resolve.

Read the analysis
Writing a change management plan the steering committee can follow milestone by milestone

A change management plan is, by our definition, the schedule of the mobilisation, communication and training actions that a project plans for each population whose work it changes, tied to its milestones. Management Square suggests building it in seven steps, from scope to measuring adoption, each linked to a milestone at which the steering committee can ask for its result.

Read the analysis
The signs of poorly prepared change management, spotted at the stages of an IT project

Change management in an IT project brings together the actions that prepare the users of an information system to work with it, from scoping to the aftermath of go-live. Management Square shows here how to spot, document by document, poorly prepared change (users absent from scoping, impacts discovered in testing, unnamed change agents, go-live without support), and what remains to be done.

Read the analysis

Management Square in figures

300+
projects completed
43+
clients supported
Since2015
serving our clients
  • Allianz
  • Euler Hermes
  • Groupe BPCE
  • ODDO BHF
  • Candriam
  • Ledger
  • Saur
  • Veolia
  • Voltalia
  • emeis
  • Bonpoint
  • Legal Suite

FAQ

Frequently asked questions

Another question? Ask us

What is change management?

Change management is the set of actions that prepare and support the people affected by a project, so that they adopt the new ways of working. It includes impact analysis, stakeholder engagement, communication, training and monitoring of adoption after go-live.

When should change management begin?

From the framing of the project. Impact analysis influences the design of the solution, the deployment timetable and the budget. Started a few weeks before go-live, change management can only communicate and train on choices that are already fixed, including those that could have been avoided.

What is the difference between change management and project communication?

Communication informs: it says what will change, when and why. Change management aims for a different result, which is the actual change in practices. It includes communication, but also analysis of what each population loses and gains, training, support from managers and measurement of actual use.

How do you deal with resistance to change?

By first treating it as information. An objection from the field often signals a poorly assessed impact, a forgotten business scenario or an additional workload that the project has not seen. Our consultants help organise the feedback of these objections and their handling by the project team. Whatever remains then calls for explanation and management support.

Who should own change management: the project or the business?

Both, with distinct roles. The project team designs and equips the approach: impact analysis, materials, training, measurement. Business departments and their managers carry the message and the requirement day to day, because a team changes its practices when its direct manager asks it to and helps it do so.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.