A product vision describes the change a product wants to bring to an audience over a horizon of a few years: who it is for, what need it meets, what benefit it delivers and why it differs from the alternatives. It is not a plan or a feature list; it is the reference that helps the team say yes or no to each request and build the roadmap without losing direction.
How to use
- Enter the product name, the category the customer would put it in and the vision horizon.
- Describe who it is for and the need, starting with a verb.
- Write the key benefit and, if you like, the current alternative and the differentiator.
- Add business goals to tie the vision to results.
- Read the statement, the three one-line versions and the check, and export the card.
What each field asks for
| Field | What to enter |
|---|---|
| Product name | E.g. CashSure |
| Product category | How the customer would classify the product, with an article. |
| Vision horizon | How long this vision should guide the team. |
| Who it is for | The audience, in the plural and as specific as possible. |
| Need | What the audience needs to do, starting with a verb. |
| Key benefit | What the product does for the audience, starting with a verb. |
| Unlike | Optional. What the audience uses today instead of the product. |
| Our differentiator | Optional. What only the product does, starting with a verb. |
| Business goals | Optional. What the company gains if the vision comes true. |
Example
A fictional cash management app for small restaurant owners, with a 3-year horizon, generates the statement: "For small restaurant owners who need to know how much cash they will have at the end of the month, CashSure is a mobile cash management app that forecasts cash for the next 4 weeks from daily sales. Unlike spreadsheets and full management systems, CashSure works from photos of receipts alone, with no stock set-up." One of the one-line versions is "In 3 years, small restaurant owners will know how much cash they will have at the end of the month with CashSure." The board shows two business goals and the check passes all five items.
When to use
- At the start of a product, to align founders, team and sponsors on what you want to build.
- When the roadmap has become a list of requests and you lack a criterion for saying no.
- When joining an existing product, to write down the vision that lived only in people’s heads.
- Before annual planning, to check whether the vision still holds.
Frequently asked questions
What is a product vision?
It is a short description of the change a product wants to bring to an audience over a few years. It says who it is for, what need it meets and why it is different. It works as a criterion for scope and roadmap decisions.
What is the difference between vision and mission?
A mission usually speaks about the company and its lasting purpose. A product vision speaks about one product and a concrete future, with a defined audience and horizon. A company has one mission and may have several product visions.
What is the difference between vision and strategy?
The vision says where the product wants to go; the strategy says how to get there, with choices about audience, differentiator and what not to do. Business goals and the roadmap connect the two.
What is the ideal horizon?
For new products, one to three years tends to work: far enough to inspire, close enough to guide decisions. Mature products or platforms may use five years.
How does AI help in this tool?
When AI is switched on, it proposes three one-line visions from your fields, without inventing numbers or facts. Without AI, the tool builds the three variations from rules. The full statement, the board and the check are always generated by rules.
How do I know if the vision is good?
A good vision has a specific audience, a real need, a clear differentiator and fits in a sentence the team repeats without reading it. Test it by asking three team members what the vision is: if the answers differ, it is not clear yet.