Value Proposition Design Using Jobs to Be Done

The Value Proposition Precision Problem

Every B2B company has a value proposition. Most of them sound the same.

“We deliver innovative solutions that help our customers improve efficiency and reduce costs.” Change the company name and this sentence could describe any industrial manufacturer in Europe. It communicates nothing specific. It differentiates from nothing. It resonates with no one in particular.

The problem is not that product teams lack effort or intelligence. The problem is that traditional value proposition design methods — even well-regarded ones like Osterwalder’s Value Proposition Canvas — lack the precision needed to create propositions that genuinely resonate with specific customer segments.

Osterwalder asks you to map customer “pains” and “gains” to your product’s “pain relievers” and “gain creators.” This is a useful thinking structure. But it leaves the hardest question unanswered: Which pains and gains matter most, and how do you know?

Jobs to Be Done, specifically through Outcome-Driven Innovation, provides the quantitative rigor that value proposition design has been missing. When you know — with statistical precision — which desired outcomes are most important and most underserved for a specific customer segment, crafting a value proposition that resonates becomes dramatically easier.

Why Most B2B Value Propositions Fail

Before we build the solution, let us diagnose the disease. B2B value propositions fail for predictable, structural reasons.

Reason 1: They Describe Products, Not Outcomes

“Our crane offers 500-ton lifting capacity with a 60-meter boom radius.”

This is a product specification, not a value proposition. The customer does not care about lifting capacity in the abstract. They care about getting their job done — and “lifting capacity” is only valuable insofar as it enables a specific outcome.

Reason 2: They Target Everyone

“We serve the construction industry.” The construction industry includes residential homebuilders and bridge constructors, interior fit-out specialists and offshore platform installers. Their jobs, outcomes, and unmet needs are fundamentally different. A value proposition that speaks to all of them speaks to none of them.

Reason 3: They Claim Benefits Without Evidence

“Our solution reduces downtime by up to 40%.” Up to 40% for whom? Under what conditions? Compared to what alternative? Unsubstantiated benefit claims erode trust, especially with technically sophisticated B2B buyers who have heard similar promises from every vendor.

Reason 4: They Mirror Competitors

When companies benchmark their value propositions against competitors, they converge on the same language and the same claims. “Industry-leading reliability.” “Best-in-class service.” “Innovative technology.” These are table stakes claims — they describe the minimum expectation, not a differentiating position.

The JTBD Approach to Value Proposition Design

Jobs to Be Done transforms value proposition design from an exercise in copywriting into a discipline of strategic positioning. Here is how.

Foundation: The Job, Not the Product

JTBD starts with the customer’s job to be done — the functional task they are trying to accomplish, stated in a solution-agnostic way.

The customer of a crane manufacturer is not trying to “use a crane.” They are trying to “move heavy materials to the required location on a construction site.” This distinction is not semantic — it opens the aperture to all the outcomes that matter, not just the ones your current product addresses.

Precision: Outcome Statements, Not Pain Points

Where traditional methods use vague “pain points,” JTBD uses precise outcome statements. Each outcome follows the format: Direction of improvement + metric + object of control + contextual clarifier.

Compare:

• Pain point: “Changeovers take too long” (vague — how long is too long? For whom? In what context?)
• Outcome statement: “Minimize the time required to reposition the crane between lifting locations on a multi-story construction site” (specific, measurable, contextual)

When you have 80-120 of these outcome statements for a job, you have a complete map of what the customer is trying to accomplish — not what they want from your product, but what they need from any solution.

Quantification: Opportunity Scores

For each outcome, quantitative research measures importance and satisfaction. The opportunity score (Importance + max(Importance - Satisfaction, 0)) reveals which outcomes are most underserved.

This is where the magic happens for value proposition design. Instead of guessing which customer needs to emphasize, you know. Outcomes with scores above 12 are significantly underserved — customers care deeply but current solutions fall short. These are the outcomes your value proposition should address.

Segmentation: Different Propositions for Different Jobs

Cluster analysis on outcome data often reveals segments with distinct patterns of unmet needs. Each segment needs a different value proposition — not a different brand, but a different emphasis on which outcomes you address.

Case Study: From “Lifting Capacity” to “Job Completion Speed”

Consider a crane manufacturer (composite example based on patterns observed across client engagements) that had traditionally positioned its products around technical specifications: lifting capacity, boom length, wind resistance ratings.

A JTBD study with 220 construction site managers and crane operators identified 94 desired outcomes for the job “move heavy materials to the required location on a construction site.” The top underserved outcomes were:

Notice what is not on this list: lifting capacity. It scored 8.9 on importance but 7.8 on satisfaction — an opportunity score of 10.0. Customers cared about it, but current solutions were doing a reasonable job. It was table stakes, not a differentiator.

The top underserved outcomes all related to speed and availability — not lifting power, but the speed at which the crane could be set up, repositioned, and made available for the next task.

