Learn · Change & adoption
Low usage is information, not a discipline problem. It usually means the new way of working costs someone more than the old one, or that nobody has been given a reason and the time to change. Both are fixable, and neither is the users' fault.
The short answer
Design the change with the people doing the work, make the new path measurably easier than the workaround, and support it long after launch. Practically: involve real users in configuration decisions, train on their actual work rather than on features, give teams a named person to ask, and measure a small number of behaviors so you can see where support is needed.
Written for
01
Every new process shifts effort. Someone gains visibility while someone else does more data entry. Name that trade explicitly and address it, because unaddressed cost is exactly where adoption stops.
02
Feature tours are forgotten within a week. Sessions built on the team's real requests, projects and assets are remembered because people leave having done their actual job in the new way.
03
Adoption is decided in the four to eight weeks after go-live, when people hit their first unusual case. That is when a named person who can answer quickly matters more than any documentation.
04
Pick the small number of signals that show whether the new way of working is happening, and read them as a prompt for support rather than as a scorecard for teams.
05
Sustainable adoption needs people inside your organization who understand both the process and the configuration. That is why we teach as we build and document in your language, so capability does not leave when a project ends.
What goes wrong
A change designed without the people doing the work gets rejected on contact with reality.
The questions that matter arrive in week three, and again with every new hire.
If the old path is still faster, people use it — and the data stays incomplete.
Measurement used to judge teams stops being useful information and starts being a game.
A single trained administrator makes every absence a risk to daily operations.
Launch is where adoption starts. Support has to be funded past that date.
In practice
Enablement, training and change management support are part of how we work rather than an add-on line item — and our senior team stays available as your teams settle into a new way of working.
01
Managed Services: ongoing training, change management support and configuration adjustments as the work evolves.
02
Implementations: teaching-first delivery with milestones, plus Post Deployment Care where a dedicated expert helps with adoption, measuring value and planning ahead.
03
Partnership Solutions: an embedded practitioner inside your team during the period when support matters most.
Keep reading