Why Your Team Knows Change Is Coming - And Still Does Not Move

Why Your Team Knows Change Is Coming - And Still Does Not Move

By Richard Allen

Two CEOs. Two entirely different industries. Same comment, made independently, within months of each other.

"We know what we need to do, and we have made it clear that they have a job to do. Why do they not just do it?"

It’s one of the most frequently expressed frustrations in organizational life. Leadership sees the problem. Leadership sends the email. And then - nothing. Or not enough. Or too slowly. The message sits unread, gets buried under the next urgent thread, and the moment passes.

While the world changes rapidly around us, some strategic and organizational principles remain constant. The dynamics of human resistance to change are among the most durable. Understanding them is not optional for leaders who want their organizations to actually move.

The River

Imagine a group of people going down a white water river in a raft. The group has done this many times and enjoyed the tradition. Today there is a note in the raft from the owner telling the group to turn into a different fork of the river part way down and to the right.

The group never did take the fork. Before the day was over, disaster struck. The owner could not figure out why the group did not pay attention. The note was perfectly clear.

What happened?

As the group started down the river, they passed the note around. Some thought they had seen similar notes from the owner in the past. Others thought - okay, as long as someone tells me when to turn.

Some looked for the fork off to the right but did not know when it would appear. They began to lose interest. Others kept looking but saw tree stumps and rocks to the right. It was going to be hard getting over there. Others had always gone on these trips just to relax and enjoy the beauty. They had paddles in their hands but did not ever think about paddling hard. In fact, if someone asked them to paddle hard to get over to the new spot, truth be known they would not know how.

Others were anticipating seeing the view later that morning - a particular spot on their standard course that was breathtaking. They had no interest in going down a new fork. They liked what they had always done.

This was springtime, and the heavy rains kept the river flowing fast. There was momentum. Frankly, it was easier to stay on this river.

After a while the note fell on the raft's floor, got soaked and tore apart. A particularly rough stretch of water splashed its remains over the side. The day was beautiful, the sun was out, the trees were blooming. Life was good and things were going well. The fork in the river was forgotten, and no one reminded the boaters to keep looking for it.

In hindsight, the owner thought it would have been useful to include in his note that a bridge had collapsed downstream, leaving rubble and obstacles. The river was impassable and dangerous. But he did not want to scare the boaters. "I know the river, I run the boats. The boaters should have known that what I wrote was important. Why did they not just do what they were supposed to do?"

What Actually Happened

In a nutshell, people resisted change. Not vindictively, and not for one particular reason. They resisted for a variety of good reasons and often did not even know they were resisting.

This is the part that most leaders miss. Resistance is rarely defiance. It’s usually a perfectly rational response to incomplete information, competing priorities, unclear expectations, or simple human momentum. The river was flowing. It was easier to stay on it.

Knowing what has to change is only the tip of the iceberg. Leaders have to understand how to help their teams make changes and have to be willing to devote the time and energy to actually leading them.

The river raft owner made a recognizable set of mistakes. He undercommunicated - one note, sent once. He assumed someone would take responsibility for the turn without being explicitly assigned. He ignored the obstacles that already existed or would be created along the way. He assumed everyone had the skills they needed for new tasks. He failed to listen to different points of view. He ignored the power of momentum. He failed to remind and monitor progress. He assumed everyone else had the same sense of urgency as he did - that everyone saw the pending crisis. He positioned the change as optional. And he believed that just because he, the manager, said something once or twice or three times, that anyone cared.

The SaaS Version of the River

The story translates almost perfectly into the world of SaaS leadership in 2026.

The bridge is out downstream. It’s called margin compression. It’s called AI cost unpredictability. It’s called a cloud bill that climbs every quarter while the customer-level economics remain invisible. The owner - the CEO, the CFO, the board - can see it coming. An email goes out. A slide deck gets presented. A quarterly review raises the issue.

And then the raft keeps going down the same river.

Some team members heard the message but are waiting for someone else to take the turn. Some looked for the fork but the path seemed too rocky and the tooling too unfamiliar. Some are focused on the breathtaking view of the product roadmap they have been building and have no interest in a detour into cost analytics. The river of existing momentum - the sprint cycles, the customer commitments, the hiring plans - is flowing fast. It is easier to stay on it.

Meanwhile the email gets buried. The urgency fades. The next rough patch of business pushes it further down the thread. And no one reminds the team to keep looking for the fork.

What Better Change Leadership Looks Like

The river raft owner's mistakes are a checklist in reverse. Better change leadership in a SaaS context means communicating repeatedly and through multiple channels - not one email, not one all-hands slide, but consistent reinforcement of the direction and the reason for it.

Name the burning platform explicitly. The owner did not want to scare the boaters. But the bridge was out. Sugarcoating the urgency of an AI cost problem does not make the problem smaller - it makes the response slower.

Assign clear ownership. Someone specific needs to be responsible for taking the turn, not the group in general.

Acknowledge the obstacles. The rocks and tree stumps to the right are real. Pretending the new path is easy when it is not destroys credibility and trust.

Build the skills the team needs. If people do not know how to paddle hard toward the new fork, that is a training and enablement problem, not a motivation problem.

Monitor and remind. The fork does not announce itself. Someone has to keep watching for it and keep the team oriented toward it.

And recognize that urgency is not contagious. The leader's sense of crisis does not automatically transfer to the team. It has to be earned through clear communication, shared data, and consistent follow-through.

The Closing Thought

Think about a recent initiative in your organization that never quite clicked. A cost reduction program that lost momentum. A new pricing model that never got implemented. A strategic shift that everyone agreed with in the room and nobody executed in the field.

We will bet that some of the behaviors from the river look familiar.

The river is always flowing. The question is whether your team knows the fork is coming, why it matters, and how to get there before the bridge runs out.

*Richard Allen is a contributing writer on strategy and organizational effectiveness for Beakpoint Insights.