A change effort can look sensible from the outside and still fail in practice for a simple reason: the people leading it keep asking everyone else to carry the extra work.

That is the quiet problem this topic exposes. Not resistance. Not poor communication. Friction.

When a leader adds another approval, another handoff, another check-in, another reporting layer, they may believe they are improving control. But from the other side of the work, the change now feels heavier, slower, and less worth the effort. People do not need a grand argument against it. They just need a Tuesday.

The real issue is not whether the change sounds right in the meeting. It is whether the organization has been designed so that the next step is easier to take than the old one.

The pattern underneath the event

Many change efforts fail because the people designing them treat adoption as if it were mainly a question of explanation. If the case is strong enough, if the message is clear enough, if the intent is good enough, people will follow.

But people do not adopt a change in the abstract. They adopt it inside calendars, queue lengths, approval paths, service levels, inboxes, and unfinished work. They adopt it while trying to protect time, reduce risk, and keep the current operation running.

That is why a leader’s own friction matters so much. Every time leadership makes the change slightly more complicated for everyone else, the organization gets a small lesson: this new thing is not here to make work easier. It is here to be carried.

Once that lesson settles in, behavior shifts. People comply on paper and work around the change in practice.

Design creates behavior

The design problem is usually ordinary, which is part of the problem. A duplicated approval here. A handoff that requires the same information in three places. A steering group that meets too often to decide too little. A workflow that asks front-line teams to adapt without removing anything from their existing load.

Those are not dramatic failures. They are design choices that quietly make certain behavior more likely.

If a change requires people to wait for sign-off, they will wait. If it requires them to chase clarity across functions, they will build side channels. If it asks them to do new work while the old process remains available, they will keep one foot in the familiar system and one foot in the new one. That is not disobedience. It is practical survival.

The leader who keeps adding steps is usually trying to reduce uncertainty. More checkpoints feel safer. More reporting feels more responsible. More control feels like leadership. But to everyone else, the message is different: before you start, absorb this extra burden.

That changes behavior quickly. People stop treating the change as something useful to join. They start treating it as something to manage.

Behavior becomes operations

Once the design has trained people to protect their time, operations change shape.

The work slows down in small, predictable ways. Teams delay decisions because they are waiting for someone else to complete a step that should never have existed. Managers spend more time coordinating than leading. Frontline staff build workarounds because the official process is too awkward for the pressure of real work. Meetings multiply because no one fully trusts the last handoff. Quality suffers because people are rushing between competing demands.

You can often see the pattern in the language people start using. “Can we do this offline?” “Do we really need that approval?” “Let’s just keep the old version for now.” “I’ll handle it another way.” Those phrases are not just resistance. They are signals that the system has become expensive to use.

The same thing happens when leaders ask others to absorb their friction. Suppose the change owner is uncertain and responds by creating more review layers. Suppose they are uncomfortable with local judgment and respond by tightening rules. Suppose they want progress but keep asking the same teams for more updates, more evidence, more patience.

The operation starts to bend around that behavior. People begin feeding the process instead of improving the work. The change becomes a destination for effort rather than a way to reduce it.

Operations become economics

Operational friction always turns into economic cost, even when nobody names it that way.

Extra approvals consume time that could have gone to customer work. Duplicate coordination creates delay, and delay carries a cost in missed deadlines, slower response times, and lower throughput. When people have to work around the formal process, the organization pays twice: once for the designed system and again for the unofficial one that appears to make the system usable.

There is also a quieter cost. Trust is expensive to rebuild. Every unnecessary layer tells people the organization does not expect them to act well without supervision. That changes the quality of commitment. People stop investing themselves in the change and start investing in how to survive it with the least exposure.

In commercial terms, friction is not neutral. It lowers productivity. It stretches cycle times. It increases error rates in handoffs. It creates hidden labor in coordination and exception handling. It makes adoption slower, which means the return on the change arrives later, if it arrives at all.

And because capacity is finite, the burden does not disappear. It moves. Often onto the very people the organization needs most: the people close to customers, close to delivery, close to actual execution.

What this means for change leaders

This is where the useful question changes. Not: how do we get people to comply? Not: how do we communicate more clearly? The better question is: what friction are we creating that other people now have to carry?

That question matters because change does not spread just because it has been approved. It spreads when it becomes easier, more useful, and more realistic to adopt than to keep doing things the old way. If your design adds burden instead of removing it, you are asking people to choose the harder path without giving them a reason to stay there.

That is also why visible behavior matters more than intention. If a leader says the change should be simple but continues to add checkpoints, the organization will believe the checkpoints. If a leader says they want ownership but keeps re-owning every decision, people will wait for permission. The behavior is the message.

In Waves of Change terms, this is where the work starts with ME and often needs to return to WE again. First, the leader has to notice how their own habits create drag. Then they have to adjust the change so it is lighter to join. Not perfect. Lighter.

That adjustment may be small. Remove one approval. Clarify one handoff. Stop asking for one report that nobody uses. Replace a broad request for “alignment” with one concrete decision that reduces confusion. These are modest moves, but they tell people something important: the change is being designed around the work, not around leadership comfort.

A practical question to ask

What burden are we asking other people to carry so this change can keep its current shape?

It is a better question than “Why aren’t they onboard?” because it shifts attention away from attitude and toward design. It also exposes the hidden trade-off most organizations avoid naming. If the change depends on someone else absorbing more steps, more uncertainty, or more coordination, then the problem is not lack of will. The problem is that the current design is borrowing against someone else’s capacity.

That question helps leaders see what the organization is actually doing, not what it says it is doing. And once that becomes visible, the next move is usually clearer than people expect: remove the friction before you ask for more commitment.

Closing reflection

Most leaders do not mean to make change heavier. They just keep adding what feels responsible from their side of the table.

But change is rarely lost in the strategy deck. It is lost in the extra step, the unclear handoff, the second job, the burden nobody admitted was there.

If you want to know whether a change is ready to move, do not start by asking whether people agree. Ask whether the design makes the next step easier for the people who have to live with it. That is where the work begins.