About four years into running a significant talent development function, I sat through a strategy session where we developed what we called our three-year strategy. By the end of it, we had a document: a vision statement, four strategic pillars, each with two or three supporting goals, and a set of success metrics. It was well-structured. The presentation looked professional. Everyone felt good about it. And it was not a strategy.
What we had produced was a set of aspirations: things we wanted to achieve, framed as strategic priorities. "Build a world-class leadership pipeline." "Become the most trusted internal partner to the business." "Develop capability at scale." These were things we wanted, stated in a form that felt strategic because they were written at a high level of abstraction and organized into a structured document. They were not strategy because they contained no answer to the one question that separates strategy from aspiration: given the constraints we face and the competitive dynamics we're operating in, what specific choices will we make about where to focus and where not to focus, and why will those choices produce an outcome we couldn't achieve by simply trying to be good at everything?
The distinction between goals and strategy is among the most consequential that leadership practitioners need to understand, and it's one of the most consistently blurred. Organizations spend enormous amounts of time on "strategic planning" processes that produce goal documents. They then wonder why, despite the energy invested in alignment and planning, the organization doesn't behave differently than it would have without the strategy. The answer is typically that there was no strategy — there were goals, and goals, without the strategic logic that determines how to achieve them, are wishes with better formatting.
The precise distinction
A goal describes where you want to be. Strategy describes how you will get there given the specific constraints and opportunities you face — and crucially, what you will not do in order to make genuine progress on the thing you've decided matters most.
This negative element is what most strategy documents omit entirely and what makes strategy genuinely difficult to produce. Goals feel good to articulate: they describe a positive future state everyone can endorse. Strategy feels uncomfortable: it requires making specific choices about where not to invest, which opportunities to decline, which constituencies to disappoint. A genuine strategy for the talent development function I ran would have said something like: we will invest our limited capacity in leadership capability at the director and VP level rather than distributing broadly across the organization, because that's where the evidence shows the greatest return for business performance, which means the training and development needs at individual contributor level will be met primarily by managers rather than by the central function. That's a strategy. It commits to a specific logic and implies specific decisions that will be made differently because of it.
The goal version says: we'll build leadership capability across the organization at all levels. That's a wish. It implies nothing about how resources will be allocated, what will be done when the senior leadership request and the broader organizational request conflict, or what the function will say no to. It produces exactly the same decisions the function would have made without it, because it provides no basis for making any decision differently.
Why the distinction costs organizations so much
The operational cost of running on goals rather than strategy is significant and often invisible until it compounds into a major problem. Without genuine strategic logic, resource allocation decisions default to the political equilibrium: whoever has more influence gets more resource, whoever makes more noise gets more attention, whatever seems urgent displaces whatever is actually important. Over time, the organization's actual pattern of investment diverges from its stated priorities, producing the uncomfortable situation where the strategy document says one thing and the budget says something entirely different. People in the organization notice this gap and conclude, accurately, that the strategy document is performative rather than functional.
The second cost is decision overhead. In organizations with genuine strategic clarity, a large class of decisions can be made efficiently by reference to the strategic logic: "does this help us be better at the thing we've committed to being better at?" When that logic is absent, every resource allocation, every priority conflict, every competing request requires the same negotiation from scratch. The overhead is significant, and it increases with organizational complexity.
The third cost is the talent cost. High-performing people want to work in organizations where the direction is clear and the resource decisions make sense. When the strategy is actually a set of goals with no logical basis for prioritization, high performers notice the gap between what is said and what happens. They may stay for other reasons — compensation, relationships, interesting work — but they don't bring their full strategic capacity to an environment they've concluded lacks genuine strategic direction. The execution gap is almost always larger in organizations that are running on goals than in organizations that have genuine strategic clarity.
What strategy actually requires
Producing genuine strategy requires doing things that are uncomfortable for most organizations. The most important is making genuine choices — not choosing between things you want and things you don't want, but choosing between multiple things you do want, with the explicit acknowledgment that the unchosen things will be done worse or not at all. This is fundamentally different from goal-setting, and the difference is where most strategy processes fail. The leadership team gets to the point where they would have to choose something over something else they also care about, and they create a structure that appears to include both, diluting the strategic choice into meaninglessness.
The second requirement is grounding the strategy in an honest analysis of competitive position and resource reality. Strategy is situational: what constitutes good strategic direction depends entirely on the specific position, capabilities, constraints, and opportunities of the organization in question. Generic strategic advice — "focus on your core," "build competitive moats," "invest in innovation" — is not strategy; it's vocabulary that could describe almost any organization's intentions without generating a single specific decision. Genuine strategy requires confronting what is actually true about the organization's position, which often involves acknowledging limitations and constraints that the leadership would prefer to paper over.
The third requirement is a commitment to the logic, not just the goals. Strategy that is abandoned the first time following it is inconvenient is not strategy; it's a statement of preferences that held until they conflicted with convenience. The strategic thinking capability required to hold to a genuine strategic logic under pressure is more demanding than the capability required to articulate it when there's no pressure. The pressure test is where strategy is made real or revealed as aspiration.
Making the distinction in practice
The most practical tool I know for distinguishing between a goal and a strategy is to ask: "what decisions will we make differently because of this?" If the answer is "we'll make better decisions" or "we'll be more thoughtful about our investments" — that's a goal. If the answer is "we'll decline requests X, Y, and Z; we'll stop investing in A to fund B; we'll say no to clients who fit profile C in order to serve clients who fit profile D more deeply" — that's strategy.
The related test is to ask whether the strategy has made any enemies. Genuine strategic choices produce genuine disagreement, because they represent a decision that some important stakeholders will experience as a loss. If everyone endorses the strategy enthusiastically, it almost certainly doesn't contain genuine choices; it contains aspirations that everyone can endorse because they don't threaten anyone's interests. Real strategy alienates people whose interests are subordinated by the choices it requires. That is not a failure of the strategy; it is evidence that the strategy is real.
The function I led eventually developed something closer to genuine strategy after two years of running on goals. The process required the leadership team to have a genuinely difficult conversation about what we would stop doing, which took three separate sessions before we could reach an agreement that didn't simply expand the scope to include everything again. The output was uncomfortable to communicate — there were constituencies in the organization who were explicitly deprioritized by the choices we made. But the decisions about resource allocation in the following two years were significantly easier to make, the team's energy was more coherently directed, and the function's actual impact on business outcomes became more measurable. The discomfort of genuine strategic choice turned out to be much less costly than the diffuse ambiguity of running on goals with no clear logic.