methodatlas
Session Builder

Plan my session

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

Method session2-3 hWorkshop or asyncCompleted Lean UX Canvas

Session: Lean UX 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 3-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 Completed Lean UX Canvas. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Business Problem

    15-20 min

    State the current business problem in one to two sentences. Who is affected, what happens, how much does it cost? Back up with data or observations. Hint: If the business problem is phrased as “we need more users,” it is too vague. Require a concrete, measurable pain point.

    FacilitatorCompleted Lean UX Canvas
  2. 2

    Phase 2: Business Outcomes

    15-20 min

    Desired business outcomes: measurable changes (revenue, conversion, cost, retention). Maximum 3 outcomes. For each outcome define baseline and target value. Hint: Outcomes without metrics are wishful thinking. For each outcome define a number and source. If a metric is missing, mark it as assumption and plan measurement setup.

    FacilitatorHypothesis list
  3. 3

    Phase 3: Users

    20-25 min

    Which user segments are affected? For each segment provide concrete description with behavior and context. If personas exist, reference them. Hint: Anyone writing “all users” has not segmented. Lean-UX-Canvas requires narrowing to one to three segments, otherwise User Outcomes are not specific.

    FacilitatorFirst experiment
  4. 4

    Phase 4: User Outcomes

    20-25 min

    What do users want to achieve (Jobs to be Done)? Which behavior change would produce the business outcome? Connect Users and Business Outcomes. Hint: User Outcomes and business outcomes must be logically linked. If users reach their outcomes, business outcomes should naturally follow. If not, test the model.

    FacilitatorCompleted Lean UX Canvas
  5. 5

    Phase 5: Solutions

    20-25 min

    Collect multiple solution ideas that enable user outcomes. At least 5 options. Use 1-2 sentences per idea, no feature-level detail. Hint: If only one solution is written in Phase 5, Phase 4 was too narrow. Optionality is the value, the experiment decides later.

    FacilitatorHypothesis list
  6. 6

    Phase 6: Hypotheses

    15-20 min

    Formulate hypotheses for top solutions: “We believe solution X at user Y will produce outcome Z.” Maximum 3 hypotheses for the first test. Hint: Hypotheses without clear subject-solution-outcome structure are not testable. Keep the format strict, otherwise Phase 8 cannot be derived.

    OwnerFirst experiment
  7. 7

    Publish artifact

    10 min

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

    OwnerCompleted Lean UX Canvas
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Lean UX Canvas

Goal

Artifact: Completed Lean UX Canvas

Working Question

Which testable hypothesis links business problem, desired outcomes, users, solution idea, and critical assumptions so that the next experiment is clear?

Context

Current business problem in one sentence; strategy or goal anchor; research snippets (interviews, data); known assumptions from earlier initiatives; desired workshop outcome (hypothesis list, first experiment).

Setup

  • Format: Method session
  • Duration: 2-3 h
  • Mode: Workshop or async
  • Participants: One facilitator (PM, designer); cross-functional team (PM, designer, engineer, possibly business); sponsor for reviews and outcome setting; stakeholders as input providers.
  • Owner: One facilitator (PM, designer)
  • 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 Completed Lean UX Canvas. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Lean-UX-Canvas template (8 fields) as whiteboard, Miro, FigJam, or A1 printout; sticky notes in two colors (content, assumption); pens; visible timer; research excerpts as pre-read.

Preparation

Display the canvas template with fields 1-8: (1) Business Problem, (2) Business Outcomes, (3) Users, (4) User Outcomes, (5) Solutions, (6) Hypotheses, (7) Critical Assumptions, (8) Experiments. Keep sequence.

Agenda

  1. Phase 1: Business Problem (15-20 min) Owner: Facilitator Action: State the current business problem in one to two sentences. Who is affected, what happens, how much does it cost? Back up with data or observations. Hint: If the business problem is phrased as “we need more users,” it is too vague. Require a concrete, measurable pain point. Output: Completed Lean UX Canvas

  2. Phase 2: Business Outcomes (15-20 min) Owner: Facilitator Action: Desired business outcomes: measurable changes (revenue, conversion, cost, retention). Maximum 3 outcomes. For each outcome define baseline and target value. Hint: Outcomes without metrics are wishful thinking. For each outcome define a number and source. If a metric is missing, mark it as assumption and plan measurement setup. Output: Hypothesis list

  3. Phase 3: Users (20-25 min) Owner: Facilitator Action: Which user segments are affected? For each segment provide concrete description with behavior and context. If personas exist, reference them. Hint: Anyone writing “all users” has not segmented. Lean-UX-Canvas requires narrowing to one to three segments, otherwise User Outcomes are not specific. Output: First experiment

  4. Phase 4: User Outcomes (20-25 min) Owner: Facilitator Action: What do users want to achieve (Jobs to be Done)? Which behavior change would produce the business outcome? Connect Users and Business Outcomes. Hint: User Outcomes and business outcomes must be logically linked. If users reach their outcomes, business outcomes should naturally follow. If not, test the model. Output: Completed Lean UX Canvas

  5. Phase 5: Solutions (20-25 min) Owner: Facilitator Action: Collect multiple solution ideas that enable user outcomes. At least 5 options. Use 1-2 sentences per idea, no feature-level detail. Hint: If only one solution is written in Phase 5, Phase 4 was too narrow. Optionality is the value, the experiment decides later. Output: Hypothesis list

  6. Phase 6: Hypotheses (15-20 min) Owner: Owner Action: Formulate hypotheses for top solutions: “We believe solution X at user Y will produce outcome Z.” Maximum 3 hypotheses for the first test. Hint: Hypotheses without clear subject-solution-outcome structure are not testable. Keep the format strict, otherwise Phase 8 cannot be derived. Output: First experiment

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

Closeout

  • Update result artifact: Completed Lean UX 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

Completed Lean UX Canvas: Lean UX Canvas

Working Question

Which testable hypothesis links business problem, desired outcomes, users, solution idea, and critical assumptions so that the next experiment is clear?

Context

Current business problem in one sentence; strategy or goal anchor; research snippets (interviews, data); known assumptions from earlier initiatives; desired workshop outcome (hypothesis list, first experiment).

Participants

  • Owner: One facilitator (PM, designer)
  • Participants: One facilitator (PM, designer); cross-functional team (PM, designer, engineer, possibly business); sponsor for reviews and outcome setting; stakeholders as input providers.

Input

Lean-UX-Canvas template (8 fields) as whiteboard, Miro, FigJam, or A1 printout; sticky notes in two colors (content, assumption); pens; visible timer; research excerpts as pre-read.

Template

Lean UX 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

  • Completed Lean UX Canvas:
  • Hypothesis list:
  • First experiment:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Completed Lean UX 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

Lean UX Canvas Working Template

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

lean-ux-canvas-working-template.md

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

Lean UX 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

  • Completed Lean UX Canvas:
  • Hypothesis list:
  • First experiment:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Completed Lean UX Canvas.
  • Date and initiative in the header. New canvas for each iteration with reference to prior version. Track hypothesis status (open, in test, confirmed, disproven). Run experiments in a separate experiment log.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet