We talk a lot about adaptive leadership. We talk about leaders who can navigate uncertainty, listen differently, make difficult decisions and adjust when the environment shifts around them. All of that matters. But there is a question we ask far less often: what happens when an adaptive leader is inside an organization that cannot adapt?
A leader can see that something has changed. They can listen to employees, study the data and make the right call about what should happen next, and still find themselves leading an organization that cannot move. That is because adaptability is not only a leadership capability. It is an operational one. An organization’s ability to adapt depends on something more fundamental: its ability to keep learning, make decisions from what it learns and change how work happens because of those decisions.
We already teach leaders to learn before they act
Think about how we prepare someone for a new leadership role. A central idea in Michael Watkins’ The First 90 Days is that transitions require deliberate learning. The new leader has to understand the situation they are entering and work out what that particular environment needs, instead of assuming one approach works everywhere.
So they come in and listen. They ask questions, learn the people and the history, and find out how decisions actually get made and where the formal process differs from what people really do. Only then do they start deciding what should change.
That makes perfect sense. But it raises a question I keep coming back to: why do we treat learning as something a leader does when they arrive, instead of something the organization is designed to do all the time? The leader’s first 90 days eventually end. The organization’s learning should not.
An organization should be able to learn itself
Every organization is constantly producing information about how well its system works. The employee who builds a workaround because the official process takes too long is information. So is the complaint that keeps coming back, the program that needs twice the staffing it was projected to need, and the manager who has quietly become the approval point for seventeen unrelated decisions. And the employee who says, “We’ve been telling leadership this for two years,” is definitely information.
The question is not whether your organization produces this information. It is whether you have built the capacity to learn from it, because collecting is not learning. A dashboard, a survey, a staff meeting and an assessment can all collect information. Learning happens when that information changes your understanding of the system. Organizational learning happens when that new understanding eventually changes what the organization does.
This is where adaptive leadership becomes adaptive operations
Ronald Heifetz’s work on adaptive leadership separates technical problems, which existing expertise can largely solve, from adaptive challenges, which require learning, experimentation and new capacities because the existing answer is not enough.
That distinction has real consequences for operations. If a challenge requires learning, the organization needs a way to learn. If it requires experimentation, it needs room to experiment. And if something fundamental has to change, someone still has to be able to make that decision and move resources behind it. David Teece’s research on dynamic capabilities offers the organizational counterpart. It points to the processes, structures and decision rules underneath an organization’s ability to sense change, act on what matters and reconfigure its resources. Without that architecture, adaptive leadership eventually hits a wall: the leader is ready to move, and the organization is not.
So what does an adaptive operation actually look like?
It is not chaos, constantly shifting priorities or a strategic plan thrown out every six months. And it is definitely not asking employees to “be flexible” every time the organization fails to plan.
An adaptive operation has a repeatable way to move through that loop. Frontline information has a way to travel, and people have space to make sense of what they are seeing instead of simply reporting numbers. Everyone knows who can make which decisions, and those decisions turn into real changes in resources, roles, processes or priorities. Then the organization asks whether it actually worked, and starts again.
Decision-making is the hinge
Imagine your organization spots a problem tomorrow, and follow the information. Who notices it first, and where does it go? Who decides whether it is an isolated issue or a sign of something larger? Who has the authority to respond, what do they need to know, and how long does that decision take?
Then keep going. Does a process change, a role shift or money move? How will you know whether the decision worked, and if it did not, how quickly will you find out?
Those questions tell me far more about an organization’s adaptability than whether its strategic plan uses the word “agile.” Your organization cannot adapt faster than it can learn and decide, and it cannot sustain adaptation faster than it can execute.
Trust is part of your learning infrastructure
At NJW Operations, we use the NJW Operational House™ because organizations are systems, and operational problems rarely stay inside one department. Strategy, ownership, workflows, visibility, decisions, systems and capacity all affect one another. Trust runs through every room, because it decides whether the information moving through the house is accurate in the first place. An organization can only learn from information it is willing to receive. If raising problems makes employees look difficult, problems stop getting raised. If bad numbers are met with punishment instead of inquiry, leadership starts receiving increasingly polished versions of reality. If departments guard information from one another, decisions get made from fragments.
We tend to treat trust as something soft that belongs to culture. I don’t think that is accurate. Trust shapes what your organization is able to know. When people can say “this isn’t working,” “I made a mistake” or “our clients are asking for something different,” leadership has information it can use. When they can’t, the organization’s picture of itself becomes distorted, and you cannot adapt accurately to a reality you cannot accurately see.
The same question, in every sector
The principle travels even when the environment changes. In a public library system, a branch may start seeing shifts in patron demand or community needs. The question is whether those observations can travel across branches and eventually shape staffing, programming or budgets. At a port or public authority, the signals might be workforce capacity, maintenance demands, capital projects or regulatory change. Different environment, same questions: can information move, can the organization interpret it, can someone decide, and can the operation change because of it?
In a nonprofit, a funding stream changes, community demand shifts, or a program outgrows the infrastructure built to support it while staff quietly absorb the extra work. The organization can ask everyone to work harder, or it can learn: is the staffing model still right, where has the workload moved, and what should stop? Schools, health and human-services organizations and multi-site businesses learn through different signals, but underneath all of them is the same question: what have we learned, and what will we do differently because we learned it?
Growth changes how an organization learns
With six employees, learning can happen informally. Someone walks into your office and says, “This isn’t working.” You talk about it, you change it, and you are done. At sixty employees, that same information may have to move through supervisors, department heads, leadership meetings and budget cycles. At six hundred, you may need formal systems built specifically to collect, interpret and act on it.
That is why an organization can feel incredibly responsive when it is small and painfully slow a few years later. It did not become less intelligent. It outgrew the mechanism it was using to learn. Growth creates distance between the person experiencing a problem and the person authorized to solve it, and your operational infrastructure has to account for that distance.
Don’t confuse efficiency with adaptability
Good operations create consistency. Processes, SOPs, role clarity, automation and standardization all matter, and you don’t want employees reinventing the organization every Tuesday. But every system that says “this is how we do it” also needs a way to ask whether it still makes sense. An adaptive organization can hold both: this works, let’s make it repeatable, and this no longer works, let’s understand why.
Adaptability also should not become another word for growth. An organization can learn something important and decide not to add a location, launch a program, chase a new funding stream or scale. Sometimes what it learns is that it lacks the capacity, or that the opportunity would pull it away from what it does exceptionally well. That is an adaptive decision too. The purpose of organizational learning is not perpetual expansion. It is better choices about when to move and when not to.
Learning before intervention
When I enter an organization, I am not only looking for what isn’t working. I want to understand why the system exists the way it does: what problem a process was designed to solve, where informal knowledge lives, and where employees have already adapted even though the formal system hasn’t.
The goal is never to walk in, point at everything that looks unusual and replace it with someone else’s idea of best practice. First, understand the system. Then decide what should be preserved, strengthened, connected, redesigned or retired. The longer-term goal is to leave the organization more capable of doing that work for itself.
The real measure of organizational maturity
We spend a lot of time asking whether we are performing, whether we hit the target and whether we grew. Those questions matter. I would add one more: are we getting better at understanding why our organization performs the way it does?
A mature organization recognizes patterns sooner and tells symptoms apart from system problems more accurately. It keeps what it learns instead of rediscovering the same lesson every few years, and it gets steadily better at turning learning into action. When that learning connects to decision-making, capacity, trust and strategy, it becomes organizational adaptability.
An adaptive organization is not one that predicts every disruption. It is one designed to notice, learn, decide and adjust. The point of operations is not to build an organization that never has to change. It is to build one that can understand when change is necessary, decide what to do about it and actually do it.