Product Strategy: How to Define Yours in 12 Exercises

One practical way to define your product strategy is to decide who the product is for, what it needs to do better than the alternatives, which bets will get you there, and which numbers will prove it is working. It helps to write those choices on one page, along with the evidence that would make you change course.

Most early teams don't lack ideas. They lack the discipline to choose between them.

A fast way to force those choices is a structured workshop: twelve time-boxed exercises, done in order, moving from vision down to metrics and kill criteria. We'd budget about one full day for a founding team, or two half days. What comes out is a one-page document, not a fifty-slide deck.

What a product strategy is (and is not)

A strategy is a set of choices about where you will win and how. That framing comes from Playing to Win by A.G. Lafley and Roger Martin, who define strategy as an integrated set of choices, including where to play and how to win. For a product, it names the customer, the problem, the advantage, the sequence of bets, and the numbers that prove progress.

A roadmap isn't a strategy. It's what a strategy produces. A vision isn't one either; it's the input.

Gibson Biddle, former VP of product at Netflix, whose essay series on defining product strategy shaped much of the thinking behind this workshop format, describes product strategy as a set of hypotheses for delighting customers in hard-to-copy, margin-enhancing ways (his "DHM" model). We like that framing because each of its three parts can be tested.

Our favorite test of a strategy is whether it helps you say no. Richard Rumelt, author of Good Strategy/Bad Strategy, makes a similar point: strategy involves focus and therefore choice, and a good one pairs a diagnosis of the challenge with a guiding policy and coherent actions. If every feature request still sounds reasonable after you've written it down, you probably have a description, not a strategy.

Why early-stage founders need a product strategy framework

