The problem is usually not that they rejected the idea. It is that the change asked them to do two jobs at once. One job is the work they were already carrying. The other is the new layer of process, reporting, checking, or coordination. When the week gets busy, the old path wins because it is still the cheaper way to move.

The pattern underneath the event

The deeper pattern is simple and common: organizations often introduce change as an add-on instead of a replacement. They ask people to adopt the new workflow, but they do not remove the old controls, the old reporting, the old sign-offs, or the old habits that made the original process feel necessary. The result is not a clean transition. It is a stacking of work.

That stack is easy to miss from the center. A leadership team may see a sensible redesign and assume the business has moved. On the ground, people see something different: one more step before the real step, one more system to update, one more meeting to explain the meeting. The change may be approved, communicated, even agreed to. It still has not been made livable.

Design creates behavior

This is a design problem before it is a behavior problem. When a new process is layered on top of the old one, the system quietly teaches people what matters. It tells them that the new route is optional, because the old route still exists. It tells them that compliance matters more than simplification, because nothing is being removed. It tells them that the organization is willing to ask for extra effort, but not willing to make room for it.

People respond accordingly. They try the new process when it is watched, when the issue is fresh, or when there is time to be careful. Then pressure returns. A deadline appears. A customer waits. A manager asks for the familiar report. The old way becomes attractive again because it is faster, safer, and already absorbed into the rhythm of the week. This is not laziness. It is capacity management. People protect their remaining attention.

Behavior becomes operations

Once that pattern settles into day-to-day work, operations start to carry the cost. Teams duplicate steps. They enter the same information in two places. They keep parallel workflows alive because nobody has had the authority, patience, or appetite to turn one of them off. Managers reconcile between systems instead of improving the work. Frontline teams spend time explaining why the new process was followed here but not there, or why the old exception still exists.

This is where change becomes fragile. Parallel processes create confusion about ownership. People are never sure which path is current, which approval actually counts, or which version of the truth should be used in a meeting. The more effort it takes to keep the two systems aligned, the more likely the organization is to let drift take over. A process that needs constant reminding is already expensive. A process that needs constant reconciling is worse.

The visible sign is often small: more comments, more returns, more “just checking,” more side messages, more manual cleanup. The work itself has not become more valuable. It has simply become more expensive to move through the organization.

Operations become economics

The economics follow quickly. When the old way is never removed, the organization pays twice. It pays for the new process on paper and then pays again to keep the old one alive in practice. That second cost often hides inside ordinary labor: extra handling, duplicated checks, slower throughput, and more time spent coordinating what should already be clear.

Those hidden costs matter because they consume the same capacity the organization needs for real work. A team that spends more time reconciling process than completing work has less room for serving customers, solving problems, or improving quality. The return on the change shrinks. What looked like a control improvement becomes an overhead increase. What looked like a cleaner process becomes a quieter form of drag.

There is also a strategic cost. When people learn that every new process arrives without anything being removed, they stop believing the next one will be different. They do not say this loudly. They simply keep a copy of the old way close by, just in case. That habit makes the next change harder to adopt, because the system has taught them that “new” usually means “additional.”

What this means for change leaders

This is where the practical lesson from Waves of Change becomes useful without needing a formal model discussion. Change does not spread because it has been approved. It spreads when it becomes easier to live with than the current way. If adoption requires extra effort, the change is competing with the very capacity it needs.

Before pushing communication harder, leaders should ask a more grounded question: what did this change replace? If the answer is “not much,” then the organization is probably asking people to carry both systems at once. That is why early enthusiasm fades. Agreement is not adoption. A process that adds work but removes nothing will always be vulnerable when priorities tighten.

The better design question is not how to persuade people to do one more thing. It is how to remove enough old work that the new behavior has a chance to become the easier path. Sustainable change usually depends on subtraction: fewer steps, fewer handoffs, fewer parallel checks, fewer reasons to retreat to the familiar route.

A practical question to ask

One question changes the conversation quickly because it forces the design problem into the open:

What work did this change remove, and if nothing was removed, who is carrying the extra load?

That question matters because it moves the discussion away from intention and into reality. It reveals whether the organization has designed for adoption or simply added another layer. It also gives leaders a useful test for every new initiative: if people have to do the old work and the new work at the same time, then the system has not changed. It has only multiplied effort.

Closing reflection

Most people will carry a surprising amount for a while. They will adapt, improvise, and try to make a sensible change work inside an overloaded week. But they will not do that forever. If the new process quietly asks for a second job, the old one will remain the default whenever pressure returns.

Change becomes durable when the organization makes room for it. Not just in the message, and not just in the meeting, but in the actual work.