I spent months building a project plan. Weeks of stakeholder alignment, timeline negotiations, vendor coordination, contract reviews. The kind of work that does not make for exciting stories but makes the difference between something launching and something stalling. We were getting close to signature, and then the dreaded "Let's pause that."
No new data had surfaced. No market shift had happened. Just a change of direction, delivered casually, as if months of work was a whiteboard sketch someone decided to erase between meetings.
If you have been in leadership long enough, you have heard some version of that story. Let's pause. Let's pivot. Let's table this and revisit next quarter. And you know the feeling that comes with it. Not anger, exactly. Something closer to exhaustion. Because you were not just building a plan. You were building momentum. And momentum, once killed, does not restart with a memo.
The first time I went to Trader Joe’s, I didn’t bring a list. Big mistake. I wandered aisle by aisle, circling back to sections in case I had missed something. An hour later I had a cart full of what I didn't need, double the budget, and none of what I'd actually come in for.
That is what it looks like when a leader operates without a clear strategy. Every shiny idea becomes the next priority. Every new input triggers a course correction. The team starts moving in one direction, gains traction, and then gets pulled somewhere else before the first effort has time to prove itself. It feels productive because things are happening. But nothing is finishing. And the cost of that pattern is staggering.
PMI's research consistently identifies the same top reasons for project failure: change in organization's priorities, change in project objectives, and unclear requirements. Not bad teams, lack of talent, or insufficient budgets, but shifting direction.
Here is what leaders underestimate. When you change direction, you are not just stopping one thing and starting another. You are spending down trust.
Every time a team invests energy into a direction, they are making a bet on their leader's conviction. They are saying, with their effort, "I believe this is worth doing because you said it was." When that direction gets scrapped halfway through, the team does not just lose the work. They lose a piece of confidence in the next direction. And the direction after that. Eventually, you get a team that does not fully commit to anything because they have learned, through experience, that commitment gets wasted.
Peter Drucker captured this tension perfectly: there is nothing so useless as doing efficiently that which should not be done at all. The flip side is equally true. There is nothing so demoralizing as doing something important that gets abandoned before it has a chance to work.
This is not an argument against course corrections. Strategy has to be responsive and agile. Markets shift. Customer needs evolve. New information should change decisions. That is leadership, not weakness.
But there is a sharp line between a strategic pivot and a reactive flail. A pivot comes with reasoning. It comes with an honest assessment of what changed, why the current direction no longer serves the goal, and what the new direction will cost the team in energy and trust. A pivot is communicated, not just announced.
A flail comes from a lack of clarity. The leader was never fully committed to the direction in the first place. And when the change mandate comes in, the reasoning stays vague. So the team is left to absorb the cost without understanding the cause.
When the plan is unclear, anything goes. That is the root of the problem. A leader without a defined strategic lane will chase every lane that looks promising. And every lane change costs the team fuel, time, and trust.
The fix is simpler than most leaders think, but it requires discipline.
First, commit publicly. If a direction is worth pursuing, say it clearly and tie your credibility to it. Not with a casual mention in a team meeting. With specificity. "This is what we are building toward. This is why. This is the timeline. And I will not change it unless the conditions that justified it change." That statement alone shifts the dynamic. It tells the team this is not a test. It is a plan.
Second, build in a review window, not a react window. Set a point, maybe 60 days out, where you evaluate the direction with real data. If the evidence says adjust, then shift. But between those windows, hold the line. Small tweaks are fine. Wholesale direction changes are not, unless something genuinely urgent emerges. The discipline of waiting for evidence protects the team from the whiplash of impulse.
Third, when you do change direction, name the cost. Tell the team: "I know this shift means the last eight weeks of work changes. That is a real cost. Here is why I believe the new direction justifies it." Leaders who acknowledge what they are asking their teams to absorb earn something back in return. Not all the trust. But enough to move forward together.