Product Vision and Product Strategy

Definition

Cagan splits long-range product direction into two distinct artifacts with different jobs. The product vision is a persuasive, multi-year picture of the future the team is trying to create — deliberately not a specification, and not the same as a company mission statement, which says what the company is for but not how it will get there. The product strategy is the sequence of products, releases, or product/market fits the team plans to deliver on the way to realizing that vision — and its central discipline is picking one target market to focus on at a time rather than trying to serve everyone at once. He frames the difference as analogous to leadership versus management: "leadership inspires and sets the direction, and management helps get us there."

In the Book

Chapter 24 argues that a compelling vision functions as one of an organization's most effective recruiting and retention tools — strong engineers and designers are drawn to work they find meaningful, and buying into a vision is "always a bit of a leap of faith" since the team can't yet know if or how they'll deliver on it. The strategy side is where Cagan is most prescriptive: he advises structuring the product strategy around a deliberate sequence of product/market fits — by vertical market for B2B companies, by customer persona for consumer companies (his example: an education product targeting high-school students first, then college students, then working professionals), by geography, or by a logical sequence of milestones. The point of sequencing, he stresses, isn't that any one order is provably optimal — "you can never know how things might have gone if you sequenced your product work differently" — but that committing to one target market at a time is what lets an entire product organization know what "smallest actual deliverable product" success looks like right now, and align sales and marketing to sell only where product/market fit has actually been demonstrated.

He also notes a scaling rule: the vision belongs to the organization, not to each individual product team — every team's local objectives should trace back to contributing to one shared vision, not to inventing their own.

Why It Matters

Ambition and focus pull in opposite directions, and most organizations fail by picking only one: a vision with no sequencing turns into an unfunded multi-year mega-project that satisfies nobody, while a sequence of milestones with no vision degenerates into a list of disconnected features nobody understands the point of. Separating "what we're ultimately trying to build" from "what market we're proving it in right now" lets an organization hold both an inspiring long horizon and a disciplined short one simultaneously, without either collapsing into the other. The underlying move — decouple the aspirational target from the ordered sequence of steps that gets you there, and let each do a different job — generalizes to any effort spanning a horizon too long to plan in a straight line.