Professional

Agile leadership in organizations that aren't agile: how to survive in no man's land

Automatic translation · View original

Topic illustration: Agile leadership in organizations that aren't agile: how to survive in no man's land

You know the principles. You know how to facilitate a retrospective, write user stories with good judgment, and create an environment of psychological safety. But when you get to work, you find weekly status meetings that decide nothing, roadmaps carved in stone six months in advance, and a hierarchy that approves even the color of the sticky notes. This is the reality of thousands of agile professionals who operate in organizations that aren't agile. It isn't a knowledge problem: it's an ecosystem problem. And it has more nuances than any Scrum manual can anticipate.

The most widespread narrative among frustrated agilists is that their organizations simply "don't understand" what agility is. If only executives read the Agile Manifesto, if only they attended a training session, everything would change. This explanation is seductive because it places the problem in knowledge and, therefore, suggests it has a technical solution: more training, better arguments, presentations with more data.

The problem is that it is rarely that simple.

Dave Snowden, creator of the Cynefin framework, has spent decades arguing that organizational systems are complex adaptive systems, not machines that can be redesigned by following a blueprint. Organizations have inertia, history and, above all, incentives that sustain existing behaviors far more effectively than any statement of principles. When a project manager has spent fifteen years being evaluated on their ability to deliver a plan down to the millimeter, it's not that they "don't understand" agility: it's that the system they operate in actively penalizes it.

This distinction matters enormously for anyone who wants to exercise agile leadership in that context, because it determines which strategies make sense and which are simply a waste of energy.

The mirage of transformation from within


One of the most persistent myths of the agile movement is that anyone, with enough persistence and the right tools, can transform their organization from within. There are real cases that illustrate this. There are also many more cases that are never published, featuring exhausted professionals who invested years trying before acknowledging that the system simply wasn't ready to change.

Lyssa Adkins, in her work on agile coaching, introduces a distinction worth recovering here: the difference between a system that wants to change and a system that says it wants to change. The first is ready for the real discomfort that any transformation entails; the second seeks cosmetic updates that allow it to keep functioning exactly as before. In practice, many agile initiatives within traditional organizations fall into the second category: ceremonies are adopted, vocabulary is changed, but power structures, incentives and decision-making processes remain intact.

This isn't cynicism: it's an observation about the nature of cultural change. Edgar Schein, whose theory of organizational culture remains one of the most solid in this field, argued that an organization's real values are not found in its public declarations but in what it rewards, what it tolerates and what it sanctions day to day. From this perspective, the relevant question is not "Does this organization have declared agile values?" but "What behaviors does it actually reward and punish?".

What it means to lead in an agile way when the system isn't


If we accept that not everyone has the position, energy or circumstances to transform their organization, and that this honesty is not defeat but realism, the practical question changes: what can an agile professional do to lead effectively within an organizational context that doesn't share their principles?

The answer is not unique, and it depends greatly on the level of real influence one has. But there are some patterns that consistently appear.

Clarity about what you can control


Stephen Covey popularized the distinction between the circle of concern and the circle of influence, but the most honest application of this principle in organizational settings comes from recognizing that the real circle of influence of a Scrum Master or agile coach without formal authority is often quite small. And that's fine. The problem arises when someone tries to operate in the circle of concern as if it were the circle of influence.

Clarity about what you can change, such as the behavior of your immediate team, the quality of conversations in your ceremonies, and the way you protect the team's focus during a sprint, and what you cannot change, such as the reporting structure, performance evaluation criteria, and the organization-wide meeting culture, is not resignation. It is a precondition for acting effectively.

Working with constraints, not against them


Agile professionals with the most experience in non-agile organizations tend to share one trait: they have learned to work with the system rather than collide head-on with it. This doesn't mean capitulating to dysfunctional practices; it means understanding what is negotiable and what isn't at each moment, and finding room to maneuver within real constraints.

Henrik Kniberg described this balance precisely in his reflections on implementing Scrum at Spotify: agile frameworks are tools, not religions. Adapting them to context is not betraying their principles; it is applying them with maturity. A team that holds weekly retrospectives in an environment that demands waterfall reports may be cultivating a very real culture of learning, even though the artifacts sent upward are the ones the system requires.

