A capable leadership team can approve a well-reasoned plan on Monday and find, by Friday, that little has moved. Meetings become cautious. Questions multiply. Long-standing processes acquire unexpected defenders. When leaders ask why teams resist change, the answer is rarely that people are simply difficult, complacent or opposed to improvement.
Resistance is usually information. It may indicate that the proposed change threatens identity, status, relationships, competence, workload or a deeply held understanding of the organisation’s purpose. Treating it as obstruction closes down precisely the conversation leaders need to have. Treating it as data creates the possibility of a more durable transition.
For charities, faith communities and mission-driven institutions, this matters acutely. People often give more than their contractual time and energy because they believe in the work. Change is therefore not merely operational. It can feel personal, moral and relational.
Why teams resist change when the case seems clear
Senior leaders can see a strategic imperative long before the wider organisation can. They may have encountered financial pressure, governance risk, demographic shifts, funder expectations or evidence that the current model is no longer sustainable. By the time a decision reaches staff or volunteers, leaders may feel they have already spent months considering it.
Others have not had that journey. They receive the conclusion without the context, the discarded alternatives or the difficult trade-offs. What looks to leaders like an urgent and obvious response can look to a team like a sudden disruption imposed from above.
This gap is not solved by sending a longer announcement. People need enough context to understand the problem, enough honesty to recognise what is genuinely uncertain, and enough opportunity to influence decisions that have not yet been made. Consultation after every meaningful choice has already been settled does not build trust. It teaches people that participation is ceremonial.
Change can threaten more than a job description
A revised structure may alter reporting lines, but its effects reach further. A manager may worry about losing hard-won authority. A respected practitioner may fear that a new system will expose skills they have not had reason to develop. A volunteer may hear a proposal to centralise activity as a judgement on years of local commitment.
These concerns are not always expressed directly. They may emerge as technical objections, requests for more evidence, delays in implementation or a renewed attachment to familiar routines. Leaders should not assume that every practical question masks bad faith. Equally, they should listen for the human question beneath the practical one: what might this change mean for me, my colleagues and the work I value?
Trust determines how change is interpreted
The same proposal can be received very differently in two organisations. Where leaders have communicated candidly, followed through on commitments and handled past difficulty fairly, people are more likely to grant the benefit of the doubt. Where there is a history of unexplained decisions, abandoned initiatives or inconsistent treatment, even a sensible proposal will be examined with suspicion.
Trust cannot be manufactured during a launch meeting. It is accumulated through ordinary leadership conduct: clear expectations, fair processes, timely explanations and the willingness to acknowledge mistakes. When trust is low, leaders must allow more time for engagement and demonstrate reliability through action, not reassurance alone.
The organisational conditions that intensify resistance
Not all resistance is about the change itself. Often it is a rational response to the conditions in which change is being introduced.
Change fatigue is one such condition. Teams that have experienced repeated restructures, new systems or shifting priorities may reasonably ask whether this initiative will last. They are not resisting novelty for its own sake. They are protecting their limited attention from another programme that may disappear before it delivers benefit.
Capacity is another. An organisation may have a persuasive strategy but no credible plan for who will undertake the additional work, what will stop, or how people will be supported while learning new ways of working. If staff are already stretched, enthusiasm for another initiative is not a reliable measure of commitment. It may be a measure of exhaustion.
Ambiguity can be equally damaging. A change programme framed in broad language such as ‘becoming more agile’ or ‘improving collaboration’ gives people little basis for action. They need to know what will change, what will remain stable, who holds authority, how decisions will be made and what success will look like. Clarity is not an administrative detail. It is a form of respect.
In governance-heavy settings, conflicting authority can create further paralysis. A chief executive may be expected to lead implementation while a board, committee or influential founder continues to intervene in operational decisions. Staff then receive mixed signals and sensibly wait to see which instruction prevails. Before asking teams to change, leaders may need to clarify their own decision rights.
How leaders can respond without becoming defensive
The first task is to distinguish between disagreement and sabotage. A team member who identifies risks, asks difficult questions or argues for a different approach may be offering valuable judgement. Mature organisations make room for challenge before a decision, then establish clear expectations once the decision is made.
That balance matters. Endless consultation can leave an organisation immobilised, particularly where financial viability, safeguarding, governance or community confidence is at stake. Yet premature closure produces compliance at best and quiet disengagement at worst. Leaders should be explicit about the boundary: these are the issues open for input; these are the decisions already determined; this is how and when we will decide.
Communication should be repeated, not merely delivered once. People process change through conversation, especially when it affects their role or relationships. A clear written explanation has value, but it cannot replace small-group discussion, space for questions and visible follow-up. If leaders cannot answer a question yet, they should say so plainly and specify when an answer will be available.
Leaders also need to name loss honestly. Every change creates some loss, even when the overall direction is right. It may be the loss of a familiar routine, a trusted colleague, local discretion or a cherished part of organisational culture. Pretending that everyone will experience only gain makes leaders seem detached. Recognising loss does not weaken the case for change. It makes that case more credible.
Build ownership through meaningful involvement
Ownership does not mean asking everyone to approve every decision. It means involving people where their knowledge can improve the work and where their participation affects implementation. Those closest to service delivery, pastoral care, fundraising, operations or community relationships often see consequences that are invisible from the boardroom.
The quality of involvement matters more than its volume. Invite teams to identify risks, test assumptions, shape practical processes and define what support they need. Then show what happened to their input. If a suggestion cannot be adopted, explain why. If it materially changes the plan, acknowledge its source. People can accept a decision they did not choose more readily when they can see that their perspective was taken seriously.
Visible local leadership is also essential. Middle managers and senior practitioners translate strategy into daily reality. If they are unclear, unconvinced or excluded until late in the process, the wider organisation will feel it. Give them early access to the reasoning, help them work through their own concerns, and equip them to hold honest conversations rather than simply repeat approved messages.
A more useful question for leaders
Rather than asking, ‘How do we overcome resistance?’, ask, ‘What is this resistance trying to protect, and what does it reveal about our plan?’ The answer may confirm that the change is necessary. It may also reveal an avoidable design flaw, an unaddressed capacity problem or a trust deficit that requires attention first.
There are times when leaders must proceed despite discomfort. A board may need to make an unpopular decision to preserve the organisation’s future, meet its obligations or protect those it serves. Values-led leadership is not the avoidance of difficult choices. It is the discipline of making them transparently, fairly and with due regard for the people asked to carry them out.
A team that questions change is not necessarily a team standing in the way of progress. With careful listening, clear authority and honest communication, its concerns can become part of the work that makes change safer, wiser and more likely to endure.