The System Is Live. Why Isn't the Organization Changing?
- moriseriki
- 1 day ago
- 4 min read
The implementation team did its job.
The system launched.
The data migrated.
Users received training.
The executive sponsor sent the announcement.
The project celebrated go-live.
Three months later, the organization has a different problem:
People are not using the system the way leadership expected.
Some employees still maintain spreadsheets.
Managers approve work outside the platform.
Data fields remain incomplete.
Users rely on informal shortcuts.
Certain features are ignored.
Teams complain that the new process takes longer than the old one.
Leadership starts asking:
Why aren't people adopting the system?
The answer is often uncomfortable.
Because installing technology does not automatically change how an organization works.
Adoption is behavioral
Technology implementation is technical.
Adoption is human and operational.
For adoption to occur, people must change something:
· How they enter information.
· Where they go for answers.
· How they complete a task.
· Who approves decisions.
· What sequence they follow.
· Which data they trust.
· What tools they stop using.
· How managers review performance.
Those changes happen in the context of real work.
If the new way makes sense, supports performance, and receives consistent reinforcement, adoption becomes easier.
If it creates friction, conflicts with established processes, or lacks leadership reinforcement, people adapt around it.
That adaptation often looks like "resistance."
Sometimes it is.
Sometimes it is feedback.
The old process may still be alive
One common mistake is implementing a new system while preserving the old operating model.
The technology changes.
The work does not.
That creates duplicate effort.
Users enter information in the new system and maintain the old spreadsheet.
The new workflow exists, but leaders still expect email approval.
The system assigns responsibility one way, while the organization chart implies something else.
Employees learn the new tool, but performance metrics still reward the old process.
In that environment, users have to choose.
Most will choose whatever helps them get the work done with the least risk.
That is not irrational behavior.
It is a design problem.
Training cannot carry adoption alone
Organizations frequently respond to adoption problems by offering more training.
Again, sometimes that is correct.
If people genuinely do not know how to use the system, training matters.
But if they know how and choose not to use it, the problem is somewhere else.
Ask:
· Does the process make sense?
· Are roles clear?
· Do leaders use the system themselves?
· Are employees rewarded for the new behavior?
· Are old tools still available?
· Are system requirements aligned with real operating conditions?
· Do users understand why the change matters?
· Did implementation teams respond to user feedback?
· Is the technology solving the problem it was intended to solve?
Training should support adoption.
It cannot substitute for alignment.
Managers determine what becomes normal
Executive sponsorship helps launch change.
Frontline and middle managers often determine whether it sticks.
Employees watch their immediate leaders closely.
If a manager asks for the old spreadsheet after leadership says the new platform is the source of truth, the spreadsheet remains the source of truth.
If supervisors bypass the workflow when deadlines get tight, employees learn that the workflow is optional.
If managers cannot explain why the change matters, the system becomes another administrative requirement.
This is why manager readiness deserves deliberate attention during implementation.
Managers need more than talking points.
They need to understand:
· What is changing.
· Why it is changing.
· What employees will experience.
· What behavior they must reinforce.
· Where they have discretion.
· What they should do when problems emerge.
· How performance will be measured.
Go-live should start a feedback loop
No implementation team understands everything before launch.
Real use reveals things testing cannot.
· Unexpected process dependencies.
· Role conflicts.
· Data problems.
· Unclear instructions.
· Performance-support needs.
· Unnecessary steps.
· User behaviors no one anticipated.
Strong organizations treat those signals as information.
They measure.
Learn.
Refine.
That does not mean abandoning governance every time someone dislikes the new system.
It means distinguishing between:
resistance to necessary change
and
legitimate evidence that the solution needs improvement.
The ability to make that distinction is one of the most important capabilities in sustained transformation.
Measure adoption differently
Login counts are not adoption.
Training completion is not adoption.
Awareness is not adoption.
Useful adoption measures should tell you whether the new system is changing the work.
Examples might include:
· Process compliance.
· Transaction quality.
· Cycle time.
· Error rates.
· Data completeness.
· Use of required workflows.
· Reduction in offline tools.
· Manager reinforcement.
· User proficiency.
· Business outcomes.
The exact measures depend on what the system was meant to improve.
Which brings us back to the original business case.
If you cannot define what successful adoption looks like in operational terms, it becomes difficult to manage it.
The technology is only part of the transformation
A system can be technically successful and organizationally unsuccessful.
That is why I do not treat implementation as a technology project with a training workstream attached.
The real transformation includes:
Technology. Process. Roles. Capability. Leadership. Behavior. Measurement.
Those components have to move together.
Otherwise, the system may be live while the organization continues operating much as it did before.
So when leaders ask:
Why aren't people using the system?
I would broaden the question.
What about the organization still supports the old way of working?
That is often where the real answer begins.
CONTINUE THE CONVERSATION
Preparing for an ERP, HRIS, LMS, AI platform, or major process implementation? A Transformation Readiness Toolkit is planned for the Shop.
Comments