methodatlas
RunsheetProduct Strategy

Value Proposition Canvas

ComplexityMedium
Time1-2 h
Participants2-8
FormatWorkshop + async
MaturityCanonical
01

Prerequisite

What needs to be finished first

Complete firstJobs-to-be-Done

A documented JTBD statement or at least 5 structured job interviews exist, from which Customer Jobs can be derived.

Without: Without JTBD foundation, jobs are constructed from assumptions or personas and the customer profile becomes fuzzy.
Complete firstUser Interviews

At least 5 fresh interviews from the target segment exist, with pains and gains evidenced by exact quotes.

Without: Without quotes, pains and gains become generic and the canvas cannot be checked.
02

Preparation

What needs to be ready before start

Materials

Value Proposition Canvas template (Strategyzer format): circle for Customer Profile (Jobs, Pains, Gains), square for Value Map (Products & Services, Pain Relievers, Gain Creators); stickies in two colors; markers; interview quotes at hand.

People / roles

Product owner or strategy lead as facilitator; one to three discovery people with interview context; one to three people who know the product (PM, designer, engineer).

Pre-read

Defined customer segment (one concrete subgroup); interview quotes sorted by job context; current list of product features and services; known complaints and positive mentions.

Time needed

1-2 h

Setup

Place canvas on shared surface. Customer Profile right, Value Map left. Rule: complete right side first, then left. Timer at 90 min.

03

Core question

The one question this method answers

How exactly do the segment's pains, gains, and jobs fit the provider's products, pain relievers, and gain creators, and where is the gap?

04

Flow

Marker: Phase

StepDurationActionHint
1Phase 1: Fix customer segment
10 minName concrete sub-persona with role, context, and situation. One canvas iteration equals one segment.Generic segments make the canvas unusable. Prefer several specific canvases over one blurred one.
2Phase 2: Customer jobs
15-20 minIdentify functional, social, and emotional jobs. Write each job as verb sentence from customer view. Mark top 3-5.Jobs are tasks, not wishes about your product. "Submit tax return on time" is a job; "have a better app" is a wish.
3Phase 3: Pains and gains
20-30 minPains: what annoys, blocks, costs time/money/reputation. Gains: what would be better, faster, more prestigious. Mark severity and support with interview quotes.Pains without quotes are assumptions. Generic pains such as "costs time" without specifics are filtered out.
4Phase 4: Value Map - Products and Services
10-15 minList current or planned products and services. No marketing language, only concretely what the customer receives.If a product has no direct bridge to jobs, it is either marketing or scope creep. Mark it.
5Phase 5: Pain relievers and gain creators
15-20 minFor each pain, add one or more pain relievers. For each gain, add one or more gain creators. Draw arrows from map to profile.A prioritized extreme pain without reliever is a product gap. A reliever pointing to no pain is an orphaned feature.
6Phase 6: Fit assessment
10-15 minAsk: Problem-Solution Fit, Product-Market Fit, Business Model Fit. Note gaps as hypotheses.Canvas alone does not confirm fit, it makes gaps visible. Only experiments and sales confirm fit.
05

Artifact

What comes out at the end

Form

Value Proposition Canvas as image or structured document with segment description, jobs/pains/gains and map items, plus fit-gap list with priority, hypotheses, and owner for validation experiments.

Versioning / ownership

Own canvas per segment with date and iteration in title. Create new version on each iteration, do not overwrite. Link lessons from interviews so sources remain traceable.

Tool alternatives
  • Strategyzer tool or Canvanizer
  • Miro with VPC template
  • Notion with two-column layout
  • FigJam with circular Customer Profile

value-proposition-canvas-working-template.md

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

Value Proposition Canvas Working Template

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

  • Value Proposition Canvas:
  • Fit Gaps:
  • Hypotheses:

Open questions

  • ...

Next step

Owner, date, success signal.

06

Example output

Concrete filled scenario, fictional example

value-proposition-canvas-beispiel.md

Concrete filled scenario, fictional example

Value Proposition Canvas - InvoiceFlow for solo tax advisors (v2, 2026-05-18)

Segment: tax advisors with 30-80 clients, solo or with 1-2 employees, DATEV as standard tool.

Customer Profile

Jobs (Top 3): book receipts legally compliant | inform clients promptly | keep own capacity for complex clients

Pains (prioritized):

  • EXTREME: 4-6 h/week manual receipt matching (quoted in 5/5 interviews)
  • EXTREME: VAT-code errors create rework (4/5 quoted)
  • MODERATE: client communication for missing receipts consumes time

Value Map

Products/Services: OCR receipt upload, rule matcher, DATEV export, client portal

Pain Relievers:

  • OCR + rule matcher -> receipt matching from 4 h to <30 min/week
  • Pre-filled VAT codes with plausibility check
  • Client portal with receipt upload

Fit Gaps

  • Client portal only partly addresses communication pain. Hypothesis: invitation via DATEV integration raises usage above 60%. Owner @anna, experiment CW 22.
07

Pitfalls

Recognize symptoms and steer against them

Trap

Segment too generic

Symptom

Customer Profile describes "the tax advisor" in general.

What to do

Sharpen sub-persona: role, size, tool stack, current pain. Prefer 3 specific canvases over one generic.

Trap

Pains from gut feeling

Symptom

Pains and gains are brainstormed without interview evidence.

What to do

Require source per pain/gain. What cannot be evidenced becomes hypothesis.

Trap

Map without arrows to profile

Symptom

Pain relievers and gain creators stand alone without explicit connection.

What to do

Draw arrows. Orphaned items are scope creep.

Trap

Marketing language

Symptom

Products described as innovative, intuitive, seamless.

What to do

Name concrete functionality. Use OCR upload plus rule matcher instead of buzzwords.

Trap

Fit declared without validation

Symptom

Team declares fit from canvas and plans scaling.

What to do

Canvas shows gaps, validates no fit. Need sales, retention, or real customer reactions.

08

Stop criteria

Done signals checkable in under a minute

Segment is not delimited, canvas becomes generic description.
No interview data available, pains and gains would be invented.
Product is still too vaguely defined, value map cannot become concrete.
Team understands jobs as product features rather than tasks.
Stakeholder forces a certain value proposition, canvas becomes theater.
Several segments should be represented in one canvas, sharpness is lost.

Finished the runsheet?

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