JTBD‑Based Segmentation Framework

1. What Is the JTBD‑Based Segmentation Framework?

JTBD stands for Jobs‑to‑Be‑Done. A JTBD‑based segmentation groups customers according to the underlying “jobs” they are hiring a product or service to accomplish—functional, emotional, and social outcomes—rather than by demographics, firmographics, or surface behaviors. It answers a simple question with profound implications: “When customers choose us (or a substitute), what progress are they trying to make, in what circumstance, and what outcomes matter most?”

Within the Segmentation, Targeting & Positioning (STP) toolkit, JTBD segmentation is a needs/outcomes‑first approach. It distinguishes distinct “job contexts” (e.g., “get dinner on the table fast with no planning” vs. “discover new recipes to cook with family on weekends”) and clusters customers by patterns of unmet outcomes. Those clusters guide proposition design, pricing fences, channel choices, and message architecture far more directly than broad personas or demographics.

Practitioners use JTBD segmentation when they need to break out of category conventions, stop competing on feature checklists, and design offerings that align to what customers actually hire them to do—often revealing non‑obvious competitors and white space.

2. Origin and Background

Jobs‑to‑Be‑Done was popularized by Clayton M. Christensen (Harvard Business School) and colleagues—especially the 2005 HBR article “Marketing Malpractice: The Cause and the Cure,” and later the book “Competing Against Luck” (2016). Tony Ulwick advanced a related quantitative approach, Outcome‑Driven Innovation (ODI), from the 1990s onward, emphasizing measurable customer outcomes and opportunity scoring. Practitioners such as Bob Moesta helped operationalize JTBD in product development.

Why it was created: to solve a recurring failure in marketing and innovation—teams optimize features for an average persona or a demographic slice and miss the underlying progress customers seek in specific contexts. JTBD reframes markets around customer progress and outcomes, enabling clearer segmentation and more resonant propositions.

How it became widely known: through HBS teaching, innovation case studies (the “milkshake” story among them), and adoption in design thinking and product strategy circles. Over time, the method has been codified into research and quantification practices suitable for enterprise decision‑making.

3. How JTBD‑Based Segmentation Works

The core logic: identify the distinct jobs customers hire solutions to do, enumerate the outcomes that define success for those jobs, quantify which outcomes are underserved for whom, then cluster customers by patterns of unmet outcomes. Those clusters are your segments.

Key Concepts

• Job (in a circumstance): The progress a customer seeks in a specific context, articulated as “When [situation], I want to [progress], so I can [outcome].” Jobs have functional, emotional, and social facets.
• Outcomes: Stable, measurable statements that describe how customers judge success on the job (e.g., “minimize time to decide what to cook,” “avoid wasting ingredients,” “feel proud serving guests”). Unlike features, outcomes don’t change as technology shifts.
• Importance and satisfaction: For each outcome, customers rate how important it is and how well current solutions satisfy it. Patterns of high-importance/low-satisfaction signal opportunity.
• Opportunity scoring: A prioritization method combining importance and satisfaction to identify underserved outcomes (e.g., “high importance and low satisfaction” ranks highest). Some practitioners formalize this with an opportunity index; the principle is to focus on outcomes that matter and are poorly served.
• Segmentation by unmet outcomes: Cluster customers based on their outcome importance/unmetness profiles and contexts. Each cluster becomes a JTBD segment with distinct implications for product, pricing, channels, and messaging.

Typical Outputs

• 3–6 JTBD segments, each defined by a job context and a set of underserved outcomes
• A prioritized list of outcomes per segment to guide proposition design and roadmap
• Price/willingness‑to‑pay indications tied to critical outcomes
• Activation “handles” (context cues, behaviors, and data attributes) to identify segments in channels and CRM
• Messaging architecture and proof points aligned to each segment’s outcomes

4. When to Use JTBD‑Based Segmentation

Most helpful when you are:

• Designing or repositioning a product/portfolio and need sharper, outcome‑anchored guidance
• Facing commoditization and feature wars; seeking to create white space or defend margin
• Entering new segments or markets where traditional demographic cuts are misleading
• Setting pricing/packaging fences aligned to value delivered on specific outcomes
• Clarifying channel and message choices based on use contexts (weekday rush vs. weekend exploration; field vs. remote; mobile vs. desktop)

Company types: Applicable across B2C and B2B. Especially powerful for services, software/SaaS, consumer packaged goods with diverse usage contexts, and regulated categories where outcomes (e.g., risk reduction, compliance) dominate choice.

