When I was thirteen years old, my mother decided it was time to change the furniture in my room. She didn’t ask for my opinion – one day I simply came home from school to find strangers carrying out my favorite desk. “It’s for your own good,” I heard when I started to protest. Twenty years later, working as an agile consultant in a financial services corporation, I heard almost identical words: “This transformation is for the good of the entire organization.”
Peter Senge was right: People don’t resist change; they resist being changed. And the difference is fundamental.
Anatomy of Resistance – When Good Change Meets Poor Communication
In that financial corporation, I encountered a situation that perfectly illustrates the mechanism of resistance. The organization employed over 3,000 IT specialists, most of whom had worked in the waterfall model for years. The board made a strategic decision to transition to agile methodologies – and rightly so, because today’s financial market demands the speed of response that waterfall simply cannot guarantee.
The problem was that the change was announced, not introduced. During one of the first meetings, the development manager told me directly: “We got an email saying that starting next month we’re working in scrum. Where’s the room for our opinion?”
That was the moment I realized I wasn’t fighting resistance to agile. I was fighting resistance to being changed without participation in the change process.
When “They” Become “Us” – The Psychology of Ownership
The human psyche has one fascinating feature: what we create automatically becomes part of our identity. That’s why the best changes are those in which people feel like co-creators, not passive recipients.
In that corporation, I decided to apply a strategy I call “infiltration from within”. Instead of imposing ready-made solutions, I started with questions:
- What problems do teams encounter in the current work model?
- Where do they waste the most time?
- What frustrates them most in daily processes?
It turned out that people know perfectly well what doesn’t work. After three weeks of workshops, one of the senior developers said: “You know what, our daily standups are basically daily scrum, just nobody called it that.”
Bingo. I wasn’t introducing something foreign – I was helping to name and structure what already existed.
“Not Invented Here” Syndrome
Every organization has its cultural DNA, its way of thinking about itself. In financial corporations, that DNA often sounds like: “we’re unique, our processes are complicated, no external methodology will understand our specificity.”
This uniqueness syndrome is one of the strongest defensive mechanisms2. People don’t reject change per se – they reject change that ignores their context, their knowledge, their experience.
Therefore, a key moment in my work was showing that agile isn’t a ready-made suit you have to put on, but rather fabric from which you can tailor a custom suit. Instead of saying “this is how you do scrum,” I said “let’s see how we could adapt these practices to your needs.”
Influence as Medicine for Resistance
The most effective medicine for resistance is a sense of influence. When people feel they have real influence on the shape of change, resistance transforms into engagement3. This isn’t motivational theory – it’s basic human psychology.
In that organization, the breakthrough was when teams began proposing modifications to standard agile practices themselves. The Product Owner from the mortgage department suggested that in their context, sprint review should be held in two parts: technical demo for IT and business demo for stakeholders. “Otherwise,” he explained, “half the people get bored, and half understand nothing.”
That was brilliant. And more importantly – it was their idea.
Change as Journey, Not Moving
We think about organizational change like moving house: you pack old things, transport them to a new place, unpack. Meanwhile, change is rather gradual metamorphosis – a process where old and new coexist for some time, and people have space for adaptation4.
In practice, this meant I didn’t impose total revolution. Instead, we introduced changes iteratively (how agile, right?). We started with daily standups in three pilot teams. Then we added retrospectives. Sprint planning came only after a month. Each element was tested, adjusted, familiarized.
Communication as the Glue of Change
One of the biggest mistakes in change management is assuming that information equals communication2.Information is “what is changing.” Communication is “why it’s changing, how it will affect me, and what I can do about it.”
In that corporation, the first step was creating a transparent communication channel. Not another newsletter from management, but a real place for information exchange. We created an internal agile community where people could ask questions, share concerns, propose solutions.
The most interesting were questions like: “What will happen to my project manager role?” or “Is scrum master a promotion or demotion for a team lead?” These questions showed where the real source of resistance lay – in fear of losing position, competence, professional identity.
Error Culture vs. Fear Culture
In organizations with strong control culture, people learn that error is a threat3. Therefore, any change that introduces uncertainty meets with resistance. Agile assumes experimentation, learning from mistakes, adaptation – everything that in traditional corporations is perceived as risk.
Breaking this paradox required reprogramming the way of thinking about errors. Instead of talking about “failures,” we started talking about “lessons.” Instead of “problems” – “improvement opportunities.” This may sound like PR newspeak, but it has a real impact on team psychology.
When Resistance Becomes an Ally
Paradoxically, at some point resistance became our greatest ally. People who were initially most skeptical, after being convinced of the change, became its best ambassadors. Why? Because they went through the full cycle: from resistance, through understanding, to internalization5.
The senior developer who initially said “another project management methodology,” after three months of working in scrum, organized an internal agile conference. “I want other teams to try this too,” he said. “But on their own terms, not because someone tells them to.”
Lessons from the Front Lines
After six months of work in that organization, when I look back at the entire transformation, I see several key truths about resistance in organizations:
Resistance is not the enemy of change – it’s a natural defensive mechanism that protects the organization from chaotic, ill-conceived decisions4. Intelligent change management uses resistance as feedback, not fighting it as an obstacle.
People aren’t afraid of change – they’re afraid of losing control over their work environment. Give them a sense of influence on the shape of change, and resistance will transform into engagement.
The best change is one that people feel as their own – even if the original impulse came from above. The art lies in transforming external mandate into internal motivation.
And finally: Peter Senge was right. People really don’t resist change – they resist being changed. The difference is fundamental and has enormous practical consequences.
In the end, organizational change isn’t moving furniture. It’s more like moving to a new apartment – you can take with you what’s valuable, but you must be ready for a new environment. And it’s best if that decision is yours.