Leadership Mistakes in Agile: Why Your Transformation Is Stalling (And It’s Not the Teams’ Fault)

You put the teams together. You brought in a coach. The whiteboards were covered with Post-it notes, the meetings were renamed, and for a few weeks, there was a different atmosphere. Eighteen months later, the deadlines are pretty much the same as before, and the same three people are still signing off on any decision that matters.

The easy conclusion is that your organization “isn’t cut out” for agility, or that the teams lacked commitment. That’s almost never the case. The mistake usually lies with leadership and comes from one level higher: you launched a transformation that changes how others work while leaving intact what you control—what gets decided, how money is allocated, who gets rewarded, and what your own job entails. You changed everyone except the system you govern.

Why does an Agile transformation stall even when the teams are doing their part?

Because the hardest part isn’t done by the teams. According to a 2021 global McKinsey survey of more than 2,000 executives, two out of every three organizations that embark on an agile transformation fall short, with little real impact on the business. And when the study looked into what prevents organizations from making the leap, technology ranked near the bottom. The main obstacles were culture, structures, incentives, and funding mechanisms—in other words, the framework that sets the direction, not the teams that carry it out.

There’s one detail in these data that stands out. The three most visible actions of any transformation—renaming teams “squads,” drafting a governance manual, and setting up a generic agility course for the entire workforce—were the ones that showed no correlation, or a negative correlation, with success. What is visible from the outside is often precisely what doesn’t change anything on the inside.

You change how the team works, but not who makes the decisions, who pays, and who gets rewarded.

The four leadership mistakes that perpetuate this stagnation are almost always the same:

1. You delegate the work, but you reserve the right to make the decisions.
2. Based on a one-year timeframe, what you say you want is flexibility.
3. You reward the usual things: sticking to the plan and individual performance.
4. You’ve changed the teams’ roles, but not your own.

Do you delegate decisions, or do you just assign tasks?

Delegating tasks is easy; handing over the decision-making behind them is what almost no one does. When you delegate work without transferring context or decision-making authority, you end up with teams that execute well but ask for guidance on everything. The trendy question is, “Do you trust your team?” but it’s too vague to be useful. There’s a more specific one: Who can say no to a business request—or halt a delivery—without having to go up the chain to ask for permission?

Take a look at the decisions that still get escalated: the order of the backlog, talking to the client, moving a deadline, or putting a release on hold. If they all end up in the same committee, you haven’t delegated—you’ve just spread out the execution. And this isn’t fixed by suddenly letting go of control. Practices like Management 3.0’s Delegation Poker are designed precisely to agree, decision by decision, on how much autonomy the team has and where the limits lie—rather than leaving it up to intuition from week to week. If you want to delve deeper into this shift in role, we explore it in “How to Be an Agile Leader.”

Question for your committee: What decisions is this level of management still making that a team would be better suited to make—with more information and closer to the customer?

Are you still estimating a one-year timeline for a project that you say you want to be agile?

Here’s the obstacle that nobody talks about in any daily meeting: the annual budget. You can ask a team to “respond to change” as much as you want, but if their funding and roadmap are decided once a year, every quarterly prioritization is an empty gesture: the big bets have already been locked in since the previous fall. It’s no coincidence that McKinsey points to funding mechanisms and the rigid annual budget as among the factors preventing agility from scaling.

The CFO will rightly respond that a company cannot be run without a budget. That’s true, and the point isn’t to eliminate it. The point is to shift the allocation decision to a quarterly basis: to fund stable teams rather than one-off projects, and to reallocate resources based on what we’ve learned. It’s the same logic we use at SmartWay when we recommend revising OKRs every quarter: flexibility isn’t just talk—it’s built into the schedule for allocating funds.

The consequence: any significant reallocation must wait until the end of the year. The solution: shift from funding projects to funding teams, and review the allocation every quarter.

Who does your incentive system really reward?

What shapes behavior isn’t what you say at the outset; it’s what ultimately determines bonuses and promotions. If you keep rewarding individual performance and “sticking to the plan,” it doesn’t matter how much you talk about collaboration: people will optimize for what they’re measured on. That’s why many transformations remain confined to the scorecard (you change metrics, from story points to whatever else) without touching payroll, which is where the real stakes lie.

Speed is a good example. It measures activity, not results; it rewards being busy, not getting it right. Replacing it with another process metric doesn’t solve anything if the team is still not held accountable for business results. The transformations that did work redesigned career paths to reward contribution and expertise over seniority—not just the plaque on the wall.

Deliverable: A list of the three behaviors you currently reward with bonuses or promotions, and what message each one sends. If all three focus on individual performance and meeting the plan, you already have your diagnosis.

Have you changed your own role, or just the teams’ roles?

You asked the teams to work differently. But what about your own role? In most transformations, the job description of the person sponsoring the change remains unchanged: the same meetings, the same approvals, the same reporting cycle. Everyone changes except the person in charge.

There are two layers that almost always get left out of the loop. The first is middle management: they’re asked to “facilitate” rather than “lead,” but they’re given a new verb and no framework, time, or training to put it into practice. They are, at the same time, the ones best positioned to drive change—they’re closely tied to the teams and the strategy—and the ones who perceive it most as a threat. The second level is you. According to a 2018 McKinsey study on leadership, leadership itself and the culture it creates are the biggest barriers to transformation, far ahead of technology. In other words: as long as your agenda and decision-making filters remain the same, the system assumes that, deep down, nothing has changed.

Start by: giving your middle managers a new, written role—not just a new verb—and choosing the two approvals that currently go through you and that you’re going to delegate this quarter, with clear boundaries.

Six Questions to Find Out If Your Leadership Is Holding You Back

Answer them quickly and briefly. Count how many times the honest answer falls into the “uncomfortable” category.

1. In the last three months, has any team made a major decision without consulting you or your committee? (If the answer is “no,” that’s a bad sign.)
2. Could you reallocate funds from one initiative to another this quarter, without waiting until the end of the year?
3. Was the last promotion or significant bonus you received based on a team result or individual merit?
4. When a middle manager asks you, “So what’s my role now?”, do you have a written answer, or do you wing it?
5. Since the transformation began, has anything changed in your own schedule (meetings you attend, documents you sign), or is everything still the same?
6. If you were to remove the new terms (“squad,” “tribe,” “daily”) tomorrow, what would really change in terms of how people make decisions and get paid?

How to read it. None or one in the “uncomfortable” box: the transformation is happening to you, not just to the teams; you’re on the right track. Two or three: You’ve shaken up the teams, but not the system around them; choose a lever (budget, incentives, or decision-making) and pull it now—don’t put it off until next year. Four or more: what you have is a facade—a lot of new trappings on top of the same old organization. And that can’t be fixed at the team level.

Where to Start When Transformation Has Stalled

The leadership mistakes that stall an Agile transformation all stem from the same root cause: they all occur at a level above the team. When change fails to take hold, the temptation is to demand more from the teams: more discipline, more ceremonies, another training course. The data points in the opposite direction. The lever that’s hardest to move is almost always the one that’s yours—and the one that hurts: the pace at which the budget is decided, or the criteria you use to promote people. Moving one of those two is what shows the organization that the transformation includes you, too; everything else is just window dressing.

So stop wondering if your teams are agile enough, and ask yourself this: What would change in your company if the next budget committee meeting were held every 90 days instead of once a year?

At SmartWay, that’s exactly where we come in. Our Agile consulting goes beyond just building teams: it helps executive committees redesign decision-making processes, funding, and incentives so that agility becomes more than just a superficial change. If you want an honest, outside perspective on what’s holding you back, let’s talk. 🙂