Resistance Is Relational, Not Just Personal

When a team resists change, the default diagnosis is individual: they don't understand, they're afraid, they need more training. The interventions follow the diagnosis — more workshops, more communication, more town halls explaining the why.

This misses the point entirely.

Resistance is produced, not possessed

Resistance doesn't live inside a person. It lives in the relational field between people — in the unspoken contracts, the competing commitments, and the gap between what leadership asks for and what the system actually rewards.

When a team nods along in a retrospective and then does exactly what they did before, that is a perfectly rational response to the incentive structure they operate in, not ignorance. The stated goal is agility. The actual reward is predictability. The team read the room correctly.

The relational lens

Co-creative Transactional Analysis offers a different frame. Instead of asking "why is this person resistant?", it asks: "what is being co-created in this relational field that makes resistance the most coherent response?"

This shifts the focus from individual deficiency to systemic intelligence. The resistance is the diagnostic signal.

Three questions to ask when resistance appears:

• What contract is being violated? Every change initiative implicitly breaks a psychological contract. Identify which one. Name it. Renegotiate it explicitly rather than pretending it doesn't exist.

• What competing commitment is at play? People aren't resisting the new way. They're committed to something the new way threatens — status, competence, relationships, identity. Find the competing commitment and you find the real negotiation.

• Who benefits from the current arrangement? Resistance often protects a power structure. Not maliciously — structurally. The current arrangement serves someone. Change threatens that arrangement. The resistance is the immune system doing its job.

From diagnosis to design

The implication for transformation leaders is straightforward but uncomfortable: if resistance is relational, then fixing it requires changing the relationship, not the resistor.

It starts with renegotiating the psychological contract before demanding new behaviour. You can't ask people to act differently while every implicit signal tells them the old rules still apply.

Then the competing commitment has to be made explicit, as a shared problem, not an accusation. "We're asking you to move fast, and we're also asking you to never fail. Those two things are in tension. Let's talk about which one we actually mean."

And what's being lost has to be acknowledged. Every transformation requires people to give something up: competence, status, certainty, belonging. If leadership doesn't name it, the organisation will grieve it underground. And underground grief looks exactly like resistance.

People don't resist change. They resist loss.

The practitioner's responsibility

If you're coaching a team through change and you find yourself thinking "they just don't get it," pause. That thought is a signal — not about the team, but about the quality of the relational contract between you and them.

Whether the team understands the change matters less than whether the change has been offered in terms the system can accept: terms that honour what's being asked, acknowledge what's being lost, and make the new arrangement genuinely better than the old one.

Resistance is the transformation's feedback loop, and it only helps if someone is listening.

---

This article is adapted from Chapter 8 of The Art of Creating Self-Organizing Teams, published by Apress / Springer Nature.