It’s Not Resistance. It’s the System.

"You are getting resistance."

This might be the most common explanation for why change efforts stall. The strategy is sound. The vision is clear. The executive team is aligned. And yet progress slows, adoption stays inconsistent, and old behaviors keep showing up.

So we reach for the easy conclusions:

•People are resisting

•The strategy needs to be changed

•The vision was not clear enough

But in most cases, that is not what is happening. Rather, people are responding exactly as the system around them is designed to produce.

When proposed with a change of some kind, how many times have you heard "we have tried that before" or "that's not the way we do things around here" inside an organization? Resistance builds early with dismissal.

If the change proposal actually gets called into action, then you've probably seen the classic signs of work avoidance. That typically looks like diversion of attention and displacement of responsibility, where blame shifts to process and people, and processes get put into death traps for progress (ex. non-actionable committees, parked for later in each meetings, etc).

Perhaps it progresses beyond some of the barriers of work avoidance (which is uncommon in adaptive challenges. People who were blamed get removed. Processes change or get axed. Compromise after compromise occurs to water down the adaptive work of the change. Eventually, the change effort either stalls, or gets taken out. If enough heat is raised in the system, you might even close your own job!

So while it is easy to blame resistance for stalled change efforts, the harder truth to accept is that the system in which your organization lives in is doing exactly as it was designed to do. Like the body fighting off an invading virus, the system fights back to preserve its state of equilibrium. In organizational life, what looks like resistance is actually the system pulling itself back to center. Human systems are remarkably effective at preserving the status quo regardless of how much energy and disequilibrium you throw at it.

This is why smart and capable people can work incredibly hard to change, and produce the same outcomes year after year. It has nothing to do with intelligence or commitment, as the underlying conditions simply have not changed. To paraphrase Deming, systems will beat good and smart people every-time ... unless you understand the system well enough to know how to change it.

People and process always seems to be the focus of the work with change. This is is partly true. The "right" people and the "right" process depends on the nature of the system at play. Odds are if the problem persists despite continuous change of people and process, you have an adaptive challenge that is systemic in nature.

A more useful starting point is to stop asking "why are people resisting?" or "what other process can we try?", and start asking:

• "What keeps happening here?" •"Where does this issue show up repeatedly?"

•"When does it tend to emerge?"

•"What do we do in response each time?"; and

•"What assumptions are governing how we look at this?"

This is what systems-informed leadership practice actually looks like in practice. Questions like these help reveal patterns clearly enough to intervene in the right place. This requires a more thorough diagnosis process, multiple stakeholders in the challenge beyond your level of view within the organization, and an experimental mindset to intervene effectively.

Our work at Well•Led helps organizations make these patterns visible. Through a facilitated system mapping process, leaders and stakeholders step back from the noise of day-to-day work to see how their actions, decisions, and assumptions are connected. What often feels like isolated problems begins to reveal itself as a set of reinforcing dynamics that keep producing the same results. The result? A way to literally see the system as it currently functions, as well as truly understand it on a deeper level (think a big "A-HA!" moment").

Creating that level of clarity requires more than just mapping in a polite dialogue. The process, therefore, requires a holding environment where people can surface what is usually left unsaid: the pressures, tradeoffs, and assumptions that quietly shape behavior. When those dynamics are seen clearly and shared collectively, the conversation shifts. What looked like resistance becomes truly understandable. Thus, once the system can be truly seen and understood, leaders can begin to intervene in ways that actually make progress.