Product Vision and Strategy Template

Product Vision and Strategy: [Product name]

A product vision and strategy document: where the product is going in three to five years, who it is for, which problem it solves, how the team intends to win (diagnosis, guiding policy and strategy pillars), the north star metric that shows progress, the strategic bets for the next planning horizon and the things the team will deliberately not do. There is no formal standard for this document. It follows common product management practice as described by Cagan (Inspired, 2nd edition, 2017), Lombardo, McCarthy, Ryan and Connors (Product Roadmaps Relaunched, 2017) and Rumelt's kernel of strategy (Good Strategy Bad Strategy, 2011), written in original words. Replace every [bracketed] value and every row marked Example.

Document control

Approvals

Revision history

Contents

1. Summary on one page
2. Product vision
3. Target customer
4. Problem and evidence
5. Diagnosis: market and context
6. Strategy: guiding policy and pillars
7. North star and input metrics
8. Strategic bets
9. Non-goals
10. Risks and assumptions
11. From strategy to roadmap and OKRs
12. Review cadence and decision rights
13. Glossary
14. References

1. Summary on one page

Example (Tallow Notes):

2. Product vision

Vision statement: [For whom, what changes for them, by when]

Vision narrative: [Three to six sentences describing a day in the life of the target customer once the vision is real. Name the situation, what they do, what they no longer have to do and how it feels.]

Example: A designer joins a nine-person studio on Monday. By lunchtime she has read the three notes the team pinned for newcomers, and when she wonders how invoices are approved, she types the question and gets the answer with a link to the note her colleague wrote last year. Nobody had to file that note in the right folder. When she writes up her first client meeting, two colleagues add to it the same afternoon. The studio never appointed anyone to "own the wiki", yet the knowledge stays current because writing and finding it takes less effort than asking.

Questions to answer:

• Who is better off when this vision is real, and how would they describe the change in their own words?
• What does the product make unnecessary (a meeting, a role, a workaround)?
• Which current ideas or requests would the vision rule out?
• Would the vision still be worth pursuing if a competitor shipped half of it next year?

3. Target customer

Link the personas that describe these customers in detail: [product/persona documents].

Pitfall: defining the customer by demographics only. A product strategy needs the situation and the job, because those decide what the product must do first.

4. Problem and evidence

Problem statement: [Customer] struggles to [job] because [cause], which leads to [consequence].

Example: Small teams struggle to reuse what they already know because knowledge sits in chat threads and personal files that nobody can search together, which leads to repeated questions, slow onboarding and decisions made without earlier context.

Questions to answer:

• How do customers cope today, and what does the workaround cost them in time, money or risk?
• Which evidence is causal and which is only correlation?
• What would you expect to see if the problem were smaller than you think?

5. Diagnosis: market and context

The crux: [One sentence naming the critical challenge.]

Example: Most workspaces never get a second active member, so the product stays a personal notebook and is displaced by the free suite tool; the challenge is to make the team, not the individual, successful in week one.

Link competitor detail to product/competitive-analysis rather than repeating it here.

6. Strategy: guiding policy and pillars

Guiding policy: [One or two sentences.]

Example: Win the team, not the individual. Concentrate product effort on the first week of a new workspace and on the moments when a second and third member join, and grow through invitations rather than paid acquisition.

Coherent actions: list the actions that reinforce each other across pillars, because a strategy is stronger when the pillars support each other.

• [Action that serves more than one pillar]
• Example: Starter spaces (P1) come with pinned onboarding notes that question-style search (P2) can answer from, and are created with admin roles already set (P3).

7. North star and input metrics

Full definition, tree and calculation: [link to product/north-star-metric document].

8. Strategic bets

Discovery bets (where evidence is weak): [List the questions you will answer before committing build capacity, and link the product/opportunity-solution-tree that holds the work.]

Capacity split for the horizon (a statement of intent, not a promise):

Check that the shares add to 100%.

9. Non-goals

10. Risks and assumptions

11. From strategy to roadmap and OKRs

Rule of thumb: any roadmap item that cannot be traced to a pillar is either maintenance, a customer commitment, or a signal that the strategy is missing something. Record which.

12. Review cadence and decision rights

Communication plan: [How the strategy is shared: all-hands walkthrough, written FAQ, recorded session for new joiners, and where the current approved version lives.]

13. Glossary

14. References

• Cagan, M. (2017). Inspired: How to Create Tech Products Customers Love, 2nd edition. Wiley. ISBN 978-1-119-38750-3. Product vision, product strategy and the four product risks are discussed in the book; this template paraphrases the ideas only.
• Lombardo, C. T., McCarthy, B., Ryan, E. and Connors, M. (2017). Product Roadmaps Relaunched. O'Reilly Media. ISBN 978-1-4919-7172-7. Theme-based, outcome-oriented roadmaps that start from vision and strategy.
• Rumelt, R. P. (2011). Good Strategy Bad Strategy: The Difference and Why It Matters. Crown Business. ISBN 978-0-307-88625-5. The kernel of strategy: diagnosis, guiding policy and coherent action.
• Related templates: product/north-star-metric, product/opportunity-solution-tree, product/roadmap, product/prioritization, product/persona, product/competitive-analysis, product/pricing-packaging, business/okr, dev/engineering-strategy.

Standard and licence note

Based on common product management practice; there is no formal standard for product vision or strategy documents. The structure draws on ideas from the books listed in section 14, which are cited by name only. No text, figures or tables are copied from them, and all wording, the structure and the Tallow Notes example are original. The books are paid publications:

• Official text: Wiley, purchase or licensed access: https://www.wiley.com/en-us/INSPIRED%3A+How+to+Create+Tech+Products+Customers+Love%2C+2nd+Edition-p-9781119387503
• Official text: O'Reilly Media, purchase or licensed access through https://www.oreilly.com/ or a bookseller (ISBN 978-1-4919-7172-7).
• Official text: Crown Business (Penguin Random House), purchase or licensed access through the publisher or a bookseller (ISBN 978-0-307-88625-5).

Template licence: MIT.