Product vision
A product vision describes the better future a product aims to create for its customers. It gives a team a shared direction for decisions, rather than a feature list, delivery schedule or revenue target.
How it works
Name the customer, the problem and the future you want to create. Use the vision to decide which opportunities belong and which to reject.
Strategy explains how you will pursue that future. A roadmap describes the work you expect to do. Neither replaces the vision.
Turning a vision into a measurable goal
For a hypothetical invoicing app, the layers might look like this:
| Layer | Example |
|---|---|
| Product vision | Independent contractors get paid reliably without chasing invoices. |
| Objective | Within six months, reduce invoice-chasing time per customer from 4 hours to 1 hour a month. |
| First experiment | Test automatic payment reminders with existing customers. |
Hitting the objective would save 4 - 1 = 3 hours per customer each month, a 3 / 4 = 75% reduction. These are illustrative targets, not measured results.
The vision stays useful even if reminders fail and the team tries another approach. That is the point: it names the outcome without locking everyone into one feature.
In a fundraising deck, distinguish today's evidence from tomorrow's ambition. Show what customers can do now and what still needs to become true.
Questions people ask
What is the product vision in SAFe Agile?
In the Scaled Agile Framework (SAFe), the vision describes the future state of the solution under development. It connects customer and stakeholder needs with the proposed features and capabilities intended to meet them.
What's the difference between vision and objectives?
Vision describes the future you want to create. Objectives set specific results to pursue, often with a deadline. In the example, reliable payment is the vision; reducing invoice-chasing time within six months is an objective.