A typical pre-seed or seed team is small (Carta's H2 2025 compensation report puts the median seed-stage team at four employees), has limited runway, and faces a hundred plausible things to build. Without a written strategy, the roadmap gets set by whoever spoke last: the loudest customer, the latest investor call, the founder's newest idea. Velocity stays high. Direction wanders.

A written product strategy helps in three ways:

Better small decisions. Engineers who know the reason behind each priority tend to make better calls without asking.
A consistent investor story. "Why this, why now, why you" gets a consistent answer, which matters when investors compare notes. Our guide to how venture capitalists make investment decisions shows how they weigh that story.
An explicit failure signal. You're more likely to pivot on evidence than on exhaustion.

The 12-exercise product strategy workshop

Each exercise has a time box, a question, and an output. Write outputs in one shared document as you go, and keep answers under about 60 words unless noted. The time boxes are starting points; adjust them to your team.

Exercise 1: Vision statement (20 minutes)

Question: if you succeed, what does the world look like in five years? Output: one sentence describing the changed state of the customer, not your product. Weak: "the leading platform for X." Strong: "every independent physical therapist runs their practice without a front desk."

Exercise 2: Target customer (30 minutes)

Question: who is the one specific customer you plan to win first? Output: a profile with three concrete attributes (role, company size or life situation, and a trigger event). Also name who is explicitly not your customer for the next 12 months. This is the exercise founders want to rush, and in our view it's one of the biggest levers in the whole workshop. Narrow feels risky. Broad is usually riskier.

Exercise 3: Jobs to be done (30 minutes)

Question: what job is this customer hiring your product to do, and what do they use today? Clayton Christensen and his coauthors laid out this "hire a product for a job" lens in a 2016 Harvard Business Review article. Output: one primary job written in the job story format that Alan Klement described for Intercom ("when [situation], I want to [motivation], so I can [outcome]"), plus a list of current alternatives, including spreadsheets, email, and doing nothing.

Exercise 4: Sharp pain ranking (20 minutes)

Question: of all the pains around that job, which is most frequent, most expensive, and most urgent? Output: three to five ranked pains with a one-line reason for each rank. As a rule of thumb, your first product should nail the top one. If none of the pains is sharp enough that people would pay to make it stop, that's worth hearing now (our take on painkillers versus vitamins).

Exercise 5: Differentiation (30 minutes)

Question: what will you do that alternatives cannot or will not? Output: two or three "we win because" statements. Ideally each is hard for a competitor to copy within a year: a data advantage, a distribution channel, a workflow insight, or a cost structure. "Better UX" alone is usually not enough. If your product is built on AI models, the model itself is unlikely to be the answer (why we don't think AI alone is a moat); our guide to AI startup moats covers which advantages investors still treat as defensible. Mapping competitors first helps; investors use a similar exercise, described in our piece on building a venture capital market map.

Exercise 6: Delight versus margin (30 minutes)

Question: for each major product area, does it exist to delight customers, to protect margin, or both? Output: a two-column list. This is Biddle's delight and margin tension made practical. Delight features tend to earn love and retention; margin features (pricing, automation, self-serve) earn a business. A strategy with only delight features can burn cash. One with only margin features may give customers little reason to care.

Exercise 7: Strategic bets (40 minutes)

Question: what three to five big bets, if they prove true, get you to the vision? Output: for each bet, the hypothesis, the evidence you would need, and the rough cost to test it. Bets are the bridge from vision to roadmap, and calling them bets keeps everyone honest about the odds.

Exercise 8: Roadmap themes (30 minutes)

Question: what are the two or three themes for the next two quarters? Output: named themes tied to bets, not feature lists. "Make onboarding self-serve" is a theme; "add SSO" is a feature that may or may not belong to it.

Exercise 9: North star and input metrics (30 minutes)

Question: which single metric best reflects value delivered to the target customer, and which inputs drive it? Amplitude's North Star framework recommends one north star plus three to five input metrics the team can directly influence. Output: the north star, its inputs, a current baseline, and a six-month target. If you cannot measure it yet, instrumentation is a natural first roadmap item. Our startup KPI framework goes deeper by stage.

Exercise 10: Pricing and packaging hypothesis (25 minutes)

Question: how will you charge, and what is the value metric? Output: a one-line pricing model (per seat, per usage unit, flat tier, or take rate), a starting price range, and why a customer would accept it. You're stating a testable belief, not signing a contract. Our article on startup revenue models helps you choose.

Exercise 11: Kill criteria (20 minutes)

Question: what would have to be true in six months for you to abandon or fundamentally change this strategy? Output: two or three specific, dated thresholds, such as "if fewer than 25% of activated users return in week four by March, we revisit the target customer." The threshold is yours to set. What matters most, in our view, is writing it down while you're calm rather than arguing about it while you're scared. The "very disappointed" survey in our guide to finding product-market fit makes a useful, repeatable criterion.

Exercise 12: The one-page strategy (30 minutes)

Consolidate everything onto one page under these headings: vision, customer, job and pain, differentiation, bets, themes, metrics, pricing hypothesis, and kill criteria. Read it aloud as a team and cut anything that doesn't change a decision. If a line wouldn't stop you building something, it's decoration.

How to run the product strategy workshop well

Split the roles. A facilitator keeps time and a scribe records outputs. It usually works better if the CEO isn't the scribe.
Write silently first. Give everyone five minutes to write their own answer before discussion, so the loudest voice does not anchor the room.
Treat disagreement as data. If co-founders disagree on the target customer, that may be the most important thing you learn all day.
Bring evidence. Recent customer interviews run the YC way, usage data, and sales call notes. Strategy built only on opinion is guessing with better formatting.
Hold the time boxes. If an exercise runs over, log the open question and move on.

Common product strategy mistakes

Goals mistaken for strategy. "Reach $1M ARR" is a target, not a plan. Rumelt lists this confusion among the hallmarks of bad strategy.

Vision written as a feature. "An AI assistant for lawyers" describes a product, not a changed world. Push one level up.

Customer defined by industry alone. "Restaurants" is a market. "Independent restaurants with two to five locations that just hired their first operations manager" is a customer.

Differentiation that is really a to-do list. "We will build it faster" is rarely an advantage on its own. Keep asking why a well-funded competitor couldn't do the same.

No kill criteria. In our view it's one of the most often skipped exercises and one of the most valuable. Without it, sunk cost decides for you.

Not revisiting. A common rhythm is to re-run exercises 2, 7, 9, and 11 each quarter, and the full workshop once a year or after any major pivot.

Where this fits with 1752vc programs

Our read: investors at pre-seed and seed are largely asking whether you've made deliberate choices about customer, wedge and metrics. A written strategy is a core step toward being investor-ready. 1752vc's Ignite program, a 12-week startup academy for first-time founders (especially those working on an MVP), is a natural place to pressure-test a strategy like this one. If you have validated the product, have early traction and want to turn the strategy into sales, the GTM Accelerator picks up from there, teaching founders to sell, recruit, fundraise and build traction over 12 remote, self-paced weeks. To see how the strategy reads in your deck, get feedback from the Pitch Deck Analyzer, and see our go-to-market strategy framework for the next step.

If you remember one thing

The page you produce matters less than the arguments you have while producing it. Those arguments are where a team finds out whether it agrees on anything.

A roadmap tells your team what to build.

A strategy tells them what to ignore.

Key takeaways

A product strategy is a set of choices about customer, problem, advantage, bets, and metrics; if it does not help you say no, it may not be a strategy yet.
One approach is to run the twelve exercises in order, with firm time boxes and silent writing before discussion, and finish with a one-page document.
The narrowness of your target customer is, in our view, one of the biggest levers in the framework.
It helps to balance delight features with margin features, and to pick one north star metric with three to five instrumented inputs.
Consider writing dated kill criteria while you are calm so evidence, not sunk cost, decides when to change direction.
Many teams revisit customer, bets, metrics, and kill criteria quarterly, and re-run the whole workshop after any pivot.

Frequently asked questions

What is a product strategy framework?

A product strategy framework is a repeatable structure for making the core choices behind a product: which customer to serve, which problem to solve, how to beat alternatives, which bets to place, and which metrics prove progress. The twelve-exercise workshop in this article is one such framework, built for early-stage teams.

How do you define a product strategy for a startup?

One approach: start with a vision of the customer's changed world, narrow to one target customer and their primary job, and define two or three hard-to-copy differentiators. Then list strategic bets and roadmap themes, choose a north star metric with input metrics, state a pricing hypothesis, and write dated kill criteria, all on one page.

What is the difference between product strategy and a product roadmap?

Product strategy is the set of choices about where you will win and how; the roadmap is the sequence of work that follows from those choices. A roadmap without a strategy tends to be a prioritized backlog, and a strategy without a roadmap rarely ships. Many teams review the strategy quarterly and let the roadmap change more often.

What are kill criteria in product strategy?

Kill criteria are specific, dated thresholds that trigger a serious review of the strategy if they are not met, such as a minimum activation or retention rate by a certain month. They help stop you from investing in a direction out of sunk cost rather than evidence.

How often should a startup update its product strategy?

A common rhythm is to review the target customer, strategic bets, metrics, and kill criteria each quarter, because those are the choices most likely to drift as you learn. Re-running the full twelve-exercise workshop makes sense once a year, after a major pivot, or whenever a kill criterion is hit.

Sources

Disclaimer: This guide is for general education only and is not legal, tax or investment advice. Laws, market data and program terms change, so it may not reflect the latest developments or fit your situation. Treat it as a starting point, not a source of truth, and talk to a qualified lawyer, accountant or financial adviser before you make decisions.