Jobs-to-Be-Done and Personas: Better Together

The False Debate

Spend enough time in product circles and you’ll hear it. “We don’t do personas anymore. We use Jobs-to-Be-Done.” Said with the quiet confidence of someone who has found the one true way.

It’s a false choice. And it’s costing teams real clarity.

Arguing personas versus JTBD is like arguing whether a map or a compass is more useful when you’re lost in the woods. The map shows you the terrain — ridges, rivers, landmarks. The compass tells you which direction you’re heading. You want both. You need both.

Personas are the map. They show you who your customer is — the terrain of their life, context, and constraints. JTBD is the compass. It shows you where they’re trying to go — the progress they’re desperate to make.

The “versus” framing comes from a real frustration. Bad personas — the ones stuffed with demographics and stock photos — genuinely don’t help. JTBD emerged partly as a reaction to that laziness. Fair enough. But the answer to bad personas isn’t no personas. It’s better personas — ones that borrow the best ideas from JTBD.

What Is Jobs-to-Be-Done?

The core idea is elegant. People don’t buy products. They hire them to do a job.

That’s it. That’s the framework in one sentence.

Clayton Christensen — the Harvard professor who popularized JTBD in Competing Against Luck — had a famous example. A fast-food chain wanted to sell more milkshakes. They did the usual stuff: surveys, focus groups, taste tests. They made milkshakes thicker, thinner, sweeter, cheaper. Nothing moved the needle.

Then someone asked a different question. Not “how can we improve our milkshake?” but “what job is the milkshake being hired to do?”

They watched the store. A huge number of milkshakes sold before 8am. To people alone. In cars. On their commute. These people didn’t want a milkshake because it was delicious. They hired it to solve a specific problem: a long, boring drive where they needed something in one hand, something that lasted the whole commute, something more interesting than a banana and less messy than a bagel.

The job wasn’t “satisfy my sweet tooth.” The job was “make my commute less boring and keep me full until lunch.”

That insight changed everything. The competition wasn’t other milkshakes. It was bananas, bagels, boredom, and Snickers bars.

Every job has three dimensions:

Functional. The practical thing they’re trying to accomplish. “Get fed during my commute.”

Emotional. How they want to feel. “I don’t want to feel like I’m making an unhealthy choice at 7am.”

Social. How they want to be perceived. “I don’t want to walk into work with Cheeto dust on my shirt.”

Most product teams only address the functional job. The emotional and social dimensions are where real differentiation lives. Tony Ulwick’s Outcome-Driven Innovation framework hammers this point: when you map all three dimensions, you uncover unmet needs your competitors aren’t even looking at.

What JTBD Gets Right That Personas Sometimes Miss

Let’s be honest about where traditional personas fall short.

Context over demographics. A persona that says “Sarah, 34, marketing manager, likes yoga” tells you almost nothing about what Sarah needs from your product. JTBD doesn’t care about yoga. It cares about the moment she’s at her desk at 4pm, trying to pull together a campaign report, and her current tool is fighting her every step. That’s the moment that matters. Demographics are wallpaper. Context is structure.

The struggling moment as trigger. JTBD spotlights what makes someone switch. Not satisfaction scores. Not loyalty programs. The moment of frustration that pushes someone to search for an alternative. Personas often describe a steady state — who someone is. JTBD describes a transition — who someone is becoming.

Progress over satisfaction. Traditional research asks “how satisfied are you?” JTBD asks “what progress are you trying to make?” Satisfaction is backward-looking. Progress is forward-looking. When you frame everything as progress, you stop asking “what features do they want?” and start asking “what’s standing between them and their goal?”

Competition redefined. A persona might mention competitor products. JTBD redefines competition entirely. Your project management software isn’t just competing with other PM tools. It’s competing with spreadsheets, email chains, sticky notes, and the team lead who keeps everything in their head. As Alan Klement argues in When Coffee and Kale Compete, if you only think about direct competitors, you miss the real alternatives your customers are hiring.

These are genuinely powerful ideas. The question is: does that mean you throw out personas? No. Because JTBD has its own blind spots.

What Personas Get Right That JTBD Sometimes Misses

The human element. JTBD is beautifully analytical. It’s also, frankly, a bit cold. “Job executor hires solution to achieve desired outcome” is precise. It’s also the way a Vulcan would describe going to a restaurant. People aren’t rational job-executors. They’re messy, emotional, contradictory humans. Personas hold onto that humanity.

Team alignment through shared character. Here’s a practical truth JTBD purists rarely acknowledge: teams rally around people, not job statements. “We’re building this for Maria, the overwhelmed first-year teacher who spends her Sundays lesson planning” sticks in someone’s brain. “We’re addressing the job of efficiently preparing weekly instructional materials under time constraints” sticks in no one’s brain.

