Method guideProduct Strategy

Lean Canvas

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium

Time45-90 min

Participants1-6

FormatWorkshop + async

MaturityCanonical

Plan Lean Canvas work

Prerequisite

What needs to be finished first

Complete firstOne product bet

A clear scope, initial audience, and decision question are known.

Without scope, several bets mix and the fields become generic.

Complete firstAccess to learning signals

Observations, interviews, or planned access to affected people exist or are marked as gaps.

Without access, the canvas remains an unsupported idea list.

Preparation

What needs to be ready before start

Materials

Lean Canvas template with nine fields, notes, pens, existing observations, and a place for hypothesis tests.

People / roles

A facilitator protects scope and hypothesis status. Participants bring customer, product, and economic perspectives. An owner follows up on tests.

Pre-read

Gather customer signals, known alternatives, initial costs, and possible channels.

Time needed

45 to 90 minutes for a first draft. Validation and experiments are planned separately.

Setup

Use one surface per bet. Mark statements as fact, assumption, or open question. Leave missing fields empty or name the knowledge gap.

Core question

The one question this method answers

Which assumptions about problem, segment, solution, and economics must we test next?

Flow

Phases with goal, actions, output and pitfall

Lean Canvas places problem, customer segments, solution, and business assumptions in nine fields. Each statement remains a hypothesis until suitable evidence supports it.

Lean Canvas

Fictional neighborhood tool-lending example

Nine canonical core fields for an early product bet.

Problem

Which unresolved problems matter for the segment?

Fictional: Rare use often does not justify buying a tool.

Solution

Which minimum solution addresses the prioritized problem?

Fictional: Checked tools with simple pickup.

Unique Value Proposition

What concrete progress do you promise the segment?

Fictional: The right tool is available nearby.

Unfair Advantage

What is hard to copy and already plausible?

Leave blank if no real advantage is evidenced.

Customer Segments

Who experiences the problem most strongly? Who are the early adopters?

Fictional: Households with a renovation date soon as early searchers.

Key Metrics

Which few signals show behavior or learning?

Fictional: Searches, pickups, and repeat use.

Channels

How will you reach the segment for learning and delivery?

Fictional: Neighborhood groups and local meeting places.

Cost Structure

Which major costs apply to this bet?

Fictional: Maintenance, support, and storage.

Revenue Streams

Which revenue assumption applies to this bet?

Fictional: A possible fee per lending transaction.

LEANSTACK Lean Canvas

1
Scope
Bound the bet and segment
Goal
A testable frame is defined.
Inputs for this step
- Product idea or existing offer
- Decision question
Actions
- State the bet in one sentence
- name the primary segment and early adopters
- record scope and date
Output
Bounded product bet and segment
One version covers one bet.
Quality check
The segment is narrower than a whole market. Early adopters are described as people with an early need or search.
Pitfall
The canvas speaks about several audiences at once. Choose one audience and park other variants as separate versions.
Timing: 10–15 minutes
2
Problem
Clarify problems and alternatives
Goal
Problem hypotheses are separated from solution ideas.
Inputs for this step
- Observations or interviews
- Known workarounds
Actions
- Write up to three problems
- collect existing alternatives and workarounds
- mark evidence status for each statement
Output
Prioritized problem hypotheses and alternatives
Missing evidence remains visible as a hypothesis.
Quality check
Problems describe an affected state. Alternatives include doing nothing and manual paths.
Pitfall
Problem fields already contain features. Extract the feature and describe the state it should change.
Timing: 15–20 minutes
3
Solution
Sketch solution and value proposition
Goal
Solution, value, and differentiation are linked as hypotheses.
Inputs for this step
- Prioritized problems
- Early user perspectives
Actions
- Sketch the smallest fitting solution
- sharpen the unique value proposition around customer progress
- name an unfair advantage only when a plausible distinction exists
Output
Solution sketch with value proposition
Unbacked statements remain assumptions.
Quality check
The solution addresses a prioritized problem. Unfair advantage is more than an easily copied feature.
Pitfall
The UVP promises technical properties instead of customer value. Rewrite it around the progress the segment should make.
Timing: 15–20 minutes
4
Economics
Connect channels, metrics, and economics
Goal
The bet shows how it could be reached, measured, and sustained.
Inputs for this step
- Solution sketch
- Initial cost and revenue assumptions
Actions
- describe channels and first activation
- choose a few useful key metrics
- record revenue and cost structure as assumptions
Output
Connected operating and learning assumptions
Do not present unsupported numbers as forecasts.
Quality check
Metrics show behavior or learning rather than only reach. Costs and revenues refer to the same bet.
Pitfall
Many metrics hide the one learning question. Reduce to signals that enable a next decision.
Timing: 15–20 minutes
5
Risks
Prioritize critical hypotheses
Goal
A small experiment backlog with decision criteria is ready.
Inputs for this step
- Completed Lean Canvas
- Evidence gaps
Actions
- order statements by risk and learning value
- define the next test with audience, signal, and timebox
- record criteria for continue, change, or stop
Output
Prioritized hypotheses and experiment backlog
The canvas starts learning; it is not proof.
Quality check
The first test addresses a critical uncertainty. Signal and decision criterion are observable.
Pitfall
The team treats completed fields as a validated business model. Write hypothesis status and planned evidence next to critical statements.
Timing: 15–20 minutes

Artifact

What comes out at the end

Sketch: what the artifact looks like

Lean Canvas · Startup-RisikenProblem, Segment, Nutzenversprechen, Lösung, Kanäle, Kennzahlen, Kosten und Erlöse auf einer Seite prüfen

Form

Dated Lean Canvas with nine fields, evidence status, critical hypotheses, and a prioritized experiment backlog.

Versioning / ownership

Each version gets a date, scope, and owner. New evidence creates a new version or linked change.

Tool alternatives

Paper canvas with sticky notes
Digital whiteboard
Document with nine fields

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

lean-canvas-beispiel.md

Concrete filled scenario, fictional example

Fictional example: neighborhood tool lending

Bet: Households with occasional needs borrow checked tools close to home.

Problem: Buying and storing tools is poor value for rare use. Alternative: Hardware store, neighbor, or doing nothing.

Hypothesis: Reliable pickup matters more than maximum variety. This is unproven.

Next test: Run a small manually supported lending round and observe searches, pickups, and repeat use.

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

Bound the bet and segmentThe canvas speaks about several audiences at once.View in phase
Clarify problems and alternativesProblem fields already contain features.View in phase
Sketch solution and value propositionThe UVP promises technical properties instead of customer value.View in phase
Connect channels, metrics, and economicsMany metrics hide the one learning question.View in phase
Prioritize critical hypothesesThe team treats completed fields as a validated business model.View in phase

Stop criteria

When to pause, resolve prerequisites, or choose another approach

The bet or primary segment is unclear.

Several business models are mixed on one surface.

A critical problem has no access to people or learning signal.

The team treats canvas statements as proof.

No decision criterion exists for the next test.

Where to go next?

Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.

Product Discovery

Assumption Mapping

Sorts the canvas's critical hypotheses by importance and evidence strength.

Product Discovery

Riskiest Assumption Test

Tests the riskiest hypothesis from the experiment backlog first and directly.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profile More methods