A product strategy is the set of deliberate choices that determine where a product will compete, what it will do, and - just as importantly - what it will not do. It is not a roadmap. It is the logic that makes a roadmap defensible.
I was on a call last month with a founder who runs a healthcare platform. Smart person, good instincts. His product strategy was: We want to be the Amazon of healthcare. I asked him what that meant for what they were building this quarter. He paused, then described four different user segments, three distribution models, and two acquisition targets he was evaluating simultaneously. None of them connected to each other.
That is not a strategy. That is a collection of options dressed up as one.
His actual business had a weight management vertical that was growing fast, converting well, and had a clear path to $100M. He knew this. But every time someone proposed focusing there, his response was the same: If we specialize, we become a small company. The strategy problem was not analytical. It was psychological. He was confusing the decision to focus with a decision to give up.
What is product strategy?
Product strategy is a set of integrated choices that answer three questions: Where will your product compete? How will it win in that space? What will it not do in order to stay coherent? A real product strategy makes some people uncomfortable because it says no to things that seem reasonable.
The SVPG definition - product strategy is the path to achieving the product vision - is accurate but not useful. Vision tells you where you want to end up. Strategy tells you which road you are taking and which roads you are not taking. Most product teams skip the second part.
At TripAdvisor, when we decided to build instant booking into the metasearch product, the strategy was not simply let customers book hotels. The strategy was: own the transaction in categories where supply fragmentation made the booking experience painful, and use that ownership to build a data advantage that independent comparison sites could never replicate. Every roadmap decision for three years ran through that filter. Features that did not serve that specific thesis got cut - including some features users asked for directly. That is what a strategy looks like in practice.
Why most product strategies fail
Most product strategies fail for one of three reasons.
The first is that they are not actually choices. A strategy document that says we will serve enterprise and SMB customers across North America with a best-in-class product experience has made no choices. It has described a market and attached some adjectives. Every competitor could sign the same document. A strategy only exists when it excludes something.
The second failure mode is confusing strategy with roadmap. A roadmap is a sequenced list of bets. A strategy is the logic that explains why those bets - and not others - are the right ones. When the strategy is missing, roadmaps become negotiation documents where whoever is loudest or most senior wins the argument about what gets built next.
The third failure is treating strategy as a one-time artifact. I see this constantly in companies between Series A and B. They write a strategy document, present it to the board, and then treat it as settled. But the document was written based on assumptions about the market, about what customers will pay for, about what competitors will do. When those assumptions change - and they do - the strategy needs to change too. Companies that treat strategy as a living instrument outperform companies that treat it as a deliverable.
| What strategy is | What strategy is not |
|---|---|
| A set of integrated choices | A vision statement |
| The logic behind your roadmap | The roadmap itself |
| A living instrument | A one-time deliverable |
| What you will not do | A list of everything you want |
| Defensible under pressure | Comfortable for everyone |
How to build a product strategy
Assess value creation
Where are customers actually paying and staying - not necessarily where you want them to be.
Identify strategic bets
Three clear bets with conviction beat ten bets with hedge. Pick where the return is asymmetric.
Make non-bets explicit
The step most teams skip. Say no to stakeholders in writing. This is where strategy becomes real.
The process that works is simpler than most frameworks suggest. It starts with an honest assessment of where you are creating value today - not where you want to create value, but where customers are actually paying and staying. That sounds obvious. It rarely is. Most founding teams have a theory of their product that diverges meaningfully from what their retention data and cohort analysis shows.
At EverQuote, I spent the first month mapping exactly where in the insurance shopping funnel we were generating revenue versus where we were burning cost. The business had a strategy on paper. The actual revenue was concentrated in two carrier verticals, two traffic channels, and a narrow band of the consumer funnel. Everything else was overhead. The real strategy question was whether to double down on what was working or keep funding the periphery. We doubled down. That decision drove $200M in incremental revenue over the next two years.
The second step is identifying the strategic bets. A bet is a place where you are going to invest disproportionate resources because you believe the return is asymmetric - either because you have a structural advantage, or because the market is underserved, or because your data tells you something competitors do not see yet. Most companies have too many bets. Three clear bets with conviction beat ten bets with hedge.
The third step is making the non-bets explicit. This is the step most teams skip because it requires saying no to stakeholders. The non-bets are as important as the bets. They protect the team from scope creep, they make prioritization decisions faster, and they allow you to communicate clearly to customers and partners what you are not trying to do.
What separates good product strategy from bad
Good product strategy survives contact with reality. When a competitor moves, when a channel dries up, when a key customer churns, a good strategy tells you what to do next because it is built on logic, not on assumptions about a stable world. A bad strategy requires a rewrite every time something unexpected happens.
The other signal is whether the strategy travels. Can your PM team explain the strategy to an engineer without you in the room? Can an engineer use the strategy to make a prioritization call without asking? If the answer is no, the strategy is not clear enough to be useful. A product strategy that lives in the head of the CPO is not a strategy - it is a dependency.
I have worked with companies where the founding CEO held the strategy so tightly that no one else could make a product decision without their approval. That works at ten people. At fifty it is the primary growth constraint. Part of what a fractional CPO or product leader does is externalize the strategy - pull it out of the founder's head, make it legible, and build the decision-making infrastructure that lets the team operate without being blocked.
Good product strategy is also honest about the stage of the company. The right strategy for a $3M ARR business is not the same as the right strategy for a $30M ARR business, even if the product vision is identical. Stage determines what you can afford to test, what your customers will forgive, and where your competitive moat actually sits. The founders who get into trouble are usually the ones running a $30M ARR strategy on a $3M ARR resource base, or running a $3M ARR strategy when they need to be thinking about defensibility at scale.
The founder who would not focus
The healthcare founder I mentioned at the start eventually agreed to a 90-day sprint focused on the weight management vertical. We scoped it as a test, not a permanent decision, which made it psychologically easier to accept. In 90 days, the unit economics in that vertical improved enough that the board conversation changed. He stopped talking about being the Amazon of healthcare and started talking about being the category leader in weight management. The strategy got sharper because the business got sharper.
That is how product strategy works in practice. It is not written once in a conference room. It is forged through the accumulation of real decisions - what to build, what to kill, where to bet, where to stop. The document matters less than the discipline.
