What is a strategy, really?

"It's a strategic question." "We have a digital strategy." "This is strategically important to us." The word strategy has become one of the most-used — and least precise — words in business. Often it means nothing more specific than "important" or "something we should do," which makes it a convenient way to avoid the analysis and hard prioritization a real strategy actually requires.

Richard Rumelt, professor at UCLA and one of the most influential strategy researchers of modern times, devoted an entire book to sorting out the difference. His definition is uncomfortably simple: good strategy is coherent action, backed by an argument. Not a vision. Not ambition. Not a list of goals. An argument for why these specific actions, in this specific combination, actually solve the problem.

Four signs it isn't a strategy

Rumelt became known for systematically identifying "bad strategy" — documents, presentations, and plans that are called strategy but lack the underlying logic. Four recurring patterns:

• Fluff: high-flown language and complicated terminology that makes a banal idea sound sophisticated. If a statement sounds impressive but turns out empty once translated into plain language, it's fluff.
• Failure to face the challenge: a strategy that never actually names what's standing in the way. If no one can answer the question "what, specifically, makes this hard?" there's no strategy to speak of — just a wish for a better outcome.
• Mistaking goals for strategy: "We will grow revenue by 20 percent" is a goal, not a strategy. A strategy explains how you get there, given the actual obstacles in the way.
• Bad objectives: objectives that are either too vague to guide any decisions at all, or that are simply a long wish list of everything the organization would like, with no prioritization between them.

Recognize any of that from a strategy document at work? You're not alone. Rumelt's point is that this pattern is the rule rather than the exception — which is exactly why the word "strategic" nowadays more often signals that a question won't be properly analyzed than that it will.

The kernel: diagnosis, guiding policy, coherent action

Rumelt's most-cited contribution is what he calls the kernel of strategy — a simple logical structure shared by all good strategy, regardless of industry or scale:

1. Diagnosis — what, specifically, is standing in the way? A good diagnosis simplifies a complex reality by identifying which parts of the situation are actually critical, and which are noise. Rumelt's colleague John Mamer summarized it as there really being only one question in every diagnosis: "What's going on here, exactly?"

2. Guiding policy — an overall approach for dealing with what the diagnosis identified. Rumelt compares it to highway guardrails: it directs and constrains action without fully defining every step.

3. Coherent action — concrete, coordinated measures, resource commitments, and priorities that together actually carry out the guiding policy. The key word is coherent: a list of good initiatives that don't reinforce each other is still not a strategy — just a to-do list.

A classic example Rumelt himself uses is Nvidia's 1995 turnaround. The diagnosis: "we are losing the performance race against competitors." The guiding policy: "release a faster chip, three times more often than the industry norm." The coherent actions: three overlapping development teams, investment in simulation to avoid production delays, and reclaiming driver development from board makers. Three simple sentences — but each part builds on and reinforces the other two.

Why this matters beyond word choice

It's easy to dismiss this as semantics — who cares whether we call it strategy or a plan? But the consequence of conflating them is real. An organization that believes it has a strategy, when it actually just has a wish for a better outcome, will make decisions as if the problem were already solved. Resources get spread thin instead of concentrated. Priority conflicts get postponed instead of resolved. And when the results don't materialize, it's hard to understand why — because there was never an argument to test in the first place, just a hope.

The test is simple to apply to the next document that calls itself a strategy: can you point to the diagnosis? Is there a guiding policy that actually rules out certain courses of action, not just permits everything? And do the actions reinforce each other, or is it just a list of things that would be nice to do?

If the answer to any of those is no, it isn't a strategy. It's a wish list with a strategic label on the cover.

The next step is connecting the kernel to something every organization already has: a vision of where it's headed. The question is how a vision actually translates into strategy — not one, but several parallel ones, one for each competitive advantage the vision is meant to deliver.

We'll take that on in the next part.

Want to go deeper: Richard Rumelt's Good Strategy / Bad Strategy is the foundational text this article builds on. Rumelt's follow-up The Crux: How Leaders Become Strategists goes deeper into how to actually identify the right diagnosis in practice. A.G. Lafley and Roger Martin's Playing to Win: How Strategy Really Works is a practical complement — a framework (including the question "where will we play, and how will we win there") often discussed alongside Rumelt's kernel.