What Their Resistance Is Actually Telling You

At some point in almost every meaningful engagement, the work slows down in a way that feels personal. The client who was engaged becomes hard to schedule. The leader who received the findings thoughtfully starts finding reasons why the recommendations do not quite fit this particular situation. The room that was open closes, not dramatically but incrementally, one qualified agreement at a time. And the practitioner, sitting with an accurate diagnostic and a sound plan, starts to wonder what they did wrong.

Usually, the answer is nothing. The resistance is not a response to the practitioner. It is a response to what the practitioner found.

That distinction sounds simple. Living inside it, when a client is pushing back on work you know is right, is considerably harder. This piece is about what to do in that space \u2014 not how to overcome resistance, but how to read it. Because resistance, interpreted correctly, is not the end of the engagement's productive life. It is often the beginning of it.

---

What resistance actually is

Resistance is information. It is the organization telling you, through behavior rather than language, what the finding has contacted.

This framing matters because the alternative \u2014 treating resistance as obstruction, as a problem to be managed or overcome \u2014 puts the practitioner in an adversarial relationship with the very signal they most need to understand. An organization that is not resisting anything is an organization whose friction has not yet been located. The appearance of resistance means the diagnostic found something real. The only question worth asking is what, specifically, the resistance is protecting.

There are things worth protecting. Not everything an organization resists changing should be changed. A leadership team that pushes back on a recommendation to restructure a function that has been the organization's core competency for twenty years is not being defensive. It is being careful about something it has reason to be careful about. A founder who resists a finding that implicates her founding instincts is not in denial. She is weighing the cost of revising something that has worked before against the evidence that it is no longer working now. These are not irrational responses. They are reasonable people in contact with the real cost of what the work is asking.

The practitioner who cannot distinguish between resistance that is protecting something worth protecting and resistance that is protecting something that needs to change will misread the engagement at its most critical moment. Both look the same from the outside. What distinguishes them is what the resistance is pointing at \u2014 and that requires the practitioner to look past the behavior to the source.

---

The four things resistance is usually protecting

Resistance in organizational engagements tends to cluster around a small number of sources. None of them are irrational. All of them are worth understanding before the practitioner decides what to do with them.

Identity. The finding implicates something the leader or organization understands as fundamental to who they are. A founder whose decisive, move-fast leadership style built the company and is now being identified as the source of its friction is not resisting the data. She is resisting the suggestion that the thing that made her effective has become the thing making the organization less so. That is a genuinely difficult thing to absorb, and it deserves more than a restatement of the finding. It deserves acknowledgment that what is being asked is not small \u2014 and that the leaders who have done it, who have revised their self-understanding in the middle of a career built on a particular way of operating, are the ones whose organizations tend to come out the other side of the engagement stronger than they went in.

Relationships. The finding implicates someone the client cares about, has history with, or feels responsible for. A CEO who built his senior team over a decade, who promoted three of them himself, who considers two of them close friends, is not going to receive a finding about that team's dynamics the way a new leader inherits it. The relationships are load-bearing in ways that do not appear in the diagnostic. The resistance is not a refusal to see the data. It is a request \u2014 often wordless \u2014 for the practitioner to understand that acting on the data has a human cost the instrument did not measure.

Politics. The finding is accurate and the client knows it, but the path to resolution runs through a relationship, a structure, or a decision that the client does not have the standing or the safety to touch. A division president who can see clearly that the source of her team's friction sits two levels above her in the organization is not resisting the finding. She is resisting a recommendation that would require her to have a conversation she does not have the organizational protection to have. The resistance here is rational. The engagement has surfaced a real problem that the sponsor cannot solve from where they sit. That is not a failure of willingness. It is a failure of scope, and it requires a different conversation about what resolution actually requires and who needs to be in the room for it.

