Strategy Is Not a Goal

A business analyst I worked with kept asking the same question.

"Yeah, but what's the strategy?"

Every time they got an answer, they asked it again. The room got tense. Frustration built on both sides. People started assuming the analyst didn't understand what was being said.

They understood perfectly. They just wanted to know something different.

What they actually wanted to know was: what are we trying to achieve? That's not strategy. That's a goal. They were using different words for different things, and nobody had ever stopped to untangle them — including the analyst themselves.

What the words actually mean

A goal is the outcome you are working toward. It is the destination. Revenue target, market position, product shipped, capability built.

Strategy is how you intend to make progress toward that destination given your current constraints and context. It accounts for what you have, what you're up against, and what you're choosing not to do. It is the logic of the route, not the place you're trying to reach.

They're related. You can't have a sensible strategy without a clear goal. But they are not interchangeable, and treating them as such creates real problems.

Why the confusion happens

Most people were never explicitly taught the difference. They absorbed the words through exposure — meetings, decks, annual planning processes — where "strategy" is often used loosely to mean everything from a high-level plan to a single tactic.

In practice, the word gets used as a signal of seriousness rather than a precise description of what's being discussed. Saying "our strategy is to grow enterprise revenue by 30%" sounds more substantial than "our goal is to grow enterprise revenue by 30%, and our strategy for getting there is to focus on regulated industries in three markets."

So the vocabulary drifts, and the distinction collapses.

Where it actually causes damage

In most team settings, the confusion is roughly harmless. People figure out what's meant from context. Conversations meander slightly but land somewhere useful.

In senior settings, the stakes are different.

When a leader presents to a board and says "strategy" where the board expected to hear a goal, trust quietly drops. The board leaves thinking the team doesn't understand what strategic thinking actually involves. They may not say so in the room. But they carry that impression into the next conversation, and the one after that.

On the other side, when a board asks "what's the strategy?" and the executive team hears "what's the plan?", they sometimes answer with tactics when what's needed is a clear statement of intent and logic. Both sides leave thinking they're aligned when they're not. Only one side finds out later.

This pattern — where both parties believe a shared understanding exists, but are actually operating from different interpretations — is one of the more reliable sources of executive frustration in growing organisations.

A simple test

If what you are describing is a target or outcome, it's a goal.

If what you are describing is the reasoning about how you will reach that target given your specific situation, constraints, and choices about what not to do, it's closer to strategy.

Most "strategy documents" contain both, often without labelling which is which. The discipline is in separating them — stating the goal clearly, then making the strategic logic explicit: why this approach, given this context, compared to the alternatives.

It is not a complicated distinction. But it is one that is almost never taught, and the gap it creates shows up in boardrooms all the time.