Kasra VaziriGood Product Strategy Is Deciding What Not to Build
Real product strategy is focus and sacrifice. It's mostly the good ideas you choose not to build. On the cost of saying yes, why pleasing everyone is no strategy, and how to make focused bets.
Ask ten product teams for their strategy and you'll get ten roadmaps. A wall of bullet points, every one a "priority," every quarter heavier than the last. It reads like ambition. It's actually the opposite. A list where everything matters is a list where nothing has been decided, and a product strategy that refuses to decide isn't a strategy at all. The real work of product strategy is subtraction: choosing, on purpose, the good ideas you will not build.
I've shipped enough to know that the hardest document I write isn't the roadmap. It's the anti-roadmap — the short, uncomfortable list of things we are explicitly not doing this year, with reasons. That list is where the strategy actually lives. Everything else is just scheduling.
Product strategy is a set of choices, not a wish list
Richard Rumelt, in Good Strategy / Bad Strategy, argues that real strategy has a "kernel": a clear diagnosis of the challenge, a guiding policy for meeting it, and a coherent set of actions that follow. What he calls bad strategy is the stuff most decks are made of — fluff and buzzwords masking an absence of substance, and a quiet failure to actually choose. Ambition gets mistaken for a plan. "Become the leading platform for X" is a goal wearing a strategy's clothes. It tells you nothing about what you'll do, and worse, nothing about what you'll give up to do it.
That last part is the tell. If a strategy doesn't sacrifice anything, it isn't one. Choosing to win in one place means choosing not to compete in five others. A document that promises to delight every persona, enter every adjacent market, and ship every requested feature hasn't made a single hard call. It has just deferred all of them to a future that never arrives, because the team is too busy being mediocre at ten things to be excellent at one.
The cost of yes is invisible until it's everywhere
Every yes feels cheap in the moment. One more setting. One more integration. One enterprise logo's must-have. None of them looks like the thing that kills your product, and that's exactly why they're dangerous. The cost of yes isn't the build — it's the carry. Every feature you ship is something you now maintain, document, support, regression-test, and reason about forever. It widens the surface area of your product and narrows the surface area of your attention.
Des Traynor of Intercom put the discipline plainly: if you're building a product, you have to be great at saying no — "not 'maybe' or 'later'. The only word is no." The reason that's hard is that the requests aren't dumb. Bad ideas are easy to reject. The ideas that test your strategy are the good ones — genuinely useful, championed by a real customer, defensible in a meeting — that simply don't belong in the product you're trying to build. Saying no to a bad idea is hygiene. Saying no to a good idea is strategy.
In his Business of Software talk on product strategy, Traynor makes the same case at the level of the whole product: building a great product isn't accumulating tactically useful features that are tangentially related. It's delivering one coherent thing with well-defined edges. Coherence is a budget. Every off-strategy yes spends it.
Focus is the whole point, and it makes people unhappy
When Steve Jobs returned to Apple in 1997, the company was building in, by his own count, eighteen different directions. His fix wasn't a new product. It was a campaign of deletion — killing most of the lineup down to a handful of bets. At that year's WWDC he said the thing that's now a poster but was, at the time, a genuinely radical reframe: "focusing is about saying no." Not saying yes to the one thing that matters — saying no to the hundred good things that don't.
He'd later sharpen it into the line everyone quotes: "innovation is saying no to 1,000 things." I'd add the part that gets left off the poster — that saying no costs you. It disappoints customers you respect. It annoys a salesperson who had the deal half-closed. It means a smart engineer's pet idea dies. If your strategy never makes anyone unhappy, you haven't focused; you've just spread the disappointment evenly across a worse product. Focus is unpopular by design. That's how you know it's real.
How to make focused bets
Subtraction sounds noble in a blog post and feels like loss in a planning meeting. Here's how I make it concrete:
Write the diagnosis before the plan. Name the one central challenge in a paragraph a new hire could understand. If you can't, you don't have a strategy yet — you have a backlog. Rumelt's kernel starts with diagnosis for a reason: everything downstream is just noise until you know what problem you're actually solving.
Pick a painfully small number of bets. Two or three things that, if they work, change the trajectory — not the twenty "critical" initiatives that are really just everyone's pet project with a deadline attached. The instinct to keep the list long is the instinct to avoid choosing. Resist it.
Keep a written not-doing list. For each big bet, name the good ideas you're declining because of it, and why. Make the trade-off legible. When someone reopens a closed door next quarter — and they will — you point at the list instead of relitigating from scratch.
Make "no" a default with a high bar, not a fight. A new request doesn't earn a slot by being good. It earns one by being better than something already on the list, which means displacing it. Tie every yes to an explicit no. If nothing comes off, nothing goes on.
Revisit the bets on a slow clock. Focus isn't stubbornness. Strategy should change when the diagnosis changes — but on the cadence of real learning, not the cadence of the loudest meeting. A strategy you abandon every two weeks was never a strategy; it was a mood.
The uncomfortable truth under all of this is that good product strategy looks, from the outside, like underachievement. You shipped fewer features than the competitor down the street. You told real customers no. Your roadmap is suspiciously short. And yet the product is sharper, the team is calmer, and the thing you bet on actually works — because the whole organization was pointed at it instead of scattered across the hundred other things you had the discipline not to build.
Anyone can write down what to do. Strategy is the courage to write down what you won't. (Related, if focus is on your mind: why most features go unused.)