Stop Calling it Resistance: Why Pushback Shows Intelligence

Stop calling it resistance when teams push back on strategy. Learn how to recognize intelligence in dissent and integrate valuable feedback without derailing strategic goals.

When someone pushes back on your brilliant strategy, your first instinct is to label them resistant. They don't get it. They're stuck in old ways. They're afraid of change.

But what if they're right?

The people closest to the work see things you don't. They know which customers complain. They know which processes break. They know what actually happens versus what the flowchart says happens.

The View from the Ground

I learned this watching a software company try to "modernize" their support system. Management hired consultants. The consultants designed a beautiful new process. The support team immediately started raising concerns.

Management called it resistance. Six months later, after losing their biggest client because the new system couldn't handle edge cases, they finally listened. The support team had spotted every problem in advance. They weren't resisting. They were trying to save the company from itself.

Intelligence Looks Like Resistance

Here's the thing about smart people doing complex work: they spot problems fast. When you announce a change that will break their workflow, they don't smile and nod. They tell you.

This looks like resistance if you're not paying attention. Someone says "that won't work" and you hear "I don't want to change." But they're usually saying "that won't work because of X, Y, and Z that you haven't considered."

Three Ways to Listen Better

First, assume intelligence. When someone objects, your first thought should be "what do they know that I don't?" not "how do I overcome their resistance." This simple shift changes everything.

Second, dig for specifics. Vague resistance might be fear. Specific concerns are usually intelligence. "I don't like it" tells you nothing. "This will break our integration with the inventory system" tells you everything.

Third, create safe channels for dissent. People need ways to raise concerns without seeming like troublemakers. Anonymous feedback. Skip-level meetings. Whatever works in your culture. Just make sure the intelligence can flow upward.

The Strategy Paradox

Good strategy needs both vision and ground truth. Vision comes from stepping back and seeing the big picture. Ground truth comes from the people doing the work every day.

Most organizations are terrible at combining these. Leaders think their vision is complete. Workers think leaders are clueless. Both are partially right.

The best strategies emerge when you treat pushback as data, not defiance. When someone says your plan won't work, that's valuable information. When multiple people say it, that's a pattern.

Making It Work

Smart organizations build dissent into their process. Amazon's "disagree and commit" isn't about overcoming resistance. It's about surfacing intelligence before committing.

They argue first. They surface all the ways things could go wrong. Then they decide with eyes open.

This takes longer than steamrolling through objections. It also produces strategies that actually work.

The Bottom Line

Every organization says it values feedback. Most organizations punish people who give it. They label them negative. Resistant. Not team players.

Then they wonder why their strategies fail.

The intelligence you need is already in your organization. It's in the people you've labeled resistant. It's in the concerns you've dismissed. It's in the pushback you've tried to overcome.

What intelligence are you ignoring by calling it resistance?