Data and time requirements: A practical program takes 6–10 weeks: qualitative discovery (2–3 weeks), survey instrument design and fielding (2–3 weeks), analytics and segmentation (2–3 weeks), activation planning (1–2 weeks). Lightweight versions can be run in 3–5 weeks if you leverage existing data and a focused survey.

When it’s less useful or can mislead:

• Ultra‑homogeneous categories with a single dominant decision criterion (pure price markets)
• When teams substitute features for outcomes (confusing solution with job), or skip quant validation—leading to arbitrary segments
• When you cannot identify segments in your channels (no activation handles or proxy signals)

How it’s used today: Modern practice blends qualitative JTBD discovery with quantitative opportunity analysis, segments on unmet outcomes, and connects segments to activation via behavioral and contextual signals in CDPs and platforms.

5. How to Apply JTBD‑Based Segmentation: Step‑by‑Step

1. Clarify scope, decisions, and success metrics

   Define the domain (“grocery shopping from inspiration to clean‑up,” “mid‑market IT security onboarding”), the decisions you must inform (positioning, roadmap, pricing/packaging, channel mix), and how you’ll judge success (win rate, ASP, CLV uplift, NPS). Be explicit about the time horizon and geographies.

2. Conduct JTBD qualitative discovery

   Interview 15–30 customers across contexts. Elicit job stories using prompts:

   “When I [situation], I want to [progress], so I can [outcome].”

   Probe for functional, emotional, and social dimensions; switching moments; non‑consumption (what they do instead); and substitutes. Map the “job journey” (define, locate resources, prepare, execute, monitor, modify, conclude) to surface outcomes at each step.

3. Translate into outcome statements

   Convert insights into precise, testable outcomes (avoid features). Good outcomes are stable, quantifiable, and solution‑agnostic. Examples:

   – “Reduce time to decide what to buy for dinner”

   – “Increase confidence that my data migration will not corrupt records”

   – “Minimize social awkwardness when sharing a new dish with guests”

4. Design and field the quant survey

   For each outcome, ask respondents to rate:

   – Importance (e.g., 1–10)

   – Satisfaction with current solutions (e.g., 1–10)

   Include context questions (when, where, with whom), current solution set, switching barriers, and willingness‑to‑pay indicators. Target sample sizes: B2C n=1,000–3,000; B2B decision‑makers n=300–800. Ensure coverage of key contexts and segments.

5. Quantify opportunity and identify underserved outcomes

   Compute opportunity scores combining importance and dissatisfaction to rank outcomes (the spirit: high‑importance + low‑satisfaction = big opportunity). You don’t need fancy equations; the principle is to spotlight outcomes that matter and are poorly served, by context and cohort.

6. Segment on patterns of unmet outcomes

   Use clustering (e.g., k‑means, hierarchical, latent class) on importance/unmetness vectors and contextual variables to derive 3–6 segments. Each segment should exhibit a distinct unmet‑outcome profile and context (e.g., “Weeknight Time‑Starved Cooks,” “Weekend Social Hosts,” “Health‑Optimizing Planners”). Validate segment stability and interpretability.

7. Size and value segments

   Estimate segment share and contribution (revenue, margin, CLV). Link segments to current behavior (SKU mix, channel usage), price sensitivity, and churn patterns. Identify non‑consumption segments (where customers opt out entirely)—often fertile ground for growth.

8. Translate segments into propositions, pricing, and channels

   For each segment, define:

   – Value proposition focused on top underserved outcomes

   – Feature/experience priorities (what to raise/reduce/eliminate/create)

   – Pricing/packaging fences aligned to valued outcomes (e.g., guaranteed delivery windows, advanced automation features, concierge support)

   – Channel and message choices keyed to context (mobile push vs. email; retail vs. D2C; expert reviews vs. creator content)

9. Map to activation handles

   Define how to identify segments in the wild: contextual signals (time/day, device, location), behavioral cues (content consumed, features used), product ownership, and self‑declared preferences. Build a lightweight classification model or rules to assign a probable JTBD segment in your CDP/CRM.

10. Test, iterate, and govern

    Run segment‑specific experiments (creative, offers, features). Track performance by segment (conversion, ASP, retention, NPS). Refresh outcome ratings and segment assignment annually or upon major product/channel changes. Maintain a change log for outcome taxonomy and segments.

