Most strategies don't fail because they're wrong. They fail because nobody ever translates them into the decisions that would make them real.
The deck gets signed off, the all-hands happens, the new direction goes up on the intranet, and then on Monday morning every team goes back to doing more or less exactly what they were doing before. They heard the strategy fine. Their KPIs, budgets, and approval chains still point at the old one, so the old one wins.
This is the gap I've spent twenty years watching open up between what a company says its strategy is and what its people actually do all day. It isn't a communication gap, even though it almost always gets treated as one. It's a translation gap, and it has structural causes nobody likes to talk about.
Strategy is a system, not a slide deck
The first thing to get out of the way: a strategy deck is not a strategy. It's an artefact of a strategy. Sometimes it's the artefact of a strategy that exists. More often it's the artefact of a strategy that was almost made but never quite finished.
A real strategy has three parts, and Richard Rumelt named them better than anyone: a clear-eyed diagnosis of the situation you're actually in, a guiding policy for how you're going to deal with it, and a coherent set of actions that follow from the policy. Most "strategies" I see have only the third part, and even that is usually a wish list rather than a coherent set. The diagnosis is missing. The guiding policy is implied but never stated. What's left is a list of goals (grow X by Y, improve Z by W) dressed up as direction.
Goals are not a strategy. Goals are what you want. Strategy is how you're going to get there when reality doesn't cooperate, and what you're willing to give up to make it happen.
Roger Martin says the same thing from a different angle. Strategy, in his framing, is a cascade of choices: where to play, how to win, what capabilities you need, what management systems will support them. The whole cascade has to hold together. Skip any of those questions and you don't have a strategy, you have an aspiration. And you can tell whether a strategy has been made by looking at what the organisation has explicitly chosen not to do. If the answer is "nothing, we're doing all of it," there isn't a strategy yet. There's just a bigger to-do list.
Michael Porter pushes this even further. The essence of strategy, in his view, is choosing what not to do. Choosing which customers you're not going to serve well so you can serve the right ones brilliantly. That trade-off is the part most leadership teams refuse to make. It feels like leaving money on the table. It feels like risk. So they spread the budget thinly across everything, which Porter famously called "peanut butter spreading," and then wonder why the organisation feels busy but directionless.
Rumelt, Martin and Porter agree on something the average strategy deck quietly avoids. Strategy is hard because it requires sacrifice. The plans, the KPIs, the workshops, and the long hours create the illusion of strategy. But if nothing has been chosen against, no real strategy has been made.
Why strategy decks don't run companies
Here's the part that gets almost no airtime in strategy books. Even when the diagnosis is sharp, the choices are real, and the trade-offs are honest, the strategy still won't execute itself. Because a strategy deck is just a document. The thing that runs a company is the operating model: decision rights, budget structure, information flows, the coordination mechanisms between teams. And in most organisations, none of that gets touched when the strategy changes.
I've watched this happen so many times it stopped being surprising. A company declares "customer-centric" as its new direction. The CEO communicates it. The strategy team builds the deck. Twelve months later, customer experience is still measured the same way, owned by the same people, funded out of the same siloed budgets, and constrained by the same approval chains that made the old way slow. Nothing structural changed. So nothing operational changed. So nothing actually changed, except the words on the website.
This is the gap I keep coming back to. Strategy is supposed to flow from the boardroom into Monday morning decisions. In most organisations, it doesn't, and the response is always the same: more communication, town halls, OKR rollouts and alignment workshops. The implicit theory is that people aren't doing the strategy because they don't understand it well enough. If we just explain it one more time, with one more deck, they'll get it.
But the people on the ground usually understand the strategy fine. They just can't act on it, because the structure they work inside still rewards the old behaviour. Their KPIs measure the old thing. Their budgets fund the old thing. Their decision rights point at the old thing. You can't communicate your way out of a structural problem.
That's why strategy execution is its own discipline. Not strategy formulation. That's the part everyone focuses on. Execution is what happens after the deck is signed, and it's the part almost nobody owns. Nobody's job title is "make sure the strategy actually changes how we operate." So it doesn't.
The translation gap
When I trace why a strategy isn't landing, the failure is almost never in the strategy itself. It's in the translation layer between the strategy and the rest of the business. Strategy says "be more customer-centric." The translation layer is supposed to answer: what does that mean for sales next Monday? For onboarding? For the support team's prioritisation? For how product decides what to build first? For how operations measures success? For how the leadership team reviews progress?
In most organisations, that translation layer doesn't exist as anyone's responsibility. The strategy team writes the deck and hands it off. The functions are expected to "interpret" what it means for them. Each function interprets it through the lens of what they were already doing, because that's the only frame they have. The result is six different versions of customer-centric, none of which connect, all of which feel busy, none of which add up to the strategy on the slide.
Strategic clarity at the top, structural confusion everywhere else. That's the pattern.
The fix isn't a better deck. It's a translation discipline. Someone has to sit down and answer, function by function and decision by decision, what specifically changes. Not vaguely. Concretely. Which approval gets removed. Which KPI gets replaced. Which budget line moves. Which team takes over an outcome that used to be split across three. Until those concrete shifts happen, the strategy hasn't reached the operating model yet, and the operating model is what actually runs the company.
A 5-minute test you can run this week
You don't need a consulting engagement to find out whether your strategy has actually landed. Three questions will get you most of the way there.
One. Can you point to a specific structural decision made in the last six months that exists because of the strategy? Not a communication decision. A structural one. A change in who decides what. A change in how budget flows. A change in who owns a cross-functional outcome. If you can't find one, the strategy has stayed in deck-land.
Two. When something is "everyone's responsibility," who actually moves it forward? Customer experience is the classic example. Everyone agrees it matters. Often nobody has the authority to change the handovers between departments that shape it. Shared responsibility, in practice, almost always means nobody moves.
Three. Does your budget structure fund the work that happens between functions, or only inside them? Most budgets fund silos. Sales has a budget. Product has a budget. Operations has a budget. The handover from sales to onboarding, the feedback loop from support to product, the translation from strategy to what operations actually does on Monday: none of those have a line. So none of those get fixed.
If those questions are uncomfortable to answer, that's the diagnosis. The strategy isn't broken. The translation into structure never happened.
Where this connects to the rest of the work
Strategy execution doesn't sit alone. It bumps into two other disciplines that decide whether the strategy survives contact with reality.
The first is operating model design. Once you know what the strategy demands, somebody has to redesign how the organisation actually runs to deliver it. This means new decision rights, new ownership of cross-functional outcomes, and new budget structures that fund value streams instead of just functions. This is the work most strategies skip, and it's the reason they quietly die. I've written about that in detail in the Operating Model Design series. If your strategy keeps running on old rails, that's where to start.
The second is concept validation. Big strategic bets (a new product line, a new customer segment, a new business model) are bets, not proofs. The honest response to a strategy that depends on a major bet is to validate it before committing. Cheap, fast, structured validation in weeks, not years. That's the Concept Validation series. The more ambitious your strategy, the more it needs validation built into it from the start.
Strategy without operating model change is a deck. Strategy without validation is a guess. The pillar you're reading now is about the first move: making sure the strategy itself is real enough to be worth executing in the first place.