JTBD vs User Personas: When to Use Each (And How to Combine Them)

You’ve probably heard both terms thrown around in product discussions: “We need to define our personas” and “What’s the job-to-be-done here?” But these frameworks aren’t interchangeable, and using the wrong one at the wrong time can lead you astray.

Here’s the short answer: JTBD tells you why people buy. Personas tell you who is buying. Both matter, but for different decisions.

What’s the Real Difference?

User Personas Focus on Who

A persona is a semi-fictional representation of your ideal customer based on research and data. It typically includes:

Demographics (age, job title, income)
Behaviors and habits
Goals and frustrations
Preferred channels and tools

Example persona:

“Marketing Mary” is a 34-year-old marketing manager at a B2B SaaS company. She manages a team of 3, reports to the CMO, and is evaluated on MQLs. She’s frustrated by disconnected tools and spends too much time in spreadsheets.

JTBD Focuses on Why

Jobs-to-be-Done describes the progress a customer is trying to make in a specific circumstance. It’s solution-agnostic and focuses on outcomes, not demographics.

Example job statement:

“When I’m preparing for a board meeting, I want to quickly pull together campaign performance data, so I can demonstrate marketing’s impact without scrambling at the last minute.”

Notice: The job statement could apply to Marketing Mary, but also to a startup founder, a freelance consultant, or a VP of Growth. The job is the same even if the person is different.

When to Use Each Framework

Use JTBD When…

1. You’re deciding what to build

JTBD helps you understand the progress customers want to make. This reveals opportunities that demographic-based thinking misses.

Example: Milkshakes. Clayton Christensen’s famous study found that people “hired” milkshakes for the morning commute—not because they wanted breakfast, but because they wanted something to make a boring drive interesting while keeping one hand on the wheel. The job wasn’t “eat breakfast.” It was “make my commute less boring.”

2. You’re entering a new market

When you don’t know your customers yet, JTBD helps you find them by the job they’re trying to accomplish, not by demographics.

3. You’re positioning against competitors

JTBD reveals the real competition. Your project management tool doesn’t just compete with other PM tools—it competes with spreadsheets, email threads, and sticky notes. Same job, different solutions.

4. You’re prioritizing features

Ask: “Does this feature help customers make progress on their core job?” If not, cut it.

Use Personas When…

1. You’re crafting marketing messages

Personas help you tailor how you communicate. The job might be the same, but a Fortune 500 IT director wants different language than a startup CTO.

2. You’re designing user experiences

Technical proficiency, context of use, and accessibility needs differ by persona. A power user wants keyboard shortcuts; a casual user wants guided flows.

3. You’re segmenting for go-to-market

Sales and marketing teams need to know who to target. “People who need to make their commute less boring” isn’t a targetable segment. “Suburban commuters aged 25-45 with 30+ minute drives” is.

4. You’re prioritizing which customers to serve first

Not all customers are equal. Personas help you identify which segments are most valuable, reachable, or strategic.

The Problem With Personas Alone

Personas without JTBD can lead you astray. Here’s why:

1. Same persona, different jobs

“Marketing Mary” might be hiring your tool for three completely different reasons:

To impress her boss with better reporting
To save time on repetitive tasks
To look innovative to her team

Each job requires a different solution. The persona is the same, but the jobs are different.

2. Different personas, same job

A startup founder, enterprise PM, and freelance consultant might all be trying to “quickly validate an idea before investing time building.” Same job, wildly different personas.

If you build only for the persona, you might miss that these three segments share a common need—and a common solution.

3. Personas can become stereotypes

“Marketing Mary likes yoga and drives a Prius” doesn’t help you build a better product. It’s noise that distracts from what actually matters: what progress is she trying to make?

The Problem With JTBD Alone

JTBD isn’t a complete solution either:

1. Jobs aren’t targetable

You can’t buy ads targeting “people who want to make their commute less boring.” You need demographic and behavioral data to reach customers.

2. Jobs don’t capture context of use

The same job might require different solutions for different users. A mobile-first user has different constraints than a desktop user, even if the job is identical.

3. Jobs don’t prioritize segments

Knowing the job doesn’t tell you which customers are most valuable or easiest to acquire.

How to Combine JTBD and Personas

The best teams use both. Here’s a practical approach:

Step 1: Start With Jobs

Before you know who to target, understand why anyone would buy.

Conduct JTBD interviews asking:

What were you trying to accomplish?
What alternatives did you consider?
What would happen if you couldn’t solve this?

Step 2: Identify Job Performers

Once you know the job, find the people who experience it most acutely.

Ask:

Who has this job most frequently?
Who has the highest stakes when the job fails?
Who is already spending money to solve this job (poorly)?

Step 3: Build Personas Around Jobs

Instead of generic personas, create job-based personas:

“Scrambling Sarah” isn’t just a marketing manager—she’s specifically someone who experiences the job “quickly pull together performance data for executives” multiple times per month, has been burned by missing data in presentations, and currently cobbles together spreadsheets from 4 different tools.

The persona is defined by the job context, not just demographics.

Step 4: Validate With Both Lenses

When evaluating features or positioning:

JTBD check: Does this help customers make progress on their job?
Persona check: Does this resonate with our target segment’s context and constraints?

Quick Reference: JTBD vs Personas

Question	Use JTBD	Use Personas
What should we build?	✅
How should we message it?		✅
Who are we competing with?	✅
Who should we target first?		✅
Why do customers switch?	✅
How should the UX feel?		✅
What progress do customers want?	✅
What channels reach our customers?		✅

Practical Example: Combining Both

Let’s say you’re building an AI writing assistant.

JTBD research reveals three main jobs:

“Write first drafts quickly so I can overcome blank page paralysis”
“Edit my writing to sound more professional”
“Repurpose content across channels without manual rewriting”

Persona research reveals three segments:

Content marketers at B2B SaaS companies
Freelance copywriters
Founders doing their own marketing

Combined insight:

Job #1 (blank page paralysis) is felt most acutely by founders doing their own marketing—they’re not writers by trade and hate staring at an empty doc.

Job #2 (sound professional) is the primary job for freelance copywriters who need to match client brand voice.

Job #3 (repurpose content) is the main job for content marketers managing multiple channels.

Now you can:

Build features that solve specific jobs (not generic “AI writing”)
Position differently for each segment (founders: “Never face a blank page again”)
Prioritize which segment to target first based on market size and accessibility

Key Takeaways

JTBD and personas answer different questions. JTBD = why people buy. Personas = who is buying.
Start with JTBD. Understand the progress customers want before defining who to target.
Build job-based personas. Define personas by their relationship to the job, not just demographics.
Use both for decisions. JTBD for product strategy; personas for go-to-market.
Avoid common traps. Same persona can have different jobs. Different personas can share the same job.

Next steps:

Learn the complete Jobs-to-be-Done framework
Build your own statements with our JTBD Statement Builder
See how to conduct JTBD interviews effectively