Understanding Customer Change Resistance
Resistance is rational behavior responding to perceived loss. Surface it, acknowledge it, and design the rollout so resisters keep something they value.
Most failed implementations are not technical failures; they are human ones. The end users feel something is being taken away — autonomy, expertise, status, a workflow they know — and they push back. The mistake is to treat that resistance as ignorance to be educated away. The better move is to the loss, acknowledge it explicitly, and design the change so resisters keep something they care about.
Deep practical explanation
Common forms resistance and what they actually mean:
- 'It won't work for our edge cases.' — fear that expertise built around the old workflow will be devalued.
- 'We don't have time.' — fear that learning cost will not be recognized by management.
- 'We tried something like this before.' — pattern memory being asked to absorb change without support.
- 'Senior people won't use it.' — political concern that the rollout has no top cover.
Prosci's ADKAR model (Awareness, Desire, Knowledge, Ability, Reinforcement) names the every individual must move through. Skipping a stage causes the change to revert.
Real-world example
A finance team rolled out a new close-management tool. The senior controllers, who had built personal authority around mastery the legacy spreadsheets, quietly refused to use it — keeping the spreadsheets in parallel and eroding the rollout. The had assumed resistance was about training and pushed more training, which made it worse.
The turn came when the ran a 30-minute roundtable purely to listen. The controllers said, in effect, 'we are worried our years accumulated knowledge no longer matter.' The CFO publicly named those controllers as the design owners of the new process and gave them the authority to define the close standard inside the tool. hit 95% within two months.
Tactical steps
- the people the change affects, not just the use cases.
- For each affected role, name the loss — explicitly — and design what they keep.
- Hold a listening session before any training; it changes which training is needed.
- Recruit one visible respected user per affected team as a co-designer, not a target.
- the rollout so early wins go to the most influential resisters.
- Reinforce the change for at least 90 days post ; without reinforcement, behavior reverts.