Jesse Jacoby
A chief operating officer at an industrial manufacturer told me his team had just come through “the hardest eighteen months in the company’s history.” A new ERP platform, a restructuring that flattened two layers of management, and a plant consolidation, all stacked on top of one another. He described it the way people describe surviving a storm. We got through it.
Then he told me what was coming next. An AI-enabled quality initiative, a new commercial operating model, and a likely acquisition. And he asked me, without a trace of irony, how to “get the organization ready to resist change less.”
That question contains the whole problem. After eighteen months of relentless disruption, his instinct was still to treat the next wave as a discrete event to be survived and resistance as the enemy to be subdued. What he had not built, despite all that hard-won experience, was any durable capacity to absorb what was coming. Each transformation had cost him roughly what the last one did. Some had cost more.
This is the quiet failure at the center of modern change leadership. We have become competent at managing resistance to specific changes and remarkably poor at building the capacity to handle change as a permanent condition. The two are not the same discipline. One is reactive, episodic, and expensive. The other is an asset that compounds. Most organizations invest almost entirely in the first, then wonder why every transformation feels like starting from zero.
Resistance Is the Symptom, Not the Enemy
The dominant model of change management treats resistance as friction to be overcome. Stakeholder maps identify the resistors. Communication plans are engineered to win them over. Adoption dashboards track how quickly the holdouts fall in line. The entire apparatus is organized around a single change, with the goal of moving the organization from current state to a defined future state with the least possible drag.
There is nothing wrong with this when the change is genuinely one and done. The trouble is that one-and-done change no longer exists. The COO’s organization wasn’t facing a transformation. It was facing a queue of them, with no end date. When you organize your whole approach around defeating resistance to the change directly in front of you, you optimize for a world that ended years ago.
And you misread resistance itself. Resistance is rarely stubbornness for its own sake. It’s information. It tells you where the change collides with how the work actually gets done, where trust has already been spent, where people have absorbed all they can hold. An organization that treats every objection as an obstacle to be cleared learns nothing from the signal. An organization that reads resistance as data gets smarter with each change. The first posture burns energy fighting the same fight repeatedly. The second converts friction into capability.
What Resilience Actually Is
Resilience has a public relations problem. The word conjures grit, toughness, the ability to endure hardship without complaint. Framed that way, it becomes a property of individuals, the resilient people who power through, and a quiet expectation that everyone else should toughen up. This is a convenient story for leaders because it shifts the burden of absorbing disruption onto employees and away from organizational design.
The more useful definition is structural. Organizational resilience is the built capacity to absorb disruption without losing function and to adapt without trauma. It is procedural, not emotional. It lives in how the organization is designed, resourced, and led, not in the constitution of the people who happen to work there.
That distinction matters because structural capacity can be deliberately built, while character cannot be mandated. A resilient organization has a few things the brittle one lacks. It carries enough operational slack to absorb shocks rather than running every function at the edge of its limits. It holds reserves of trust that let people extend leaders the benefit of the doubt when a change is hard to explain. It has sensing systems that surface problems early, while they’re still cheap to fix. It has decision rights that still function when conditions are ambiguous. And it has managers who are fluent in change rather than freshly overwhelmed by each new one. None of that is personality. All of it is design.
Why Organizations Build Resistance Management Instead
If resilience is so much more valuable, why do so few organizations invest in it? The answer is in how change gets funded and rewarded.
Every transformation arrives as a project, with its own budget, timeline, and success metrics. Capacity-building has no project. It has no go-live date, no steering committee, no line item. It is the connective tissue between initiatives, and connective tissue rarely gets funded because it never shows up as a deliverable. So organizations pour resources into the change in front of them and treat the organization’s ability to handle the next one as somebody else’s problem, later.
The incentives compound the bias. The leader who pulls off an impossible rollout through sheer force of will gets promoted. Nobody is measured on whether the organization is more capable after the change than before it. The heroics get celebrated. The depletion they leave behind is invisible on every scorecard that matters. So the next transformation begins with the same exhausted starting point, and the same heroics are required again, and the cycle hardens into a culture that mistakes survival for success.
This is how a company can accumulate years of transformation experience and grow no more capable of transforming. Experience without capacity-building is just scar tissue.
Building Adaptive Capacity as a Standing Asset
The shift from resistance management to resilience starts with treating capacity as something you build on purpose, between and beneath individual changes, rather than something you hope survives them.
A few moves matter more than the rest:
- Treat recovery as infrastructure. Organizations that change continuously need deliberate periods to absorb and stabilize, the same way athletes need recovery between efforts. Sequencing changes so people can metabolize one before the next arrives is not softness. It’s how you keep the capacity to change at all.
- Develop managers as the absorption layer. Front-line and middle managers are where change is translated into daily work or where it stalls. Investing in their change fluency, not as a one-time training but as an ongoing capability, does more for resilience than any communication plan.
- Build trust reserves before you need them. Trust is the currency that lets an organization move through a hard change without fracturing. It accumulates through consistency and honesty over time, and it can only be spent if it was banked first. Leaders who treat every interaction as a deposit have something to draw on when the difficult moment comes.
- Create sensing systems that work. Resilient organizations find out what’s breaking while it’s still small. That requires real channels for honest upward signal, and leaders who reward the messenger rather than shoot them.
None of these are exotic. What’s rare is the decision to fund and protect them when there’s no single project demanding it.
Measure Capacity, Not Just Compliance
You cannot build what you refuse to measure. Most organizations measure only adoption of the change in front of them. Did people log in, complete the training, hit the milestone. Those metrics say nothing about whether the organization is getting better at change.
Resilience has its own leading indicators, and they’re trackable. How long does it take the organization to stabilize and return to full function after a disruption? How much trust do people carry into a change, measured before it starts rather than after it fails? How confident are managers in their ability to lead their teams through whatever comes next? How quickly does bad news travel up? Track those over time and you have a read on capacity itself, the thing that actually determines whether the next transformation succeeds. Track only attendance and adoption, and you’ll keep being surprised.
The Question Worth Asking
I went back to the COO with a different version of his question. The goal isn’t to get your organization to resist change less. Resistance isn’t the variable you should be optimizing. The goal is to build an organization that can absorb more, recover faster, and adapt without each change costing what the last one did.
Resistance management gets you through the transformation in front of you. Resilience gets you through the ones you can’t see yet. In an environment where disruption has become the baseline rather than the exception, the organizations that win won’t be the ones that fought resistance most effectively. They’ll be the ones that quietly built the capacity to stop fighting it at all.
