The Fragility Of Agile Transformations

I’ve been part of multiple so-called agile transformations in both small and large organizations. And one pattern keeps standing out: they are surprisingly fragile.

Even in organizations with 1,000+ employees — after years of effort and massive investments in training — things often collapse when just a few key people leave. And more often than not, those people were the driving force behind the transformation in the first place.

This raises an important question:

“If agile work methods are meant to be resilient, why do they so easily fall apart?”

When Agile sticks — and when it doesn’t

The most successful agile transformations I’ve seen weren’t just about adopting frameworks or processes. They were deeply tied to something real — like delivering a mission-critical product that engaged the entire organization. When there was a clear goal and shared urgency, people naturally found ways to work more effectively together. 🎯

But here’s the tricky part: the urgency disappeared once the product was released. People celebrated, and many key figures moved on — sometimes outside the company. And that’s when you find out if the spaghetti sticks to the wall.

When it doesn’t, it’s not necessarily a failure. Organizations don’t stand still; they evolve in (eco-) cycles. That’s why I take issue with the very idea of an “agile transformation.” The word transformation implies an end state. However, organizations are never finished; they are constantly adapting.

Making agility stick

So, how do you ensure agility isn’t just a passing phase?

Leaders — whether formal or informal — need to embed agility into the organization’s DNA by making it a shared effort. Instead of talking to employees about why agility matters, they need to talk with them. There’s a big difference.

This means:
✅ Defining the purpose together — why does agility matter beyond this project?
✅ Developing experiments, practices, and strategies as a shared effort.
✅ Making agility practical by showing how it improves daily work, not just using agile buzzwords.

People don’t fully embrace change unless they’ve had a hand in shaping it. No matter how inspiring your agile vision is, it won’t stick unless employees make it their own.

If you’re wondering how to scale this conversation in a 1,000+ organization, check out Liberating Structures — they help turn engagement into action.

💬 What’s your experience with agile transformations? Have you seen them fall apart — or succeed? What made the difference?