Why did so many of the early agile transformations fail?

Published on
5 minute read

Why did so many of the early agile transformations fail?

I think a better question is to ask why so many agile transformations fail, period, because the early agile transformations failed for the same reasons current agile transformations fail.

Misalignment between implementation and decision-making.

The people who are involved in the implementation are often not the people who get to decide on what is going to be implemented, how it is best implemented, and why this choice has been made.

In other words, a ‘solution’ is imposed on the team rather than cocreated with the teams.

Leadership will decide that X is going to be adopted, but the people actively doing the work know that it’s the wrong solution. It simply isn’t a great fit and doesn’t solve the problems that the product development teams are experiencing.

Often, this happens when a consultant sells an off-the-shelf agile solution rather than investing time and effort with the teams, customers, and product stakeholders to select the agile framework that best serves the environment.

This happens with all kinds of change.

  • Agile transformations

  • Digital transformations

  • Sweeping HR policy transformations

And so forth.

Alpha organizations

In the top-down, command and control structures you tend to witness a great deal of this.

The people at the top make the decisions, but the people who do the work are actively excluded from this process and have decisions imposed on them, regardless of whether these are a great fit for the environment or not.

An agile environment embraces the experts, who are actively doing the work, being part of the decision-making around how best to build the solution or solve the problem. I would advise that you start the process by including individuals and teams in the decision-making process.

In 90% of these command-and-control cases, the people that you want to work in a certain way simply don’t want to work in that way because they don’t believe it will work, improve the situation, or allow them to serve customers effectively.

In the context of how to get work done effectively, the experts who actively perform the work are way smarter, more informed, and knowledgeable about the environment than the leaders who seldom set foot in those environments.

If they are consulted throughout the process, you gain buy-in across the team environment and are much more likely to have a successful adoption of agile that achieves the objectives and outcomes that you are looking for.

The people on the ground have:

  • More relevant and useful information than you do.

  • They have a greater understanding of the problems in the environment.

  • They have a greater understanding of what will work in the environment.

  • They have a greater understanding of what will improve flow throughout the system.

  • They have a greater understanding of the customer environment.

  • They have a greater understanding of how suppliers integrate into the system.

  • They have a greater understanding of how partners integrate into the system.

So, it really does serve leadership teams to embrace the unique knowledge, skills, and capabilities of the experts in the team environment and include them in decision-making for the transformation.

Open Space Agile

There has been a lot of great work produced by Open Space Agile  that allows relevant people to be involved in decision-making throughout the organization.

The folks at Open Space Agile understand that it can be a significant transition to agile, and in an effort to help organizations facilitate better decision-making, in the context of Agile, they created practices, processes, and systems that allow you to tap into the expertise on your team.

The process allows you to eliminate resistance and sabotage.

Even if people don’t 100% agree with the solution that is going to be adopted, they will still back the initiative because their voices have been heard, their contribution has been embraced, and although a few flaws may be present, it is still a step in the right direction that can be improved over time.

In other words, they have cocreated the solution and are a great deal more emotionally invested in the positive outcome than they would be if it were simply imposed on them.

They will be supporting and helping to improve the solution as they move forward rather than actively fighting or sabotaging the process. Google Open Space Agile and invest a little research in identifying how this framework can help you and your teams.

So, in my opinion and experience, this is the greatest reason why agile transformations fail and it’s easily avoided, easily overcome, and easily transformed into a positive and engaging experience for teams if you include them in the process.

About NKD Agility

Naked Agility is an #agile consultancy that specializes in #scrumtraining, #agilecoaching and #agileconsulting to help teams evolve, integrate, and continuously improve.

We recognize the positive impact that a happy AND inspired workforce can have on customer experience, and we actively help organizations to tap into the power of creative, collaborative, and high-performing teams that is unique to #agile and #scrum environments.

If you are interested in #agiletraining, visit https://nkdagility.com/training/ 

If you have identified the need for #agilecoaching and #agileconsulting, visit https://nkdagility.com/agile-consulting-coaching/ 

We would love to work with you.

#scrum #agile #scrumteam #agileprojectmanagement #agileproductdevelopment #projectmanagement #productdevelopment #agilecoach #agileconsultant #agiletraining #scrumtraining #scrumorg

So the question is, why did so many of the early agile transformations fail? I think a better question is just, without the early part on it, right? Why do so many agile transformations fail? Because the early ones failed for the same reason as they do now.

That’s the people who are doing the implementation are not involved in the process of deciding what we’re implementing. Right? That’s why it fails. Because your leadership decides we’re going to do it this way, and everybody else goes, “Okay, but that’s the wrong way.” Suddenly, they’re resistive and unhappy because they feel like it’s imposed upon them.

If you know that old saying, “If I’d been asked, I would have…” right? They would have said to do something different. You get that through organisations, and it can be agile transformations, it can be digital transformations, it can be just changing something, right?

The top-down command and control triangle model in alpha organisations, right? Where you’ve got the people at the top making the decisions and the people at the bottom doing the work. All the decisions are made at the top, and we steer the rest of the organisation based on those decisions. You’re always going to get into that situation where the people that you need to do the stuff don’t want to do it because, in this context, they’re smarter than you are.

They have more information, they have more understanding, and they perhaps have more skills in that space. So they’re the ones that should be involved in driving it. I think there’s been a lot of good work done by open space agile and specifically, as well, on top of that, open space beta to allow methods and systems to be created, a practice to be created that allows you to involve everybody in the organisation in making those decisions.

If you involve everybody in the organisation in making those decisions, then even though it might not be the decision that they would have made if they were sitting there on their own, right? Because they were involved in making that decision, they feel like their voice is heard. If they feel like their voice is heard, they’re more likely to get behind whatever the ultimate decision was because it’s a collective decision, right?

Decentralisation and democratisation of the ideas, and then they’ll be supporting and helping with the transition as you move forward rather than getting in the way and hindering because they just don’t care, because you didn’t ask me anyway.

That’s what I think is why agile transformations fail, and I think it’s just as true today as it was in the early days. It’s just in the early days, there was a small number of high-profile agile transformations, and today, there are hundreds of thousands of actual transformations going on.

People and Process Decision Making Agile Leadership Beta Codex Agile Strategy Agile Philosophy Agile Project Management Sociotechnical Systems Agile Transformation Organisational Change

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Healthgrades Logo
Lean SA Logo
Slaughter and May Logo
Lockheed Martin Logo
Philips Logo
SuperControl Logo
Boeing Logo
Alignment Healthcare Logo
ALS Life Sciences Logo
New Signature Logo
Illumina Logo
Ericson Logo
Akaditi Logo
ProgramUtvikling Logo
Bistech Logo
Microsoft Logo
Hubtel Ghana Logo
Genus Breeding Ltd Logo
Washington Department of Enterprise Services Logo
Department of Work and Pensions (UK) Logo
Nottingham County Council Logo
Washington Department of Transport Logo
Royal Air Force Logo
New Hampshire Supreme Court Logo
Cognizant Microsoft Business Group (MBG) Logo
New Signature Logo
Bistech Logo
Epic Games Logo

NIT A/S

Healthgrades Logo