If you’ve spent any time in a product organization, you’ve seen the document. It’s forty slides long. It opens with a mission statement no one remembers writing. It lists fourteen strategic priorities (each one “critical”). And somewhere around slide thirty-two, buried between a SWOT analysis and a wishlist of features, there’s a single sentence that might — if anyone noticed it — actually change what the company does.
That sentence never lands. Because the structure around it can’t hold weight.
This is the problem with how most teams write strategy: they confuse comprehensiveness with coherence. A long list of reasonable ideas is not a strategy. A strategy is a system of choices that make other choices unnecessary.
What strategy actually is
The word gets stretched to cover almost anything directional — a quarterly plan, a product vision, a set of OKRs. But strategy has a specific job. It sits between your ambition (where you want to go) and your actions (what you’ll do next week). It’s the logic that connects them.
Most teams skip the middle step. They jump from goals to tactics and call the result a strategy document. What they actually have is a to-do list with an ambitious title.
“A strategy is not a list of things you plan to do. It’s a set of choices that make other choices unnecessary.”
The diagnostic test
Here’s a simple test: can someone on your team use your strategy to say no to something?
If a stakeholder asks “should we build an integration with Salesforce?” and the answer depends entirely on who you ask, you don’t have a strategy. You have a collection of opinions. A real strategy makes the answer legible: “We don’t invest in enterprise integrations until we’ve proven retention in the self-serve segment.” That’s a choice with consequences.
Good strategy is exclusionary. It draws a boundary around what matters and declares everything outside that boundary out of scope — at least for now.
The kernel of strategy
Every good strategy has three parts:
1. Diagnosis
What’s the actual situation? Not the aspirational one. The real one. What are the forces at play? Where is the friction?
2. Guiding policy
This is the choice of how you’ll deal with the situation. An approach, a stance — not a list of actions.
3. Coherent action
The specific things you’ll do to execute the guiding policy. Each one reinforcing the others.
Why teams avoid real strategy
Real strategy is uncomfortable to produce and uncomfortable to socialize. It requires admitting constraints. It requires making choices that will be second-guessed. It requires living with uncertainty.
Most organizations would rather spread their bets across every plausible direction — which is itself the most reliable way to fail.
Starting where you are
Start with the next decision in front of you. What’s the diagnosis? What’s the guiding policy? What are the coherent actions? Write it down. Share it with your team. Invite disagreement.
The alternative isn’t “no strategy.” It’s implicit strategy — a set of unstated priorities that everyone assumes but no one has agreed to. And implicit strategy is just another name for organizational drift.