Framework Guide
Personas describe who. Jobs-to-be-Done describes why. The framework, the interview method, and how to layer JTBD on top of your persona work for sharper decision-driver clarity.
Jobs-to-be-Done (JTBD) is a framework developed by Clayton Christensen and Bob Moesta. The central claim: customers don't buy products. They hire products to make progress on a job they're trying to do.
The classic example: a person doesn't buy a milkshake because they're in the "milkshake-buying" demographic. They buy a milkshake because they have a long, boring commute and need something that takes 20 minutes to drink, doesn't make a mess, and gives them something to do with their hands. The "job" is to fill the commute time. The milkshake just happens to do that job well.
Once you know the job, you can identify all the alternatives a customer might "hire" — and the criteria they use to choose between them.
Personas describe who the buyer is. JTBD describes what they're trying to accomplish. The two are layered, not substituted.
| Element | Persona | JTBD |
|---|---|---|
| Unit of analysis | A person | A goal/job |
| Primary question | Who is this? | What are they trying to do? |
| Use case | Targeting, messaging, sales | Positioning, product, decision criteria |
| Output | Persona doc with goals, pains, behavior | Job statement, alternatives, hiring criteria |
A persona without JTBD tells you who to talk to. A JTBD without a persona tells you what message resonates but not where to deliver it. Both together tell you who to target, what message to use, and what alternatives you're competing against.
Every job has three layers:
Products that nail the functional job but miss the emotional and social layers underperform products that hit all three. This is why brand matters even in B2B — emotional and social signaling is part of the job.
JTBD interviews are different from standard persona interviews. The technique is forensic: walk customers through the actual sequence of events that led to their purchase decision.
The key questions, in order:
Run 10-15 of these interviews. The patterns are usually clear after 8-10. The "alternatives" question is especially revealing — customers often consider non-obvious alternatives that competitive analysis would miss.
The JTBD question that produces the most actionable insight: "What were you doing before that wasn't working?" This surfaces the alternative the customer was actually trying to replace — often a manual spreadsheet, a workaround, doing nothing — which is your real competition. Naming the real competitor changes positioning.
The canonical JTBD format:
Example: "When I'm preparing for a board meeting (situation), I want to know which marketing programs actually drove pipeline this quarter (motivation), so I can defend my budget and direct next quarter's investment (desired outcome)."
Notice the job is the same regardless of the product. The board-meeting prep job exists whether the customer uses Salesforce reports, Marketo, Bizible, HubSpot, or a spreadsheet. Your job is to be the best way to do that job.
Once you have your job statements, they should change three things: