You made the business case. You sent the follow-up. You presented the data, tried a different framing, asked a colleague to weigh in.
Nothing moved.
The natural conclusion is that you need a better argument. Here is a different possibility: the argument was never the problem.
Resistance is the normal condition of leading change, however good the strategy. Leadership that won't resource the work. A procurement team that agrees in the meeting and does nothing after. Suppliers who are already underwater. Colleagues with a different set of priorities. None of them said no. All of them are saying no.
Reasons for resistance to change
Start from the assumption that there is a real reason. There almost always is: fear of losing something, a different set of priorities, incomplete information, or simply being at capacity. People are not resisting change in the abstract. They are resisting a specific consequence of a specific change, and that consequence is usually real.
Workload. The change adds fourteen minutes to a process that runs forty times a week, and nobody has said which existing task comes off the list. They are not against the idea. They are against doing it for free on top of a full day.
Credibility. They told their team six months ago that the current way was the right way. Adopting yours means walking that back in front of people whose trust they need next week. The cost is paid in their standing, not in your project plan.
Identity. Some changes carry a quiet message about who is still valuable. When a new system automates the judgment somebody spent fifteen years developing, "I don't think it's ready" is often a sentence about being needed.
Prior experience. They have done this before, with a previous sponsor, the thing broke, and they cleaned it up. What you are meeting is the residue of a change nobody debriefed.
Loss of control. People accept difficult changes they helped design far more readily than easy ones handed to them finished. That is what involvement buys, and it is the reason co-creating a solution outperforms presenting one.
Underneath all of them, the same shape. Something is being protected. More training will not move somebody who is protecting something. Finding out what they're protecting will.
Five kinds of no
The word is one label for at least five different situations, and the strategy that works on one will make another worse. Naming which one you are dealing with is the whole first move.
They can't see it. Sustainability isn't in their field of vision yet. They are not ignoring you, and they will later tell you honestly that they never saw the email. Pushing harder does nothing here, and neither does more data. What works is entering through a door they already have open: the cost pressure, the risk, the client relationship they are already trying to manage.
They won't prioritize it. They understand the ask and have competing pressures on the budget, the calendar, or their own political exposure. Some of this group are risk averse, and talking about future benefits rarely moves them, because our brains weigh a possible loss now more heavily than an equivalent gain later. Naming what the gap is costing the organization today lands where a future benefit doesn't.
They're stuck in place. Change feels threatening, unfair, or forced. The person benefiting from how things currently work has established relationships, proven processes, and standing at stake. Ask what the current system does well before you propose what needs to change, listen seriously, then show how those strengths carry forward. The goal is to make change feel like evolution rather than repudiation.
They're pushing back in public. Vocal, repeated, unconstructive criticism. Persistence is also a signal of engagement, which is why bringing this person inside as an advisor so often works better than arguing with them. Being asked to help solve the problem they keep naming changes the role they are playing.
They want to move and can't. This is the largest group and the one most often misread. They are committed and have no idea what to do first, or they are so far past capacity that anything new registers as a threat. Neither is resistance. One needs a very specific first step. The other needs you to lead with relief: something your initiative takes off their plate rather than adds to it.
The question that comes before strategy
Before you pick a move, ask a harder question. Is this conversation mine to have?
People move when they hear from someone they trust, respect, and see themselves in. That is rarely the sustainability team. Credibility comes from shared experience: the person who sat in the same seat, faced the same pressures, had the same doubts and moved anyway. When that person speaks, the distance between where your stakeholder is and where they need to go suddenly feels crossable.
As the person leading this, you are often too far ahead. You have been on the journey for years. You know the path, and that distance is exactly what makes you the wrong guide for someone at the beginning of it. Someone one step ahead, still in the messy part, is a better messenger than someone who has arrived.
Four moves that change the conversation
There is a facilitation approach used widely in health behavior change called motivational interviewing. Rather than telling people what to do, it helps them find their own reasons. Four techniques carry most of the weight.
→ Ask open questions. Instead of "have you considered switching suppliers?", try "what options have you already explored?" Open questions invite exploration. Closed ones invite defense.
→ Reflect before advising. Say back what you heard before you offer anything. "It sounds like your team supports the goal and procurement is worried about cost risk." This shows respect, and it often helps the person clarify their own thinking.
→ Affirm the effort. Change is hard and recognition sustains it. "You've clearly put a lot of time into trying to move this." Affirmation builds confidence, which is what most stalled people are short of.
→ Summarize the insight. Bring the threads together at the end. "So the core challenge is aligning procurement incentives with the goal." Summaries are what move a conversation into an action.
Then resize the ask until it fits the week they actually have, and check it. On a scale of one to ten, how confident are you this happens by the end of the month? Under a seven means the plan is wrong, not the person.
What makes resistance worse
Pushing harder. Escalation gets you compliance with the letter of the change and costs you every discretionary effort after it.
More evidence. If the objection is about workload, credibility, or a bad experience three years ago, a stronger deck answers a question nobody asked. People understand. That was never the problem. The problem is that they don't feel heard.
Going around them. Sponsor override works exactly once, and it converts a person with a solvable objection into a person with a grievance, in full view of their peers.
Calling it resistance out loud. The label does real damage. It reframes a legitimate constraint as a character flaw, and once someone has been positioned as the blocker, telling you the truth becomes dangerous for them.
Resistance to change in healthcare
Healthcare shows the whole pattern at high resolution. A new protocol arrives, clinical staff adopt it in the documentation, and within a month there is a shadow process keeping the day running. Leaders call this resistance. It is closer to triage.
The people working around your change are not the ones who care least. They usually carry the most direct accountability for what happens if the day stops moving, and their workaround is a precise map of where the new process breaks: the step that assumes two free minutes that don't exist, the handoff that assumes both people are on the same shift.
Treat that as design input rather than a compliance issue and two things happen. The process gets better, and the most credible people in the building become the messengers for the next round.
Where to start
Take the one stakeholder who has been stalling you longest. Don't bring a deck. Ask what this would cost them and what they would have to stop doing, then run the confidence question.
Think about that person now. Which of the five kinds of no are you actually dealing with? What have you already tried, and what did it change? And who in your organization looks like them, has already moved, and could carry this message better than you can?