Read enough corporate strategy documents and a pattern emerges. Ambitious statements about becoming the leading provider. Targets for growth and margin. Values. A list of priorities, usually five or six, all of them important.
None of that is strategy. It's a description of desired outcomes, which is a different thing, and the difference matters because one of them tells people what to do and the other doesn't.
The test
A useful diagnostic: does the document say what you will not do?
Strategy is a set of choices about where to compete and how, which necessarily means choosing not to compete elsewhere and not to do things that would otherwise be attractive.
A document containing no such choices isn't constraining anything, which means it can't guide a decision. If every option is consistent with the strategy, the strategy provides no information.
The second test: could a competitor have written the same document? If the strategy is "deliver outstanding value to customers through innovation and operational excellence", then yes, and it's therefore not a strategy but a description of business in general.
What goes wrong
Several recognisable failure modes.
Goals presented as strategy. "Grow revenue by thirty percent" is an objective. The strategy is how, and specifically what you'll do that others aren't and what you'll give up to do it.
Everything is a priority. A list of eight strategic priorities means there aren't any. Prioritisation is ordering under scarcity; a list where nothing is deprioritised hasn't performed the function.
The initiative list. A collection of projects, each individually sensible, with no explanation of why these and not others, or how they relate. This is a plan, not a strategy, and plans without strategies tend to produce activity without direction.
Avoiding the diagnosis. The hardest part of strategy is stating clearly what the problem is, and that frequently involves saying something uncomfortable about the organisation. Documents that skip the diagnosis and go straight to aspiration are avoiding the difficult conversation, which is usually the only conversation worth having.
What a real strategy contains
The framework I find most useful has three parts, and the first is the one people skip.
A diagnosis. What is actually going on. Not a list of everything, but an identification of the critical factor — the thing that, if addressed, makes other things easier, and if unaddressed makes everything harder.
Good diagnoses are frequently unwelcome. "Our product is no longer differentiated and we're competing on price in a market where we're not the low-cost operator." That's a sentence with consequences.
A guiding approach. The overall method for dealing with the diagnosis. Not a goal, an approach. "Focus on the segment where our service model is genuinely valuable and exit the commodity end."
Coherent actions. A set of steps that support each other. The test of coherence is whether the actions reinforce one another or merely coexist. Actions that would each be sensible independently, with no relationship between them, indicate the strategy isn't doing any work.
The political reason it doesn't happen
Worth being direct about why organisations produce vague documents when the alternative is clearly better.
Real strategy allocates resources, which means somebody gets less. It says some parts of the business matter more than others. It closes options that people have built careers around.
A vague document offends nobody. It can be signed off by everyone because it constrains no one. That's not incompetence, it's a rational response to an environment where making enemies is costly and where the consequences of a bad strategy arrive later than the consequences of a difficult meeting.
Which means the barrier to good strategy is usually organisational courage rather than analytical capability.
A practical approach
Some things that help when you're actually trying to do this.
Write the diagnosis first and circulate it separately, before proposing anything. If people disagree about what the problem is, there's no point discussing solutions, and that disagreement is usually invisible until you force it out.
Force a ranking. Not a list of priorities but an ordered list, with resources attached. The conversation about what's third rather than second is where the actual strategy gets made.
Write the stop-doing list explicitly. Every strategy implies things you'll cease. Naming them makes the strategy real and makes it possible to resource the things you've chosen.
And test it against a decision. Take a real choice the organisation faces and ask whether the strategy tells you what to do. If it doesn't, it isn't finished — whatever the document says.
Communicating it afterwards
A well-made strategy fails routinely at the next stage, which is getting anybody to act on it. The document circulates, people read it once, and behaviour continues unchanged.
The failure is usually specificity. A strategy expressed at the level of the whole organisation does not tell an individual what to do differently on Monday, and without that translation it remains an artefact.
What works is cascading it into concrete implications by team — what this means we start doing, stop doing, and decide differently. Written by the people who will do it rather than handed down, because the act of translation is where understanding forms.
And repetition well past the point of tedium. Leaders consistently underestimate how many times something must be said before it is absorbed, largely because they have been thinking about it for months and everyone else heard it once.