A COO called me in to help refresh the organization’s strategy. Over the course of about three months, I worked with the COO and the executive leadership team to clarify the strategy, sharpen the priorities, and define six strategic pillars with supporting goals and objectives. By the end of that process, the team believed they had something solid—a strategy that was both reasonable and executable.
About six months later, the COO called me back.
He had a concern he could feel but could not yet fully name. The strategy was not being executed as well as he thought it should be. Deliverables were being missed. Project deadlines were slipping. There were signs of increased workload and mounting strain in the system. Something was off, but it was not immediately clear whether the problem was the strategy itself, a shift in the external environment, or something happening inside the organization.
So we brought the leadership team back together and took a closer look.
The strategy still held up. The six strategic pillars were still sound. The problem was not that the organization had chosen the wrong direction.
The problem was that execution had drifted.
As we worked through the actual portfolio of work underway across the organization, we began putting every active initiative on the board. By the time we were done, there were 63 distinct projects in motion.
That was the moment the lights went on.
Only about half of those 63 items were directly tied to the strategy.
The rest fell into a familiar set of categories: legacy work that had simply continued, pet projects people did not want to let go of, and new initiatives that had emerged because someone believed they were important enough to pursue. None of them were irrational. Most could be justified. In fact, nearly all of them were consistent with the mission of the organization and beneficial to some part of the client base.
That was part of the problem.
When work is obviously foolish, it is easier to stop. When work is mission-consistent, useful to someone, and defensible on its own terms, it is much harder to challenge. But strategy is not the same as mission. Mission is broad. Strategy is selective. Strategy requires choice. It requires trade-offs. It requires deciding not only what matters, but what matters most now.
This leadership team had agreement in the room, but not alignment in execution.
That distinction matters.
A team can agree on a strategy, nod in the meeting, and still remain misaligned in how it allocates time, attention, resources, and political cover afterward. That is exactly what was happening here. The strategy had been endorsed, but it was not yet governing the work.
The deeper we went, the clearer the pattern became. People were not only working on strategic priorities. They were also continuing work they believed was important, even when it was not part of the strategic plan. And when they raised those projects with the COO, the response was often some version of, “It is part of our mission, so I guess we should do it.”
That logic is understandable. It is also how execution gets diluted.
At a later prioritization meeting, one of the team members mentioned a project the CEO was sponsoring—a high-profile external initiative for which he had received some national recognition. We asked the same question we had begun asking about everything else: Where does this fit in the strategy?
The answer was: it didn’t.
I remember saying, “That means it’s a hobby.”
That was not a throwaway line. It clarified the issue.
If a project is not tied to the strategy, essential to revenue, necessary to protect expense, or required by the business in any immediate way, it may still be meaningful. But it is not strategic. And if senior leaders use organizational resources to support it anyway, they teach the system something important: the strategy is not really the strategy. It is only one set of priorities competing with everything else leaders personally care about.
Once that happens, the rest of the organization learns the lesson quickly.
This is where many senior teams get into trouble. They mistake verbal agreement for real alignment. But real alignment is not measured by what is said in the meeting. It is measured by what gets funded, protected, prioritized, and stopped afterward.
Strategy without execution is a dream. Execution without strategy is chaos. And change without activation is inertia.
What this team lacked was not intelligence or effort. It was leadership cohesion and organizational discipline. They had not built a shared system for deciding what would move, what would wait, and what needed to stop.
That became the real work.
The organization had to learn how to stop doing things that were not part of the strategy. That sounds obvious after the fact, but it was not a habit they had built. A process had to be established with the COO to review work in motion and determine whether it was truly strategic, mission-critical, or simply important to someone. No new project would move forward unless it was clearly tied to the strategy and high enough in priority to justify the investment of resources.
That required a shift in leadership behavior as much as in process.
Leaders had to stop treating every worthwhile idea as work the organization should absorb. They had to stop confusing mission-consistent activity with strategic priority. And they had to hold themselves—including the CEO—to the same discipline they expected from everyone else.
That is what real alignment looks like.
It is not simply agreement on the strategy document. It is shared discipline about what gets done, what does not, and who gets to decide.
Senior teams often say they are aligned because no one objected in the room. But if priorities multiply, pet projects survive, trade-offs remain unmade, and resources keep flowing to work outside the plan, then the team is not aligned. It is only agreeable.
And agreeable leadership teams often create the most confusing organizations of all: polite in discussion, fragmented in execution.
The test of alignment is not how the meeting felt. The test is what happened afterward.
- Did the strategy actually govern the work?
- Did leaders make the same choices publicly and privately?
- Did the organization learn what to stop?
That is the point at which alignment becomes real.
And that is also the point at which execution begins to improve.
