Product Vision FAQ

Marty Cagan answers common follow-up questions about product vision, clarifying how it differs from a roadmap and how it should be scoped, owned, detailed and maintained. He argues a vision should describe a desired end state several years out, apply to the broadest sensible unit (such as a whole marketplace rather than each side of it), and be owned by the head of product with real buy-in from the CEO. He outlines a facilitated off-site process for crafting it and warns that the more common failure is abandoning a vision too early rather than pivoting. The piece matters because vague or short-horizon 'visions' leave teams without a durable north star.

01Key takeaways

• Set the product vision 2-5 years out for software (5-10 for devices), not as a one-year roadmap.
• Scope the vision to the broadest unit where it still meaningfully applies, such as the whole marketplace.
• Make the head of product responsible for the vision while ensuring the CEO and leaders genuinely own it.
• Describe how customers' lives will concretely improve, not just a generic promise like 'better through automation'.
• Prepare key inputs in advance so an off-site spends its time on implications rather than rehashing facts.
• Give a vision enough time to prove out; abandoning it after months is a more common failure than a justified pivot.

02Key sections

Timeframe and scope

A product vision should look 2-5 years out for software and 5-10 for devices, and should span the broadest unit where it still means something. Splitting a marketplace into buyer and seller visions misses the dynamics between them.

Ownership and level of detail

The head of product owns the vision, but the CEO and key leaders must feel genuine ownership since they will evangelize it. It should be concrete enough to convey the customer experience without becoming a specification.

Crafting the vision through an off-site

Cagan runs a 1-2 day facilitated session with 5-15 leaders and influential contributors, using prepared inputs across business, customer, technology, competitive and organizational factors. The session supplies context so a product head and designer can draft the visiontype afterward.

Maintenance, pivots and abandonment

Strategy changes often while the vision holds steady for years. True vision pivots are rare, while the more common mistake is giving up on a vision after 6-12 months, usually due to weak discovery skills.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.