What needs to be finished first
At least five conversations with potential target users exist, documenting their problems and current workarounds.
A formulated JTBD statement exists or is created in the same session so problem and solution stay aligned to the user job.
What needs to be ready before start
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.
A venture owner (often Product Lead or founder); a facilitator; one to four additional people from Product, Engineering, or Business with domain knowledge.
Current state of customer conversations; existing competitor overview; known constraints (budget, compliance, platform); if available, an initial JTBD statement.
45-90 min
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.
The one question this method answers
Which assumptions about problem, target group, and business model must be tested next before investing further?
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Problem and customer segments | 15 min | 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". | 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? |
2Phase 2: UVP and solution | 15 min | Formulate a unique value proposition in one sentence that names outcome, not product. Sketch solution in three bullet points only afterwards. | UVP first, solution last. Teams that start with solution risk building a canvas around the existing idea and miss alternatives. |
3Phase 3: Channels, revenue, cost | 15 min | 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. | Channel "SEO" is too generic. Be specific: which query, what volume, what competitors on page 1. |
4Phase 4: Key metrics and unfair advantage | 10 min | 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. | If unfair advantage reads "better team" or "more experience," it is not defensible. Empty is more honest than a slogan. |
5Phase 5: Risk ranking | 10 min | Mark each box in red if assumption is unverified and failure would invalidate the model. Move top 3 risks to the experiment backlog. | Five to seven red boxes at start are normal. The goal is prioritization, not completeness. |
What comes out at the end
Lean-canvas document (image or structured document) plus experiment backlog with top three highest-risk assumptions, each linked to a validation idea, success criterion, and next owner.
Include date and iteration in title (for example `lean-canvas-v3-2026-05-20`). Keep previous versions, do not overwrite. Document after each iteration which assumption was disproven or confirmed.
Compact working template for Lean Canvas 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
Problem: (1) Solo bookkeepers lose 4 h/week on manual invoice matching. (2) Errors in VAT codes create rework. (3) No real-time cashflow visibility. Customer Segments: Solo tax advisors with 30-80 clients using DATEV. UVP: Match invoices in under 10 seconds per document and export directly to DATEV. Solution: OCR upload, rule-based matcher, DATEV export. Channels: Tax advisor forums (datev.community), chamber newsletter, recommendation via compliance software partners. Revenue: EUR 49/month per office, tiered by document volume. Cost: OCR API (~EUR 0.02/document), hosting (~EUR 200/mo), 1 FTE developer. Key Metrics: Documents per week per active office, matching accuracy, MRR. Unfair Advantage: (blank, none identified yet).
Top risks: Paid willingness for EUR 49, DATEV export complexity (technical uncertainty), chamber as channel (not tested).
Recognize symptoms and steer against them
Boxes are filled without risk marking. The result reads like a pitch deck.
Make risk ranking a required final step. No canvas leaves the session without top three risks and an experiment backlog.
Field says "SME", "mid-market", or "all ecommerce shops".
Narrow to a concrete early-adopter subgroup: sector, size, tool stack, and current pain point. If unclear, that becomes the first hypothesis.
Solution box is first filled, and problem is built backwards.
Force sequence: problem and customer segments first, solution only after UVP. For repeated sessions, keep solution box empty until phase 2.
UVP contains "revolutionary," "seamless," "intelligent" without concrete outcome.
UVP test: can the sentence be signed in front of a competitor? If yes, it is exchangeable. Add concrete numbers, time, or outcome.
Canvas is created once and never updated even as new interview data arrives.
Set iteration cadence (for example every two weeks) to re-score risk boxes. Keep last dated version visible in team wiki.
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.