What the Agile Transformation Work Taught Me About Leading Change and What It Didn't

The task sounded simple enough on paper. A large global financial institution needed to shift how it measured, funded, and budgeted for work. The organization was moving toward a product orientation to support Agile ways of working, and the old project-based financial model was no longer fit for what the business was asking teams to do. The solution was clear. Getting there was not.

I was part of the team tasked with convincing the CFO and the finance organization to change how they thought about value, funding, and accountability. That meant rebuilding data stores, cleaning up project management information systems, designing proof-of-concept frameworks, and building a body of evidence substantial enough to shift a financial culture that had operated the same way for decades. The technical work was heavy. The human work was heavier.

What I learned in that engagement, and in several like it across different industries, is that transformation does not move the way the methodology says it will. It moves the way people do. And the people who actually moved it were almost never the ones I would have predicted at the start.

The Map and the Territory Are Not the Same Thing

Every transformation effort I have been part of begins with a map. A roadmap, a program plan, a change management strategy. The map is necessary. It provides direction, it creates shared language, and it gives leadership something to align around. Without it, you are navigating in the dark.

But the map is not the territory. The territory is the actual organization: the informal power structures, the unwritten rules, the relationships between people who have worked together for ten or twenty years, the fears and egos and turf considerations that no org chart will ever capture. Transformation fails when the people holding the map forget that the map and the territory are two different things.

At this organization, the territory was complex in ways that mattered. The finance teams we needed to bring along had deep institutional knowledge. They understood the business in ways that no consultant or program team could replicate in eighteen months. They were not resistant because they were obstructionist. They were resistant because the change was asking them to give up frameworks that had worked reliably for years, and nobody had taken the time to speak their language about why the new approach would work better.

Who Actually Moves the Needle

The people who moved the needle in this engagement were not the ones with the most Agile certifications. They were not the loudest voices in the room or the people with the most authority on the org chart. They were the people with the deepest social capital in the organization, the ones who had spent years building trust across functions, and the ones who could translate the vision into the language of whatever stakeholder group they were sitting with.

The VP overseeing the program had extraordinary relationship depth across the organization. Her peers had the same depth in different parts of the business. And within each function, there were people who could update their own thinking more readily than others, who could see the possible future connected to the strategy and help their colleagues take one step toward it. You need all three layers. The senior leaders with the social capital to protect the effort and absorb the friction. The cross-functional peers who carry credibility in the pockets of the organization that leadership cannot reach directly. And the individuals within each group who can move, and who others watch when they are deciding whether to move themselves.

Transformation does not move the way the methodology says it will. It moves the way people do. The question is whether the right people have been found, equipped, and protected.

What this structure provides is something no project plan can manufacture: patience, buffer, and proof. When one area makes the shift and it works, that becomes the case study. When a finance team sees another finance team operating with the new model and not losing control of their numbers, that is worth more than any presentation deck ever built. You need the early adopters to make the story visible and to help translate it into language that the holdouts can actually hear.

The Saboteurs Are Real and Worth Taking Seriously

Every transformation has them. The people who are not simply skeptical but are actively working against the change, whether openly or not. Some of them are protecting something legitimate. Some are protecting something that stopped being legitimate years ago. Some are scared in ways they have not named out loud, and fear that has no language tends to express itself as opposition.

The mistake I saw repeatedly was treating saboteurs as a problem to be managed rather than a signal to be read. In most cases, the resistance pointed directly at something the transformation plan had not adequately addressed: a legitimate concern about accountability under the new model, a fear about what happens to a team when the funding structure changes, a sense that the people driving the change did not understand the operational reality they were asking others to leave behind.

Not all saboteurs can be brought along. Some cannot. But most resistance, when you get underneath it, is telling you something true about the gap between the map and the territory. Ignoring it does not make it go away. It drives it underground, where it does far more damage.

What This Has to Do With Right Now

I have been watching organizations navigate AI with the same patterns I watched them navigate Agile. The vision is clear at the top. The strategy is articulate and well-funded. And the operating model has not changed. How people are measured has not changed. How teams are resourced has not changed. How performance is evaluated has not changed.

So you have leaders who are being asked to move toward a future that the organizational infrastructure is still actively rewarding people to resist. The people who adapted to Agile in the old way are still being recognized for it. The people experimenting with AI tools are doing it on the margins, not because it is built into how the work is designed and measured. And the gap between the vision and the operating reality is producing the same symptoms I saw in every major transformation I was part of: confusion, fear, turf protection, and the particular exhaustion that comes from being asked to move fast in a system that has not yet decided to let you.

The leaders navigating this successfully are the ones who are doing what worked in those Agile engagements. They are finding the people with the social capital. They are building coalitions across functions rather than trying to drive change from a single point of authority. They are making the wins visible early and often. And they are paying attention to the resistance rather than dismissing it.

What Agile Did Not Teach

Here is what the methodology did not prepare anyone for: the identity question underneath the change. When you ask a long-tenured expert to adopt a new way of working, you are not just asking them to learn new tools. You are asking them to be less expert, at least temporarily, in a place where their expertise has been the source of their standing and their confidence. That is an identity question, not a process question. And process frameworks do not reach identity questions.

The transformations I saw go furthest were the ones where someone in the room understood this, and created space for people to name what the change was actually costing them, not just what it was asking of them operationally. That space is not something you can put in a project plan. It requires a different kind of leadership, and often a different kind of support, than most transformation programs budget for.

The organizations that figure this out are the ones that will navigate what comes next. Not because they have the best methodology. Because they have invested in the people who can move between the map and the territory, speak across the factions, and hold the human experience of change alongside the operational demands of it.

The question worth sitting with is not whether your organization has a transformation strategy. It is whether the people carrying it have what they actually need to make it land.