Product Vision Board

Discovery

Planning

Strategy

Formulate your product vision on a single page. Roman Pichler's tool to align team, users and business objectives.

Description

The Product Vision Board is a visual strategic tool created by Roman Pichler (2012, formalized in Strategize, 2016) that synthesizes a product's vision into five sections on a single page: Vision (why this product exists), Target Group (for whom), Needs (what problem), Product (what solution), and Business Goals (what result for the company). Its purpose: to give the entire product team a shared compass before investing in a roadmap or a backlog. Roman Pichler designed it as an answer to a recurring problem: teams build features without a common vision. "A product vision describes the ultimate reason for creating a product," he writes in Strategize. "It captures what the product should achieve and who it should benefit." The Product Vision Board works like your product's identity card: if you cannot fill in the five sections in 30 minutes, your vision is not clear enough to guide decisions. Each section answers a fundamental question. The Vision answers "What change do we want to create in the world?" The Target Group answers "Who are the first users we need to convince?" Needs answers "What problem are we solving for them?" The Product answers "What are the 3-5 differentiating features?" Business Goals answers "How does this product serve the company?" Unlike Ash Maurya's Lean Canvas (which covers the complete business model), the Product Vision Board focuses exclusively on the product vision. It is lighter, faster to fill in, and designed to be revisited regularly. Pichler recommends reviewing it every quarter, or even after each significant pivot.

Objectives

Identify problems
Define the vision
Understand users
Ensure strategic alignment

Used by

-Atlassian (provides a Product Vision Board template in Confluence, used internally to frame the vision for new products)

Advantages

Aligns the entire team in 30 minutes. A single page readable by the developer, designer, CEO and investor, without prior training.
Forces strategic choices early. By limiting each section to 3-5 elements, the board forces saying no before you start building.
Natural bridge between vision and execution. The board connects directly to the roadmap: each initiative must be traceable to a section of the board.
Lighter than Lean Canvas for product teams. No need to model revenue, channels or cost structure when the goal is aligning the vision.

Limitations

Does not cover the business model. The board says nothing about monetization, distribution channels or cost structure. If you need a complete business framework, use the Lean Canvas.
Quality directly tied to user research. A board filled with unvalidated hypotheses gives a false impression of alignment. Validate Needs and Target Group through interviews before engraving the board.
Risk of a "decorative" board. If the board is created once then forgotten in Confluence, it serves no purpose. Quarterly review discipline is essential.
Less suited to mature multi-segment products. With 5 target segments and 20 different needs, the one-page format reaches its limits. Consider one board per segment or use Pichler's Extended Product Vision Board.

How to apply Product Vision Board

1
Formulate the Product Vision in one sentence
Write in one sentence the change your product creates in the world. This is not a marketing slogan, it is a strategic direction. "Making project management accessible to any non-technical team" is a vision. "Being the market leader" is a financial objective, not a vision. Test: if the sentence does not guide your roadmap decisions, it is too vague. Output: a one-sentence product vision, validated by the product owner and sponsor.
2
Identify the priority Target Group
Describe the user segment you are targeting first. Be specific: "product managers at B2B SaaS startups with 10 to 50 employees" is a segment. "Professionals" is not. If you target everyone, you target no one. For a product launch, choose a single segment. For a mature product, identify the most strategic segment. Output: a documented persona or target segment.
3
List the Target Group Needs
Identify 3 to 5 fundamental needs that your target group is trying to solve. Frame them as problems, not solutions. "Loses 2 hours per week consolidating feedback from 4 different tools" is a need. "Needs a centralized dashboard" is a disguised solution. Validate these needs through user interviews, not internal assumptions. Output: 3 to 5 needs validated by user research.
4
Describe the Product (differentiating features)
List the 3 to 5 features or characteristics that set your product apart from the competition. These are not all the features, only those that make your target group choose you over a competitor or the status quo. Be specific: "real-time collaboration on priorities" is differentiating; "intuitive interface" is not. Output: 3 to 5 product differentiators.
5
Define the Business Objectives
Write the 2 to 3 business results the product must achieve. Revenue, number of active users, market share, churn reduction. These objectives connect the product vision to the company strategy. Without them, the vision remains an intellectual exercise with no financial grounding. Output: 2 to 3 measurable business objectives with dates.
6
Assemble the board on a single page
Fill in the Product Vision Board template with all five sections. The one-page format is non-negotiable: if it does not fit on one page, you have not made enough choices. Use Roman Pichler's official template, a whiteboard, or a tool like Miro or Confluence. Output: complete Product Vision Board on a single page.
7
Validate the board in a workshop with stakeholders
Present the board to the extended team (engineering, design, marketing, sales, leadership). The goal is not to reach consensus on every word, but to verify that no one has a fundamentally different vision of the product. If the CTO and CMO read two different products on the same board, you have an alignment problem to solve now, not in 6 months. Output: validated board with adjustments from the discussion.
8
Revisit the board at every strategic change
The Product Vision Board is not an archive document. Revisit it every quarter, after a pivot, after significant market feedback, or when the team starts saying "we no longer know why we are building this feature." If the Vision or Target Group changes, all sections below must be revalidated. Output: updated board with a changelog of modifications.