The Strategy Is Fine. The Operating System Isn't.
A few months ago I wrote about why strategy doesn't turn into progress. The short version: it's usually not an effort problem, it's alignment and execution.
I want to go one layer deeper.
When leadership teams are dealing with results that aren't where they should be, the instinct is almost always the same. Revisit the strategy. Rework the plan. Maybe the priorities were wrong.
Sometimes they are.
But often the strategy is fine. The market opportunity is real, the priorities make sense, and the leadership team actually agrees on where they're headed. Progress is still slower than it should be.
That's not a strategy problem. That's an operating system problem.
Strategy doesn't execute itself
A strategy is a set of choices about where you're going and what matters most. An operating system is the way an organization turns those choices into action. It is the combination of rhythms, decisions, behaviors, and mechanisms that determines how work actually gets done. It is the combination of rhythms, decisions, behaviors, and mechanisms that determines how work actually gets done, how priorities move across functions, how leaders spend their time, and how problems get surfaced before they become fires.
A strategy can be excellent and still fail inside an operating system that works against it.
Here's how it usually plays out. A company sets three clear priorities for the year. The team is aligned. The plan is communicated. Then the year starts, and a customer issue appears, a key employee leaves, an urgent request lands from another department, a project runs behind. None of it is unreasonable on its own. But without a disciplined way to manage competing demands, the strategy slowly gets crowded out by everything else. Nothing dramatic happens. The team just starts doing more and making less progress on what actually mattered.
The clues show up before anyone calls it a strategy problem
The clues usually look like this:
The same decisions keep coming back to the leadership team, weeks after you thought they were settled.
Three agreed priorities have quietly become nine, once every function adds its own.
Leaders are the escalation point for everything, including problems that should be solved closer to the work.
Meetings have become status updates, hearing what happened instead of deciding what happens next.
Your best people are building workarounds because the process, ownership, or priorities aren't clear.
Initiatives lose momentum without ever being formally stopped. They just get less attention every week until everyone quietly notices.
None of that means the strategy is wrong. It usually means there's no reliable way to execute it.
The operating system reveals what you actually value
You can say growth is the priority. But if your leadership team's time is mostly spent on operational fires, the organization experiences something different. You can say customer experience matters, but if customer issues routinely get pushed behind internal priorities, your people learn what really matters. You can say you want innovation, but if every decision needs three layers of approval, people learn to avoid risk.
That's strategy becoming behavior. The real strategy of an organization isn't just what's in the deck. It's what gets discussed, funded, measured, and protected when competing demands show up. That's why rewriting the strategy document rarely fixes the problem. Sometimes the organization needs to change how it works, not what it's decided.
Before you touch the strategy, ask this instead
Are our meetings driving decisions and focus, or are they just reporting mechanisms?
Do our priorities actually show up in where we spend time and money?
Does every major priority have an owner with real authority to move it?
Do we have a regular rhythm for checking progress and adjusting?
Can problems get solved where they occur, or do they always escalate?
What are we rewarding, on purpose or not?
What's still running simply because nobody's decided to stop it?
These aren't about adding more process. They're about removing the friction between what you've decided and what actually happens Monday morning.
Don't just add more
The temptation when execution stalls is to bolt on more meetings, more dashboards, more reporting, more accountability mechanisms. That usually makes it worse. A good operating system makes execution lighter, not heavier. You need enough structure to maintain focus, surface problems, and adjust course, not a bureaucracy built around the strategy.
The question isn't "what else should we add?" It's "what's getting in the way of executing what we've already decided matters?"
The bottom line
If your organization is struggling to make progress, don't assume the strategy needs to change before you've looked at how it's operating. Look at the meetings, the decisions, the priorities, the handoffs, where leaders spend their time, what keeps getting escalated, and what your best people are working around.
The strategy might not be broken. You might just need a better way to turn strategic choices into consistent action.
It's not only "Is our strategy right?" It's also "Are we organized to execute it?"
If that question is hitting close to home, let's talk about it. We can look at what's really slowing things down.