Most growth problems aren't marketing problems.
They're positioning problems.
Most organisations complete their annual strategic planning and strategy cycle and emerge with a document. It has sections, priorities, themes, and carefully worded statements of intent. It is, in almost every case, useless as a guide to action.
The problem is not effort. Planning cycles consume significant executive time, involve genuine deliberation, and often produce polished outputs. The problem is structural: most planning processes are designed, whether intentionally or not, to build consensus around a narrative rather than force the binding, resource-allocating decisions that constitute real strategy. The result is a plan that describes an organisation’s ambitions without committing it to anything irreversible.
This piece is a diagnostic for executive teams who suspect their planning process is producing the latter. It examines what most planning cycles actually generate, why they default to themes and priorities instead of choices and trade-offs, and what a rigorous process must produce to have any commercial effect. Working through the sections that follow, you will find a clear framework for evaluating your own process and a set of questions to carry into your next planning cycle.
The Planning Process That Produced Nothing
Three months of planning. An offsite with a skilled facilitator. Stakeholder interviews, a SWOT analysis, and a forty-page document that arrived in everyone’s inbox with a cover note about alignment and ambition.
Twelve months later, the organisation competes in exactly the same way it did before.
This is not an unusual story. It is the default outcome of most strategic planning processes, and the reason is structural, not circumstantial.
The output of strategic planning is not a document. It is a small number of binding, resource-allocating decisions: choices that commit capital, concentrate effort and foreclose alternatives. When a planning process produces themes, priorities and multi-year roadmaps with no resource commitments attached, it has not produced strategy. It has produced a well-formatted narrative.
The distinction matters commercially. Completing a planning process is an administrative achievement. Doing strategic work is a commercial one. The former fills a governance calendar. The latter changes how an organisation competes, who it serves and why customers choose it over credible alternatives. Conflating the two is precisely why most planning advisory fails before it begins.
One question exposes the difference immediately.
When your last planning cycle ended, what had you decided that you could not easily reverse?
If the answer requires hesitation, the process produced a document. The rest of this piece explains why that happens, what it costs, and what rigorous strategic positioning demands instead.
What Most Planning Processes Actually Produce
Look closely at what most planning cycles actually deliver. A set of strategic themes. A list of priorities ranked one to five. A refreshed values statement. A multi-year roadmap populated with initiatives, each one floating free of any committed budget or redeployed headcount.
None of it constitutes a decision.
There is a second problem that rarely gets named. Many organisations enter the planning process having already determined the outcome. The offsite becomes a ratification exercise dressed as an inquiry. Facilitators surface views, leadership nods, and the document that emerges confirms what the executive team privately agreed three months earlier. The process lends legitimacy; it does not produce discovery.
Part of what enables this is definitional. There is no shared standard for what a strategic plan must contain or what it must do. Without that standard, comprehensiveness becomes a proxy for rigour. A longer document, more workstreams, more sub-priorities: these signal effort, not quality.
The commercial consequence is direct. A plan that protects consensus by avoiding trade-offs leaves the organisation’s competitive position exactly where it was. Clarity requires exclusion. Without exclusion, there is no strategy.
The Difference Between a Decision and a Priority
A deeper semantic problem runs through most planning conversations. The words “priority” and “decision” are used interchangeably in most executive conversations. They are not the same thing.
A priority is a preference. It ranks options in order of importance without eliminating any of them. A decision forecloses alternatives and commits resources to a specific course of action. That distinction is not semantic. It is the difference between a plan that shapes behaviour and one that simply documents intention.
Organisations operating on priorities can pursue everything simultaneously, at reduced intensity across the board. Organisations that have made genuine decisions cannot. They have concentrated effort, accepted visible trade-offs, and created internal winners and losers. That tension is not a sign that the planning process broke down. It is evidence that it worked.
The practical test is straightforward. If your strategic plan does not specify what you will stop funding, stop doing, or stop pursuing, it has not produced a decision. Resource allocation failures are well-documented: most management teams chase too many conflicting goals and achieve few of them. The plan that names only what you will do has avoided the harder question entirely.
This is precisely where planning strategic thinking at the executive level becomes uncomfortable. Real choices eliminate options that specific stakeholders favour. Consensus-seeking processes are structurally resistant to producing them, which is why the hardest work in strategy happens before execution, at the point where choices must actually be made.
A decision earns the word “strategic” only when it constrains future behaviour and carries a genuine cost to reverse. If every element of a plan can be quietly deprioritised without consequence, the plan has no binding force.
Why Planning Produces Themes Instead of Choices
Knowing the distinction between a decision and a priority does not, on its own, explain why so few planning processes produce decisions. The explanation sits in the structure of the process itself.
Most planning processes are designed to build consensus. Workshops surface all perspectives. Facilitators synthesise divergent views. The output reflects what every senior stakeholder can accept, a document that everyone can find themselves in, produced by a process optimised for alignment over clarity. That optimisation has a cost, and it shows up directly in the mechanics.
Organisations invest significant effort in how to run the planning process: timelines, templates, offsite design, engagement surveys. Far less attention goes to defining what the process must actually produce. Process quality becomes a proxy for output quality, and a well-run planning cycle feels like rigorous strategic work even when it ends with a narrative rather than a choice.
The implementation gap follows directly. A recognised failure point in strategic planning is the gap between strategic vision and implementation: the PMI-sponsored Economist Intelligence Unit report found that 61 percent of respondents acknowledged their firms struggle to bridge that gap. But the root cause is rarely examined honestly. Organisations that cannot translate plans into action frequently assume the problem is execution discipline. Often, the problem is earlier: the plan contained no decision to implement.
The environmental cost of this pattern is no longer trivial. Competitive and operational conditions are shifting faster than planning cycles can track. An organisation still producing thematic documents on annual rhythms is not just inefficient. It is systematically slower to commit, slower to concentrate resources and slower to respond than competitors whose planning produces binding choices.
What a Rigorous Planning Process Must Answer
The problem is not the planning process. It is what the process is trying to produce.
Strategic planning and strategy only converge when the process is structured around answering specific competitive questions. When it is structured around producing a comprehensive document, the output will always be a narrative, however well-crafted.
There are three questions any serious planning output must answer.
Where will we compete? Not in which markets do we currently operate, but in which specific competitive arenas will we concentrate effort and defend position.
Who will we serve? Not a broad addressable market, but a defined customer profile whose needs this organisation is structurally better placed to meet than any credible alternative.
Why should customers choose us over those alternatives? Not a values statement or a service promise, but a competitive rationale grounded in how the organisation actually differs.
These are not marketing questions. They are structural decisions. The answers determine where capital is deployed, which capabilities require investment and how the organisation must be designed to deliver on its chosen position. The gap between strategic intent and commercial performance is rarely a planning mechanics problem; it is a strategic understanding problem, one that no amount of process refinement can compensate for when the foundational competitive questions go unanswered.
A plan that does not specify competitive rationale has produced aspiration. Understanding what competitive advantage actually requires makes clear why aspiration, however confidently stated, is not a substitute for a defined and defensible position.
The output standard follows directly. A strategic plan should be evaluable by whether it answers these three questions with decisions, not whether it addresses them with themes. Themes can coexist. Decisions cannot.
A Diagnostic for Executive Teams
Knowing what a plan should answer is one thing. Having a mechanism to evaluate whether yours actually does is another.
Apply these four questions to your most recent planning output, ideally before it is approved rather than after it stalls.
Does the plan specify what the organisation has decided not to do, not to fund or not to pursue?
If the answer is no, the plan has not made a choice. It has described intent. Every option remains open, which means no option has been genuinely selected. A plan without explicit exclusions is a list of preferences dressed as decisions.
Does the plan contain commitments that would be commercially costly to reverse?
If every element can be quietly deprioritised when competing pressures emerge, the plan has no binding force. The gap between formulation and implementation is rarely a communication failure; it is a commitment failure, a plan without binding force is simply too easy to abandon.
Does the plan answer why a specific customer should choose this organisation over a specific alternative?
If that answer is absent, the plan has not addressed competitive position. It is worth noting here that the absence of a clear, defensible competitive position is frequently mistaken for a leadership problem, when it is a strategic one. A plan that cannot articulate the customer’s rationale for choosing you has produced aspiration, not strategy.
Does the plan require any part of the organisation to give something up?
Genuine strategy always creates internal losers. A team that loses budget, a market that gets exited, a product line that gets discontinued. A plan with no internal losers has avoided the hardest decisions entirely.
This is not a retrospective audit. Run it in the board meeting, before sign-off. The questions take minutes. The answers reveal everything.
What Binding Decisions Look Like in Practice
The diagnostic questions above test what your plan contains. The examples below show what it should look like when it does.
The contrast is cleaner than most executive teams expect.
“We will prioritise customer experience” is a theme. It accommodates every function, threatens no one and changes nothing. “We will exit the SME segment by the end of the financial year and concentrate all account management resource on enterprise clients with revenue above £500,000” is a decision. It tells the sales team who to stop calling, tells finance to reallocate headcount budget and tells the board exactly what the organisation has chosen to sacrifice.
The same pattern holds across any strategic domain. “We will invest in product innovation” is a theme. “We will cease development on the legacy product line and redirect the full engineering team to the enterprise platform” is a decision. One is comfortable. The other produces a meeting.
The friction that second kind of decision creates is not a problem to manage; it is the signal that a genuine decision has been made. Binding decisions are recognisable precisely because they create immediate organisational tension. A specific function must change behaviour, relinquish resource or accept a new constraint. If no one is uncomfortable, the plan has produced a theme.
Scale-ups and mid-market organisations are particularly exposed to this failure. Rapid growth creates the appearance of momentum, and momentum creates the illusion that deliberate competitive choices are unnecessary. Why decide what to stop when everything seems to be working? The answer is that without strategic decisions that build competitive advantage, growth scales the organisation’s reach without concentrating its position. The result is size without differentiation.
The Question to Take Into Your Next Planning Cycle
The discipline matters. So does the conclusion it demands.
Strategic planning is only strategic if it ends with decisions: binding, resource-allocating choices that constrain future behaviour and sharpen competitive position. Everything else is documentation.
Carry one question into your next planning cycle. Not “what does this document say?” but “what have we decided that we cannot easily walk back?”
That question changes the room. It exposes whether the process produced genuine choices or a well-formatted consensus. It forces the conversation that most planning processes are quietly designed to avoid.
Organisations willing to ask it honestly will find something counterintuitive: their planning cycles get shorter, not longer. Harder, not smoother. And significantly more commercially effective, because the output has binding force rather than aspirational weight.
That brevity is not a stylistic choice; it is a signal that real choices were made and alternatives were genuinely closed off.
This is also where strategic management failures most commonly begin: not in execution, but in the planning stage, when competitive position is left undefined and decisions are substituted with priorities no one is accountable for.
For executive teams who recognise that distinction and want to close it, that is precisely the work Anna Elliot’s advisory practice is built around.
Conclusion
Most planning processes produce documentation. Rigorous ones produce decisions.
The distinction matters more than most executive teams realise. Real strategic planning closes off alternatives, creates accountability, and constrains future behaviour in ways that sharpen competitive position. Themes and priorities, however well-formatted, do none of that.
If your last planning cycle produced a document everyone agreed with, that is worth examining. Genuine choices create friction. They should.
