Product vision is "the mountaintop" — the problems the company wants to solve over a longer time horizon than Product Strategy addresses. Its job is alignment, not prioritization: "How do you make sure everybody's rowing in the same direction? That's product vision."
Vision and strategy answer different questions: vision says where the company is ultimately headed; strategy says which critical problems get solved right now to move toward that destination while also meeting current objectives. Small companies often don't need a written vision — everyone can hold the direction in their heads — but they do need a strategy, since without one they still face the choice of what to work on next.
Vision and strategy do different jobs. Product Strategy decides which problems get solved right now; vision's job is to get many teams rowing in the same direction — inspiring and aligning them toward one long-term direction rather than adjudicating priority.
That alignment role becomes necessary once a company scales past roughly ten product teams: below that, ad hoc coordination mostly works, but beyond it, teams need a shared vision to stay pointed the same way even while their quarterly strategies — and the problems each is assigned — differ.
Datasite's vision didn't start where it ended. Early on, the vision was a single diligence-stage platform — the tool used during the M&A due-diligence window. As the platform and organization matured, the vision expanded into a full "M&A life cycle solution" spanning pre-deal, diligence, integration, ongoing operation, and future M&A: the vision grew outward from a proven moment of value into the customer's adjacent moments of need, rather than staying fixed at the outset. See Ingredients of a Product-Model Transformation for how this expansion fits the broader shift from technology serving the business to technology serving the customer.
At Palace Hotels, buy-in for the pilot team was driven by casting an aspirational future rather than listing problems to fix: "We gave people futures to build rather than gave them problems to solve." The target reaction was made explicit on both ends of the org — leadership needed to react with "wow that is amazing," and staff on the floor needed to react with "I want to be on that team." Vision-casting here functioned as a recruiting and momentum mechanism for the transformation itself, not just a description of a future product state — see Single Pilot Team as Transformation Proof of Concept for the mechanism this vision served.
A vision has two jobs: it must inspire (people want to feel they're "leaving a dent on the universe") and it must focus/align teams like a north star — without one, companies default to incremental, revenue-only thinking. It's easy to conflate three things with a real product vision: no vision at all (see Vision Vacuum: No Vision, Not Bad Vision, Is the Real Failure Mode), a bare mission statement (see Mission → Vision → Strategy → Roadmap Hierarchy), and a culture/PR-oriented "company vision" — a real product vision is none of these; it's leadership's specific answer to what the company will do over the next few years to advance the mission.
Three non-negotiable ingredients: validated business and customer problems, alignment with corporate/executive strategy, and at least a glimpse of the revenue/monetization path — usually supplemented by a customer/business "wow" narrative and framing against industry trends (e.g. Gen AI) and competitive leapfrogging.
Three-question test for whether a real vision exists: can you say what problems you're solving and for whom; can you say how you'll make customers' lives better; can you see corporate strategy and company identity reflected in it.
A vision only functions if it's known — "it's not a vision if nobody knows about it." An unpublicized vision can't inspire or align anyone; it fails both jobs above.
Ownership: see Vision Authorship: Never a Collective Enterprise. Scope: see Vision Scope: One Integrated Vision, Except for Multi-Business-Unit Giants. Calibration: see Audacious but Calibrated: Vision Must Match Company Readiness. Time horizon: see Vision Time Horizons Are Compressing Under AI-Driven Change. Building one: see Vision Sprint Prerequisites: Homework Before the Room.