Most strategies are not rejected. They are diluted.
Leadership agrees on a direction in October. By the time it reaches a customer the following autumn, what shipped bears a family resemblance to what was decided and no more than that. Nobody dissented. Nobody sabotaged anything. Every individual decision along the way was locally reasonable.
The planning cycle is where this happens, and it is almost never examined, because planning is treated as administration rather than as the mechanism by which strategy either survives or does not.
The four places it leaks
Translation into functional plans. Every function reads the strategy and asks what it means for them. That is the correct question and it produces four different answers, each defensible, none of which is the strategy. What was one direction becomes four adjacent directions.
Capacity reconciliation. The plans, summed, exceed capacity by some large multiple. Rather than removing initiatives, most organizations shrink all of them proportionally, because shrinking is a spreadsheet operation and removing is a conversation. Everything survives at 60% scope, which for most initiatives is below the threshold at which they do anything.
Metric ownership. Each function needs to show impact on a company-level metric, so each makes decisions that optimize for its own contribution. Product, marketing, sales and customer success all behave rationally. The system gets worse. This is the single most common failure in product-led businesses and it is structurally invisible, because every part of it looks like good management.
Re-planning. Something urgent arrives in month four. Capacity moves. Nobody re-derives what the strategy implied, because that would mean reopening October. The bet quietly loses a third of its funding and nobody records the decision.
The OKR pathology
Worth naming specifically, because it is so widespread.
If your key results are activities, “launch X”, “migrate Y”, “run Z experiments”, you have written a project plan with better formatting. Activities can be completed on time, in full, and change nothing.
Worse is when a KPI becomes the objective. “Increase trial-to-paid by 15%” sounds like an outcome and is actually a solution in disguise: it forecloses the possibility that the answer is to reduce trials, or to change who you acquire, or that trial-to-paid is the wrong measure entirely. You have handed a team a number and removed their ability to think about it.
The test I use: can a team hit every key result and leave the business unchanged? If yes, you have written activities.
What holds a strategy together
Name what you are not doing, in the same document. A strategy without an explicit not-doing list is a wish list, and every function will reasonably assume their thing survived.
Fund fewer things at full strength. Three initiatives at 100% will beat eight at 40% every time, because most initiatives have a threshold below which they produce nothing. Proportional cuts feel fair and are the most reliable way to waste a year.
Give cross-functional outcomes a single owner. If activation is a company metric and four functions each own a slice, nobody owns it. One name, with the authority to make decisions inside the other three functions’ territory, or accept that it will not move.
Make re-planning explicit. When something urgent takes capacity, write down what it took capacity from. One line in a shared document. This single practice does more to keep strategy intact than any planning framework I have used, and it costs nothing.
Review the plan against the strategy quarterly, not the plan against itself. The question is not “are we on track”. It is “is what we are doing still what we said we would do, and if not, when did that change and who decided.”
Why this is a design problem
None of this is fixed by a better strategy document. The document was probably fine.
It is fixed by treating the planning cycle as a system with known leak points, and designing against them, the same way you would design a funnel with known drop-off. Decision rights, cadence, and the explicit not-doing list are the mechanism. A strategy the organization cannot execute is not a strategy, it is a position paper.
