The implementation finished. The adoption did not.
Nothing went wrong in the implementation. The problem is change management. And it started before kickoff.
Change management is a delivery responsibility.
Most PS teams do not think of themselves as change managers. That framing belongs to consultants and organizational development people.
But every implementation is a change management exercise. You are asking a group of people to stop doing something the old way and start doing it the new way. That is change. And change has resistance built into it.
When PS does not own change management it does not get done. CS inherits a customer that was never prepared to adopt and spends the first six months trying to recover ground that should have been laid during implementation.
Adoption failure is a delivery problem.
The conditions for adoption success or failure are set during the implementation. Who the stakeholders are. Whether the right people were in the room. Whether anyone identified who was going to resist the change and built a plan to address it.
By the time CS inherits the account those conditions are already baked in.
The three things that kill customer adoption.
The wrong stakeholders were involved. The person who signed the contract is not always the person who will use the product. If your implementation only engaged economic buyers and ignored end users the product lands in an org that was never prepared to adopt it.
Nobody identified the resistors. Every change has people who benefit from the old way. In enterprise implementations there is almost always someone whose job gets harder or whose authority decreases when the new system goes live. If you did not identify that person and build a plan to address them they will quietly undermine adoption after you are gone.
There was no activation plan. Go live is not the end. It is the beginning of the hardest part. If your implementation ends with a handoff document instead of a designed activation period you are handing CS a problem and calling it a finished project.
What to do about it.
At the start of every engagement map the stakeholder landscape. Who will use the product daily. Who will manage it. Who approved the purchase. Who did not want it.
For each group ask two questions. What does success look like for them specifically. What would make them resist adoption.
Build a week by week plan for the post go live period before go live happens. Not after. CS should inherit an activation playbook not a blank slate.
This runs per engagement not once.
Change readiness is not a one time exercise. Every customer is different. Every org has different politics and different resistors.
The teams that get this right run some version of this assessment at the start of every significant engagement. It takes less time than you think and it prevents the conversation nobody wants to have at renewal.
Want a structured way to run this?
The Change Readiness Planner gives your delivery team a structured framework to map stakeholder risk, identify resistance points, and build a week by week adoption plan before go live.
Start for free at app.cadenceops.io/signup