--- title: Jobs-to-be-Done · The framework that makes personas useful · RGM Learn url: https://realgrowthmatters.com/learn/personas-icp/jobs-to-be-done/ updated: 2026-06-10 source_html: https://realgrowthmatters.com/learn/personas-icp/jobs-to-be-done/ --- ## What Jobs-to-be-Done means 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. ## How JTBD complements personas Keep going · Free training ### Customer Research & ICP Persona work that actually drives decisions takes practice — RGM's training walks through customer interviews, ICP scoring, JTBD methodology, and persona operationalization. Free. [Start the training →](/training/) 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. ## The three layers of a job Every job has three layers: - **Functional.** What is the customer trying to accomplish, practically? "Send a presentation to my client." - **Emotional.** How do they want to feel? "Confident that the presentation reflects well on me." - **Social.** How do they want others to perceive them? "Seen as someone who delivers quality work." 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. ## The JTBD interview method 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: 1. **"When did you first realize you needed a new solution?"** Identifies the trigger event. 2. **"What was the moment you decided you had to do something?"** Identifies the push. 3. **"What did you do next? Who did you talk to?"** Maps the buying journey. 4. **"What else did you consider? Why did you rule those out?"** Maps the alternatives. 5. **"What worried you about choosing us? What almost stopped you?"** Surfaces objections. 6. **"What made you finally pull the trigger?"** Identifies the activation moment. 7. **"Looking back, what about your situation made our solution feel like the right fit?"** Synthesizes the job. 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. #### RGM experts say 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. ## Writing a job statement The canonical JTBD format: Job statement template When [SITUATION], I want to [MOTIVATION], so I can [DESIRED OUTCOME]. 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. ## Operationalizing JTBD Once you have your job statements, they should change three things: - **Positioning.** Your homepage hero should speak to a job, not a feature. - **Competitive comparison.** Your "vs" pages and battlecards should be organized around the job, not around features. - **Product roadmap.** Features that don't make the job easier shouldn't be priorities. ## Related content [Step-by-step**Buyer personas** Build the who layer of JTBD.](/learn/personas-icp/buyer-personas/) [Templates**JTBD interview guide** Question protocol for JTBD interviews.](/learn/personas-icp/templates/) [Framework**The Alignment Framework** JTBD ties into Market-Product Fit.](/learn/frameworks/alignment-framework/)