Jobs-to-be-Done vs Customer Personas
Personas describe who the customer is. JTBD describes what the customer is trying to accomplish. The difference shapes which features you build.
Both claim to model the customer. The model is different in a way that shows up in the product roadmap.
At a glance
| JTBD | Personas | |
|---|---|---|
| Unit | A job the customer is hiring a product for | A person (often composite) representing a customer segment |
| Output | "When [situation], I want to [job], so I can [outcome]" | A profile: name, age, role, goals, pain points, quotes |
| Stability over time | High (jobs are stable) | Low (personas drift as users change) |
| Best for | Product strategy, competitive set definition | Marketing copy, UX research synthesis |
| Origin | Christensen / Ulwick / Moesta | Alan Cooper, The Inmates Are Running the Asylum, 1999 |
| Common abuse | Vocabulary-only ("our job is to help users feel productive") | Stereotypes ("Sarah, 34, busy mom") that aren't grounded in research |
When personas help
- UX research synthesis: collapsing 30 interviews into 3 typical-user profiles helps designers reason about edge cases without listing every interview verbatim
- Marketing copy and persona-driven landing pages: when the value prop varies meaningfully by who the buyer is
- Sales enablement: arming reps with profiles of who they're likely to be selling to
- Cross-functional alignment: easier to say "Sarah won't understand this" than "users in segment 2 with the following attributes"
The persona's value is anchoring. It makes an abstract user concrete enough for the team to reason about.
When JTBD helps
- Defining a new product or feature: what job is this hired for?
- Identifying real competitors: what else gets hired for the same job?
- Pivoting or repositioning: when the apparent customer hasn't changed but engagement has, the job probably has
- Killing features: ones that don't serve the job, regardless of how nice they are
The JTBD's value is focus. It forces the team to articulate the outcome the customer is trying to achieve.
The pattern that works
Use both, in this order:
- JTBD first — name the jobs your product is hired for. Surfaces the durable demand.
- Personas second — for each job, who tends to hire the product for that job? Maps job to buyer/user characteristics.
The combination tells you both what the product needs to do (JTBD) and who you're talking to about it (Personas).
The common mistake
Picking the framework that requires less customer research. Both done badly produce fiction; both done well require interviews.
- A persona built from a strategy offsite without customer interviews is just stereotypes the team agreed on.
- A JTBD job written without customer interviews is just the product team's pitch deck.
Neither tool excuses you from talking to users. They're both synthesis tools — what you synthesize depends on the quality of inputs.
The diagnostic
If your team can describe the customer's day (what they do hour by hour, what frustrates them, what they're trying to accomplish), you have enough material for a JTBD. If your team can describe the customer's role and demographics (where they work, what title, what tools they use), you have enough material for a persona. Most teams have both — and most should produce both.
If neither — go do 5–10 user interviews before reaching for any synthesis framework.