There comes a moment, familiar to anyone who has led under real pressure, when the plan stops working—when it falls apart. Not because the plan was necessarily flawed. Not because the people were necessarily wrong or incompetent. But because the situation is doing something the plan never anticipated, and every instinct pulls in opposite directions at once.
I have stood in that moment more times than I can count, in dark compounds with men I trusted completely, and in situations that had just become something no one had prepared for. The temptation when I was young—and I felt it every time—was to reach for control. To decide faster. To mobilize harder. To be the thing the chaos was waiting for.
It took me years, and eventually a second career in complex systems science, to understand why that instinct, though completely human, was also precisely wrong.
Adaptive leadership deserves genuine respect. In a field dominated by frameworks that would not survive contact with a real organization—let alone a crisis—it achieved something important. It differentiated between problems that expertise can solve and those that require learning and adaptation. It advised leaders to stop seeking technical solutions to adaptive challenges. It also introduced the idea that real change is always uncomfortable and that discomfort is not a sign that something is wrong. These are meaningful contributions, and the leaders who absorbed them lead better for it.
But adaptive leadership carries a flaw deep in its structure—not in its values or intentions, but in its grammar. And grammar, it turns out, shapes everything.
Read its core definition carefully: “Leadership is the process of mobilizing others to tackle their tough complex challenges and thrive in the face of rapid change.”
The subject is the leader, and everyone else is the object. The process flows in one direction, from the person doing the mobilizing outward to those being mobilized. It is a sentence based on a premise so deeply rooted in our ancient architecture that we barely notice it anymore: that the leader is the engine, and the organization is the vehicle the engine drives.
This is not a complexity model. It is a classical mechanics model wearing complexity’s vocabulary.
Here is what the biology actually shows.
Four hundred million years ago, multicellular life began solving the same problem every organization faces today: how to get thousands—and eventually trillions—of specialized agents, each with their own local information, to work together coherently and adaptively at scale. How do you build a system that can survive disruption, learn from stress, and grow stronger without anyone at the top knowing in advance what the solution will look like?
The solution was not, as the US Military still believes, to find a better mobilizer. It was to develop a more resilient interaction architecture—a structured set of relationships, roles, simple rules, and response mechanisms, or feedback loops, so well-tuned that adaptive behavior emerges from the interactions themselves, without anyone commanding it.
Your immune system doesn’t wait for a commander to give orders. When a pathogen enters your bloodstream, the network responds automatically. Local agents sense the threat, signal their neighbors, amplify what’s helpful, and suppress what’s not. Some cells act as leaders in the moment and step back once the moment passes. Others carry the memory of the encounter forward, so the next response is faster and more precise. No one mobilized any of this. The system’s structure produces it naturally.
Your body has been running this operating system for as long as our species has existed. You are reading this because it works.
Now look at your organization.
Somewhere in it right now, there is someone who sees what is coming before leadership does. They are close enough to the core of the working network but distant enough from the formal structure that the signal hasn’t reached the top yet. They’ve been trying to get someone to listen. The message keeps arriving at each management layer slightly altered—a little more palatable, a little less alarming, a little less truthful—until by the time it reaches the decision-makers, it is almost unrecognizable.
This is not a communication failure. It is a structural one. And no amount of mobilization from the top corrects it.
Or consider this: you roll out an initiative. You communicate it clearly. You resource it adequately. You hold people accountable. Six months later, the metrics look good. A year later, you realize that the culture never changed at all — people only learned to report the right numbers, while the underlying pattern remained exactly as it was before. The initiative was absorbed. The attractor—the routine cognitive-emotional-behavioral state—held. The system interpreted your intervention as theater, and theater is what it produced. In the US Military, it rhymes with Vietnam, Afghanistan, and Iraq.
Adaptive leadership’s response to this, broadly, is to mobilize harder, challenge more courageously, and push the adaptive work back onto the people. In a leader with real skill and genuine care, this can move things incrementally. But it cannot alter the attractor—the gravitational well—because the attractor is not the product of insufficient courage. Instead, it stems from the system’s structure—its specific configuration of relationships, roles, rules or norms, and feedback mechanisms—that channels behavior into familiar grooves regardless of who is pushing against it.
You cannot mobilize your way out of an attractor. You have to reshape the terrain that produced it. And you can’t do that alone.
This is where the upgrade lives.
If leadership isn’t mobilization, then what is it? The clearest answer I’ve found—and it is an answer I arrived at through two careers that seemed, for a long time, to have nothing to do with each other—is this: leadership is signal modulation within a living system.
Every formal leader sits at a high-traffic node in a network. Their behaviors—not just their words—spread through that network faster and further than those of almost any other agent in the system. MIT researcher Sandy Pentland, a data scientist, spent years measuring this. The manner in which people communicate—their behavioral signals—predict team performance better than the content of their speech, their intelligence, or their technical skills combined. How the leader shows up matters more than what they say.
What this means in practice is both humbling and liberating. The leader’s primary role is not to mobilize the organization. Instead, it is to achieve coherence within themselves—alignment between what they think, what they feel, and what they do. Because a leader who advocates calm while broadcasting anxiety does not produce calm. The system reads the anxiety and organizes around it. A leader who declares “We value dissent” but tenses up when the first dissenter speaks has just conveyed to the entire network what is actually valued, and no subsequent all-hands meeting can undo that signal.
Think of a tuning fork. When struck, it doesn’t command other strings to vibrate. Instead, it emits a steady tone, and anything tuned to that same frequency begins to resonate—not through coercion, but through coherence. That is the mechanism. Not mobilization but resonance.
But the leader’s coherence is only one dimension of the work, and it is the most visible, which makes it the most dangerous one to stop at.
Beneath the leader’s signal lies a structural terrain—the interaction space—and it is this terrain, not just the signal itself, that determines what the system is capable of producing or becoming. The interaction space is the real network of people, relationships, roles, rules, and feedback mechanisms through which every signal the leader sends must travel. You can have a coherent, well-meaning leader broadcasting excellent signals into a network whose topology ensures those signals die at the first cluster boundary, become distorted at each intermediate node, or arrive at the periphery—where true adaptive intelligence lives—as noise.
When a healthy immune system functions properly, it’s not because it has a better general or commander. It’s because the system’s architecture ensures the correct signals reach the right agents at the right time. The structure of the network is its strategy.
This is the question adaptive leadership does not ask: What is the actual structure of the network through which my leadership—my signals—must operate? Where do my signals amplify? Where do they die? Who are the trusted bridges—the people who span different clusters and carry credibility on both sides—and what signals are they actually carrying? Because whatever those individuals are circulating through the network right now is the real leadership signal, regardless of what core values are posted on the intranet.
There is one more dimension, and it may be the most consequential.
Adaptive leadership’s highest goal—thriving in rapid change and growing stronger under stress—is exactly right. It’s a warrior’s stance—it’s anti-fragility, and it’s what living systems do at their best. The problem isn’t the destination; it’s the vehicle. Mobilization is a leader-driven push toward a property that no leader can produce alone. Anti-fragility is not achieved by the leader’s effort; it emerges from the system’s own interaction architecture—the feedback loops, the distributed sensing, and the structural capacity to absorb perturbation and reorganize. A leader who mobilizes others toward anti-fragility is, without realizing it, centralizing the very process that anti-fragility requires to be distributed.
Complex systems don’t just face their environments; they co-evolve with them. The truly adaptive organization isn’t the one led by the most daring leader battling against the headwind of rapid change. Instead, it’s the one whose internal structure has developed enough adaptive capacity—enough feedback speed and accuracy, enough variation in perspectives, enough psychological safety for honest signal transmission, enough modularity to absorb local failures without causing a global cascade. Such a system learns from every perturbation it encounters and emerges, over time, more capable than it was before.
This is resilience in its deepest sense. Not just bouncing back, but evolving through. A system that recovers to its previous state has survived—it’s robust. A system that reorganizes itself through disruption into a more capable configuration has adapted—it’s regenerative. The key difference isn’t the leader’s ability to mobilize but the quality of the system’s interaction architecture.
I spent twenty-five years in an organization that understood this on an operational level before science could explain it. At my former command, enlisted operators subjected themselves to 360-degree feedback from their teammates—a practice unique in the US Military. And it’s even better now. Your teammates determine how high you rise, not your chain of command. Not your performance reviews. The people working alongside you in the most demanding conditions on earth decide whether you’ve earned the right to lead again in those conditions. The feedback is fast, accurate, honest, and consequential. It’s exactly the kind of feedback loop that keeps a complex adaptive system learning instead of drifting.
In my day, we didn’t call it complexity science. We called it staying alive.
If you are an adaptive leader, you are doing work that matters.
You have already made the most important paradigm shift that most leaders never make: you stopped looking for technical fixes to problems that require learning. That is not a small thing. Do not let anyone tell you otherwise.
But there is a next step, and it’s available to you.
The next step is to move from mobilizing the system to understanding it—its actual structure, its real feedback mechanisms, its current attractor states, and its processing capacity. To ask not just “How do I challenge the status quo” but “What produced this status quo, what keeps it in place, and what would need to change in the structural terrain for a different pattern to emerge?” To recognize that you are not the engine. You’re a gardener—and what gardeners know, that engineers often overlook, is that you can’t command the seed to sprout. You can only tend the soil, regulate what reaches it, remove what poisons it—ideology, bias, and toxic behaviors—and trust the biology.
Nature has been running this operating system for four hundred million years. It produces immune systems, ecosystems, neural networks, coral reefs, and, at its best, human teams capable of doing things no individual could have planned or predicted.
You don’t have to build it from scratch. You just have to stop getting in its way.
Dave Cooper is a retired Command Master Chief of Naval Special Warfare Development Group and a complex systems scientist. He is the founder of Verge LLC and the creator of the Complexity-Informed Leadership curriculum.