Resistance to change: the symptom, not the cause

Few phrases close as many conversations in a company as 'the thing is, people resist change.' It sounds like a diagnosis, but it works as an excuse: it turns a communication problem in leadership into a character flaw in the team.

Resistance is information

When someone resists, it's rarely because they hate improving. It's because the change reached them as an order without a why, because it threatens something they value, or because they've already lived through three previous 'transformations' that came to nothing. Each of those reasons is valuable data, not an obstacle to overcome.

A team that resists isn't blocking change. It's telling you, in its own language, what wasn't translated well.

What resistance is usually translating

• “I don't understand what it's for”: the vision wasn't translated into day-to-day meaning.
• “I don't trust that this time is different”: there's a debt of previous changes left unfulfilled.
• “This makes me look incompetent”: the change threatens someone's identity or mastery.
• “Nobody asked me”: the change was designed without the people who'll live it.

From overcoming resistance to translating it

The difference between imposing and supporting is translation. It's not about convincing people to accept something, but about translating the change into their reality: what they gain, what's asked of them, what they stop doing and why it makes sense. When the why truly arrives, resistance stops being a wall and becomes participation.