Blocks of different materials on a tabletop conveyor, with a blue gate allowing one block through while others remain behind.

Continuous transformation needs limits, too

Adapting is not the same as accumulating changes. Transformation requires deciding what to preserve, what to replace, and which existing commitments must be reconsidered.

Alejandro Mayorga7 min read

The idea of permanent transformation leaves one question unanswered: what must an organization be able to preserve as it changes? Continuity in a priority, a relationship of trust, or a way of making decisions rarely carries the appeal of a new initiative. Yet if everything can be reconsidered at any moment, it also becomes difficult to know what foundations are solid enough to commit to. A willingness to learn requires some continuity through which we can recognize what we are learning and why it would be worth carrying into the work ahead.

This is not an argument for an immobile organization. Some practices lose their reason for existing, and some decisions must change even when doing so is uncomfortable. But between recognizing a shift in the environment and demanding another transformation lie choices made by leadership. Someone determines its scope, preserves certain obligations, and removes others. Presenting change as a demand imposed entirely from outside leaves that part of the process unexplained and makes it easier for its contradictions to reappear as people’s difficulty adapting.

Deloitte offers one signal of this tension in its Global Human Capital Trends 2026 (opens in a new tab): only 27% of survey respondents believe their organization manages change effectively. The chapter proposes embedding learning, practice, and support in everyday work. That approach addresses a real need; the figure reflects respondents’ perceptions, not a universal failure rate, and does not establish that better support alone will suffice. Before deciding how we will help people adapt, we still need to examine whether the demands we are placing on them can coexist.

When the new does not replace the old

Consider an organization introducing cross-functional teams to bring decisions closer to the problem. In this hypothetical situation, people receive shared responsibility for a deliverable, yet individual goals, budgets, and authorizations still depend exclusively on their original departments. A specialist needs to devote time to resolving a dependency for the new team while meeting a functional target that does not recognize that contribution. The specialist’s manager may understand the value of collaboration and still be accountable for a result that requires recovering that time. Neither necessarily has the authority to change the commitments. The new structure begins operating through informal negotiations: favors, exceptions, and agreements that must be rebuilt for each delivery, because announcing the change did not resolve which priority should prevail when the two conflict.

This is an important distinction between introducing something new and replacing a way of working. In the first case, it is enough to add a practice, a meeting, or a system; in the second, someone must decide what ceases to apply. The cross-functional team needs to know which previous approvals are still necessary, and why. Its manager needs performance criteria compatible with the contribution the team is being asked to enable. A transition may require two ways of working to coexist for a time, but that coexistence needs a purpose and conditions for ending it. Otherwise, the organization is not moving through a transition: it has retained every demand and left its members to reconcile them.

A bright lobby with turnstiles; the central passage is open.

The continuity I propose protecting emerges precisely there, in the ability to sustain agreements clear enough to act upon. A team can experiment with different solutions if it knows the purpose it must protect and the discretion within which it can decide. It does not need to preserve a particular technique forever. It needs to be able to trust that the criteria against which its work will be judged will not change silently after it has made a commitment. Leadership can change the objective, but it should do so explicitly, revise the scope, and acknowledge the consequences for what was already agreed. This way of changing preserves something valuable: the relationship between the authority that establishes an expectation and the responsibility of those working to meet it.

It also makes it possible to learn from a practice before replacing it. To judge a new way of coordinating, we need to give it a chance to work under the conditions that would make it viable. If the cross-functional team retains conflicting objectives and depends on approvals no one has reconsidered, its difficulties tell us little about the merit of the design supposedly being tested. Switching models at that point may leave the problem untouched and create yet another experience of unsuccessful novelty. Maintaining the design indefinitely would solve nothing either. The task is to identify the missing conditions, decide whether they can be created, and establish what observations would justify continuing, correcting, or abandoning the proposal.

The experience of previous changes is also part of what people bring to that test. In Haunted by the Past (opens in a new tab), published in 2011, Prashant Bordia and his coauthors found associations between beliefs about a history of poorly managed change, lower trust, and less openness to change. Those beliefs also predicted employee departures over the following two years. Without turning that study into an explanation for every instance of resistance, its findings give us reason to take seriously a question that may sound unenthusiastic at another launch: how long will what we are being asked to learn last this time?

The person asking may be defending a familiar comfort. They may also be trying to decide whether it is worth investing in relationships, knowledge, and agreements they expect to see replaced soon. Telling the difference requires listening to the experiences behind that expectation and comparing them with the current proposal. Skepticism does not give anyone a veto over change, but calling it resistance does not relieve us of the obligation to answer its reasons.

Making decisions under pressure, too

There are constraints leadership cannot choose. A serious service disruption may demand an immediate change in how work is done. Urgency narrows the alternatives, but it does not make every previous commitment simultaneously achievable. Someone must decide which deliveries to renegotiate, where to reduce scope, and where to concentrate support. When these decisions remain unresolved, they end up being made under pressure by people with less information and less authority, who may later be evaluated as though they could have fulfilled everything. The need to act quickly increases the importance of making those tradeoffs visible.

I would not, therefore, set a universal maximum number of initiatives an organization can absorb. Two small changes may contradict each other, while a far-reaching transformation can bring order to work if it genuinely replaces what came before. I would examine how the demands relate to one another and which decisions lack an owner when they converge. For the team in our example, resolving one of those contradictions might contribute more than another change-support program, even if it produced less visible activity and required no new name.

This obligation extends to those of us who advise organizations on transformation. Identifying a real problem or proposing a better practice is not enough to justify an intervention: we must be able to explain how it will enter an organization already occupied with other work. Adding recommendations and leaving those who receive them to make everything compatible reproduces, in consulting, the very omission we criticize in leadership. Sometimes our most responsible contribution will be helping remove a demand that has lost its purpose, or sustain a decision that still deserves a fair chance.

The next time we ask for adaptability, we should be able to say what we intend to preserve, what we are prepared to reconsider, and what we will stop demanding. Not to shield ourselves from every discomfort, but to give the effort a direction that can be sustained. If the only answer is that people will have to learn to withstand everything, what still needs transforming is the way we lead.