methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session1-2 hWorkshop or asyncProduct Vision Board

Session: Product Vision Board

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 2-8. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Product Vision Board. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 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? Hint: If the vision contains feature lists or tech stack, it is not vision but roadmap. Vision must survive even if the product pivots.

    FacilitatorProduct Vision Board
  2. 2

    Phase 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. Hint: If target group is "everyone" or "companies", it is too broad. Market size and reachability cannot be estimated without concretization.

    FacilitatorVision Statement
  3. 3

    Phase 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. Hint: Needs are often confused with solutions ("needs app"). Need is problem or outcome ("needs faster clarity on accounting status"), product is solution.

    FacilitatorAnnahmen und Validierungsfragen
  4. 4

    Phase 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. Hint: 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.

    FacilitatorProduct Vision Board
  5. 5

    Phase 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. Hint: Business Goals without measurement are PR. At least one metric per goal with source. If source is missing, mark as assumption with needs setup.

    FacilitatorVision Statement
  6. 6

    Phase 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. Hint: Vision Board without marked assumptions suggests certainty that does not exist. At least 5 assumptions are realistic in every early phase.

    OwnerAnnahmen und Validierungsfragen
  7. 7

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerProduct Vision Board
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Product Vision Board

Goal

Artifact: Product Vision Board

Working Question

Which shareable product vision connects target group, needs, product idea and business goals so discovery and roadmap can align to it?

Context

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.

Setup

  • Format: Method session
  • Duration: 1-2 h
  • Mode: Workshop or async
  • Participants: 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.
  • Owner: One facilitator who guides through the fields and marks assumptions
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Product Vision Board. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Product Vision Board template (5 fields: Vision, Target Group, Needs, Product, Business Goals) as whiteboard, Miro, FigJam or printed A1; stickies; pens; visible timer.

Preparation

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.

Agenda

  1. Phase 1: Vision (15-20 min) Owner: Facilitator Action: 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? Hint: If the vision contains feature lists or tech stack, it is not vision but roadmap. Vision must survive even if the product pivots. Output: Product Vision Board

  2. Phase 2: Target Group (15-20 min) Owner: Facilitator Action: Name target group and segments concretely. For each segment, note market size, reachability and strategic priority. Narrow to Primary and Secondary Segment if needed. Hint: If target group is "everyone" or "companies", it is too broad. Market size and reachability cannot be estimated without concretization. Output: Vision Statement

  3. Phase 3: Needs (20-25 min) Owner: Facilitator Action: Name core needs and problems of the target group from research. Link source per need (interview, data, market report). Label uncertain needs as assumption. Hint: Needs are often confused with solutions ("needs app"). Need is problem or outcome ("needs faster clarity on accounting status"), product is solution. Output: Annahmen und Validierungsfragen

  4. Phase 4: Product (15-20 min) Owner: Facilitator Action: 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. Hint: 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. Output: Product Vision Board

  5. Phase 5: Business Goals (15-20 min) Owner: Facilitator Action: Define 2-4 Business Goals as measurable outcomes (revenue, market share, cost saving, strategic lock-in). Per goal, success measurement and rough timeframe. Hint: Business Goals without measurement are PR. At least one metric per goal with source. If source is missing, mark as assumption with needs setup. Output: Vision Statement

  6. Phase 6: Assumptions and next steps (15-20 min) Owner: Owner Action: Review all assumption stickies. Per assumption: risk (what happens if wrong?), validation path (interview, data, experiment), owner and deadline. Define review rhythm. Hint: Vision Board without marked assumptions suggests certainty that does not exist. At least 5 assumptions are realistic in every early phase. Output: Annahmen und Validierungsfragen

  7. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Product Vision Board

Closeout

  • Update result artifact: Product Vision Board
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Product Vision Board: Product Vision Board

Working Question

Which shareable product vision connects target group, needs, product idea and business goals so discovery and roadmap can align to it?

Context

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.

Participants

  • Owner: One facilitator who guides through the fields and marks assumptions
  • Participants: 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.

Input

Product Vision Board template (5 fields: Vision, Target Group, Needs, Product, Business Goals) as whiteboard, Miro, FigJam or printed A1; stickies; pens; visible timer.

Template

Product Vision Board Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Product vision board:
  • Vision statement:
  • Assumptions and validation questions:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Product Vision Board is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Product Vision Board Working Template

View templateCompact working template for Product Vision Board with context, input, output artifacts, and next step.
canvas

product-vision-board-working-template.md

Compact working template for Product Vision Board with context, input, output artifacts, and next step.

Product Vision Board Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Product vision board:
  • Vision statement:
  • Assumptions and validation questions:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Product Vision Board.
  • 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.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet