• Agile & Scrum Basics

How do you deal with resistance to Agile within traditional organizations?

Implementing Agile promises a lot: agility, shorter feedback loops, more ownership by teams. But in organizations with a traditional, hierarchical structure, Agile also sometimes leads to a good deal of resistance. Not because people are against change per se, but because change simply also brings uncertainty and fatigue. In this article I elaborate on 3 ways to deal with it.

Sometimes people are simply tired of new trajectories all the time, without previous initiatives having been completed or evaluated. Change fatigue is then not an unwillingness, but a signal of overload. At Scrum Academy, we guide organizations dealing with this area of tension. Our experience? Resistance is not a blockage, but a valuable signal.

When a manager says, “Agile doesn’t work for us,” he or she often means, “I don’t know how to fill my role in this new system.” Or when a team member says, “Why do we have to do everything differently again?”, it’s about a need for clarity or fatigue from previous changes that never really landed. In other words, resistance is rarely against Agile itself, but a reaction to what people think Agile is asking of them. Or to what they are already behind.

Three ways to deal constructively with resistance

1. Name the tension and normalize it
A move to Agile often means a shift from control to trust, from top-down control to shared ownership. This chafes with existing structures, processes and habits. Name that.

This tension, by the way, is not only logical but also human. When people are faced with successive changes (think of new systems, roles or processes) this can lead to emotional exhaustion. Change fatigue then expresses itself as withdrawal, cynicism or, on the contrary, resistance. This is sometimes wrongly seen as sabotage, while it is mainly a sign that there has been insufficient room for processing and involvement.

By making explicit that this friction is normal and even necessary, you create space for an open conversation. Not to dismiss resistance, but rather to take it seriously.

2. Involve people early and sincerely
Agile is not an IT party. It affects the entire organization. Therefore, involve people from all layers early on. Not only to create support, but to discover together: what does Agile mean in our context?

Getting involved means more than an invitation to a kick-off session. Give space to feelings of fatigue, doubt or frustration, without wanting to fix everything immediately. The ongoing conversation without judgment creates safety and opens the door to renewed motivation.

Also, be sure to ask people not just what they need to move along, but ask them what they have learned from previous changes. Change fatigue often decreases when people feel heard, acknowledged and taken seriously.

3. Support leadership in transition
In hierarchically organized companies, many executives feel outflanked by Agile terminology. Their role suddenly seems redundant, while Agile leadership is crucial. Therefore, give leaders the tools to reshape their role: from decision-maker to facilitator, from controller to direction-giver. Because Agile leadership does not start with frameworks, but with the courage to really listen and let go.

This requires leaders to also make more room for reflection. Indeed, many (middle) managers find themselves in an area of tension: they have to facilitate new ways of working, while still being judged by old KPIs and controlling expectations. Precisely they therefore need support to work with:

• an open mind to look at their role
• an open heart to listen to the concerns of their teams
• an open will willing to let go of old patterns.

Agile requires culture change, not a copy of a framework

Resistance within traditional organizations does not disappear through training or implementing a toolset. It requires dialogue, adaptation and time. Agile is not a “recipe” you follow, it is a process of learning and evolving together. This is why it is important to approach change not as an implementation project, but as a learning process. A learning process where there is also room for fatigue, doubt and recovery.

We at Scrum Academy do not see resistance to Agile as an obstacle, but as an opportunity. By acknowledging the area of tension, actively involving people and supporting leadership, the space for real, sustainable change is created. Agile does not succeed through dogma, but by taking people seriously.

Discover how to initiate a supported Agile transition within your organization?

We like to help. Not with a blueprint, but with customization. Contact us for a no-obligation sparring session.