---
id: value-proposition-jtbd
title: "Value Proposition & Jobs-to-be-Done — JTBD, ODI & the VPC"
category: marketing
platform: both
tags: [value-proposition, jtbd, jobs-to-be-done, positioning, canvas]
sources: ["https://www.christenseninstitute.org/theory/jobs-to-be-done/", "https://hbr.org/2016/09/know-your-customers-jobs-to-be-done", "https://strategyn.com/outcome-driven-innovation-process/", "https://en.wikipedia.org/wiki/Outcome-Driven_Innovation", "https://www.strategyzer.com/library/value-proposition-design-book-summary", "https://www.b2binternational.com/experience/methods/faq/what-is-the-value-proposition-canvas/"]
updated: 2026-07-09
---

# Value Proposition & Jobs-to-be-Done — JTBD, ODI & the VPC

Before you design a hero section or write a headline, you need to know what *progress* the customer is trying to make. This doc covers the three tools that get you there — Jobs-to-be-Done, Outcome-Driven Innovation, and the Value Proposition Canvas — and how to turn their output into copy, features, and onboarding.

## Jobs-to-be-Done (Christensen)

- **Core idea:** people don't buy products, they **"hire" them to make progress** in a specific circumstance. If a product does the job, they hire it again; if not, they **"fire"** it and hire a substitute. Popularized by Clayton Christensen (*Competing Against Luck*, HBR "Know Your Customers' Jobs to Be Done").
- **A job is progress, not a product.** Define it as *the progress a person is trying to make in a given circumstance* — e.g. "help me feel confident I won't miss anything important today," not "a to-do app." Products change; jobs are remarkably stable over time. Anchoring on the job frees you from your current solution.
- **Every job has three dimensions:**
  - **Functional** — the practical task/outcome (get from A to B; schedule a meeting without back-and-forth).
  - **Social** — how the customer wants to be *perceived* by others (look organized, look competent to a client).
  - **Emotional** — how they want to *feel* or avoid feeling (in control, unstressed, not embarrassed by a double-booking).
  - Miss the social/emotional dimensions and your product competes on features alone — and loses to whatever *feels* better.
