Jobs to Be Done (JTBD)
Originated by Clayton Christensen (popularized) in 2003
A framework that reframes the question of why customers buy by focusing on the underlying job they're trying to get done — not the product they choose to do it.
There’s a line often attributed to Theodore Levitt that goes: “People don’t want to buy a quarter-inch drill. They want a quarter-inch hole.” Clayton Christensen took that idea and built a research methodology around it, and it changed how a lot of product and marketing teams think about why customers really buy things.
The core provocation of Jobs to Be Done is that we systematically misunderstand customer motivation. We segment by demographics (age, income, location) or by product category (users of our product vs. users of competitors’). What we miss is the actual job the customer is trying to get done — and that job reveals competitors we never thought to track and messaging angles we never considered.
What the Framework Actually Does
JTBD reframes the unit of analysis from “who is the customer” to “what is the customer trying to accomplish.” A customer doesn’t buy a milkshake because they’re a milkshake person. They buy a milkshake at 8am on the way to a long commute because they need something to occupy one hand and hold off hunger until lunch without getting messy. That’s the job. The competitors for that job aren’t other milkshakes. They’re bananas, bagels, granola bars, and nothing (just waiting until lunch).
That realization changes everything. The product feature set, the marketing message, the distribution channel, the price point, and the brand positioning all look different when you understand the job rather than just the product category.
The framework distinguishes three types of jobs. Functional jobs are the practical outcomes the customer wants: prevent running out of milk, get from A to B, fix the leaking pipe. Emotional jobs are about how the customer wants to feel: reassured, proud, competent, adventurous. Social jobs are about how the customer wants to be perceived: responsible parent, taste-maker, serious professional. Most significant purchases serve all three, and the weighting varies by context.
The job map adds process structure: getting any job done involves a sequence of stages (defining the goal, locating what’s needed, preparing, executing, monitoring, completing). Each stage is a potential site of friction, and reducing friction at a key stage is often more valuable than improving the core product.
The Origin
Clayton Christensen developed the Jobs to Be Done framework through his research at Harvard Business School in the late 1990s and early 2000s, building on earlier work by Tony Ulwick who had developed a related methodology called Outcome-Driven Innovation. Christensen and his colleagues published versions of the framework through the early 2000s, with his book “The Innovator’s Solution” (2003) serving as a key popularization.
The milkshake example, which Christensen discussed extensively in his later work including “Competing Against Luck” (2016), came from a fast food restaurant study. Researchers had tried to improve milkshake sales by segmenting customers and adjusting product attributes. Nothing worked. When they switched to observing who actually bought milkshakes, at what time of day, in what context, and then interviewing them about what they were trying to accomplish, the morning commute job emerged clearly. The insight led to product changes (thicker shakes that lasted the commute, smaller sizes for afternoon purchases by children) that actually moved the needle.
Bob Moesta, who worked with Christensen on that research, has since developed the framework further and is probably the most prolific practitioner teaching it today through his Rewired Group consulting practice.
How to Apply It
The methodology is built around interviews, but not the standard kind. You’re not asking customers what features they want or what they like about your product. You’re asking them to reconstruct the purchase story: what was happening in your life when you first thought to buy this? What had changed? What had you tried before? When you walked into the store, what went through your mind?
Those reconstruction questions reveal the job better than direct questions do, because customers who are asked “what job were you hiring this product for” will give you their rationalized, post-hoc answer, not the actual context that drove the decision.
Look for patterns in the circumstances, not the demographics. If you interview twenty customers and find that twelve of them bought when they were facing a new social situation where they felt out of their depth, that’s a job: belonging and competence in an unfamiliar context. The demographics of those twelve might be completely diverse.
Once you’ve identified the job, map the competitive set properly. Your real competitors are everything else the customer might hire to do the same job, including doing nothing. This often surfaces non-obvious competition that your category-based analysis misses.
Then test your messaging. Does your current marketing speak to the job? Or does it describe the product’s features and assume customers will translate features into job completion? The strongest marketing in JTBD terms meets the customer at their circumstance and says: we understand the situation you’re in, and here’s how we help you get through it.
A Real Example
The “Got Milk?” campaign discovered a JTBD insight before the framework had that name. The research, done by the agency Goodby Silverstein & Partners in the early 1990s, involved tracking milk consumption in customers’ homes. What they found was that people didn’t think about milk most of the time. They thought about it intensely in one specific moment: when they reached for something (cereal, cookies, cake) and the milk was gone. The job wasn’t “enjoy milk.” The job was “don’t get caught without it when you need it.” The campaign’s famous “deprivation” approach, where ads showed people desperately needing milk at the worst possible moment, was a direct response to that insight.
De Beers and the diamond engagement ring is a masterclass in engineering a social and emotional job. The functional job of an engagement is simply to signal commitment. That could be accomplished by a handshake, a verbal declaration, any number of things. De Beers created the cultural norm that the social job requires a diamond, and specifically a diamond whose value corresponds to the depth of the commitment. The “A Diamond Is Forever” campaign wasn’t selling stones. It was selling the tool for a very specific social job: creating a permanent, public, socially legible symbol of a life decision.
Snickers’ “You’re not you when you’re hungry” is almost a literal job statement. The functional job: restore yourself to your normal functioning self when hunger is impairing your behavior. The emotional and social job: don’t be that person who’s irritable and off their game. The campaign works because it named the circumstance (the hunger-impaired state) so precisely that viewers recognized it immediately.
Airbnb’s positioning against hotels addresses a different job than most hotel marketing speaks to. Hotels speak to the comfort and convenience job. Airbnb’s “Belong Anywhere” framing speaks to the social and emotional job of feeling like a local rather than a tourist, of having an authentic experience rather than a sanitized one. That’s a different job, which is why the two aren’t direct substitutes for every customer even when they serve the same functional travel need.
When the Framework Falls Short
The level of abstraction problem is real and it trips up a lot of JTBD practitioners. Define the job too narrowly (“help me make good coffee at home at 7am”) and you miss the broader competitive landscape. Define it too broadly (“help me feel alert and productive”) and everything from energy drinks to exercise to therapy is your competitor, which isn’t actionable.
Finding the right level requires judgment and iteration, and the framework doesn’t give you a formula for it. You have to triangulate through research and test whether your job definition actually changes any decisions.
Customer articulation is also a genuine challenge. The best JTBD insights come from observational research and skillful reconstruction interviews, not from surveys or focus groups. Customers in a group setting will give you socially acceptable, product-feature answers. The real jobs emerge from one-on-one conversations about specific purchase experiences, conducted by interviewers who know how to probe without leading. That kind of research takes skill and time that many teams don’t invest in.
The framework also doesn’t help much with prioritization across jobs. If you find that five distinct customer segments are hiring your product for five different jobs, JTBD tells you that’s what’s happening. It doesn’t tell you which job to optimize for.
When to Use It (and When to Reach for Something Else)
JTBD is most valuable when you’re feeling stuck on why customers do or don’t choose your product, when your messaging isn’t resonating despite what feels like a solid value proposition, or when your product development team keeps building features customers don’t use. Those are signs that you may be working from a product-centered view of the market rather than a job-centered one.
It’s also particularly powerful for finding non-obvious competitive threats. If you think about your competitors only as the other products in your category, you’ll miss the alternatives customers actually consider when they’re trying to get the job done.
Reach for buyer personas or customer journey maps when you need to understand the texture of the customer experience across touchpoints rather than the fundamental motivation. JTBD answers the “why” question. Journey mapping answers the “what happens when” question. Both are useful, and they complement each other.
If your challenge is primarily about market segmentation and targeting rather than understanding motivation, STP Marketing will be more directly applicable. JTBD is a research lens, not a segmentation tool. Use it to inform your segmentation decisions, but pair it with frameworks that give you the targeting and positioning structures to act on what you find.
The JTBD Components
- Functional Job: The practical, task-oriented outcome the customer is trying to achieve. The problem to be solved at a basic level.
- Emotional Job: How the customer wants to feel (or avoid feeling) as a result of getting the job done.
- Social Job: How the customer wants to be perceived by others through the product they use.
- Job Map: The sequence of stages in getting a job done: define the goal, locate inputs, prepare, confirm readiness, execute, monitor, modify if needed, conclude. Identifies where friction lives.
When to Use This Framework
- You're struggling to understand why customers choose your product over alternatives
- Product development is churning out features customers don't actually use
- You want to find non-obvious competitors you're not currently tracking
- You're writing messaging and value propositions that aren't resonating
Limitations and Criticisms
- Identifying the right level of abstraction is genuinely difficult — too broad makes everything a competitor, too narrow misses real insight
- Customers often can't articulate their jobs clearly in research settings; requires skilled interviewing
- Doesn't provide clear guidance on prioritization when multiple customer segments have different jobs
- Works better for evaluating existing markets than predicting entirely new ones
Case Studies That Demonstrate This Framework
Related and Alternative Frameworks
- Buyer Persona Development
- Customer Journey Map
- SWOT Analysis
- Blue Ocean Strategy
Key Takeaway
Nobody buys a drill because they want a drill. Understanding the actual job reframes who your real competitors are and what your messaging should say.
See these frameworks in action: Marketing Case Studies