What needs to be finished first
At least 5 documented conversations or data points from the target group are available, so Target Group and Needs are not only invented internally.
What needs to be ready before start
Product Vision Board template (5 fields: Vision, Target Group, Needs, Product, Business Goals) as whiteboard, Miro, FigJam or printed A1; stickies; pens; visible timer.
One facilitator who guides through the fields and marks assumptions; Product Lead or PO as owner; 2-6 participants from engineering, design, business; sponsor for reviews if needed.
Research snippets from interviews; known business goals and constraints; existing personas or segment descriptions; previous version of Vision Board if any; definition of what is decided after the workshop.
1-2 h
Template clearly visible. Vision in the center, four fields around it. Phones away. Rule: first Vision, then Target Group, then Needs, then Product, then Business Goals. Assumption stickies in second color.
The one question this method answers
Which shareable product vision connects target group, needs, product idea and business goals so discovery and roadmap can align to it?
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Vision | 15-20 min | Formulate vision as ambitious target state in one sentence. What would be true in 3-5 years if the product is successful? Test vision: is it inspiring, focused and product-agnostic enough? | If the vision contains feature lists or tech stack, it is not vision but roadmap. Vision must survive even if the product pivots. |
2Phase 2: Target Group | 15-20 min | Name target group and segments concretely. For each segment, note market size, reachability and strategic priority. Narrow to Primary and Secondary Segment if needed. | If target group is "everyone" or "companies", it is too broad. Market size and reachability cannot be estimated without concretization. |
3Phase 3: Needs | 20-25 min | Name core needs and problems of the target group from research. Link source per need (interview, data, market report). Label uncertain needs as assumption. | Needs are often confused with solutions ("needs app"). Need is problem or outcome ("needs faster clarity on accounting status"), product is solution. |
4Phase 4: Product | 15-20 min | Sketch product roughly: what it is, what it is not, key stand-out features. Maximum 5 bullet points. Keep description deliberately rough, no feature detail. | If Product field has 20 features, it is a backlog. Limiting to 5 forces strategic selection. Stand-out features are those users would switch for. |
5Phase 5: Business Goals | 15-20 min | Define 2-4 Business Goals as measurable outcomes (revenue, market share, cost saving, strategic lock-in). Per goal, success measurement and rough timeframe. | Business Goals without measurement are PR. At least one metric per goal with source. If source is missing, mark as assumption with needs setup. |
6Phase 6: Assumptions and next steps | 15-20 min | Review all assumption stickies. Per assumption: risk (what happens if wrong?), validation path (interview, data, experiment), owner and deadline. Define review rhythm. | Vision Board without marked assumptions suggests certainty that does not exist. At least 5 assumptions are realistic in every early phase. |
What comes out at the end
Filled Product Vision Board as A1 poster, board export or markdown document; supplemented by assumption list with validation path, review cadence and links to research sources.
Date and version in header. Every update as new version (for example v0.2) with delta to previous version. Archive previous version, do not overwrite. Quarterly review as standard, ad-hoc on strategic changes.
Compact working template for Product Vision Board with context, input, output artifacts, and next step.
What is this method used for?
Which question should be answered at the end?
Which data, observations, or materials are available?
Owner, date, success signal.
Concrete filled scenario, fictional example
Concrete filled scenario, fictional example
Vision: In 4 years, solo self-employed people in DACH know their tax and liquidity position at any time without prior knowledge.
Target Group:
Needs:
Product:
Business Goals:
Top assumptions:
Review: Quarterly, next 2026-09-30.
Recognize symptoms and steer against them
Vision field contains "app that can X, Y, Z" instead of a target state.
Test question: would this vision still hold without app? If no, it is roadmap. Reformulate vision so it is product-agnostic.
Needs are plausible, nobody can name an interview note or data source.
Source mandatory per need (interview ID, survey question, data dashboard). Without source, label as assumption and plan validation path.
"SMEs in DACH" as target group, nobody can describe typical customer in one sentence.
Narrow to Primary Segment that can be described in one sentence. Other segments as Secondary with own rationale.
"Become market leader" or "be successful" is written in the field.
One measurable quantity with time horizon per goal. If metric is missing, do not include goal or mark as assumption.
Vision Board has been hanging unchanged for 12 months, reality has moved on.
Plan review cadence (quarterly) as binding in setup. Ad-hoc review on pivot, funding round or top hire. Versioning forces visible update.
Fields look certain, nobody sees which statement has been checked.
Assumption stickies in second color. At least 5 marked assumptions per board. Validation path with owner and deadline.
Done signals checkable in under a minute
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.