The Paradox
Your team complained about the old process for months. Meetings were too long. Decisions took forever. Information was siloed. Everyone agreed something needed to change.
You spent three months building a new process. You consulted the team. You incorporated their feedback. You rolled it out with a clear communication plan.
And now the same people who demanded change are pushing back against it.
This is not hypocrisy. It is one of the most predictable patterns in organizational change. Wanting change and experiencing change activate completely different parts of how people respond. Wanting change is about imagining a better future. Experiencing change is about losing the familiar present.
The Gap Between Wanting and Experiencing
When people ask for change, they are imagining the end state. The efficient meetings. The faster decisions. The free flow of information. They picture the destination without accounting for the journey.
When change arrives, they experience the journey. New systems to learn. Old habits that no longer work. Uncertainty about whether the new approach is actually better. The loss of competence that comes with any transition. It is the uncomfortable period where the old way is gone and the new way is not yet natural.
This gap between wanting and experiencing is universal. It appears in every change effort, regardless of how much input the team had in designing the change.
Why Input Does Not Prevent Resistance
Most change management advice says: involve the team in designing the change and they will own it. This is partially true and incomplete.
Involvement increases buy-in for the design. It does not prepare people for the discomfort of the transition. A team that co-designed the new process still has to live through the awkward phase where the new process feels slower, less natural, and more error-prone than the old one.
The same thing shows up in Lead the Endurance. Leaders who understand a change in their heads still struggle with it in their gut. Even the most committed change advocates resist when the change disrupts their sense of competence.
What Does Resistance Look Like When the Team Asked for the Change?
It rarely looks like a revolt. It looks like polite drift. The old spreadsheet stays open "just as a backup." Meetings run the new way for the first ten minutes and the old way after that. People say "we are still testing it" in week six. Someone who pushed hardest for the change goes quiet in the room and talks in the hallway.
None of this means the team lied when they asked for change. They meant it. They also did not know what the middle would cost them.
Take a common case. A team begs for a faster weekly decision meeting. You cut it from ninety minutes to thirty and move to written pre-reads. By week two, three people have not read the pre-reads, one person feels exposed because nobody can hide in a long meeting any more, and the strongest talker now has less airtime. All of them wanted shorter meetings. Each of them lost something real. That loss is what you are hearing as resistance.
How Do You Tell Resistance From a Real Problem With the Change?
Not every complaint is the dip. Sometimes the new process is broken. Four questions help you sort it.
First, is the complaint about the change, or about how it feels? "This form has a field we cannot fill in" is a design problem. "This feels slower" is the dip. Second, is it getting better week over week? The dip fades. A real flaw stays flat or grows. Third, who is complaining? If your newest people and your most experienced people raise the same issue, look at the design. If only the experts push back, look at identity and competence. Fourth, what do people do when you ask "what would make this easier next week?" Teams with a real flaw give you specifics. Teams in the dip give you feelings first and specifics second.
Treat the feelings as information, not as a vote against the change. Then fix the real flaws fast, so the team sees that pushback gets heard. That is how you keep the honest complaints coming.
What Shackleton Did When the Plan He Sold Collapsed
The crew of the Endurance signed on for a crossing of Antarctica. In 1915 the ice crushed the ship and the plan they volunteered for was gone. Shackleton did not argue the original plan back to life. He named the new reality, kept the daily routines going, and gave every crew member a role in the next step. People who had wanted the adventure now had to live a very different one.
That is the move for any leader whose team asked for a change and now struggles with it. Do not defend the original pitch. Name where you are, keep the rhythm steady, and hand people a clear job in what comes next. Participants in Lead the Endurance practice this under real pressure, as Senior Advisors facing the decisions Shackleton faced. And when the whole situation feels uncertain, how to lead a team through uncertainty covers the next layer.
The Competence Dip
Every change produces a competence dip. In the old system, people knew how things worked. They had shortcuts, relationships, and workarounds that made them effective. In the new system, all of that expertise is temporarily worthless.
This competence dip is the hidden driver of resistance. People do not resist the change itself. They resist the feeling of being incompetent during the transition. And this feeling is especially intense for high performers who built their identity around being good at what they do.
Leaders who understand the competence dip can name it: "The next four weeks will feel slower and more frustrating than the old way. That is normal. It does not mean the change is wrong. It means we are in the transition, and transitions are uncomfortable."
This naming does not eliminate the discomfort. It normalizes it. And normalized discomfort is manageable. Unnamed discomfort becomes resistance.
Naming it for one team is a conversation. Naming it across a whole rollout is a plan. See how leaders map resistance to change before the change goes live.
AI is the sharpest version of the competence dip. Every expert on the team becomes a beginner in the same week. See what leading an AI rollout looks like when the dip hits everyone at once.
The Baggage Factor
The Baggage Framework explains another layer of resistance to desired change. Every team member carries baggage from previous change efforts. The reorganization that was supposed to improve collaboration and instead created chaos. The new system that was rolled out and abandoned six months later. The initiative that started with enthusiasm and ended with blame.
This baggage creates an emotional filter: "Here we go again." Even when the current change is different, the emotional residue from past changes colors the response. A team member who was burned by a previous change effort will instinctively protect themselves against this one, even if they genuinely wanted it.
In Lead the Endurance, the Baggage Framework gives leaders a way to surface and address this residue. When a team member names their baggage — "The last time we changed our process, it took a year and nothing got better" — the leader can address it directly rather than watching it undermine the change invisibly.
Four Practices for the Paradox
Practice 1: Name the competence dip. Before the change launches, tell the team exactly what to expect: "You will feel less effective for two to four weeks. This is the transition, not a signal that the change is failing."
Practice 2: Celebrate messy progress. During the competence dip, celebrate the effort, not the output. "The new process felt clumsy in today's meeting and we still got to a decision. That is progress." This recognition sustains people through the uncomfortable transition.
Practice 3: Create safety for frustration. Give the team explicit permission to be frustrated without interpreting frustration as resistance. "You can hate how this feels right now and still be committed to making it work." This distinction keeps people honest about their experience without feeling disloyal.
Practice 4: Share your own struggle. Leaders who admit that the change feels hard for them too build trust and reduce isolation. "I am also still learning the new process. I defaulted to the old approach twice this week." This vulnerability is not weakness. It is leadership.
The Timeline Promise
The competence dip has a timeline. Depending on the complexity of the change, it typically lasts two to six weeks. After that, the new approach starts to feel natural and the benefits begin to materialize.
Leaders who can promise and deliver on this timeline sustain change through the dip. "Give it four weeks. If the new process is not working better than the old one by then, we will adjust." This promise gives the team a finish line for the discomfort and demonstrates confidence in the change.
The broader pattern sits in why teams resist change and what resistance really means, which covers resistance when nobody asked for the change at all. For leaders who need the skill itself, see the change leadership skill nobody teaches. And explore why your leadership offsite energy dies by Monday for why change momentum fades. See how the leader development path builds change leadership capability.