Jobs-to-Be-Done (JTBD) is a product strategy framework that focuses on the underlying task or outcome a customer is trying to achieve, rather than their demographics or product features. The core principle: customers hire products to make progress in specific situations. Understanding the job — not the buyer — drives better product decisions, sharper messaging, and stronger product-market fit.
Most marketing asks "who is our customer?" JTBD asks "what are they trying to accomplish?" That shift in question changes everything — from how you build features to how you write copy to who you actually compete with.
What is Jobs-to-Be-Done (JTBD)?
JTBD defines products by the "job" customers hire them to accomplish. Clayton Christensen popularized this framework at Harvard Business School using a milkshake study. He found that morning commuters weren't buying a beverage — they were hiring the milkshake to make their commute less boring and keep them full until lunch. Different job, different product decision entirely.
The framework identifies three types of jobs customers are trying to complete:
- Functional jobs — the practical task they need to accomplish (publish SEO content consistently)
- Emotional jobs — how they want to feel doing it (confident, not anxious)
- Social jobs — how they want to be perceived (as a business that takes marketing seriously)
All three types often run simultaneously. A marketing director who hires a content tool isn't just looking for articles — she wants to feel confident her team's output matches competitors and wants her CEO to see the pipeline as under control.
A 40-year-old dentist and a 28-year-old SaaS founder can share the exact same job: "get more qualified leads from Google without doing the work myself." Traditional buyer personas would treat them as completely different segments. JTBD collapses them into one product brief.
Why Jobs-to-Be-Done matters for product and marketing
Traditional research anchors strategy to demographics. JTBD anchors it to outcomes. The difference shows up in four measurable ways:
- Better product decisions. Features get built when they serve an actual job, not because they're technically interesting. Every sprint starts with: "What job does this feature serve?"
- Clearer messaging. Outcome-focused copy converts better than feature-focused copy. "Get 30 SEO articles published monthly without hiring a team" speaks to the job. "AI-powered content platform with scheduling" describes a feature.
- Unexpected competitor mapping. A CRM doesn't just compete with other CRMs — it competes with spreadsheets, sticky notes, and a salesperson's memory. JTBD surfaces the real competitive set.
- Product-market fit signal. When customers consistently describe the same job in customer interviews, you've found the core job worth building around.
How to apply the JTBD framework
The framework runs in four stages. Each stage produces a usable artifact — not just insight.
1. Identify the job
Interview customers with two questions: "What were you trying to accomplish when you started looking for a solution?" and "What did you use before?" The answers reveal functional, emotional, and social outcomes they were chasing — not the features they evaluated.
2. Write the job statement
Use a consistent format so the job is unambiguous across the team:
When [situation],
I want to [achieve this outcome],
so I can [broader goal].
# Example
When I'm running a local business with no marketing team,
I want to publish SEO content consistently,
so I can get found on Google without doing the work myself.
3. Map the full competitive set
Define competition as anything a customer might hire for the same job. For a content tool, that includes: marketing agencies, freelancers, internal hires, DIY approaches, paid advertising, and referrals. Not just similar SaaS tools.
4. Align product and marketing to the job
Strip features that don't serve the primary job. Rewrite value propositions around the outcome. Build content that answers the job. Measure whether customers succeed at the job — not just whether they use the product.
Types of jobs in the JTBD framework
| Job Type | What it captures | Example | Marketing use |
|---|---|---|---|
| Functional | Practical task to complete | Publish 30 SEO articles per month | Product features, pricing |
| Emotional | Desired feeling during/after | Feel confident content output won't fall behind | Tone, reassurance copy |
| Social | How they want to appear to others | Be seen as the business that takes SEO seriously | Case studies, social proof |
| Consumption chain | Jobs during purchase process | Evaluate options without wasting 5 sales calls | Self-serve demos, pricing pages |
Real JTBD examples in marketing and product
Example 1 — Functional job: content production
A small business owner doesn't want "30 SEO articles per month." She wants "a steady stream of leads from Google without doing the work myself." Articles are the mechanism; the job is get leads from search, hands-free. Messaging built around the mechanism fails. Messaging built around the job converts.
Example 2 — Emotional job: reducing anxiety
A marketing director doesn't just want increased organic traffic. She wants relief from the anxiety of watching competitors publish 3x more content. The emotional job — "feel confident my content strategy is covered" — drives the buying decision as much as the functional outcome. Ignore it and your demo never closes.
Example 3 — Unexpected competition surfaced by JTBD
A project management tool company thought they competed with Asana and Monday. Customer interviews revealed the real alternative most prospects were switching from was a shared Google Sheets doc. JTBD exposed the actual competitor — and reshaped their entire onboarding messaging.
JTBD vs buyer personas — which to use
Both tools have a place. The question is what decision you're trying to make.
Use JTBD when
- Defining what to build next
- Writing conversion copy and value props
- Identifying the real competitive set
- Running customer interviews pre-launch
- Diagnosing why customers churn
Use buyer personas when
- Choosing ad targeting parameters
- Writing channel-specific tone of voice
- Selecting media placements and partnerships
- Building sales qualification criteria
- Segmenting email nurture sequences
6 best practices for applying JTBD
- Start with switch interviews. Talk to customers who recently switched to your product. Ask what triggered their search, what they tried first, and what made them commit. Switching moments reveal the job more clearly than satisfaction surveys.
- Separate the job from the solution. The job is "get leads from Google." The solution is "publish 30 SEO articles per month." Don't conflate them. New solutions for the same job emerge constantly.
- Document all three job types. Capture functional, emotional, and social jobs from interviews. The emotional and social jobs often drive purchase decisions more than functional ones.
- Run the job statement by the team. If three people on your team write the job statement differently from memory, it's not clear enough yet. Iterate until one sentence captures it.
- Map competition to the job, not the category. Ask: "What else could a customer hire to do this job?" Include non-software alternatives. This reshapes your differentiation entirely.
- Rewrite copy around the outcome, not the feature. Test two landing page versions — one feature-led, one job-led. JTBD-based copy consistently wins in A/B tests when the job is accurately identified.
Teams often write job statements like "I want an AI writing tool that produces 30 articles per month." That's a solution, not a job. The job is "publish enough content that Google starts sending me consistent leads." One describes what the product does; the other describes what the customer needs to accomplish. Build around the second one.
Common JTBD mistakes to avoid
- Skipping the interview step. You cannot guess the job from inside the building. JTBD requires real customer conversations — at minimum 8-10 switch interviews.
- Serving too many jobs. Products that try to serve 7 different jobs serve none of them well. Identify the primary job and protect it.
- Writing demographic personas disguised as jobs. "Our customer is a 35-45 year old marketing manager at a mid-market B2B SaaS" is a persona, not a job. A job starts with "I want to..."
- Ignoring emotional and social jobs. Functional jobs explain what to build. Emotional and social jobs explain why people buy. Skipping them leaves conversion copy flat.
- Treating JTBD as a one-time exercise. Jobs evolve as markets shift. Run switch interviews quarterly, not once at launch.
Frequently asked questions
Buyer personas describe who the customer is — demographics, role, company. JTBD describes what they're trying to accomplish. Two completely different people can share the same job. A dentist and a lawyer both need to get more local leads from Google. Different personas, same job.
Most successful products serve one primary job and 2-3 secondary jobs. Attempting to serve too many jobs creates an unfocused product. Identify the core job and build around it first.
Yes. Write content that addresses the job customers are trying to do, not just product features. "How to get more leads from Google" (the job) consistently outperforms "Features of our SEO tool" (the product).
Clayton Christensen popularized JTBD at Harvard Business School using a milkshake study. He found that morning commuters weren't buying a beverage — they were hiring the milkshake to make their commute less boring and keep them full until lunch.
A job statement uses the format: "When I'm in [situation], I want to [achieve outcome], so I can [broader goal]." Example: "When I run a local business, I want to publish SEO content consistently, so I can get found on Google without hiring a marketing team."
Related glossary terms
Sources
