CX Methods
Resistance to CX change is rational fear
Detractors are protecting something specific. Name the fear, then reframe the change as a benefit to the team resisting it.
Resistance to customer-centric change is rarely ignorance. Sales fears lower commissions, engineering fears slower delivery, product fears losing status. Transformations move when leaders name what each function is protecting and show how the change serves it.
When a customer experience program stalls, the instinct is to blame politics. Look closer and the resistance is usually rational. Detractors pressure colleagues, micromanage, and sometimes quietly sabotage, but each is protecting something specific. Sales fears customer-centricity will slow deals or cut commissions. Engineering worries it will pile process onto already tight roadmaps. Product fears losing its golden-child status or having to share credit. None of this is irrational; each team is defending the thing it is measured on.
Why it matters to the business
Stalled transformations forfeit real money. McKinsey reports that journey improvements lift revenue 10 to 15% and cut cost to serve 15 to 20%, gains that never materialize when functions dig in. The competitive field is wide open: Forrester's 2024 US CX Index put customer experience quality at an all-time low, with only 3% of companies qualifying as customer-obsessed. And self-interest framing works at the budget level too: Gartner finds CX teams that tie their metrics to growth and margin are 29% likelier to secure the budget they request.
How to use it
- Interview each resisting function privately and name what it is protecting: quota, velocity, status, headcount.
- Reframe the change in their currency: show sales how reduced friction shortens cycles, show engineering how fixing root causes cuts rework.
- Put known detractors on the redesign team so the work carries their fingerprints.
- Buy credibility with a lighthouse win: McKinsey's approach prototypes one redesigned journey in 6 to 12 weeks before asking anyone to scale.
- Publicly credit resisting teams when the win lands; shared recognition dissolves the status fear.
Where teams get it wrong
Leaders treat resistance as ignorance and respond with evangelism: more decks, more values workshops, louder repetition of the customer-first message. Fear does not respond to volume. It responds to evidence that the person's own scoreboard improves, which is why one concrete win inside a resister's domain outperforms a year of persuasion.
Ask your team
- Which team is quietly slowing our CX work, and what exactly do they stand to lose if it succeeds?
- Can our CX lead state, in sales's own numbers, what this program does for quota attainment?
- What is our lighthouse: the one visible win that makes this change concrete within a quarter?
Detractors are not obstacles. They are protecting something they value; name it, then serve it.
Apply this
Reading about resistance to cx change is rational fear is one thing. Seeing where it applies in your journey is the useful part.