Part 11 of Governance Beyond Compliance — building accountable leadership, resilient organisations and healthy cultures. First published on LinkedIn, 30 September 2026.
Why the most effective leaders never fight resistance – they make it unnecessary
Key takeaways
- The most effective leaders do not fight resistance — they make it unnecessary.
- Resistance is shaped by vested interest, trust and identity threat; designing around these reduces it.
- Principled disagreement is a governance asset, and culture is a design decision.
There is a question that comes up in almost every leadership development conversation, every management training program, and every coaching engagement that touches on team dynamics.
How do you handle resistant people?
It is the wrong question.
Not because resistance does not exist – it does, in every organisation, at every level, in every sector and every culture encountered across four decades of professional practice. But because the question assumes that resistance is the primary variable to be managed, and that the leader’s job is to develop techniques for overcoming it after it has emerged.
The leaders who build the most effective teams do not handle resistance well.
They rarely encounter it.
Not because they are fortunate. Not because they work with unusually cooperative people. Not because the organisations they lead are free of the tensions, competing interests, and interpersonal complexity that generate resistance in every human system.
Because they have designed their teams in ways that make resistance structurally unnecessary before it has the opportunity to emerge.
That is the distinction this article is about. Not resistance management. Resistance prevention. And the difference between those two approaches – in the teams they produce, the cultures they create, and the outcomes they deliver – is significant enough to constitute a fundamentally different model of leadership.
What resistance actually is
Before examining how resistance is prevented, it is worth being precise about what resistance actually is – because the word is used to describe several different phenomena that have different causes and require different responses.
The first form of resistance is rational self-interest. A person resists a change, a process, or a direction because they have assessed it – correctly or incorrectly – as contrary to their interests. This is not irrational behaviour. It is the entirely understandable response of a person who does not yet see how the proposed change serves them.
The second form of resistance is relational distrust. A person resists not because they have assessed the substance of what is being proposed, but because they do not trust the person proposing it. The resistance is not to the idea – it is to the relationship. This form of resistance is particularly common in organisations that have experienced leadership transitions, broken promises, or governance failures – environments in which the rational response to a new proposal from a new leader is to wait and see whether this one is different from the last one.
The third form of resistance is identity threat. A person resists because the proposed change threatens something they understand as central to who they are – their expertise, their role, their status, or their understanding of how the organisation works and what their place in it is. This form of resistance is often the most deeply felt and the most difficult to address – because it is not primarily about the proposal at all, but about the person’s experience of themselves in relation to it.
The fourth form of resistance is principled disagreement. A person resists because they have thought carefully about what is being proposed and believe, on the merits, that it is wrong – that a different approach would produce better outcomes for the organisation, the team, or the people the organisation serves.
Principled disagreement is not resistance in the negative sense that the word usually implies. It is a governance asset – the kind of honest challenge that healthy teams require and that leaders who confuse compliance with agreement systematically suppress. A team in which nobody ever disagrees is not a team in which everyone agrees. It is a team in which the conditions for honest disagreement have not been established.
Understanding which form of resistance you are encountering – rational self-interest, relational distrust, identity threat, or principled disagreement – is the first step in determining whether the appropriate response is to address the resistance or to redesign the conditions that produced it.
The vested interest principle
The most consistent observation across forty years of building teams in organisations across four countries and eight sectors is this: genuine resistance is rare in teams where every member has a clearly understood and genuinely held stake in the collective outcome.
This is not a motivational observation. It is a structural one.
When a person understands – specifically, concretely, and in terms that connect to their own definition of success – how the team’s outcome serves their individual interests, the calculus of resistance changes. Withholding contribution, obstructing progress, or protecting information at the expense of the collective outcome becomes self-defeating. The resistant behaviour costs the resistant person more than it costs the team.
That structural condition does not emerge by itself. It is designed – through the conversations that happen before the work begins, in which each person’s individual ambitions, goals, and definitions of success are understood, and the connection between those individual definitions and the collective purpose is made explicit.
Those conversations are not team-building exercises. They are diagnostic and alignment conversations – in which the leader learns what each person is working towards, and each person learns how the team’s work serves what they are working towards. The connection between individual and collective interest is not assumed. It is established – explicitly, personally, and before the work creates the conditions in which that connection will be tested.
The practical form of this conversation is simple.
- Not: what are your professional development goals?
- Not: where do you see yourself in five years?
- But: what does success look like for you – in your career, in your life, in the things that matter to you beyond this role? More income. Promotion. Security. Family. Recognition. Growth.
Whatever the answer is, it is the answer that allows the leader to make the invisible connection visible: the path to what you want runs through what we are building together.
When that connection is real – when the person can see it, believe it, and feel it in the daily texture of the work – resistance to the collective outcome becomes resistance to their own interests. It becomes, in the most practical sense, irrational.
Most people are not irrational. When the conditions are right, they do not choose resistance. They choose contribution.
The trust foundation
The vested interest principle addresses the rational self-interest form of resistance. It does not address the relational distrust form – the resistance that is not to the substance of what is being proposed but to the person proposing it.
Relational distrust is addressed by a different mechanism: the consistent demonstration, over time, that what is said and what is done are the same thing.
This is not a complex principle. But it is a demanding one – because it operates at the level of every interaction, not only the significant ones. The trust that makes relational resistance unnecessary is not built through a single memorable gesture or a compelling vision statement. It is built through the accumulation of small consistencies – of doing what was said, arriving when committed, following through on what was promised, and treating every person in the team with the same standards of honesty and respect regardless of their positional relationship to the leader.
In organisations that have experienced governance failure – where the relational distrust is not personal but institutional, where the entire team has learned through experience that leadership commitments are unreliable – the trust-building process is slower and requires more deliberate investment. The team is not waiting to see whether this particular leader is trustworthy. They are waiting to see whether this is an organisation in which trust is possible at all.
In those environments the trust foundation is built not through words but through the sequence of actions that demonstrate – to people who have reason to be sceptical – that this time the experience will be different. That the commitment will be honoured. That the concern will be heard. That the governance will function as described rather than as performed.
This takes time. It cannot be accelerated by sincerity alone. Sincerity is necessary – but in an environment of institutional distrust, sincerity without track record is indistinguishable from the sincerity that preceded every previous disappointment.
The track record is built one consistent action at a time. There is no shortcut.
The identity threat – and why designing around it matters
The identity threat form of resistance is the most challenging to address – because it operates at a level that rational argument and trust-building alone cannot reach.
When a proposed change threatens something a person understands as central to who they are – their expertise, their role, their status within the team – the resistance is not primarily to the change itself. It is to the implication that who they currently are is insufficient for what the organisation is becoming.
The most effective response to identity threat resistance is not to argue against it or to overcome it. It is to design the change in ways that make the existing identity an asset rather than an obstacle.
This requires understanding – before the change is proposed – what each person’s sense of professional identity is built on, and how the proposed change relates to that foundation. A team member whose identity is built on technical expertise will resist a change that appears to make their expertise obsolete. A team member whose identity is built on their role as the team’s informal leader will resist a structural change that removes the conditions for that informal leadership.
Neither form of resistance requires the change to be abandoned. Both require the change to be framed – and where possible designed – in ways that engage the existing identity rather than threatening it. The technical expert whose expertise is acknowledged and built upon in the new structure does not resist the change. The informal leader whose influence is recognised and channelled into a formal contribution does not resist the transition.
This is not manipulation. It is the recognition that genuine capability already present in the team is a resource to be engaged rather than an obstacle to be overcome. And it is the recognition that the leader who designs with their people – rather than for them – produces changes that are owned rather than imposed, and therefore sustained rather than reversed the moment the leader’s attention moves elsewhere.
Principled disagreement as a governance asset
The fourth form of resistance – principled disagreement – deserves a different treatment from the other three. Because it is not resistance in the sense that the word usually implies. It is the honest exercise of the individual intelligence that the team requires if it is to make good decisions.
A team in which nobody challenges the leader’s proposals is not a high-performing team. It is a team in which the conditions for honest challenge have not been established – in which the cost of speaking is perceived as higher than the cost of staying silent, and in which the leader’s decisions are therefore made with less information, less scrutiny, and less accountability than the quality of those decisions requires.
The leader who confuses principled disagreement with resistance has created the conditions for one of the most common and most costly team dynamics in organisational life: the team that agrees in the meeting and resists in the implementation. What appears to be compliance is, in fact, deferred resistance – suppressed in the moment by the cost of speaking and expressed later through the passive non-cooperation that produces the outcomes the leader believed had been agreed to.
The antidote is a team culture in which principled disagreement is explicitly invited, visibly valued, and demonstrably acted upon. Not a culture in which every challenge is accepted and every proposal reversed. But a culture in which the person who raises a genuine concern knows that the concern will be heard, considered, and responded to – and that the response will be honest whether or not it results in a change of direction.
That culture is built by the leader’s response to the first challenge. If the first person who challenges a proposal is heard, taken seriously, and thanked for the contribution regardless of the outcome – if the challenge is treated as a governance asset rather than a personal affront – then the team learns that speaking is safe. The second challenge comes more readily. And the third. And gradually, the team develops the habit of honest exchange that produces the quality of collective decision-making that no individual intelligence, however capable, can replicate.
If the first challenge is managed rather than heard – if the person who raises the concern is redirected, reassured, or subtly discouraged from pursuing the question – the team learns a different lesson. And that lesson, once learned, is difficult to unlearn.
The culture design decision
Designing out resistance is not a series of techniques to be applied to individual team members. It is a culture design decision – one that determines the conditions in which the team operates, the norms that govern how people interact, and the shared understanding of what the team is for and what each person’s contribution to it means.
That design decision is made – explicitly or by default – in the earliest interactions between the leader and the team. Before the first meeting. In the conversations that happen before the work begins. In the way the leader listens in the first days and weeks. In what the leader notices, acknowledges, and responds to. In the signals that the leader sends – through behaviour rather than statement – about what kind of environment this is going to be.
The leader who arrives in a new team with a plan to implement, a direction to communicate, and a timeline to meet, and who treats the early period as an obstacle to be navigated before the real work begins, has missed the moment in which the culture of the team is formed. By the time the real work begins, the team has already assessed the leader – and the assessment, once made, is the foundation on which everything that follows is built.
The leader who arrives in a new team with curiosity, with the genuine desire to understand what each person is working towards, with the patience to listen before directing and to build before requiring, has used the early period for its most important purpose. They have established the conditions in which resistance is unnecessary – because the team has already experienced what it feels like to be understood, valued, and genuinely part of something that serves their own interests as well as the collective one.
That experience is the foundation of everything this article has argued for.
And it cannot be installed after the fact. It must be designed in from the beginning.
What this means in practice
The practical implications of the resistance prevention approach are simple to state and demanding to sustain.
Have the individual conversation before the collective one. Understand what each person is working towards before you ask them to work towards what the team requires. Make the connection between individual and collective interest explicit – and revisit it when the work changes, when the team changes, or when the circumstances change in ways that affect the calculation.
Build trust through consistency rather than through sincerity. What you do is more persuasive than what you say – particularly in environments where the gap between those two things has been wide in the past. Every small consistency is a deposit in the trust account that makes the larger asks of team membership possible.
Design with people rather than for them. The change that people have helped to shape is the change they are most likely to sustain. The process that the team has contributed to is the process the team will most reliably follow. Design in – from the beginning, and at every stage – the contribution of the people whose cooperation the design requires.
Treat principled disagreement as a governance asset. Create the conditions – explicitly, visibly, and repeatedly – in which honest challenge is welcomed rather than managed. And demonstrate, through your response to the first challenge, that speaking is safe.
And above all – establish, from the outset and in the most personal terms available, that everyone in the team has a stake in the collective outcome. That the team wins together or loses together. That the knowledge one person withholds is the gap another person stumbles into. And that the path to what each person individually wants runs through what the team is collectively building.
When those conditions are present, resistance does not need to be handled.
It does not arise.
Companion resource: the Designing Out Resistance diagnostic
A short worksheet to help you apply this article: identify which of the four forms of resistance you are facing, check which design conditions are missing, and choose your next step. Enter your details and it will be emailed to you as a PDF.
Dennis Chew is a Corporate Governance specialist, Company Secretary, and Director of Operations professional with forty years of experience across NFP, faith-based, educational, and corporate organisations in Australia, Malaysia, New Zealand, and Hong Kong. He writes on governance, institutional resilience, leadership, and people development.
He is open to conversations about Director of Operations, Non-Executive Director, governance advisory, and coaching engagements in Melbourne.
The series so far:
- Article One – The Greatest Danger in a Small NFP Is Not Bad Intent
- Article Two – From Ambiguity to Architecture
- Article Three – Why Good Governance Protects Everyone Including the CEO
- Article Four – The Turnover Number Your Board Should Be Watching
- Article Five – What Information Should Your Board Be Receiving and From Whom
- Article Six – When the Leadership Compact Breaks Down
- Article Seven – Into the Gap (for Executives entering a distressed organisation)
- Article Eight – Everyone Has a Story
- Article Nine – The Test of a Teacher
- Article Ten – Salary and Wages Can Be Taken Away)
Previous: Part 10 — Salary and Wages Can Be Taken Away
All articles in Governance Beyond Compliance
Developing leaders and teams? Dennis offers speaking, mentoring and leadership development. Get in touch or see Speaking & Advisory.