The Agile Transformation Has Stalled
Teams work in an agile way, the organization does not. Sprints, boards and roles are in place, yet decisions take as long as before.
At a glance
How you recognize it
We work in sprints, but we still wait for approvals.
What lies behind it
- Decision rights did not move with the responsibility
- The organization around the teams follows the old logic
- Agility was added on top
- Leadership works as before
Where the lever is
Agility rarely fails because of the method.
It stalls at decisions that stayed the same at the top.
01
The pattern
The agile transformation has been running for some time. Teams work in sprints, there are product owners, retrospectives and boards. The first months brought noticeable progress. Since then something has set in: the teams have become faster, the organization has not.
Approvals take as long as before. Priorities change without anyone asking the teams. Budgets are still allocated once a year, and experiments have to pay off like projects. The agile roles are filled, but they decide little. In the leadership team, the explanation is that the method has not taken hold yet, and the conversation turns to the next training or a scaling framework.
02
Why it happens
-
Decision rights did not move with the responsibility
Teams carry more responsibility but may decide no more than before. What they could do faster waits for someone further away. The leadership vacuum describes this pattern.
-
The organization around the teams follows the old logic
Budgeting, controlling, procurement and approvals are built for predictability. Wherever teams learn in short cycles, every interface creates friction. The Taylor bathtub explains why structures pull new behavior back.
-
Agility was added on top
Nothing was stopped when the new way of working began. Teams run in sprints and in the old committees at the same time. That is structural overload.
-
Leadership works as before
The leadership team still steers through status reports and milestones. The organization reads from this what really counts.
03
Typical dead ends
"We need a scaling framework."
SAFe, LeSS or the Spotify model organize how many teams work together. They do not replace the decisions missing at the top. Often they add another layer of roles and meetings.
"The teams need to become more agile."
More training improves the method, not the frame. Teams that hit limits they are not allowed to move do not get faster through training, they get more frustrated.
"We need more agile coaches."
Coaching helps teams improve their work. It changes nothing about budget logic and decision rights as long as leadership does not address them.
"Agile does not work here."
This conclusion often comes too quickly. Agility does not fit everywhere, but where work is new and uncertain, what is usually missing is not suitability but a decision.
Agility rarely fails because of the method.
It stalls at decisions that stayed the same at the top.
04
Where to start
-
Check where agility fits
The Agile Suitability Canvas shows for each area how new and uncertain the work is and which form of steering fits it.
Agile Suitability Canvas -
Find the missing decision
A Transformation Discovery Workshop with the leadership team shows, along the six perspectives of the Compass, where the transformation is stuck and which decision gets it moving again.
Transformation Discovery Workshop
Related situations
These situations often occur together.