Product Vision Workshop Template

A half-day (3-4 hours) is the sweet spot. Shorter sessions rush the exercises and produce a vision that lacks depth. Full-day sessions cause fatigue and diminishing returns after lunch. If you only have 2 hours, cut Exercise 2 (Future State Visualization) and Exercise 6 (Roadmap Direction), and focus on problems, vision statement, and pillars.

Include 6-10 people: the PM or product leader, engineering leadership, design leadership, and at least one executive sponsor. Include one person from a customer-facing role (sales, support, or customer success) to ground the discussion in real customer language. Do not invite individual contributors unless they are senior enough to represent their function's perspective.

Revisit the full vision annually or when a major strategic shift happens (new market entry, pivot, acquisition, new CEO). Do not change the vision every quarter. That signals the original vision was not well-considered. Strategy pillars and roadmap direction should be reviewed quarterly, but the vision itself should be stable enough to guide 2-3 years of decisions.

Disagreement is normal and healthy. If the team is stuck, look at what they agree on (usually the customer problems) and work backward from there. A useful technique: ask each person to write down what the product should NOT be. The "anti-vision" exercise often reveals shared values that the positive framing missed. If true alignment is impossible, the executive sponsor needs to make a call.

The workshop produces a draft, not a finished strategy. Within one week, the PM or product leader should write up the vision statement, strategy pillars, and metrics into a single strategy document. Circulate it for feedback, then present it to the broader team and stakeholders. Use the [Product Strategy Handbook](/strategy-guide) as a guide for structuring the full strategy document. Each pillar owner should then write a 1-pager with specific initiatives, timelines, and resource needs. ---