What is product strategy? A working guide for founders and small teams
Most product strategy documents are lists of things a team intends to build. A strategy is the opposite of a list. It is the small set of choices that tells you what not to build, and why the thing you are building could win.
A definition you can use on Monday
Product strategy is the set of choices about who you serve, what problem you solve for them, why your version wins, and what you will therefore refuse to do.
That is the whole thing. Everything else people call strategy is either research feeding those choices, or a plan following from them. If a document does not make a choice that costs you something, it is not a strategy. A roadmap listing eleven features for the next two quarters makes no choices, because it excludes nothing that anyone was arguing for.
The reason this matters at small scale is speed. A team of three with a real strategy makes decisions in minutes, because most options are already ruled out. A team of thirty without one holds meetings, because every option is still live and nobody has authority to close it.
Strategy is not the plan. It is the reason the plan is shaped the way it is. If you cannot explain why you are not doing the obvious other thing, you do not have one yet.
The four decisions inside a product strategy
- 01
Who, specifically
Not a market, a person in a situation. Operations managers at clinics with two to six locations who still run scheduling in spreadsheets. Specific enough that you can name three real ones and phone them. If your who is small businesses, you have not chosen.
- 02
What problem, in their words
The problem as they describe it out loud, not as you would categorise it. People do not want a unified operations platform. They want to stop being called on Saturday about a double booking. The gap between those two sentences is where most products lose their footing.
- 03
Why your version wins
One honest advantage: a distribution channel you already have, a domain you know better than anyone, a level of craft the incumbents will not match, a price the incumbents cannot match without breaking their model. Better and easier to use is not an advantage. It is what everyone says.
- 04
What you will not do
The explicit refusals. No enterprise SSO this year. No mobile app until the web product is loved. No custom work for a single client. Written down, so a tempting request does not quietly become a quarter of engineering.
How to write it on one page
The page has five short parts. Each part is a few sentences, not a slide deck. If it does not fit on a page, the thinking is not finished.
- The customer: who they are and the situation they are in when they need you.
- The problem: their sentence, in quotation marks, from a real conversation.
- The wedge: the one thing you do so well that it is worth switching for.
- The advantage: why you can keep doing that when others notice.
- The refusals: three to five things you are deliberately not building this year.
Then add one number. Not a vanity metric, the number that tells you the strategy is working: activated teams per week, second-week return rate, jobs completed without support contact. One number keeps a team honest in a way that a dashboard of nine cannot.
Strategy, roadmap and backlog: which is which
| Artifact | Answers | Changes when |
|---|---|---|
| Strategy | Who we serve, why we win, what we refuse | Evidence changes your belief about the customer or the advantage |
| Roadmap | What order we tackle things in, roughly when | Every few weeks, as you learn what is harder or more valuable than expected |
| Backlog | The specific work items, sized and sequenced | Continuously. A backlog is inventory, not a promise |
The common failure is treating the roadmap as the strategy. Then when a big customer asks for something off-strategy, there is nothing to check the request against, so the answer defaults to yes. Six months later the product serves two audiences at seventy percent each.
What counts as evidence
You do not need a research department. You need conversations that could change your mind, and a way to notice when they do.
- Eight to twelve conversations with the specific person you named, about what they do now, not about your idea.
- What they currently pay for, in money or in hours. Existing spend is the strongest signal there is.
- The workaround they built themselves. A spreadsheet with forty tabs is a product brief.
- One thing they tried and abandoned, and why. This is where your refusals come from.
- A prototype in front of them inside two weeks, because opinions about descriptions are unreliable and reactions to artifacts are not.
Signs your strategy is not real yet
- It contains the words platform, seamless or end to end, and removing them removes the meaning.
- Nobody on the team can state it from memory in two sentences.
- It has never been used to say no to something a paying customer asked for.
- The customer description would fit half the companies in the country.
- The advantage is a feature. Features are copied in a quarter.
- It was written once and has not been revisited since the evidence changed.
A strategy is a living argument, not a founding document. Revisit it when something surprises you, and expect to rewrite the advantage at least once before you find the version that holds.