Strategy and Business Consulting
Change that is still there a year later
New systems, processes and structures only pay off when people adopt them. We plan for that from the start, not after go-live.
Most failed rollouts were finished projects
The system went live on time. The new process was documented. Six months later the team is back in the spreadsheet, because nobody changed how they work around it. That is not a technology failure or a people failure. It is a change that was announced instead of managed.
People do not resist change because they are difficult. They resist it because the old way works for them, the new way asks for more effort up front, and nobody has shown them what they get in return. Answer those questions honestly and resistance drops. Skip them and no amount of training will help.
We saw this directly when a client replaced paper field tickets with a digital system. Plenty of people in the field pushed back on the extra data entry. What turned them was seeing what it bought them: sales reps were paid their commissions faster, and for the first time everyone could see their own inventory. Once people had that visibility, they did not want to give it back.
A structured approach, applied with judgment
Our change practitioners use the ADKAR model (Awareness, Desire, Knowledge, Ability and Reinforcement) to plan the work and track where each affected group actually stands. The model keeps the work honest. The judgment is in knowing which group needs a clear reason, which needs a better tool, and which needs a leader to go first.
How the work runs
1Assess the change
We identify who is affected, how much their work changes, and where resistance is most likely to come from.
2Build the case
We help leaders explain why the change is happening and what it means for each group, in terms that group cares about.
3Equip leaders and managers
The people closest to a team carry most of the change. We prepare them to answer the hard questions.
4Train for the real work
Training is built around the tasks people actually do, and timed close to when they will need it.
5Reinforce and measure
We track adoption after go-live and adjust until the new way is simply how the work gets done.
What you leave with
A change impact assessment for each affected group
A communication plan leaders can actually deliver
Readiness and adoption measures, tracked through go-live
Role-based training plans and materials
A reinforcement plan for the months after launch
Honest answers
When should change management start?
At the beginning, alongside the design. Change planned in from day one costs far less than winning back adoption after a launch has already lost people.
Our people are tired of change. Where do we start?
With fewer changes, sequenced better. Change fatigue usually comes from too many initiatives landing at once with no visible payoff. Part of our work is helping leaders decide what to pause, so the changes that matter get the attention they need.
Is change management only for technology projects?
No. It stands on its own, and we support strategic, organizational, process and technology changes alike. Any change that asks people to work differently needs it.
Plan the change before you launch it
Talk with one of our change practitioners about what is coming and who it will affect.