The leadership offsite went well. Everyone agreed on the new direction, nodded at the right slides, and left feeling aligned. Three weeks later, the team is doing exactly what it was doing before, just with a new phrase stapled onto the old habits in the weekly status meeting. Leadership calls this resistance to change. I usually call it something else: nobody actually told anyone who is allowed to decide what, so people defaulted to the one thing that has never gotten them in trouble, which is doing what they did last quarter.
That is an authority problem. Not a strategy problem, not a motivation problem, and not proof your team secretly hates the new plan. I have sat with enough leadership teams to see this pattern repeat: the pivot gets approved, the deck gets updated, and the actual behavior of the organization does not move an inch, because the people expected to execute it were never given clear permission to make the decisions the new direction requires.
The strategy was never the problem
Most strategies that fail to execute were not bad strategies. They were reasonable plans, presented clearly, that ran headfirst into an organization where nobody had clarified who could actually commit resources, override an old process, or say no to a request from a director two levels up. Without that clarity, a new strategy is just an opinion competing against the organization's actual habits, and habits win almost every time.
What "authority" means here
I use authority in the group relations sense, not the org chart sense. Authority is the permission a person actually feels they have to act, decide, and be accountable, regardless of what their title says. A director can have formal authority on paper and functional authority of almost zero, if every real decision still quietly routes back to someone above them for approval. Pivots stall in that gap between the paper and the practice.
Where authority actually breaks down
Three patterns show up over and over. First, decision rights never got named specifically, so the new strategy lists priorities without saying who decides how to trade them off against each other. Second, the incentives never changed, so people are still measured and rewarded for the old behavior even while being told to do something new, and people are rational, they follow what gets rewarded. Third, leadership says it wants initiative and then quietly punishes the first person who takes it and gets it wrong, which teaches everyone watching exactly one lesson: wait for explicit direction before you move.
Any one of these is enough to stall a pivot. Most struggling organizations have all three running at once, which is why the fix has to be structural, not just a better memo about the new direction.
The hope and despair underneath resistance
I wrote a short piece years ago called Hope Is Only Part of the Strategy, and the core idea still holds up in every stalled pivot I have worked on since. A leader's job is more than planning and executing. It is containing the despair in a room so hope has somewhere to land. When a CEO lays out a clear, well-reasoned plan and the room goes quiet instead of asking questions, that silence is not agreement. It is often people who have not been relieved of the emotional weight of the organization's current struggle, and who are not going to raise their hand and say so out loud.
That matters for pivots specifically, because a pivot asks people to admit the old direction was wrong, and admitting that publicly, inside a hierarchy, is genuinely risky for most people's standing. If leadership does not make space for that discomfort, people manage it privately, which usually means quietly protecting themselves by not fully committing to the new direction until it proves safe. Authority and emotional containment are not separate problems. They are the same problem wearing two names.
How to diagnose an authority problem on your own team
Ask each person on the team, separately, what decisions they believe they personally have the authority to make without checking with anyone first. The answers will tell you almost everything. If people give confident, specific, and consistent answers, authority is probably not your bottleneck. If the answers are vague, inconsistent across the team, or everyone defers the same decision upward, the strategy was never the constraint. The organization's authority structure was.
A related tell: watch what happens in the room right after a decision gets made. Does anyone push back, ask a hard question, or name a real concern? Or does the room go quiet and compliant, the way it does when people have learned that disagreement costs more than it's worth? Quiet compliance in the room and quiet reversion at the desk are usually the same symptom.
What actually fixes it
Fixing an authority problem starts with naming decision rights explicitly, out loud, in writing: who decides this, who is consulted, who just needs to be informed. It continues with changing what actually gets measured and rewarded, so the new behavior is not competing against the old incentive structure. And it requires leadership tolerating the discomfort of people acting with real authority, including the discomfort of watching someone make a call leadership would have made differently, without immediately overriding it.
This is exactly the work I do in executive coaching and facilitation, and it is why I design offsites that produce decisions instead of alignment theater. A pivot that only lives in a strategy document changes nothing. A pivot that comes with named decision rights, changed incentives, and leadership willing to sit with the discomfort of real delegation is the version that actually shows up in how people work on Monday. If your team already agreed it was time to pivot, the authority work is what turns that agreement into behavior.
Frequently asked questions
Why does my team agree to a new strategy and then keep doing the old thing?
Because agreement in a meeting is not the same as authority to act differently once the meeting ends. If nobody clarified who owns which decisions, and what specifically should stop, people default back to the behavior their role has always rewarded, regardless of what got said in the room.
Is resistance to change always about authority?
Not always, but it is more often than leaders assume. Teams frequently get diagnosed as resistant to change when the real issue is that no one has clarified who can actually make which calls, so people default to old behavior because it is the only behavior with clear authority behind it.
What is the difference between a strategy problem and an authority problem?
A strategy problem means the plan itself is wrong. An authority problem means the plan is fine, but no one has the clarity, permission, or accountability to actually change how they work. Most stalled pivots are the second kind, misdiagnosed as the first.
How do I know if my team has an authority problem?
Ask each person on the team what decisions they believe they personally have the authority to make without checking with someone else first. If the answers are vague, inconsistent across the team, or defer everything upward, you have an authority problem hiding under what looks like a strategy problem.
Can better communication fix an authority problem?
Rarely on its own. Communication can restate the strategy more clearly, but it cannot grant someone permission to act, and it cannot change what the organization actually rewards. Authority problems need structural fixes, decision rights named out loud, not another all-hands meeting.
What role does leadership play in an authority breakdown?
Leadership either names the new decision rights explicitly or leaves people to guess, and guessing defaults to old habits every time. Leaders also have to tolerate the discomfort of people making calls without checking in constantly, which is often harder for the leader than for the team.
If your team keeps nodding along to the pivot and then quietly returning to the old playbook, stop rewriting the strategy deck. Go find out who actually believes they have permission to act differently, and fix that instead.