- **The milkshake story** (Christensen's teaching case): a fast-food chain couldn't grow morning milkshake sales by tweaking flavor. Interviews revealed the real job: commuters "hired" a thick shake to make a long, boring drive interesting and stave off mid-morning hunger — one-handed, not messy, lasting the whole commute. **Its competitors weren't other milkshakes; they were bananas, bagels, and boredom.** The lesson: define the job and the competitive set through the customer's circumstance, not your product category.
- **Competition is defined by the job.** Your rivals are everything the customer might hire to make the same progress — including doing nothing, a spreadsheet, or a habit. Name that set honestly.

### The Forces of Progress (why people switch — or don't)

Every switch to a new solution is a tug-of-war between four forces. Design around all four, not just the first two:

- **Push** — the frustration with the current situation that makes the person want change.
- **Pull** — the attraction of the new solution (the promised progress).
- **Anxiety** — fear of the new (will it work? will I look foolish? is it hard to switch?).
- **Habit/inertia** — the comfort of the current way, even when it's bad.
- **Rule:** Push + Pull must beat Anxiety + Habit for adoption. Most products over-invest in Pull (features/benefits) and ignore the two forces holding people back. Onboarding, guarantees, migration tools, and social proof exist to *reduce anxiety and inertia* — often a bigger lever than adding pull.

### Running a JTBD (switch) interview

- Interview recent switchers and reconstruct the **timeline** of their decision: first thought, passive looking, active looking, deciding, first use. Find the trigger that created the push.
- Ask what they "fired" and why, what they nearly hired instead, and what almost stopped them. You're mapping circumstance and the four forces — not asking them to design features.

### Two schools (know which you're using)

- **Christensen ("big" JTBD)** — qualitative, story-driven, focused on the high-level job and circumstance; best for discovery, positioning, and finding the real competitive set.
- **Ulwick ("small" JTBD / ODI, below)** — granular, quantitative, breaks the job into measurable outcomes; best for prioritizing what to build once the job is known. They complement each other.

## Outcome-Driven Innovation (Ulwick)

Tony Ulwick's ODI operationalizes JTBD — it turns "understand the job" into a measurable, prioritizable process. (Ulwick worked from the original JTBD lineage; ODI is the quantitative arm.)

- **Break the job into its steps**, then capture the **desired outcomes** customers use to judge success at each step. These are the metrics of the job.
- **Desired-outcome statement format** — deliberately solution-free and stable over time:
  **[direction of improvement] + [unit of measure] + [object of control] + [contextual clarifier]**
  - e.g. *"Minimize the time it takes to confirm that all attendees have agreed on a meeting slot."*
  - e.g. *"Minimize the likelihood of double-booking a room across calendars."*
  - Note there's no feature named — outcomes describe what "good" means, leaving solution space open.
- **Opportunity scoring** — survey customers on each outcome for **Importance** and current **Satisfaction**, each on a 1–10 scale, then:
  **Opportunity = Importance + max(Importance − Satisfaction, 0)**
  - **High importance + low satisfaction = underserved** = the biggest opportunity. High importance + high satisfaction = already served (don't over-invest). Low importance = ignore.
  - This gives an objective, ranked map of where to innovate instead of guessing which features matter.
- **Use ODI when you can talk to enough customers to quantify.** For early or low-volume products, use JTBD qualitatively and the VPC (below) to structure hypotheses.

## The Value Proposition Canvas (Osterwalder)

Alexander Osterwalder's VPC (from *Value Proposition Design*, Strategyzer) is the tool that maps what you offer against what the customer needs, and makes "fit" visible. It zooms into two blocks of the Business Model Canvas: a customer segment and its value proposition.

### Customer Profile (right side — the circle) — observe, don't invent

- **Customer Jobs** — the functional, social, and emotional jobs they're trying to get done (straight from JTBD).
- **Pains** — the bad outcomes, obstacles, risks, and frustrations before/during/after the job (wasted time, errors, anxiety, cost).
- **Gains** — the outcomes and benefits they want: required, expected, desired, and unexpected/delight.
- Rank each by importance to the customer, not by how easily you can address it.

### Value Map (left side — the square) — what you build

- **Products & Services** — what your offering actually is.
- **Pain Relievers** — specifically how your offering removes or reduces the ranked pains.
- **Gain Creators** — specifically how it produces the ranked gains.

### Achieving Fit

- **Fit is achieved when your pain relievers address the customer's most important pains and your gain creators produce their most important gains** — not every pain and gain, the ones that rank highest.
- Three levels of fit: **problem–solution fit** (evidence the jobs/pains/gains are real, on paper), **product–market fit** (the market actually responds), **business-model fit** (it's profitable/scalable). The canvas earns level 1; the market grants levels 2–3.
- A canvas full of relievers that map to trivial pains is a mismatch dressed up as a value prop. Match to what's important.

## How JTBD/VPC Differ From — and Feed — Positioning

Positioning is covered separately; keep the roles distinct:

- **JTBD / VPC map customer desire from the inside out** — what progress a person wants, and how your offering serves it. They're generative: they *produce* the raw material.
- **Positioning frames that offering within a competitive market from the outside in** — which category you compete in, against which alternatives, and why you win for a target segment.
- **The handoff:** the underserved outcomes (ODI), the highest-ranked pains/gains, and the well-defined job become the *inputs* to positioning — they tell you which value to lead with and which competitive frame is credible. Do JTBD/VPC first; position second. Positioning without a validated job is a claim with no ground under it.

## Turning a Value Prop Into Copy, Features & Onboarding

The point of all this is to change what you say and build. Map each analysis output to a concrete artifact:

- **Hero copy** — lead with the **highest-priority job stated as progress**, in the customer's words, not your feature. Headline = the job/outcome; subhead = the top pain relieved or gain created; the emotional dimension sets the tone. Avoid category jargon ("collaborative scheduling platform"); say the progress ("Book the meeting in one message, not ten").
- **Feature framing** — never list a feature raw. Frame it as **[feature] → [pain it relieves / gain it creates] → [job it advances]**. On the page, the benefit (relief/gain) is the headline; the feature is the proof.
- **Onboarding** — sequence steps to reach the **first desired outcome (the aha moment) as fast as possible**. Order steps by which outcomes rank highest, cut anything that doesn't advance the top job, and confirm progress explicitly ("You're all set — attendees will see your open slots"). Onboarding is where you *deliver* the value prop, not just describe it.
- **Objection handling / FAQ** — pull directly from the ranked pains; each top pain the product can't fully remove deserves a reassurance.

## Worked Example — a Scheduling App

**Job (JTBD):** "Help me lock in a meeting time with people outside my company without the back-and-forth email chain — and without looking disorganized to a client."
- Functional: agree on a time fast. Social: appear professional/on-top-of-it. Emotional: relief from the nagging dread of a missed or double-booked meeting.
- Circumstance: coordinating across calendars I can't see. Competitors: email threads, a Doodle poll, a virtual assistant, giving up and phoning.

**Desired outcomes (ODI):**
- "Minimize the time to converge on a slot that works for all attendees." (Importance 9 / Satisfaction 3 → **Opportunity 15 — underserved**)
- "Minimize the likelihood of double-booking across my calendars." (Imp 8 / Sat 4 → Opp 12)
- "Minimize the effort to reschedule when one attendee drops." (Imp 7 / Sat 3 → Opp 11)
- "Minimize the chance the invitee thinks the process felt impersonal." (Imp 6 / Sat 6 → Opp 6 — already served, don't lead here)

**VPC:**
- *Pains:* endless email ping-pong; timezone mistakes; double-bookings; looking scattered to clients.
- *Gains:* one link that just works; automatic timezone handling; a professional impression; calendar always accurate.
- *Pain relievers:* share-a-link availability; real-time two-way calendar sync; conflict detection.
- *Gain creators:* branded booking page; instant confirmations; auto-added video links.
- *Fit:* the top pain (back-and-forth, Opp 15) is met head-on by the availability link + sync — lead with that.

**Resulting artifacts:**
- **Hero headline:** "Stop emailing back and forth to book a meeting."
- **Subhead:** "Share one link. They pick a time that's actually free on your calendar. Done."
- **Feature framing:** "Two-way calendar sync → never get double-booked → walk into every client meeting looking on top of it."
- **Onboarding first outcome:** connect calendar → copy your booking link → (aha) see the first real booking land on your calendar automatically. Everything else waits.

## Messaging Hierarchy (assemble the page in this order)

Once the job, outcomes, and fit are settled, lay the message out top to bottom:

1. **Job/outcome headline** — the progress, in the customer's words.
2. **Primary pain reliever or gain creator** — the single most important one (highest-ranked), as the subhead.
3. **Proof** — the feature(s) that make the claim credible, each framed benefit-first.
4. **Anxiety reducers** — guarantees, security, ease-of-switching, social proof — to beat the anxiety/inertia forces.
5. **CTA** — phrased as the next step toward progress ("Get your booking link"), not generic ("Sign up").

## Common Mistakes

- **Describing the product, not the progress.** "All-in-one scheduling platform" says nothing about the customer's job.
- **Leading with an already-satisfied gain.** If ODI shows an outcome is high-satisfaction, don't build your pitch on it — you're competing where everyone's already good.
- **Inventing pains/gains from inside the building.** The customer profile must come from research (interviews, switch stories), not a brainstorm.
- **Mapping relievers to trivial pains.** Fit means addressing the *important* pains/gains, not merely the most numerous.
- **Skipping straight to positioning.** Without a validated job, the competitive frame has no foundation.

## Sources

- Christensen Institute — [Jobs to Be Done Theory](https://www.christenseninstitute.org/theory/jobs-to-be-done/)
- Clayton Christensen et al. — [Know Your Customers' "Jobs to Be Done" (HBR)](https://hbr.org/2016/09/know-your-customers-jobs-to-be-done)
- Strategyn (Tony Ulwick) — [Outcome-Driven Innovation Process](https://strategyn.com/outcome-driven-innovation-process/); [ODI overview (Wikipedia)](https://en.wikipedia.org/wiki/Outcome-Driven_Innovation)
- Strategyzer (Osterwalder) — [Value Proposition Design summary](https://www.strategyzer.com/library/value-proposition-design-book-summary)
- B2B International — [What is the Value Proposition Canvas](https://www.b2binternational.com/experience/methods/faq/what-is-the-value-proposition-canvas/)