methodatlas
Session Builder

Plan my session

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

Method session3-4 h for first canvas, then 1 h maintenance per quarterWorkshop or asyncProduct Canvas

Session: Product Canvas

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 Canvas. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Goal and metrics

    30 min

    Put release business goal on one card, max one sentence. Two to three metrics with baseline and target. If there are multiple goals, prioritize to one. Hint: If the team cannot name a single goal, the vision is too unclear. Pause canvas and clarify vision with stakeholder first.

    FacilitatorProduct Canvas
  2. 2

    Phase 2: Persona and needs

    40 min

    Place persona card. Add 3-5 top needs or Jobs to Be Done per persona below it. Needs must align with business goal. Hint: Needs are outcomes ("send finished invoice faster"), not features ("invoice button"). If the list slips into features, ask back for outcome.

    FacilitatorProduct Assumptions
  3. 3

    Phase 3: Big picture

    45 min

    Sketch user flows, storyboards or journeys per top need. Visualize how the need is addressed without fixing features. Hint: Big picture is sketch, not pixel design. If designers want to perfect it, stop and move to discovery spike.

    FacilitatorScope Notes
  4. 4

    Phase 4: Product details

    45 min

    Derive epics or feature slices per need. Rough effort per epic (T-shirt). Mark constraints (regulatory, technical) as red cards. Hint: More than ten epics per release is unrealistic. If the list explodes, trigger prioritization with stakeholder instead of capturing everything.

    FacilitatorProduct Canvas
  5. 5

    Phase 5: MVP slice and handover

    30-45 min

    Cut MVP slice from epics that moves at least one metric. Transfer slice to roadmap and backlog with owner and date. Hint: MVP slice must plausibly move a metric, otherwise it is not an MVP. If no movement is expected, cut again or use another method.

    OwnerProduct Assumptions
  6. 6

    Publish artifact

    10 min

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

    OwnerProduct Canvas
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Product Canvas

Goal

Artifact: Product Canvas

Working Question

Which needs of which persona does the product measurably solve in the next release, and which features are necessary rather than desirable?

Context

Product vision; persona profiles; known business goals and KPIs; current architecture constraints; list of existing features with usage.

Setup

  • Format: Method session
  • Duration: 3-4 h for first canvas, then 1 h maintenance per quarter
  • Mode: Workshop or async
  • Participants: One facilitator (usually Product Lead); Product Owner; one UX Lead; two to three engineers; optionally stakeholder from business or operations. Maximum seven people.
  • Owner: One facilitator (usually Product Lead)
  • 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 Canvas. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Product Canvas template (Roman Pichler or own variant) as A0 print or Miro board; stickies in four colors; markers; link to vision and persona; current roadmap notes.

Preparation

Canvas with quadrants: top left goal and metrics, bottom left persona and needs, top right big picture (journeys, storyboards), bottom right product details (epics, constraints). Quadrants pre-labeled and empty.

Agenda

  1. Phase 1: Goal and metrics (30 min) Owner: Facilitator Action: Put release business goal on one card, max one sentence. Two to three metrics with baseline and target. If there are multiple goals, prioritize to one. Hint: If the team cannot name a single goal, the vision is too unclear. Pause canvas and clarify vision with stakeholder first. Output: Product Canvas

  2. Phase 2: Persona and needs (40 min) Owner: Facilitator Action: Place persona card. Add 3-5 top needs or Jobs to Be Done per persona below it. Needs must align with business goal. Hint: Needs are outcomes ("send finished invoice faster"), not features ("invoice button"). If the list slips into features, ask back for outcome. Output: Product Assumptions

  3. Phase 3: Big picture (45 min) Owner: Facilitator Action: Sketch user flows, storyboards or journeys per top need. Visualize how the need is addressed without fixing features. Hint: Big picture is sketch, not pixel design. If designers want to perfect it, stop and move to discovery spike. Output: Scope Notes

  4. Phase 4: Product details (45 min) Owner: Facilitator Action: Derive epics or feature slices per need. Rough effort per epic (T-shirt). Mark constraints (regulatory, technical) as red cards. Hint: More than ten epics per release is unrealistic. If the list explodes, trigger prioritization with stakeholder instead of capturing everything. Output: Product Canvas

  5. Phase 5: MVP slice and handover (30-45 min) Owner: Owner Action: Cut MVP slice from epics that moves at least one metric. Transfer slice to roadmap and backlog with owner and date. Hint: MVP slice must plausibly move a metric, otherwise it is not an MVP. If no movement is expected, cut again or use another method. Output: Product Assumptions

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

Closeout

  • Update result artifact: Product Canvas
  • 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 Canvas: Product Canvas

Working Question

Which needs of which persona does the product measurably solve in the next release, and which features are necessary rather than desirable?

Context

Product vision; persona profiles; known business goals and KPIs; current architecture constraints; list of existing features with usage.

Participants

  • Owner: One facilitator (usually Product Lead)
  • Participants: One facilitator (usually Product Lead); Product Owner; one UX Lead; two to three engineers; optionally stakeholder from business or operations. Maximum seven people.

Input

Product Canvas template (Roman Pichler or own variant) as A0 print or Miro board; stickies in four colors; markers; link to vision and persona; current roadmap notes.

Template

Product Canvas 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 Canvas:
  • Product assumptions:
  • Scope notes:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Product Canvas 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 Canvas Working Template

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

product-canvas-working-template.md

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

Product Canvas 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 Canvas:
  • Product assumptions:
  • Scope notes:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Product Canvas.
  • One canvas per quarter or major release. Archive previous version with date and release tag. Changes during a release as edit log at canvas footer, not overwriting.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet