Skip to content
Fast Company Executive Board

The Fast Company Executive Board is a private, fee-based network of influential leaders, experts, executives, and entrepreneurs who share their insights with our audience.

Why resistance can be a secret weapon for change

The real breakthrough comes when you stop seeing pushback as the enemy and start listening to what it tells you.

Why resistance can be a secret weapon for change

[Yakobchuk Olena, Ishan / Adobe Stock]

Profile photo of kmenendez

I used to think resistance was something to overcome. Fight through. Power past. For most of my career leading digital transformations, I treated pushback like a wall to break down rather than a door to walk through.

Then came the project that began to change everything.

WHEN EVERYTHING WENT WRONG (AND RIGHT)

Picture this: 2006, major financial services company, groundbreaking digital customer experience initiative. We had the technology, the vision, the executive mandate. What we didn’t have was buy-in.

It took us two years of stakeholder pushback just to win approval for a small test. “Too complicated.” “Compliance won’t approve this.” “This will undermine the ‘guaranteed’ results from the way we’ve always done things.” The resistance felt overwhelming.

My team and I spent months trying to convert the resistors using traditional change management approaches. More presentations. Better business cases. Pushing and prodding. Nothing worked. The harder we pushed with traditional tactics, the harder they pushed back.

What I didn’t realize then was that we were applying an outdated playbook.

THE BREAKTHROUGH

The shift happened during one particularly frustrating stakeholder meeting. Instead of hearing, “We don’t trust this new approach” as obstruction, something clicked. They were telling me exactly what they needed: reassurance that our innovation wouldn’t sacrifice the quality and reliability that had made the company successful.

That comment wasn’t resistance. It was intelligence:

• “This will undermine our ‘guaranteed’ results” became “We need to show how innovation enhances rather than threatens our proven track record.”

• “Too complicated” became “We need a clear implementation plan that takes away risk.”

• “Compliance won’t approve this” became “We need updated governance frameworks that address new risk considerations.”

I stopped trying to overcome resistance and started digging below the surface to interpret it. Instead of converting skeptics, I saw that the solution was to become a bridge between what technology makes possible and what people need to embrace it.

We also got lucky, as a solution to testing revealed itself that met colleagues’ needs to avoid jeopardizing status quo methods.

THE STRATEGIC ADVOCACY FRAMEWORK

What I identified through this and later experiences was a systematic approach I call strategic advocacy—a methodology that abandons the outdated hierarchical change management model in favor of building coalitions across different perspectives.

Here’s what works:

1. Reframe resistance as resource. Every pushback statement contains valuable implementation insight. When someone questions AI decision-making, they’re telling you what transparency measures are needed. When they worry about job displacement, they’re giving you the road map for change management.

2. Know the sources of power. The org chart sometimes lies. Real influence often flows through informal networks and relationships that aren’t captured in official hierarchies. That marketing manager who everyone respects? They may be more important than the VP nobody listens to.

3. Find shared values. This was the game-changer. Instead of arguing about features and functionality, we started talking about shared values. “We foster transparency and trust.” “We support human creativity to achieve breakthroughs.” “We adapt processes to enable responsible innovation.”

Values are bridges that arguments can never be.

THE MOMENTUM ENGINE

Applying these principles systematically changes everything. Those “difficult” stakeholders are far more likely to become advocates when they see their concerns are being addressed, not dismissed.

WHAT AI CHANGES (AND DOESN’T)

Today’s AI-driven transformations can learn from but are also different from the “pre-AI” tech implemented 20 years ago. AI challenges both process and identity in ways that earlier digital tools didn’t. When you’re asking people to work alongside AI, you’re not just changing their workflow—you’re asking them to reconsider what makes them uniquely human.

But the fundamental insight remains: Resistance contains intelligence. The employees who are actively resistant to AI adoption are early warning systems telling you there are open issues to be addressed for successful implementation.

THREE THINGS TO TRY TOMORROW

If you’re leading change and therefore invariably facing resistance, here’s where to start:

• Listen deeper. When you hear resistance, ask “Help me understand more” instead of arguing. Often behind pushback is feedback you need to hear.

• Map influence and support. Plot key people on a matrix: high/low support vs. high/low influence. Who supports your initiative, who opposes it, and who’s on the fence? How do they influence each other? Work the matrix strategically.

• Find shared values. When someone raises concerns, ask what value they’re protecting. Quality? Security? Innovation? Common ground beats arguments every time.

FROM CHANGE MANAGEMENT TO STRATEGIC ADVOCACY

Twenty years later, I’ve formulated a better playbook designed for the initiatives change leaders are pursuing now. Traditional change management—with its hierarchical, top-down, siloed approach—simply doesn’t work for transformative change.

The old model assumed resistance was irrational and needed to be overcome through better communication and training. But real change comes from building coalitions across perspectives and mining insights from resistance to build authentic momentum. It’s about strategic advocacy, not change management.

Don’t overcome resistance. Decode it.

The people pushing back are handing you the implementation road map. They’re telling you exactly what shared values need to be honored, what concerns need to be addressed, and what bridges need to be built.

Ask yourself: What resistance are you hearing in your organization? What bridges does it want you to build?