Home / Our roles / Change

Change Management

Getting a tool adopted by the people who will use it

A tool that has been delivered is not a tool that has been adopted. This trade deals with the gap between the two, which is where most projects are lost.

Real adoptionShort trainingUsage measurement

Why this role

Resistance is almost never irrational. It says that a gesture is slower than before, that a piece of information has disappeared, or that nobody explained what happens to the time freed up.

What it does concretely

  • Identify who loses something in the change, and what they get back
  • Train short, on the real cases of the team, never on a generic demonstration
  • Measure actual usage rather than declared satisfaction
  • Answer the question everyone asks without asking it: does this replace my job
On a real project

On our own deployments, adoption comes first from removal: a form of thirteen fields brought down to four actually gets filled in, where the old one was worked around.

What it is not

This is not an awareness session in a lecture hall, nor an internal communication campaign about innovation.

Two ways to access it

Embedded profile

Inside your team

A profile joins your team for an agreed period, works on your tools and your data, and passes on what they build as they go.

On a project

On a deliverable

The role is mobilised on a project with a defined scope, alongside the other skills required. You receive a deliverable, not a report.

Let's talk

Does this role match your need?

We start with a free diagnostic: what can be automated, what must not be, and the profile that makes sense at your end.

Book a diagnostic