A product strategy is useful only if it constrains decisions — if everything is consistent with your strategy, you don't have a strategy. The test of a good product strategy: does it help you say no to reasonable requests? If not, it's a vision document, not a strategy.
"Strategy is not about what you'll do. It's about what you won't do. The hardest part of writing a product strategy is choosing who you're not building for — and that conversation is where most strategies collapse."
— Nora B., CPO at a Series C enterprise SaaS company
The five components of a useful product strategy
1. Target customer (specific, not generic): Not "product managers" — "product managers at B2B SaaS companies with 5–50 engineers who write 3+ PRDs per month." The specificity defines what you build and what you ignore.
2. Problem definition: The specific problem your target customer has that current solutions solve poorly. What's the gap? Why does it exist?
3. Solution differentiation: What makes your solution better than alternatives for the target customer? Not better in general — better specifically for this customer with this problem.
4. Business model: How value delivered translates to revenue. Pricing model, expansion path, unit economics target.
5. Explicit non-targets: Who you are NOT building for. This is the hardest section and the most important one for constraining roadmap decisions.
How product strategy connects to roadmap
| Strategy layer | Roadmap implication | PRD implication |
|---|---|---|
| Target customer | Features that serve non-target customers go to bottom of backlog | PRD background must connect to target customer problem |
| Problem definition | Features that don't address the core problem require strategy justification | PRD success metrics must measure progress on the core problem |
| Differentiation | Features that narrow the differentiation gap ship before nice-to-haves | PRD background explains how feature advances differentiation |
| Non-targets | Requests from non-target customers are explicitly deprioritized | PRD personas must align with target customer definition |
How to write a product strategy in practice
Start with a 1-page strategy brief: target customer (2 sentences), problem (2 sentences), differentiation (2 sentences), non-targets (bullet list). Review with leadership. Then use it in every PRD review: "Does this feature advance our strategy?" If the answer is "maybe" or "eventually," it goes to the backlog.