The question every CEO eventually asks
“We spent months developing our strategy. Why isn’t it changing the way the organization actually operates?”
Every CEO knows the feeling.
The leadership team invests an enormous amount of time developing the strategic plan. Markets are analyzed, opportunities are debated, priorities are established, and difficult choices are made. By the time the planning process is complete, everyone around the table feels a sense of excitement. The organization has a clear direction, and the future looks promising.
Then Monday morning arrives.
People return to their desks, meetings resume, customers still need attention, and the urgency of day-to-day operations begins to crowd out the excitement that everyone felt only a few days earlier.
A few months later the CEO begins asking a perfectly reasonable question.
“What happened?”
The strategy hasn’t failed. The organization simply hasn’t changed the way it works.
Over the years I’ve come to believe that strategy and strategy execution are two very different disciplines. Developing a strategy is largely an intellectual exercise. Executing that strategy is an organizational exercise. Success depends less on the quality of the document and much more on whether the organization is capable of translating that document into thousands of good decisions every day.
A Blueprint Doesn’t Build the Building
Imagine you’ve hired an architect to design your dream home.
After months of discussion, the plans are complete. Every room has been carefully designed. The structure is sound, the layout makes sense, and everyone agrees it will be a beautiful home.
Now imagine handing those drawings to the construction crew without ever discussing who is responsible for what, how the different trades will coordinate their work, how decisions will be made when unexpected situations arise, or how progress will be monitored.
No one would expect the project to succeed.
The drawings are excellent. What’s missing is the system that turns the drawings into a finished building.
Organizations often approach strategy in much the same way.
The strategic plan may be excellent, but unless the organization has a disciplined way of translating that strategy into everyday work, very little actually changes.
The strategy becomes a document. It never becomes the way the organization operates.
Strategy Is Executed One Decision at a Time
One of the biggest shifts I’ve seen in successful organizations is that they stop thinking of strategy as something that lives in a planning document.
Instead, they begin thinking of strategy as something that should influence every important decision made throughout the organization.
That sounds obvious, but it raises a much more practical question.
How does that happen?
How does a strategic objective discussed in the boardroom influence the decisions made by a supervisor six months later? How does it shape the priorities of a frontline employee serving a customer? How does it influence the daily choices people make when the CEO isn’t in the room?
Those questions fascinated me for years because I rarely found organizations with a clear answer.
That’s one of the reasons I developed the Value-Added Plan™.
Building the Bridge Between Strategy and Execution
One of the limitations of many strategic planning processes is that they stop once the strategy has been approved.
From my perspective, that’s only the beginning.
The strategy established by the CEO and executive team should become the umbrella for the planning carried out by each executive. Each executive then develops a value-added plan that explains the unique value their function must create to support the organization’s strategy.
That executive’s plan becomes the umbrella for the directors reporting to them.
Each director develops a plan that explains the value their team exists to create in support of the executive’s objectives.
Those plans then become the umbrella for managers.
Managers, in turn, develop plans that help every member of their team understand how their own work contributes to the larger objectives of the organization.
In this way, strategy doesn’t simply cascade down the organization as a series of objectives.
It cascades as a series of conversations. At every level, managers ask the same fundamental question:
“What value does my team exist to create for the level above us?”
That question changes everything because it shifts the discussion away from activities and toward contribution. People begin to understand not only what they’re expected to do, but why their work matters.
Planning Creates Context
One of the ideas I’ve emphasized throughout this series is that managers spend surprisingly little time delegating work.
Most work is performed because people understand their role. That understanding doesn’t happen by accident.
Managers have to create it.
A Value-Added Plan™ becomes one of the most effective ways to do exactly that.
The planning discussion itself creates context. It gives managers the opportunity to explain priorities, discuss trade-offs, clarify expectations, and help people understand how they should make decisions when circumstances change.
In other words, the plan isn’t simply a planning document. It’s a management conversation.
As managers revisit those plans throughout the year, they continue reinforcing that context. Team members gain a deeper understanding of how their daily decisions contribute to the broader strategy, and managers have a practical framework for coaching, adjusting priorities, and providing feedback.
The plan becomes a living discussion rather than a document that sits on a shelf.
The CEO’s Real Responsibility
One of the biggest misconceptions about strategy is that the CEO’s work is largely complete once the strategic plan has been approved.
In reality, that’s where the CEO’s most important work begins. The CEO isn’t responsible for personally executing the strategy, although undoubtedly there is some value-added work that they can do. The CEO is accountable for ensuring the organization is capable of executing it.
That means building an organization where every level understands the value it exists to create, where managers are continually creating context for their teams, and where thousands of daily decisions naturally support the same strategic direction.
When that happens, execution becomes much more than project management.
It becomes part of the way the organization thinks.
A Better Question
The next time you find yourself wondering why your strategy isn’t producing the results you expected, resist the temptation to ask whether the strategy itself was good enough.
Instead, ask a different question.
“Have we given every manager the tools and the context they need to translate our strategy into better decisions every day?”
In my experience, the answer to that question usually tells you far more about execution than the strategic plan itself.
Boardroom Thought
Learn More
Many organizations are good at developing strategy. Far fewer have a practical process for translating that strategy into consistent action throughout the organization.
In When Strategy Doesn’t Deliver, I introduce the Value-Added Plan™ framework and explain how strategy can cascade through every level of the organization, creating context, alignment, and accountability along the way.
If you’re looking for a practical approach that helps managers turn strategic intent into everyday decisions, I think you’ll find the framework both straightforward and immediately applicable.
When Strategy Doesn’t Deliver