6. Example: JTBD‑Based Segmentation in Action

Context: A $380M online grocery and meal solutions company faces slowing growth and margin pressure. Surveys and analytics suggest “busy families” isn’t a precise enough target. Leadership needs to redesign positioning, assortment, and subscription pricing to re‑accelerate growth without deeper discounting.

Approach: A 9‑week JTBD program (qual discovery, outcome survey n=2,200, segmentation, activation plan).

• Qual discovery: Interviews revealed four recurring jobs:

  – “Weeknight Rescue”: get a complete meal on the table fast with minimal planning/cleanup.

  – “Weekend Social”: host friends/family with confidence and variety.

  – “Health Reset”: control ingredients and portions; hit nutrition goals.

  – “Budget Stretch”: feed the household while minimizing waste and total spend.

• Outcomes (examples): “Reduce time to decide what to cook,” “Minimize pre‑prep tasks,” “Increase confidence that everyone will like the meal,” “Reduce risk of over‑budget basket,” “Avoid ingredient waste,” “Hit macro targets without complicated tracking.”
• Quant results: Opportunity analysis showed two underserved clusters:

  – Time‑Starved Weeknighters (34%): highest importance on decision/cleanup time and “don’t forget an item”; low satisfaction with current solutions.

  – Health‑Optimizing Planners (21%): high importance on ingredient control and macro targets; low satisfaction with simple planning tools.

  Two additional segments emerged:

  – Budget Stretchers (26%): price and waste minimization dominant.

  – Social Hosts (19%): variety and “proud to serve guests” outcomes dominant.

Decisions and actions:

• Positioning and assortment:

  – Time‑Starved: “Dinner done in 20”—pre‑bundled weeknight kits, minimal prep, one‑pan recipes, guaranteed substitutions; app UX defaults to 20‑minute meals.

  – Health‑Optimizing: macro‑friendly collections with nutrition filters, smart swaps, and nutritionist‑verified plans; clear labels and tracking integration.

• Pricing/packaging: Introduced “Express” subscription (Time‑Starved) with guaranteed slot windows and prep‑light kits at a modest premium; launched “Macro+” add‑on (Health‑Optimizing) priced as a feature fence (recipes, tracking, coaching access). Budget Stretchers received “Smart Saver” bundles and waste‑reduction tips, fenced to price‑sensitive SKUs.
• Channels and activation: Time‑Starved segment identified by evening mobile browsing + frequent saved recipes; push notifications 4–6 pm with “20‑minute dinner” carousels. Health‑Optimizing targeted via newsletter content + app filters; creator partnerships with nutritionists. Budget Stretchers reached via retail media and price‑lock promotions, fenced to maintain margin.

Outcomes (two quarters): Order frequency +11% in Time‑Starved; churn −9% in Health‑Optimizing subscriptions; gross margin +160 bps overall due to feature fences and reduced blanket discounting. NPS rose 8 points among Social Hosts after curated weekend modules. The company institutionalized JTBD segments in the CDP, powering distinct lifecycle journeys.

7. Strengths and Limitations

Strengths

• Explains choice: Anchors segmentation in outcomes that truly drive decisions, not proxies.
• Actionable design: Directly informs proposition, pricing fences, channels, and message architecture.
• Reveals non‑obvious competition: Identifies substitutes (DIY, adjacent categories) and non‑consumption.
• Durable: Outcomes remain stable even as technologies shift, providing long‑lived guidance.

Limitations

• Research intensity: Requires disciplined qualitative discovery and quantitative validation.
• Activation challenge: Jobs and outcomes must be mapped to detectable signals for targeting; otherwise insights stay theoretical.
• Risk of “feature creep” masquerading as outcomes: Teams sometimes confuse solutions with ends; rigor is required.
• Not a silver bullet: Must be paired with economics (CLV, margin), operational feasibility, and go‑to‑market realities.

8. Common Pitfalls (and How to Avoid Them)

• Confusing features with outcomes

  What goes wrong: The outcome list becomes a feature wish‑list.

  Avoid: Phrase outcomes as measures of success (“reduce time to…,” “increase confidence that…”), not solutions (“add a button”).

• Vague, catch‑all jobs

  What goes wrong: Jobs like “eat healthy” or “do my job better” are too broad to guide choices.

  Avoid: Anchor jobs in specific circumstances; include functional, emotional, and social facets.

