All methods

Product Vision Workshop

Typical duration:
1h 30m

A collaborative session where the team crafts a compelling product vision statement that aligns stakeholders on the why, who, and what of the product.

Purpose

The Product Vision Workshop creates alignment on the long-term direction of the product. A clear vision guides backlog prioritization, inspires the team, and gives stakeholders a shared north star.

At a glance

AttributeDetail
Group size5 – 15
Duration90 minutes
DifficultyMedium
Facilitation styleFacilitated ideation + convergence
SettingIn-person preferred; remote with digital whiteboard

How to run

  1. Set context (10 min) — Share market data, user research highlights, and business goals.
  2. Individual vision drafts (10 min) — Each participant writes their version of the product vision using a template such as Geoffrey Moore's elevator pitch format.
  3. Share and cluster (20 min) — Post all drafts. Read aloud. Group themes and key phrases.
  4. Collaborative drafting (30 min) — In small groups, merge themes into candidate vision statements. Each group presents their draft.
  5. Converge (10 min) — Dot-vote on the strongest elements. The Product Owner synthesizes one vision statement.
  6. Validate (10 min) — Test the vision: Is it inspiring? Is it differentiating? Can the team remember it? Adjust wording.

Materials needed

  • Vision template (e.g., Moore's elevator pitch: "For [target user] who [need], [product] is a [category] that [key benefit]. Unlike [alternative], our product [differentiator].")
  • Market and user research summaries
  • Sticky notes, markers, whiteboard or Miro
  • Dot-voting stickers

Pitfalls & common mistakes

  • Vision is too vague — "Make the world better" is not a product vision. Be specific about user and differentiator.
  • HiPPO effect — The highest-paid person's opinion dominates. Use silent writing and voting to level the field.
  • Vision stays on the wall — The vision must be referenced in every Sprint Planning and review; otherwise it is forgotten.
  • Confusing vision with strategy — Vision is the destination; strategy is the route. Keep them separate.

Inclusion & accessibility

  • Provide the vision template and context materials in advance.
  • Use silent writing before sharing to ensure introverted participants contribute.
  • Keep the final vision in plain language — no jargon.

Variations

  • Product vision board — Roman Pichler's visual canvas: vision, target group, needs, product, business goals.
  • Press release from the future — Write a fictional press release announcing the product's success 2 years from now.
  • Vision / anti-vision — Also articulate what the product is NOT, to sharpen focus.

When NOT to use this

  • If the product vision is already well established and widely understood — refine rather than restart.
  • If key decision-makers are absent — defer until they can participate.

Source & further reading

  • Moore, G. (1991). *Crossing the Chasm*. Harper Business.
  • Pichler, R. (2016). *Strategize*. Pichler Consulting.

Turn the building blocks into an agenda

Create the day, drag the blocks into the order you have in mind, and let the times work themselves out. Or describe what you are planning to your AI and let it write the first draft.

Try it free for 14 days