The power of a face and a name. This sounds superficial. It isn’t. Cognitive research consistently shows that people make better decisions when they can visualize a specific individual rather than an abstract group. When your engineer is deciding whether to polish an error message, “would this confuse Maria?” is more powerful than “does this address the user’s functional job?”

Personas make data relatable. You’ve done your research. You have transcripts, survey results, analytics dashboards. All of it is abstract until you compress it into a person. A persona is a compression algorithm for everything you’ve learned — gigabytes of research compressed into something that fits in working memory. JTBD gives you a sharper lens. Personas give you a sharper story.

Personas handle complexity. Real products serve different types of people with different jobs. A buyer persona and a user persona might hire your product for completely different jobs. JTBD alone can identify those jobs, but personas give you a framework to track which people hold which jobs, what constraints they operate under, and how they interact in the buying process.

How to Combine Them

Here’s where it gets practical. The best approach isn’t JTBD or personas. It’s JTBD-informed personas. You use Jobs-to-Be-Done thinking to discover what matters. Then you use personas to make it memorable, shareable, and actionable.

Step 1: Start with JTBD interviews

Before you build any persona, do JTBD-style interviews. Talk to recent customers — especially people who recently switched to your product (or away from it). Focus on the timeline: What first thought made them look for something new? What did they try first? What almost stopped them? What did they hope would be different?

You’re mining for struggling moments, hiring criteria, and the functional, emotional, and social dimensions of the job. This is the research foundation that keeps your personas honest.

Step 2: Cluster by jobs, not demographics

Here’s the critical move. When you look at your interview data, don’t group people by age, title, or company size. Group them by the job they’re hiring your product to do.

A 25-year-old freelance designer and a 52-year-old enterprise project manager might be hiring your product for the exact same job: “help me show stakeholders this project is on track without spending an hour building a status report.” Different demographics. Same job. Same persona.

This is where JTBD saves personas from their worst instinct — the instinct to segment by surface attributes rather than by what actually matters.

Step 3: Build personas around shared jobs

Now build your personas — but build them differently. Each persona should explicitly reference the jobs they’re hiring your product for. Not buried in a paragraph. Front and center.

A JTBD-informed persona card looks like this:

See what happened? That’s not a traditional persona. And it’s not a raw JTBD job statement. It’s the best of both. Maria is a character you can root for. Her job is crystal clear. Her struggling moment drives design decisions. You know what she’s doing now, so you know what your product needs to beat.

Step 4: Validate with real behavior

Once you’ve drafted JTBD-informed personas, check them against behavioral data. Do your analytics support the struggling moments? Do support tickets reflect the frustrations? Do your most successful customers match the job descriptions?

If data contradicts your personas, trust the data. Revise. Personas are living tools. A good persona template makes iteration easy.

When to Lead with Which

Both frameworks are always useful. But depending on where you are, one deserves more emphasis.

Great marketing copy is a job statement wrapped in a persona’s voice. A persona without JTBD context leads to pretty interfaces that miss the point. JTBD without persona context leads to functional solutions that feel inhuman.

The Pragmatic View

Frameworks are tools, not religions.

The teams that ship great products don’t follow one framework perfectly. They steal good ideas from everywhere and use whatever helps them make better decisions this week.

If personas alone are driving real conversations and alignment — great. But consider adding JTBD’s struggling moments and job dimensions to sharpen them.

If JTBD alone is working — if your team thinks clearly in terms of jobs and hiring criteria — great. But consider wrapping those jobs in a persona to make them stickier, especially as your team grows.

You need the analytical clarity of JTBD to avoid building the wrong thing. And you need the human empathy of personas to avoid building the right thing in the wrong way.

“People don’t want to buy a quarter-inch drill. They want a quarter-inch hole.” — Theodore Levitt. JTBD gives you the hole. Personas give you the person holding the drill — their grip strength, their deadline, their fear of screwing it up.

Start wherever you are. If you have nothing, start with five customer interviews focused on struggling moments. That’s JTBD. Then take what you learn and build a persona. You’ll have something better than 90% of teams in a single week.

If you already have personas that feel stale, revive them. Add the primary job. Add the struggling moment. Remove the hobbies nobody ever referenced. You don’t need to start over. You need to make what you have more useful.

And if you’re building your first personas right now, you’re in a good position. You get to build JTBD-informed personas from day one — the map and the compass from the start.

Don’t pick a side. Pick up both tools. Your customers — the real, messy, struggling humans trying to make progress — will be better served for it.