The Debate
Nobody Wins a Framework War
No customer ever got served better because a framework won an argument.
You’ve heard the line. “We don’t do personas anymore. We do Jobs-to-Be-Done.” Delivered with the calm of the recently converted.
It’s a false choice, and it costs teams real clarity. A job describes the progress someone is trying to make. A persona describes the person trying to make it. One is a compass. One is a map. Nobody hikes with just one.
The honest version of the story: JTBD rose partly as a rebellion against bad personas — the demographic wallpaper, the stock photos, the golden retriever named Biscuit. That rebellion was deserved. But the cure for a bad persona isn’t no persona. It’s a persona with a job at its core. Even Nielsen Norman Group, no pushover on method, concludes the two are complementary, not competing — jobs carry the needs; well-made personas carry the same needs plus the behavior and attitude that make them designable.
So let’s take JTBD seriously. Starting with where it came from.
Origins
Where Jobs Thinking Comes From
People don’t buy products. They hire them.
That one sentence is the whole framework. It has a lineage. Theodore Levitt told his marketing students that people don’t want a quarter-inch drill, they want a quarter-inch hole. Tony Ulwick built a rigorous version of the idea in the 1990s — Outcome-Driven Innovation — on the premise that jobs are stable while products come and go, and that customer needs are measurable outcomes, not vague preferences. And Harvard’s Clayton Christensen, working with innovation researcher Bob Moesta, made it famous.
Christensen’s canonical telling is the milkshake. A fast-food chain wanted to sell more of them. They profiled the typical customer, ran focus groups, made the shakes thicker, sweeter, cheaper. Sales didn’t move. Then the researchers stopped asking and started watching. A striking share of milkshakes sold before 8am, to people alone, in cars. The commuters weren’t buying dessert. They were hiring the shake for a job: make a long, boring drive bearable, occupy one free hand, last the whole trip, hold off hunger until lunch. The competition wasn’t another milkshake. It was bananas, bagels, and boredom. Christensen, Hall, Dillon, and Duncan laid the whole theory out in “Know Your Customers’ Jobs to Be Done” in Harvard Business Review, and at book length in Competing Against Luck.
Every job has three dimensions, and most teams only build for the first:
Functional. The practical task. “Keep me fed until lunch.”
Emotional. How the person wants to feel. “Not like I’m eating ice cream at 7am.”
Social. How they want to be seen. “Competent. Together. Not desperate.”
The emotional and social layers are where differentiation lives — and, not coincidentally, exactly the layers a good persona is built to hold.
The Physics
The Forces of Progress
Every switch is a tug of war between four forces.
Bob Moesta and the Re-Wired Group gave JTBD its physics: the four forces of progress. Two forces push a customer toward change. Two hold them where they are. People move only when the first pair beats the second.
Toward change →
Push of the situation
The Sunday-night dread. The workaround that finally broke. The frustration that makes today’s way unbearable.
Toward change →
Pull of the new solution
The imagined better life. “What if the report just built itself?”
← Holding back
Anxiety of the new
Will it work? Will I look stupid learning it? Will migration eat a weekend?
← Holding back
Habit of the present
The spreadsheet is ugly, but it’s mine. Familiar beats better, most days.
Here’s why this matters for persona work: the holding forces are the quiet ones. Customers will happily tell you about push and pull. They almost never volunteer their anxieties and habits — yet those are what actually kill adoption. A persona is the natural home for them. “Frustrations” and “objections” fields exist precisely to hold anxiety and habit where your whole team can see them.
Division of Labor
What Each Lens Sees
JTBD finds the struggle. Personas keep the person.
| Dimension | Jobs to Be Done | Personas |
|---|---|---|
| Unit of analysis | The struggling moment | The human in it |
| Key question | “What progress is being sought?” | “Who are we serving?” |
| Sees clearly | Switching triggers, real competition | Context, skill, constraints, language |
| Blind spot | Abstract; hard to rally a team around | Can decay into demographic trivia |
| Best at | Innovation and positioning | Alignment, design, and messaging |
JTBD’s great gift is redefining competition. Your project tool isn’t just fighting other project tools; it’s fighting spreadsheets, email threads, and the team lead who keeps everything in his head. Its great weakness is that job statements don’t stick in human memory. “Efficiently prepare weekly status materials under time constraints” rallies no one. “Maria, who loses every Sunday night to the Monday report” — the whole team remembers her by Thursday.
And real products serve more than one human per job. A buyer and a user often hire the same product for different jobs; an ICP defines the company while the persona defines the person inside it. Jobs identify the work. Personas track who holds which job, and how they differ.
Better Together
The Bridge: Slotting Jobs Into Personas
A job gives your persona a spine.
The cleanest connector is the job story, a one-sentence format popularized in the JTBD community: When [situation], I want to [motivation], so I can [outcome]. Every clause maps to a persona field. Watch:
Job story
When it’s Sunday night and Monday’s status meeting is looming,
I want to pull a credible report together in minutes,
so I can walk in looking on top of every project — without losing my weekend.
Holding forces: afraid a new tool means re-entering everything; the copy-paste ritual is at least familiar.
Maria, the Overloaded Lead
First-time PM · three concurrent projects
- Context:
- Sunday nights, deadline pressure, status meeting Mondays
- Goal:
- A credible report in minutes, not hours
- Success looks like:
- Seen as on top of every project; weekends back
- Frustrations & objections:
- Fears migration pain; clings to the familiar copy-paste ritual
When → Context
I want → Goal
So I can → Success
Forces → Frustrations
That card is neither a traditional persona nor a bare job statement. It’s both at once. Maria is someone your designer can picture and your copywriter can write to. Her job is explicit, so your product team knows exactly what the product must beat: the copy-paste ritual. Put the primary job at the top of every persona — not buried in a paragraph — and the profile stops being a character sketch and starts being a strategy.
One persona can carry two or three jobs; give them an order. And if two very different people share the same primary job — a 25-year-old freelancer and a 52-year-old enterprise PM hiring your product for identical progress — that’s one persona, not two. Cluster by job, not by demographics. That single move rescues personas from their worst instinct.
The Work
How to Build a Job-Informed Persona
Four steps. One week. No consultants.
1. Interview recent switchers. Find five people who recently adopted your product — or abandoned it. Walk the timeline backward: first thought, first search, what they tried, what almost stopped them. You’re listening for the push, the pull, the anxieties, the habits. Our persona interview questions include a section built for exactly this, and the broader persona research methods guide covers how to triangulate what you hear against what your analytics show.
2. Cluster by job. Group the interviews by the progress being sought, ignoring age, title, and company size. Two or three job clusters will emerge. Those are your persona candidates.
3. Write the persona around the job. Primary job story at the top. Context, goals, and success measures drawn from the clauses. Anxieties and habits filed under frustrations and objections. Real quotes from the interviews. Then the human layer — name, face, a line of story — because that’s what makes it stick in a teammate’s head on Thursday. A structured persona template keeps the job fields from getting lost.
4. Put it where decisions happen. A job-informed persona answers the two questions every product debate comes down to — who is this for? and what progress are they hiring us for? — in one artifact. That’s why it gets used in meetings instead of dying in a slide deck.
Build a persona right now — free, no signup.
Start from a job story. Get a structured, shareable persona in minutes.
Open the persona creator →When should you lead with which lens? Early exploration, positioning, pricing: lead with jobs — you’re hunting struggling moments. Daily design, copy, and team alignment: lead with the persona — you’re serving a person you can name. Messaging: both at once. The job tells you what to say; the persona tells you how to say it, in words the reader would use herself — which is why well-built personas earn their keep in marketing as much as product.
Questions
JTBD and Personas FAQ
What is the difference between jobs to be done and personas?+
A job describes the progress a customer seeks in a specific situation. A persona describes the person seeking it — context, skills, constraints, language. JTBD’s unit of analysis is the struggling moment; the persona’s is the human. The job explains why someone switches; the persona explains how to design and communicate for them.
Does jobs to be done replace personas?+
No. JTBD replaces bad personas — the demographic-heavy kind — not the persona itself. NN/g and most experienced teams treat them as complements: discover with jobs thinking, then build personas around shared jobs so the findings become memorable and actionable.
What is the milkshake example in jobs to be done?+
A fast-food chain improved its milkshakes every way customers suggested, and sales stayed flat. When researchers watched actual buyers, they found a large share of shakes sold before 8am to solo commuters hiring them to make a boring drive bearable and hold off hunger until lunch. The real competition was bananas, bagels, and boredom — not other milkshakes.
What are the four forces of progress?+
Push of the current situation, pull of the new solution, anxiety of the new, and habit of the present — a framework from Bob Moesta and the Re-Wired Group. People switch when push plus pull outweigh anxiety plus habit. The holding forces rarely get said out loud, which is why they belong in your persona’s frustrations and objections.
What is a job story and how does it fit a persona?+
“When [situation], I want to [motivation], so I can [outcome].” It maps clause-for-clause onto a persona: situation → context, motivation → goal, outcome → success measure, and the anxieties around switching → frustrations. Write the primary job story at the top of each persona profile.
Levitt’s customers wanted a quarter-inch hole, not a drill. True. But someone still holds the drill — with her grip strength, her deadline, her fear of cracking the tile. The job is the hole. The persona is the person drilling it. Serve both and you serve the customer, which was always the point.
Don’t pick a side. Interview five switchers this week, find the job, and build a persona right now — free, no signup. Map and compass, together, from day one.