What do you do when the system works, the training is complete, and adoption is still at 45%?
Picture the steering committee meeting.
The project manager presents the dashboard. The system is stable. The major technical issues have been resolved. Training attendance was strong. Communications went out according to plan.
Then the adoption figure appears.
45%.
The room becomes quieter.
Someone asks why people are still not using the system. Another person suggests sending a reminder. Perhaps the training was not clear enough. Perhaps managers need to reinforce the message.
By the end of the meeting, the project team has a familiar list of actions: communicate again, arrange refresher training and ask leaders to encourage their teams.
A month later, the adoption rate has barely moved.
In change work, I have learnt that the first number often leads us to the wrong question.
We ask:
“How do we get people to use the system?”
When we might need to ask:
“What is happening in the organisation that makes the old way of working more useful, safer or easier?”
A live system does not mean the organisation has changed
A system can be technically ready without the organisation being ready to work differently.
People may know how to use it. That does not mean the new process fits how their work happens.
Imagine a team that has been trained to enter information into a new platform. During the day, however, they continue recording everything in their familiar spreadsheet. At the end of the week, someone transfers the information into the platform.
From the dashboard, it may look as though the team is using the new system.
In reality, the old spreadsheet is still running the work.
Why?
Perhaps the spreadsheet gives them a complete view that the platform does not. Perhaps it helps them track exceptions. Perhaps their manager continues asking for the old weekly report. Or perhaps other departments have not adopted the new process, so the team must operate in both worlds.
The problem is not necessarily that employees have failed to understand the technology.
They may be responding sensibly to a system that still rewards the old behaviour.
What is the 45% actually measuring?
Adoption figures can create an illusion of certainty.
We see a number and assume we know what it means. But “45% adoption” could refer to many different things.
Does it mean 45% of users have logged in?
Does it mean they have completed a transaction?
Are they using the entire process or only one part of it?
Are people entering information into the system as they work, or merely updating it later to satisfy reporting requirements?
A person can log in every day without changing how they work. Another person may use the new process effectively but not trigger the activity the dashboard measures.
Before responding to the number, we need to understand the behaviour behind it.
Otherwise, we may succeed in increasing system activity while leaving the real work unchanged.
People follow the system that governs the consequences
Suppose employees are told to use the new platform, but their managers continue requesting updates through email.
Which process are they likely to follow?
Suppose the new system encourages teams to make decisions independently, but every decision is still questioned when something goes wrong.
Will people feel confident using that authority?
Suppose leaders say the new platform will save time, but employees now need to enter the same information into two places because an old report has not been retired.
Will the system feel like an improvement?
People pay attention to what actually happens around them. They notice which process their manager trusts, which report leadership reads and where accountability sits when something goes wrong.
The formal message may say, “Use the new system.”
The surrounding organisation may be saying something else.
When those two messages conflict, people usually follow the one attached to real consequences.
What adoption asks people to give up
We often talk about adoption as though it is simply a matter of learning something new.
But using a new system can also mean giving something up.
Someone who was highly capable under the old process may feel like a beginner again. A manager may lose visibility or control. An employee may worry that the new transparency will expose mistakes. A team may have to let go of an informal workaround that has helped them cope with an imperfect process for years.
This is where an organisational psychology lens helps us look beyond system usage. It invites us to consider confidence, trust, motivation, identity and people’s sense of fairness.
Systems thinking takes us into the wider environment: workflows, decision rights, leadership behaviour, incentives, relationships and the history of previous changes.
Together, they remind us that low adoption is not simply an individual user problem.
It is an organisational outcome.
More training may not be the answer
Training is important when people genuinely do not know how to perform a task.
But training cannot fix a system that takes twice as long to complete the work.
It cannot resolve unclear accountability.
It cannot make a manager trust information they still insist on receiving through a spreadsheet.
And it cannot repair the credibility lost when employees raised concerns during implementation but felt nobody listened.
If the barrier is knowledge, train.
If the barrier is the workflow, examine the workflow.
If the barrier is trust, another user guide will not solve it.
This sounds obvious, but when adoption is low, organisations often return to the interventions that are easiest to organise and measure. Another briefing can be scheduled. Another reminder can be sent. Another attendance list can be produced.
Understanding what is really happening takes more curiosity.
Go to where the work happens
A dashboard can tell you where to look. It cannot tell you the whole story.
Talk to the people using the system, or choosing not to use it.
Watch how the work moves from one person to another. Find out where the new process slows them down, where information goes missing and where the old method continues to help.
Ask what happens immediately before someone decides to use the spreadsheet instead.
Ask what their manager expects.
Ask what they believe they are risking if they rely entirely on the new system.
And ask what they would change if the desired outcome were to make the work more reliable, rather than simply to increase the adoption percentage.
The answers may be uncomfortable. They may reveal that the technology is working exactly as designed, but the design did not fully account for how the organisation operates.
That is useful information.
The real outcome is not system usage
A higher adoption rate may be important, but it is rarely the ultimate reason the organisation invested in the technology.
Perhaps the desired outcome was faster decision-making, better-quality data, fewer manual errors or a clearer view of what was happening across the organisation.
It is possible to achieve a higher usage figure without achieving any of those outcomes.
People can comply with the requirement to use a platform while maintaining parallel workarounds. They can complete the mandatory steps without trusting the information inside it. They can produce better-looking dashboards while decisions continue to happen elsewhere.
So when adoption remains at 45%, do not begin by asking how to move the number.
First ask whether the organisation has created the conditions for people to work differently.
The technology may be ready.
The training may be complete.
The launch may have gone according to plan.
But change does not happen when the system goes live.
It happens when the new way becomes part of how decisions are made, how work moves and how people respond when something does not go as expected.
That is the difference between implementation and adoption.
If your technology works but adoption remains low, we would welcome a conversation to understand what is happening around the system, clarify the desired outcome and identify where the real barriers may be sitting.