Resistance Is Relational, Not Just Personal

The workshop that looked successful until nothing changed

A team sits through a session on pairing, peer review, or better discovery habits. The case is strong. People nod. Nobody openly refuses. Two sprints later the old behavior is back and the story quickly becomes personal: the team is resistant, the seniors are territorial, the culture is stubborn.

This article argues for a smaller and more useful claim. Resistance is often a field signal. It tells you what the current system is making costly, unsafe, status-threatening, or politically confused. If you want the full conceptual lens, start with the co-creative TA hub. Here the focus is applied diagnosis.

Why the usual story is too small

Personal explanations arrive fast because they simplify the work. If one person is the obstacle, the coach can target persuasion or pressure there. But that move often hides the more interesting truth: the team may be adapting sensibly to mixed messages, unclear decision rights, or a recognition system that still rewards the old behavior.

Resistance therefore deserves to be read before it is judged. Not every refusal is wise, but most resistance tells you something about the conditions under which the requested change is being introduced.

Four lenses for reading the field

What resistance is usually protecting

Fear is common, but usually in social form. People fear what being wrong will do to standing, safety, belonging, or future influence. Loss of control is close behind. Teams are often told they are being trusted more while the rules of judgment remain unchanged. Recognition matters too. If the current setup gives status to being the indispensable expert, shared ownership can feel like a direct threat to identity.

Competing commitments are where the diagnosis becomes useful. A team may genuinely want better quality and also be governed by stronger hidden commitments such as do not slow down, do not expose uncertainty, and do not challenge the strongest role in the room.

How systems teach teams to resist

Resistance grows where agenda mismatch stays hidden, where authority is announced but not transferred, and where the coach starts carrying side conversations that the system is not yet willing to own directly. The team learns quickly which promises are ceremonial and which are real.

That is why resistance so often appears at the gap between Agile rhetoric and lived decision rights. If you need the full autonomy argument, that belongs in Why Self-Organisation Fails. Here the narrower point is that resistance is frequently evidence, not merely obstruction.

From winning arguments to redesigning conditions

None of this means resistance is harmless. It can waste time and freeze learning. The point is not to romanticize it. The point is to stop treating every slowdown as proof that the team needs more persuasion.

Once resistance is read as relational information, the work changes. The coach moves from pushing people over the line toward redesigning the conditions that make a different response possible.