define-vision

To create a clear product vision with stakeholders, use a guided, question-driven session that articulates purpose, design pillars, audience, constraints, and non-goals. This structured approach ensures precise decisions and outputs a shared reference document for the team.

A product vision document defines the project's core purpose, design pillars, target audience, constraints, and explicit non-goals. It serves as a concrete, shared reference to align roadmaps, features, and success criteria across the product team.

Align stakeholders on product goals and non-goals through interactive discovery sessions that enforce specificity and prevent vague statements. By asking targeted follow-ups about constraints and design pillars, you guide the group to reach precise, shared decisions.

Yes, you can define design pillars for early-stage projects through a structured conversation. This interactive discovery process applies to refinement sessions, guiding stakeholders to articulate specific pillars and constraints to shape the product direction.

The best way to prevent vague statements when defining a product vision is to apply guardrails for clarity during the discussion. This involves asking targeted follow-up questions that enforce specificity regarding the product's purpose, audience, and constraints.

Validate product vision criteria by generating a concrete artifact like docs/VISION.md during your alignment session. This document provides the specific inputs and concrete criteria required to validate features and align subsequent roadmap planning effectively.