The most common explanation for strategy failure is bad execution. "We had the right idea," goes the post-mortem, "but we just couldn't execute." This is almost always wrong — or at least backwards. Most strategy does not fail in execution. It fails before execution, because it was never strategy to begin with.

That sounds harsh. Let me be more precise.

The strategy-execution conflation

Strategy and execution are treated as sequential phases: first you develop strategy, then you execute it. Strategy is thinking. Execution is doing. The thinkers hand off to the doers and blame the doers when things go wrong.

This model is broken. Strategy and execution are not sequential — they're deeply entangled. The decisions made during "execution" are strategy. The trade-offs engineers and product managers navigate daily are strategy. The reason a company can't execute is usually that its strategy doesn't give the people doing the work enough to navigate by.

This isn't a failure of execution. It's a failure of strategy design.

What actually passes for strategy in most companies

Most corporate strategy is one of three things, none of which is strategy:

Aspiration. "We want to be the market leader." "We want to be the category winner." These are destinations without routes. They tell you nothing about what to do Monday morning that you wouldn't have done anyway.

Goal. "Grow ARR 3x in 18 months." This is a target, not a strategy. It doesn't tell you which markets to enter, which customers to prioritize, which capabilities to build, which competitors to ignore. It gives you something to measure but nothing to decide.

Activity list. "We need better customer relationships, a stronger product, and operational excellence." Companies write these lists and call them strategic pillars. But "build a better product" isn't a strategy — it's what you do when you don't have one. Every company wants those things.

Real strategy is a theory about how you're going to win. It makes trade-offs explicit. It tells you what you're not doing. It gives the person on the ground enough context to make a decision without escalation.

The test that most strategies fail

Larry Fink at BlackRock asks a simple question of every company he invests in: "What are the two or three things you're going to do really well, and how are you going to make money doing them?"

Most leadership teams can answer this question in vague terms. Very few can answer it with specificity that would allow an employee to make a decision without calling their manager.

The strategies that fail in execution are the ones that can't survive this test. They're written for the board, not for the operator. They communicate direction but not decisions. They announce intent without encoding constraints.

Why the handoff breaks down

When a strategy is handed off from leadership to teams, it loses information at every step. The strategy gets summarized into bullet points. The bullet points get summarized into OKRs. The OKRs get translated into quarterly goals. By the time the person writing the code or talking to the customer needs to make a decision, the signal-to-noise ratio has collapsed.

This isn't a communication problem you can solve with a better all-hands. It's a structural problem: the strategy was never designed to survive translation down the org chart. It was designed to sound good in a presentation.

The companies that execute well do not rely on better communication rituals alone. They write strategies for a specific audience: the person who has to make a call without escalation.