Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

When proposing to break apart an expert's role, Eric Samson was met with resistance. Instead of forcing the issue, he patiently raised the topic in multiple meetings. This iterative approach allowed the team member to process the change, voice concerns, and eventually buy in, proving more effective than a top-down mandate.

Related Insights

Resistance is critical information, not just a barrier. It often reveals a team's fear of losing something valuable, such as autonomy, their established identity, or a sense of expertise. Understanding what they're protecting is key to making change less threatening.

Instead of pushing advice, the most effective initial strategy with an unwilling team is to simply observe. This 'pull-based' approach builds trust and rapport, making the team more receptive when they eventually ask for your input, rather than feeling like you're forcing changes on them.

Change adoption follows a bell curve. Instead of assuming everyone is an eager early adopter or wasting energy on staunch resistors, focus on the large majority in the middle. Persuade them with a steady stream of small, proven, and safe wins that build comfort and trust.

To persuade someone, follow a specific sequence: 1) Validate the good in their current model. 2) Admit the weaknesses in your proposal. 3) Discuss the flaws in their approach. 4) Present your model's benefits. This non-intuitive order reduces defensiveness and makes them more open to influence.

Mandating new processes, like reducing meetings, is ineffective if the collective beliefs driving old behaviors (e.g., lack of trust) are not addressed. To make change stick, leaders must first surface, discuss, and realign the team's shared assumptions to support the new structure.

When your proposal is too far from someone's current position, it enters their "region of rejection" and is dismissed. Instead of asking for the full change at once, start with a smaller, more palatable request. This builds momentum and makes the ultimate goal seem less distant and more achievable over time.

When new owners raise standards, employees often feel their past work is being judged and criticized. Their resistance isn't to the goal of improvement (the 'what'), but to the implementation method (the 'how') which can feel demeaning. Leaders must frame changes as a shared opportunity to join a "winning team."

When a senior stakeholder proposes a potentially disruptive idea, direct resistance ('pushing') is counterproductive and strengthens their resolve. Instead, 'pull' them into a collaborative exploration. Acknowledge the idea, discuss the underlying problem it solves, and then gently steer the conversation back to how it aligns with the agreed-upon North Star, defusing tension.

When training seasoned professionals, top-down instruction often fails against skepticism. The most effective way to drive change is by facilitating moments where peers share their own success stories. This social proof is far more persuasive than any expert lecture.

Instead of forcing decisions in tense meetings, Ford's CMO would pause and then follow up with key stakeholders one-on-one. This allowed her to understand unique departmental challenges without group pressure, demonstrating humility and effectively resolving complex roadblocks.

Use Patience and Repetition to Overcome Expert Resistance to Process Changes | RiffOn