Strategy Is the List of Things You Are Not Doing

Read enough corporate strategy documents and a pattern emerges. They describe growth in every segment, investment in every capability, and improvement on every dimension. Nothing is being given up. This is not a strategy; it is an aspiration with a financial model attached.

A strategy is a set of choices about where to compete and what to forgo. The forgoing is the hard part and the reason most strategy work stalls at the point of decision.

Test one: name the sacrifice

For your current strategy, state what you have deliberately decided not to pursue. Not what you deprioritized in the last budget round, but what you have chosen to be worse at than competitors, on purpose, because the resources are better spent elsewhere.

If no one on the leadership team can answer this consistently, the organization is allocating by consensus rather than by choice, which produces a portfolio where everything is slightly underfunded.

Test two: check whether it constrains a real decision

A strategy earns its keep by making decisions easier. Take three live decisions currently in dispute — a pricing question, a hiring request, a feature tradeoff — and ask whether the strategy determines the answer.

If it does not, it is too abstract to function. "Deliver exceptional customer value through innovation" resolves nothing. "We win mid-market accounts on speed of implementation, so we will not take deals requiring more than a six-week deployment" resolves several.

A strategy that has never caused you to turn down attractive revenue has not yet been tested.

Test three: ask five people to state it

Walk the organization and ask, without warning, what the strategy is. Consistency of answer matters more than eloquence. Strategies that live in a document and not in people's heads do not affect behavior, and behavior is the only channel through which a strategy produces results.

The failure mode here is length. Anything that cannot be held in memory will not be applied when someone is deciding something on a Tuesday afternoon.

Distinguish the strategy from the plan

The plan is the sequence of activities with dates and owners. The strategy is the logic that explains why this sequence and not another. Organizations frequently produce the plan and skip the logic, which works until conditions change and nobody can tell which parts of the plan still make sense.

Write the logic down separately, in a page: where we compete, why we win there, what capability that requires, and what we are giving up. That page is what you revisit when the market moves.

Revisit the assumptions, not the ambition

Every strategy rests on a handful of beliefs about customers, competitors, costs, or technology. List them explicitly, name what would prove each one wrong, and review them twice a year.

Most strategies that fail do not fail because the ambition was wrong. They fail because an assumption quietly stopped being true and nobody had written it down clearly enough to notice.