Session Brief: Lean Canvas

Goal

Artifact: Lean Canvas

Working Question

Which assumptions about problem, target group, and business model must be tested next before investing further?

Context

Current state of customer conversations; existing competitor overview; known constraints (budget, compliance, platform); if available, an initial JTBD statement.

Setup

• Format: Method session
• Duration: 45-90 min
• Mode: Workshop or async
• Participants: A venture owner (often Product Lead or founder); a facilitator; one to four additional people from Product, Engineering, or Business with domain knowledge.
• Owner: A venture owner (often Product Lead or founder)
• 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 Lean Canvas. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Lean canvas template as nine-box grid (digital in Miro, FigJam, or A1 print); sticky notes or digital notes; timer; one color per hypothesis-risk class.

Preparation

Place the canvas on a shared workspace and sequence boxes (1 Problem, 2 Customer Segments, 3 Unique Value Proposition, 4 Solution, 5 Channels, 6 Revenue, 7 Cost, 8 Key Metrics, 9 Unfair Advantage). Set timer to 60 min. Rule: max three sticky notes per box.

Agenda

1. Phase 1: Problem and customer segments (15 min) Owner: Facilitator Action: Note up to three top problems of target users, each with current workaround. Narrow customer segments to a concrete early-adopter subgroup, not "all SMEs". Hint: If the problem is a feature request ("we need a dashboard"), it is too late. Step back: which decision or task fails without this feature? Output: Lean Canvas

2. Phase 2: UVP and solution (15 min) Owner: Facilitator Action: Formulate a unique value proposition in one sentence that names outcome, not product. Sketch solution in three bullet points only afterwards. Hint: UVP first, solution last. Teams that start with solution risk building a canvas around the existing idea and miss alternatives. Output: Core Assumptions

3. Phase 3: Channels, revenue, cost (15 min) Owner: Facilitator Action: Reduce channels to those early adopters already use today. Define revenue streams with pricing model and realistic willingness to pay per segment. Keep cost structure at MVP stage, not end state. Hint: Channel "SEO" is too generic. Be specific: which query, what volume, what competitors on page 1. Output: Experiment Backlog

4. Phase 4: Key metrics and unfair advantage (10 min) Owner: Facilitator Action: Name three to five metrics that indicate progress (activation, retention, revenue). Enter unfair advantage only if it is not easily copyable, otherwise leave the field empty. Hint: If unfair advantage reads "better team" or "more experience," it is not defensible. Empty is more honest than a slogan. Output: Lean Canvas

5. Phase 5: Risk ranking (10 min) Owner: Owner Action: Mark each box in red if assumption is unverified and failure would invalidate the model. Move top 3 risks to the experiment backlog. Hint: Five to seven red boxes at start are normal. The goal is prioritization, not completeness. Output: Core 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: Lean Canvas

Closeout

• Update result artifact: Lean Canvas
• Define location, version, and review recipients.
• Define owner, next step, and review date.

Lean Canvas: Lean Canvas

Working Question

Which assumptions about problem, target group, and business model must be tested next before investing further?

Context

Current state of customer conversations; existing competitor overview; known constraints (budget, compliance, platform); if available, an initial JTBD statement.

Participants

• Owner: A venture owner (often Product Lead or founder)
• Participants: A venture owner (often Product Lead or founder); a facilitator; one to four additional people from Product, Engineering, or Business with domain knowledge.

Input

Lean canvas template as nine-box grid (digital in Miro, FigJam, or A1 print); sticky notes or digital notes; timer; one color per hypothesis-risk class.

Template

Lean 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

• Lean Canvas:
• Core assumptions:
• Experiment backlog:

Open questions

• ...

Next step

Owner, date, success signal.

Completion Check

• Lean Canvas is complete enough for review:
• Location:
• Version / status:
• Review by:
• Next step:

Next Step

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