If everything is a priority, nothing is

Most "product strategies" I'm shown are one of two things. Either a vision so lofty it could describe any company on earth — "delight our customers, drive growth, become the platform of choice." Or a roadmap in a trench coat: a list of everything the team plans to build, with strategy written at the top.

Neither one helps anyone decide anything. And deciding is the entire job.

Strategy is what you say no to

A real strategy doesn't tell you what's important. Everything feels important — that's the problem, not the solution. A real strategy tells you what you're not going to do, so the team can pour everything into the few bets that matter.

Here's the test. If your strategy doesn't rule anything out — if every reasonable idea still "fits" — it isn't a strategy. It's a wish list. A strategy that accommodates everything commits to nothing.

Why teams avoid the hard version

Saying no is uncomfortable, so teams find ways around it. They keep their options open — calling it "staying agile" — when really they just can't bear to close any doors. They want sharp clarity later and easy flexibility now, and you can't have both.

The cost of that avoidance is brutal and quiet. When there's no clear strategy, every prioritization meeting restarts the same argument from scratch. Stakeholders fill the vacuum with their pet projects. The roadmap becomes a negotiated truce between loud voices, not a coherent plan. And the team ends up in a feature factory — shipping busily in five directions, moving in none.

The four layers that connect vision to Tuesday morning

Good strategy is a chain. Break any link and the whole thing goes slack. From the top:

1. Vision — where you're going

The long-term picture of the world you're trying to create. It should be inspiring, but more importantly it should be specific enough to exclude things. A vision that fits any company gives no guidance.

2. Strategy — the bets that get you there

The handful of choices about where you'll play and how you'll win — which customers, which problems, which advantages you'll lean on. This is the layer everyone skips, and it's the one that does the work. Three or four bets, max. If you have ten, you have none.

3. Outcomes — how you'll know it's working

Each bet translates into a measurable change in customer behavior. This is what you assign to teams — not features, outcomes — so they own the result, not just the output. (The difference matters more than almost anything; I wrote about it here.)

4. Roadmap — what you're exploring now

Last, and least sacred. The roadmap is your current best guess at how you'll hit those outcomes — a set of opportunities and bets in progress, not a contract carved in stone. It changes as you learn. That's a feature, not a bug.

How to pressure-test what you've got

Take your current strategy and run it through three questions:

• Does it exclude anything? Name three reasonable ideas it tells you not to pursue. If you can't, it's a wish list.
• Could a competitor have written it? If your strategy would be equally true on a rival's wall, it says nothing about your specific bet.
• Can a team use it to decide on its own? The point of strategy is that people far from the room can make the right call without asking you. If every decision still escalates upward, your strategy isn't doing its job.

Strategy isn't the inspiring part of product. It's the disciplined part — the willingness to bet on a few things and walk past the rest, even when the rest look tempting. Do that, and prioritization stops being a weekly brawl. The hard choices were already made, on purpose, up front. Everything after that is just execution.