The Old Value Proposition

“Industry-leading lifting capacity and reliability for demanding construction projects.”

The New Value Proposition

“Complete more lifts per day with the fastest setup and repositioning times in the industry. Designed for construction teams who cannot afford to wait.”

The new proposition is:

• Specific: It addresses measurable outcomes (setup time, repositioning time)
• Differentiated: It competes on speed, not capacity (where all competitors were already adequate)
• Segment-targeted: It speaks to time-pressured construction teams, not everyone in construction
• Verifiable: Claims about setup and repositioning times can be demonstrated and measured

The biggest shift in value proposition design is moving from what your product does to what your customer’s job requires. When a crane manufacturer stops talking about lifting capacity — their engineering pride and joy — and starts talking about job completion speed — what their customers actually lose sleep over — the commercial impact is transformative. I have watched this shift generate double-digit revenue growth in product lines that were flat for years.

Beyond Osterwalder: A JTBD Value Proposition Framework

Osterwalder’s Value Proposition Canvas maps pains and gains to pain relievers and gain creators. It is a good starting framework but lacks two critical elements: quantification and segment specificity.

Here is an enhanced framework that incorporates JTBD:

Step 1: Define the Job Context

Instead of starting with a generic “customer profile,” start with a specific job context:

• Who is the job executor? (role, not company)
• What is the job to be done? (functional task, solution-agnostic)
• In what context is the job performed? (environment, constraints, frequency)

Step 2: Map Outcomes, Not Pains

Replace “pains” and “gains” with quantified outcome statements:

• Underserved outcomes (opportunity score >12): These are your differentiation opportunities
• Adequately served outcomes (opportunity score 10-12): These are table stakes — must perform, but not differentiating
• Overserved outcomes (opportunity score <10): These are candidates for cost reduction — you may be providing more than customers need

Step 3: Build Segment-Specific Propositions

For each customer segment (identified through cluster analysis on outcome data):

• Select the top 3-5 underserved outcomes
• Design product features that specifically address those outcomes
• Craft messaging that directly connects product capabilities to the outcomes customers care most about

Step 4: Quantify the Value

For each underserved outcome your product addresses, quantify the value delivered:

• Time savings: “Setup time reduced from 4 hours to 45 minutes”
• Error reduction: “First-pass quality rate improved from 82% to 97%”
• Cost impact: “Material waste during changeover reduced by 68%”

These quantified claims are far more persuasive than generic benefit statements — especially for technically sophisticated B2B buyers.

Step 5: Test and Validate

Present the value proposition (with supporting product concept) to target segment customers. Measure:

• Does it increase predicted satisfaction on the target underserved outcomes?
• Does it resonate more strongly with the target segment than with non-target segments?
• Does it differentiate from competitor propositions in ways that customers value?

Value Proposition Architecture: Product, Segment, and Company Levels

Enterprise companies need value propositions at multiple levels. JTBD provides coherence across all three:

Company-Level Value Proposition

Broad, aspirational, and tied to the overall job your portfolio addresses: “We help construction teams complete projects faster by eliminating the equipment bottlenecks that cause delays.”

Segment-Level Value Proposition

Specific to a target segment’s top underserved outcomes: “For high-rise construction teams, we eliminate the setup and repositioning delays that cost an average of 2.3 hours per working day.”

Product-Level Value Proposition

Tied to specific product features that address specific outcomes: “The [Product Name]’s modular base system reduces setup time from 4 hours to 45 minutes — the fastest in the industry for cranes above 200 tons.”

When all three levels are anchored in the same JTBD research, messaging is consistent from brand advertising to sales pitch to technical specification. The salesperson on the trade show floor and the marketing team creating content are telling the same story — not because of brand guidelines, but because they are addressing the same quantified customer outcomes.

Practical Application: Building Your JTBD Value Proposition

Here is a step-by-step checklist for creating a JTBD-grounded value proposition:

Preparation (requires completed JTBD/ODI research):

• Complete job map with all steps and desired outcomes documented
• Quantitative research completed with opportunity scores calculated
• Customer segments identified through cluster analysis
• Target segment selected based on opportunity size, accessibility, and strategic fit

Value Proposition Development:

• Select top 3-5 underserved outcomes for your target segment
• Identify how your product (or proposed product) addresses each outcome
• Quantify the improvement your product delivers on each outcome
• Draft the proposition using outcome language, not product language
• Test: Can a competitor make the same claim truthfully? If yes, sharpen further
• Validate with target segment customers through concept testing

Activation:

• Translate the value proposition into sales enablement materials
• Align product marketing messaging across channels
• Train sales teams on the outcome language and supporting evidence
• Create segment-specific collateral that connects product features to target outcomes

For guidance on structuring your JTBD analysis, see our JTBD canvas guide.

For the complete JTBD framework, see our Jobs to Be Done guide.

Frequently Asked Questions