Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Agile was born as a grassroots movement—an antidote to bureaucratic, top-down processes that stifled innovation and collaboration, a competitor to Lean Six Sigma’s focus on cost and quality achieved using standardised ‘best practices’. Its core values champion individuals, interactions, working software, and customer collaboration over rigid tools and processes. Yet, as Agile has gone mainstream, a new phenomenon has emerged: the rise of the “Agile Industrial Complex.” This refers to the ecosystem of consulting firms, certification bodies, and tool vendors profiting from the sale of prepackaged, one-size-fits-all frameworks. While these solutions can promise transformation and order, they often ignore the unique realities of client organizations, leading to failed implementations, wasted investment, and ethical dilemmas.
- Have you experienced an “Agile transformation” driven by external consultants or frameworks that didn’t fit your organization’s needs?
- What lessons did you learn, and what would you do differently next time?
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Interesting reflection.
One thought that comes to mind is that the problem is rarely the framework itself. More often, it is the assumption that a framework can substitute for understanding the context in which it will operate.
Organizations differ in culture, constraints, objectives, governance models, and levels of maturity. A practice that creates value in one environment may create friction in another.
Perhaps the real challenge is not avoiding frameworks, but avoiding the belief that frameworks eliminate the need for judgment.
After all, no framework is a substitute for contextual thinking. Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Luis Branco I totally agree that a framwork is not the root cause. Most rameworks emerged from a successful implementation of some practices. Some frameworks are the victim of good marketing, when expectations promised are unrealistic. Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Luis Branco organisations, teams, and individuals are not the same. Similar experience or knowledge doesn't mean the same people. Blindly implementing a framework by the book always ends in failure. Lack of context understanding and adaptation of a framework or practices to the organisation's culture can have multiple causes; sometimes, the reason is financial gain, and in some instances, it is a lack of hands-on experience. Someone who never had the responsibility of a team or product is unlikely to help others. Agile is learned 'by doing it and helping others to do it', not in the training room. Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Luis Branco the real challenges are the lack of leadership, skills, experience and especially a toxic culture. Saving Changes...
Ming YeungAdjunct Professor| George Brown Polytechnic/Fanshawe College/Humber PolytechnicToronto, Ontario, Canada
Dan, I have definitely experienced Agile transformations driven heavily by external consultants and rigid frameworks, and the pattern is remarkably consistent. Instead of starting with an honest assessment of culture, constraints, and organizational maturity, the transformation begins with a preselected framework, usually something large, branded, and certification‑heavy. Teams are then expected to “adopt” it wholesale, regardless of whether it aligns with how the organization actually works. The result is often a veneer of agility layered on top of the same old command‑and‑control behaviors. One transformation I was part of introduced a scaled framework across dozens of teams overnight. The consultants were well‑intentioned, but the implementation felt more like compliance than empowerment. Teams spent more time filling out mandated templates and attending prescribed ceremonies than solving real customer problems. Unsurprisingly, morale dipped, delivery slowed, and leadership eventually questioned why “Agile wasn’t working.” The biggest lesson I took away is that agility cannot be installed; it has to be grown. Frameworks can be helpful, but only when they are adapted thoughtfully, not imposed mechanically. If I were to approach it again, I would push for a discovery phase before any framework decision: understand the organization’s goals, pain points, and readiness; experiment with lightweight practices; and let teams co‑create the operating model rather than having it dictated to them.
...
1 reply by Stelian ROMAN
Sep 08, 2026 6:28 PM
Stelian ROMAN
...
"The pattern is remarkably consistent". Not a surprise. The worst experience that I had was an "Agile Coach" paraded as proof of Senior Management's Agility. An Agile Coach should help management to change the culture, delegate authority, and not find out and help punish the 'resistance'. An ethical approach, rarely seen by me, is benchmarking the current state and proving that Agile improved the processes, at least to recover the consultancy cost.
Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Jun 26, 2026 11:25 PM
Replying to Ming Yeung
...
Dan, I have definitely experienced Agile transformations driven heavily by external consultants and rigid frameworks, and the pattern is remarkably consistent. Instead of starting with an honest assessment of culture, constraints, and organizational maturity, the transformation begins with a preselected framework, usually something large, branded, and certification‑heavy. Teams are then expected to “adopt” it wholesale, regardless of whether it aligns with how the organization actually works. The result is often a veneer of agility layered on top of the same old command‑and‑control behaviors. One transformation I was part of introduced a scaled framework across dozens of teams overnight. The consultants were well‑intentioned, but the implementation felt more like compliance than empowerment. Teams spent more time filling out mandated templates and attending prescribed ceremonies than solving real customer problems. Unsurprisingly, morale dipped, delivery slowed, and leadership eventually questioned why “Agile wasn’t working.” The biggest lesson I took away is that agility cannot be installed; it has to be grown. Frameworks can be helpful, but only when they are adapted thoughtfully, not imposed mechanically. If I were to approach it again, I would push for a discovery phase before any framework decision: understand the organization’s goals, pain points, and readiness; experiment with lightweight practices; and let teams co‑create the operating model rather than having it dictated to them.
"The pattern is remarkably consistent". Not a surprise. The worst experience that I had was an "Agile Coach" paraded as proof of Senior Management's Agility. An Agile Coach should help management to change the culture, delegate authority, and not find out and help punish the 'resistance'. An ethical approach, rarely seen by me, is benchmarking the current state and proving that Agile improved the processes, at least to recover the consultancy cost. Saving Changes...