• Skipping quant validation

  What goes wrong: Segments reflect opinions, not market reality.

  Avoid: Field an outcome survey, quantify importance/satisfaction, and cluster on unmetness patterns.

• No activation mapping

  What goes wrong: Teams can’t find segments in channels.

  Avoid: Define context and behavioral proxies; build a classifier in your CDP; test assignment accuracy.

• Ignoring economics

  What goes wrong: Investing in low‑value segments or outcomes.

  Avoid: Size and value segments; tie to CLV, margin, and payback; prioritize feasibility.

• One‑and‑done

  What goes wrong: Outcomes shift with channels and competitors; your plan lags reality.

  Avoid: Refresh annually or on major shifts; monitor performance by segment.

9. How JTBD‑Based Segmentation Relates to Other Frameworks

• Needs‑Based and Attitudinal Segmentation: JTBD is a form of needs segmentation with sharper outcome language. Attitudinal work adds beliefs and preferences; together they inform messaging and proofs.
• Personas: Personas humanize segments with context and journey details. Use JTBD to define the backbone (outcomes), then wrap with persona narratives for cross‑functional use.
• RFM/CLV: Value lenses prioritize investment across JTBD segments. High‑CLV segments may receive premium experiences or faster roadmaps for their outcomes.
• Conjoint/Max‑Diff (Pricing and Features): After defining outcomes and segments, quantify trade‑offs and willingness‑to‑pay per segment to design tiers and fences.
• Customer Journey Mapping: JTBD clarifies the outcomes customers pursue at each journey stage; journey mapping identifies friction and channels to fulfill those outcomes.
• Micro‑Segmentation / Next‑Best‑Action: JTBD guides what to say and offer; NBA selects the next action at the individual/moment level, using JTBD assignment as a feature.
• Porter’s Five Forces / Competitive Landscape: JTBD reveals where substitutes and non‑consumption sit; use structure tools to assess attractiveness and potential to defend margin.

Choosing tools: Use JTBD to define what customers hire you to do and where you are under‑serving. Layer conjoint to price, personas to align teams, CLV to prioritize, and NBA to execute.

10. Key Takeaways

• JTBD‑based segmentation groups customers by the outcomes they seek in specific contexts—and where they feel underserved.
• It directly informs proposition, pricing fences, channels, and messaging, avoiding feature wars and demographic stereotypes.
• Success requires rigorous outcome definition, quant validation, and activation mapping into your data and channels.
• Pair JTBD with CLV/value metrics, conjoint for pricing, and personas/journeys for cross‑functional adoption.
• Refresh periodically; outcomes are durable but channels, competitors, and contexts evolve.

11. FAQs About JTBD‑Based Segmentation

Is JTBD the same as needs‑based segmentation?
JTBD is a precise form of needs‑based segmentation that articulates needs as outcomes in a specific context (“When I…, I want to…, so I can…”). Many “needs” segmentations are less disciplined. JTBD’s outcome language makes it more actionable for design, pricing, and messaging.

Do we need quantitative surveys, or can we rely on interviews?
Use interviews to discover jobs and outcomes; use surveys to quantify importance and satisfaction at scale and to segment on unmetness patterns. Without quant, you risk overfitting to anecdote and missing economic prioritization.

How does JTBD connect to pricing?
Price fences should align to outcomes. After defining JTBD segments, use conjoint or max‑diff to quantify willingness‑to‑pay for features that deliver priority outcomes (e.g., guaranteed delivery windows for “Weeknight Rescue,” advanced automation for “IT Onboarding”).

Can B2B companies use JTBD segmentation?
Absolutely. Define jobs at the buying‑center level and by context (e.g., “onboard new employees securely,” “prove ROI to the CFO in 30 days”). Pair JTBD with firmographics/technographics to build ICPs and sales plays.

How long does a decision‑grade JTBD project take?
Typically 6–10 weeks from discovery to activation plan, depending on scope and data readiness. Lightweight versions can be done in 3–5 weeks to inform an upcoming launch or repositioning.

What’s the difference between JTBD and personas?
JTBD defines the outcomes and contexts that drive choice; personas humanize priority segments for execution (roles, language, journey). Use both: JTBD for the “what and why,” personas for the “who and how.”

How do we identify JTBD segments in channels?
Define activation handles: context (time/device/location), behaviors (filters used, content consumed), product ownership, simple preference prompts. Build a classifier in your CDP/CRM to assign likely JTBD segments and validate with in‑market tests.