Psychological safety as a local lever


One of the most replicated findings in research on high-performing teams is that psychological safety, the shared perception that the team is a safe environment for taking interpersonal risks, consistently predicts both team learning and team performance. Amy Edmondson, who developed this concept over decades of research, made clear in her work that psychological safety does not depend on the general organizational culture: it can be built at the team level even when the broader environment doesn't support it.

This is particularly relevant for agile leadership in non-agile organizations, because it suggests there is a real lever available at the micro level: a Scrum Master, a team leader or an agile coach can actively work to create conditions of psychological safety within their team, regardless of what happens in the rest of the organization. It is not the complete solution, but it is a real and measurable contribution.

Managing upward with the right language


One of the most underdeveloped skills among agile profiles is the ability to communicate the value of their practices in the language of those who make decisions above them. Not because one must hide that they work in an agile way, but because agility as an end in itself rarely mobilizes those who prioritize predictability, control or resource efficiency.

McKinsey's research on agile transformations has repeatedly documented that the initiatives that survive in traditional organizations are those that manage to connect their metrics with the indicators the organization already values: cycle time, reduced rework, responsiveness to market changes. This isn't manipulation: it's translation. And it is a skill that agile frameworks rarely teach explicitly.

The three most common traps


There are error patterns that recur often enough to deserve specific attention.

  1. The purism trap. Defending agile principles so rigidly that any adaptation to context is perceived as a betrayal. This stance creates unnecessary friction, alienates potential allies and frequently produces the opposite of the desired effect. The Scrum Guide is explicit that Scrum is designed to be implemented in its entirety, but also that its rules are the minimum necessary, not a dogma that ignores organizational reality.
  2. The isolation trap. Creating a team bubble so protected from the organization that it loses all ability to influence it. A team can be very functional internally and still be completely irrelevant to the broader system around it. Influence requires contact, and contact implies accepting some contamination from the environment.
  3. The silent burnout trap. Perhaps the most dangerous. Professionals who keep functioning normally on the outside while accumulating a growing frustration that they neither process nor communicate. Christina Maslach identified value incongruence (working in an environment that systematically clashes with one's own values) as one of the most powerful predictors of professional burnout. Recognizing when this is happening, before the exhaustion becomes severe, is a personal responsibility that no framework can replace.

When the honest answer is "this is not my place"


There is a conversation the agile movement has taken too long to normalize: the one that acknowledges that, in some contexts, the most sensible answer is not to persist but to leave.

Not all organizational environments can be transformed by one person from within. Not all organizations want to change, even if they say they do. And spending years in a system that actively penalizes what one professionally values has a real cost, both in performance and in well-being.

This doesn't mean that resistance is always useless or that change from within is impossible. It means that the decision to stay or to seek an environment more aligned with one's own values is legitimate, and that making it consciously is healthier than postponing it indefinitely under the narrative that "if I hold on a little longer, something will change".

Patrick Lencioni identified the absence of accountability as one of the most destructive symptoms of dysfunctional teams. Applied at the individual level: not holding oneself accountable for whether the context in which one works allows one to grow and contribute is also a dysfunction, even though no one talks about it.

The role of the community as a support network


One dimension that technical manuals rarely address is the importance of the professional community for those who work in non-agile environments. Isolation is one of the factors that most accelerates burnout.

The agile community has a solid tradition of exchange spaces that can work as a support network for those working in difficult environments. Not as a space for complaint, although some of that also serves a function, but as a place to validate perspectives, learn from similar experiences and remember that the principles one believes in make sense beyond the immediate environment.

In this context, the Scrum Manager Agile Club offers exactly this kind of space: a community of certified professionals with whom to compare experiences, access up-to-date resources and continue professional development in a sustained way, regardless of the level of agile maturity of the organization where each person works.

A note on organizational diagnosis


Before deciding which strategy to adopt in a given environment, it is advisable to have an honest reading of where that organization really stands in terms of agile maturity. This reading is not always easy: organizations in transition mix contradictory signals, and what looks like resistance to change is sometimes simply a lack of context or shared vocabulary.

Organizational diagnostic tools such as AgiLevel make it possible to obtain a more objective snapshot of where an organization stands on two dimensions: its operational practices and its cultural values. This distinction is especially useful in hybrid environments, where an organization may have reasonably agile practices in some teams but an underlying culture that hasn't changed. Knowing that gap precisely helps prioritize where to invest energy and which expectations are realistic.


The question with which we want to close this article is not "how to survive in a non-agile organization" but something more generative: what kind of leadership is possible when the system doesn't support it?

The answer is probably different for each person and each context. What does seem clear is that it requires a combination of clarity about one's own circle of influence, honesty about the real costs of certain environments, and connection with a community that sustains and broadens perspective.

No man's land can be a very rich space for learning. It can also be a place where one stays longer than is good for them. Knowing how to tell the two apart is perhaps one of the most important competencies that agile training still doesn't teach explicitly.

We'd like to know what you're experiencing. How are you managing it?

References

  • Adkins, L. (2010). Coaching Agile Teams: A Companion for ScrumMasters, Agile Coaches, and Project Managers in Transition. Addison-Wesley Professional.
  • Covey, S. R. (1989). The 7 Habits of Highly Effective People. Free Press.
  • Denning, S. (2018). The Age of Agile: How Smart Companies Are Transforming the Way Work Gets Done. AMACOM.
  • Edmondson, A. C. (2018). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Wiley.
  • Kniberg, H., & Ivarsson, A. (2012). Scaling Agile @ Spotify with Tribes, Squads, Chapters & Guilds. Spotify / Crisp.
  • Lencioni, P. (2002). The Five Dysfunctions of a Team: A Leadership Fable. Jossey-Bass.
  • Maslach, C., & Leiter, M. P. (1997). The Truth About Burnout: How Organizations Cause Personal Stress and What to Do About It. Jossey-Bass.
  • McKinsey & Company. (2021). The impact of agility: How to shape your organization to compete. McKinsey Quarterly.
  • Schein, E. H. (2010). Organizational Culture and Leadership (4th ed.). Jossey-Bass.
  • Snowden, D. J., & Boone, M. E. (2007). "A leader's framework for decision making". Harvard Business Review, 85(11), 68–76.

🔒 Restricted Poll

Please log in to your Scrum Manager account to do this.

Log in
Share:

Comments (2)

Log in to your Scrum Manager area to comment


Jorge Sánchez López ★★★
20 May 2026 11:48

Very much in line with what you're saying.

One of the things I see most in organizations is exactly that: it's not that they don't want to be agile, it's that they're not willing to truly take on what it entails.

And that's where many teams end up in no man's land.

They apply practices, change dynamics… but the underlying system stays the same:
how decisions are made, what gets measured, and what gets rewarded.

And as long as that doesn't change, it's very hard for Agile to stop being superficial.

That's why the burnout you mention is so real.

It's not just working in a non-agile environment; it's sustaining a constant incoherence between what's said and what actually happens.

Good approach, because it brings down the level of idealism and puts the focus where it hurts: on the system, not just on people.

Automatic translation · View original

Reply Reactions
Avatar
Raul Morales Galisteo ★
20 May 2026 23:30

Agile leadership in traditional organizations is not about imposing frameworks, but about acting strategically within real constraints. As a certified Product Owner, I see three key enablers for transforming the team's experience and generating tangible value:

1.- Clarity of influence: focusing energy on what we do control (Product Backlog prioritization, the quality of our conversations, and protecting the team's focus), and avoiding burning out on structures we cannot change right away.

2.- Psychological safety as a lever: building an environment where the team can experiment, learn, and make mistakes without fear. This strengthens resilience and adaptability, even if the organization as a whole is not agile.

3.- Strategic language upward: translating agile practices into metrics that leadership values (less rework, shorter cycle times, greater responsiveness to the market). This is not manipulation; it is connecting with the indicators that underpin decisions.

Agility in "no man's land" is not a dogma; it is an exercise in conscious leadership: acting where we have impact, cultivating trust within the team, and communicating value in the language of the organization. That way, even in rigid environments, we can sow resilience and competitive differentiation.

Automatic translation · View original

Reply Reactions