CX Methods
The insiders who quietly stall CX change
Detractors block CX change to protect commissions, timelines, and status. Sell the change in their currency, not the customer's.
Every CX transformation acquires internal opponents who slow-walk work, micromanage, and spread doubt. Their resistance is rarely about customers; it is self-protection. Leaders who diagnose what each detractor stands to lose convert them faster than any amount of customer-first evangelism.
Detractors are the insiders who quietly work against customer-centric change. They rarely object in meetings. Instead they slow-walk deliverables, micromanage the people doing the work, and seed doubt in hallway conversations. The mistake is reading this as ignorance and answering with more education. It is almost always self-protection. Sales fears the change will cut commissions. Engineering fears user-centered process will slow projects and make the team look bad. Product fears losing golden-child status or having to share credit. Each fear is rational from inside that person's scorecard, which is exactly why lectures about the customer do not touch it.
Why it matters to the business
Stalled transformations are expensive in a way that never appears on a budget line. Bain's research found that 80% of companies believed they delivered a superior experience while only 8% of their customers agreed. Detractors are one reason firms stay on the flattering side of that gap: they block the work that would expose it. The upside they block is measurable too. McKinsey reports that journey improvements lift revenue 10-15% and cut cost-to-serve 15-20%. When a detractor delays that work by two quarters, they have spent real money, invisibly.
How to use it
- Before launching any CX initiative, map who loses what: commissions, timelines, headcount, status. Write the fears down.
- Translate the case into each function's currency: rework avoided for Engineering, faster and more repeatable selling for Sales, retention revenue for Finance.
- Recruit one visible skeptic into the pilot team and let them co-own the first win.
- Deliver proof fast. McKinsey's transformation approach prototypes one redesigned 'lighthouse' journey in 6-12 weeks, then uses it as evidence rather than argument.
- Escalate persistent sabotage to the executive sponsor by name. Politeness that protects a saboteur funds the delay.
Where teams get it wrong
The classic error is evangelism: responding to resistance with more decks about customer virtue. A detractor is not confused, so more explanation changes nothing. Worse, the customer-first pitch restates the threat, because it signals that their scorecard still is not part of the plan. Public confrontation fails too; it drives resistance underground, where it is harder to see and slower to fix.
Ask your team
- Which function loses something real if this CX change succeeds, and what have we offered them in exchange?
- Who has quietly missed the last three CX working sessions, and who sent a delegate instead?
- Can our CX lead name our three biggest internal skeptics and the specific fear behind each one?
Nobody fights customer-centricity because they hate customers. They fight it because it threatens their scorecard.
Apply this
Reading about the insiders who quietly stall cx change is one thing. Seeing where it applies in your journey is the useful part.