Value Proposition Canvas
I first heard about this topic when I joined Apple Developer Academy @ BINUS, Tangerang, where one of the mentors, Ci Valen, told me that a value proposition canvas is a tool for marketing experts, product owners, and value creators.
She started her presentation with this statement:
Give a reason for users to choose (and buy) your product
Why do we need it?
Most products don't fail because they're poorly built: they fail because nobody wanted the thing being solved in the first place. Teams jump straight to "what should we build?" before answering "what does the user actually need relief from, or want more of?"
A value proposition canvas forces that order. It splits into two halves that have to face each other:
- User Profile (right side), who the user is: their jobs, pains, and gains.
- Value Map (left side), what you're offering: your products/services, pain relievers, and gain creators.
You don't get to fill in the Value Map until you've honestly filled in the User Profile. That's the whole point: it's a forcing function against building features nobody asked for.
How do we create it?
The canvas above breaks the process into three steps:
- Understand your user: map their jobs, pains, and gains first. No shortcuts here; this is research, not guessing.
- Identify how you can help: for every pain and gain you found, ask what would relieve it or create it. This is where the Value Map starts taking shape.
- Brainstorm the possible products: only now do you brainstorm actual features or services, each one traceable back to a specific pain or gain.
The two halves connect through what Ci Valen called product-user fit: a pain reliever is the remedy for something that's actively hurting the user, and a gain creator is the vitamin, something they didn't strictly need, but that makes their life better. Good products usually need at least one solid remedy; vitamins alone rarely convince someone to switch.
User Profile: Understanding Your User
User Jobs
What are the main tasks that users are trying to accomplish
Describe what users are trying to get done. These can be functional or emotional. Use the information you have from "User Persona" because from that you can analyze what kind of user it was and what they jobs that they are gonna do. for example :
- Users: Busy professionals aged 25โ40 years old. Working in office 8 to 5. Aspire to have a rising professional career.
- Jobs To Be Done: Learn a new language efficiently to improve professional opportunities.
Pains
Describe Bad Outcomes, risks, obstacles, and problems related to the user's jobs.
- What are the biggest challenges the users face in accomplishing their tasks?
- What frustates the users the most about current solutions?
here are some examples of pains :
- Boredom or lack of engagement in language learning
- Hard to maintain commitment
- Lack of time
- Feeling overwhelmed by language complexity
- Lack of energy transporting to the offline course
- Difficulty finding effective learning methods
Gains
Describe the positive outcomes users want to achieve when their job is done.
- What would make the users tasks easier or more enjoyable?
- What outcomes or benefits are the user hoping to achieve?
here are some examples of gains :
- Cost-effective language learning
- Improved cognitive function
- Ability to communicate with foreign colleagues/clients
- Flexibility to learn anytime, everywhere
- Culture enrichment
- Self actualization
- Extra personal values
- Increased career opportunities
Value Map: Building What You Offer
Once the User Profile is honest, flip to the other half of the canvas. For every job, pain, and gain you just wrote down, ask: what would we actually build to address this?
Products & Services
What are you offering?
A plain list of what the user gets: features, services, or the product itself. Nothing fancy here yet, just the inventory. Following the language-learning example:
- Mobile app with short, gamified lessons
- Live conversation practice with native speakers
- Progress tracking and streaks
- Offline mode for commutes
Pain Relievers
Describe how your product or service alleviates specific customer pains.
- Which of the user's pains does each item directly remove or reduce?
- Does it address the pain at its source, or just soften it?
mapped to the pains above:
- Boredom / lack of engagement โ gamified lessons instead of static drills
- Hard to maintain commitment โ daily streaks and reminders
- Lack of time โ 5-minute micro-lessons instead of hour-long classes
- Overwhelmed by complexity โ adaptive difficulty that adjusts to the learner
Gain Creators
Describe how your product or service produces outcomes the customer expects, desires, or would be surprised by.
- Which of the user's gains does each item create?
- Does it go beyond the baseline, or match what competitors already offer?
mapped to the gains above:
- Flexibility to learn anytime โ offline mode and short sessions fit any schedule
- Communicate with colleagues/clients โ live practice with native speakers, not just vocabulary drills
- Career opportunities โ certificates shareable on LinkedIn
- Cost-effective learning โ subscription cheaper than in-person courses
Product-User Fit
This is where the two halves are checked against each other. A pain reliever only counts if it maps to a pain you actually wrote down; a gain creator only counts if it maps to a real gain. If an item on the Value Map doesn't trace back to something on the User Profile, it's a feature you want to build, not one the user needs. Cut it or park it.
The strongest items are remedies: pain relievers that solve something actively hurting the user, like the 5-minute micro-lessons fixing "lack of time." Vitamins (gain creators like a shareable certificate) are worth having, but they rarely close a sale on their own. If your canvas is all vitamins and no remedies, that's a sign to go back to the Pains section and dig deeper before shipping anything.
Click to show love
Discussion
Configure NEXT_PUBLIC_GISCUS_* environment variables to enable comments.