Writing a product strategy is mostly deciding what you won't build.
A product strategy is the set of choices about which problems you'll solve, for whom, and the bets that win. Here's how to write one your team can act on, step by step, in the order that actually works.
What a product strategy is, and what it isn't
A product strategy is the reasoning behind what you build: the problems you've chosen, the customers who care most, and the bets you believe will win. It isn't a roadmap (the what and when) or a vision (the destination). A good one lets your team make trade-offs without you.
How to write it, in the order that works.
Frame the problem
Name the specific problem you're solving, for a specific customer. Not the feature you want to build, the pain you're removing.
Break it into problem domains
Split the problem into the distinct areas it spans. Each domain is a place the product will have to be genuinely good.
Find the customers who care most
Decide who feels the problem hardest. They're your beachhead, and their pull is what makes the product spread.
Sequence the cohorts you'll win
Order the customers you'll go after, one after another. You can't serve everyone at once, so pick the order deliberately.
Design the org it takes to ship
Work out the team and structure the plan actually requires, before the roadmap, so the roadmap stays honest about what you can do.
Sequence the roadmap
Turn the bets into a ranked plan where every item traces back to a choice you made. This is the when, and it comes last on purpose.
Each step becomes a section of the plan.
The playbook maps straight onto the ScaleStudio template, so the thinking and the document are the same shape.
The mistakes that make a strategy useless.
- 01It's really a roadmap: a list of features with no why.
- 02It tries to serve everyone, so it serves no one.
- 03It never says no, so the team ends up doing everything.
- 04It lives in a deck nobody reopens after the offsite.
- 05Fix these and the same team starts to compound.
“Ideas aren't unique; execution is.”
Three chapters. Sixteen sections. One coherent plan.
AI writes the first draft. You edit, refine, and operationalize with your team.
Vision
- ·Problem
- ·Solution
- ·Adoption
- ·Positioning
Solution space
- ·Customers
- ·Use cases
- ·Features
- ·Terrain
Strategy
- ·Team
- ·Roadmap
- ·Market opportunity
- ·Announcements
Or have the ScaleStudio AI draft the whole thing.
Describe the problem you're working on, and the ScaleStudio AI drafts the whole strategy: the problem domains, the customers who care, the sequence of cohorts to tackle, the org it would take to ship it and the roadmap to follow. One click and it does everything for you. Then you edit and socialize it from there.
You keep the judgment. The draft kills the blank page. Drive alignment, speed, and scale.
The obvious objections, answered.
How long should a product strategy be?
What's the difference between a product strategy and a roadmap?
Who should write the product strategy?
How often should I update it?
Can AI write my product strategy?
Write a strategy your team can act on.
Score the strategy you have, or start the one you need. Based on the frameworks and approaches used by the best Silicon Valley companies.