Fear. Sometimes the resistance is not about the finding at all. It is about what accepting the finding would set in motion. A leadership team that accepts a finding about their decision-making culture is implicitly committing to changing how they make decisions. A CEO who accepts a finding about a protected individual is implicitly committing to a conversation with that individual that has no guaranteed outcome. The resistance is not to the diagnosis. It is to the treatment \u2014 specifically, to the uncertainty of what the treatment will produce. This is the resistance that most often looks like disagreement with the data when it is actually something closer to stage fright. The practitioner who can name that distinction gently \u2014 who can say, in effect, "I think you know this is right, and I think what you are carrying right now is what comes next" \u2014 will more often than not find the client nodding before the sentence is finished.

---

How to work with it

The instinct when resistance appears is to bring more evidence. To restate the finding more clearly, to add data points, to make the case more airtight. This instinct is almost always wrong, and it is worth understanding why.

Resistance is not primarily a cognitive state. It is an emotional and relational one. The client is not resisting because the evidence is insufficient. They are resisting because accepting the evidence requires something of them that they are not yet ready to give. More evidence does not address that. It adds to the pressure without providing any more of the capacity to absorb it.

What works instead is curiosity. Not performative curiosity \u2014 not the practitioner nodding thoughtfully while mentally preparing the next restatement of the finding \u2014 but genuine interest in what the resistance is carrying. What specifically feels wrong about the finding? What would need to be true for it to feel accurate? What is the cost, as the client sees it, of the path the recommendation points toward? These are not rhetorical questions. They are diagnostic ones. The answers will tell you more about where the engagement needs to go than any amount of additional evidence.

This requires the practitioner to do something that is genuinely difficult when you know you are right: to set the finding down for a moment and pick up the client's experience of it instead. Not to abandon the finding \u2014 it will still be there. But to be more interested, temporarily, in what the resistance is protecting than in making the case for what it is resisting.

That shift \u2014 from advocate for the finding to curious about the resistance \u2014 is where the work often turns. Not because the practitioner has given ground, but because the client has felt heard. And a client who feels heard is a client who can start to move.

---

What resistance is not

Resistance is not always recoverable. This is worth saying directly, because the framing of resistance-as-information can slide into a kind of optimism that the work does not always support.

There are organizations whose resistance reflects a genuine unwillingness to absorb the cost of change \u2014 not because they are not ready yet, but because the people with the authority to act have decided, consciously or not, that the cost of resolution exceeds the cost of the friction. Those organizations are not ready, and the practitioner who reads every resistance as a recoverable signal will stay in engagements that are not going anywhere for longer than they should.

The difference between resistance that is processing and resistance that is terminal tends to show itself in one specific place: what happens when the practitioner names the resistance directly. An organization that is processing will almost always produce something \u2014 a conversation that opens, a concession that was not available before, a leader who says something in the parking lot after the meeting that did not get said in the room. An organization that is done will produce more of the same. The same reframes. The same qualified agreements. The same productive-feeling conversations that do not move anything.

You will know the difference. Trust what you know.

---

What this asks of the practitioner

Working skillfully with resistance requires something that is not in any methodology: the capacity to stay warm toward a client who is, in the moment, making your work harder. To remain genuinely curious about what they are carrying when what you are feeling is frustration. To believe, in the absence of evidence, that the organization in front of you is doing its best with what it has \u2014 and that your job is to give it more to work with, not to be disappointed that it has not already done the work you are there to help it do.

That is a high standard. It is also the standard that separates the practitioners whose clients change from the ones whose clients learn.

Resistance is not your adversary. It is the most honest thing the organization has said to you yet. It is telling you exactly where the work is, what it is protecting, and what it will take to move. The practitioner who can hear that \u2014 who can sit in a room where everything is pushing back and remain genuinely interested in what the pushing back is about \u2014 is the practitioner who will still be in the room when something finally shifts.

That shift, when it comes, is quiet. It does not announce itself. But you will recognize it. It feels like relief \u2014 not yours, but theirs. And it is the moment the engagement earns everything that came before it.