Jobs to Be Done: The Framework That Explains Why Customers Really Buy

Source: Clayton M. Christensen — HBR "Marketing Malpractice" (2005); The Innovator's Solution (Free Press, 2003, with Raynor)

"Customers don't buy products. They hire them to get a job done."

---

The Milkshake Insight (Christensen)

Research documented in HBR "Marketing Malpractice" (2005): a significant portion of milkshakes were sold in the early morning to solo commuters. The real job wasn't "satisfy a craving" — it was "get through a long, boring commute." Thick enough to last. One hand while driving. Didn't ruin lunch appetite.

The competition wasn't other milkshakes. It was bananas (too fast), bagels (too messy), coffee (too hot, gone too quickly). The milkshake competed for the job of "getting through the commute" against completely different product categories.

This is the JTBD insight: define the competitive set by the job, not the category.

---

What a Job Actually Is

A job has a specific structure: situation (what triggers the need) + motivation (what outcome do they want) + constraint (what would prevent progress).

Christensen's formulation: "When I [situation], I want to [motivation], so I can [expected outcome]."

Three levels:

• Functional: the practical task ("I need to send money to a friend")
• Social: how they want to be perceived ("I want to look like a smart investor")
• Emotional: how they want to feel ("I want to feel confident before my pitch")

Most products win or lose on emotional and social jobs when functional alternatives are comparable.

---

Why JTBD Reframes Competition

It expands where you look for insight. Founders who study only direct competitors miss what customers used before — often a spreadsheet or workaround, not another company. Understanding why they used that workaround tells you more about the job.

It changes positioning. If customers hire your product for a different job than you think, your messaging is aimed at the wrong target.

It changes market sizing. "Everyone who wants a milkshake" vs. "commuters who need an engaging, hands-free morning ritual" — different size, different adjacencies, different expansion path.

---

The Switch Interview — How to Find the Job

Structured conversation with customers who recently switched to or away from your product:

1. First thought — when did you first realize you needed to solve this? What was happening?
2. The search — what did you look at? What were you comparing?
3. The decision — what made you choose this over alternatives? What pushed you over the line?
4. First use — was the experience what you expected?

Common finding: the trigger is rarely what the company expects. Customer who switched to a new accounting tool: "I had an argument with my accountant about a mistake and realized I needed to feel more in control of my numbers." Functional job: track financials. Real trigger: emotional job surfaced by a specific event.

---

Four Practical Applications

Product development: Before building a feature, ask what job it enables. Features that serve a real job are used and retained. Features that sound useful in a brainstorm but don't serve a real job sit unused. Most users use a small core of features that address their primary job.

Positioning: Map messaging to the job, not the feature. "Reduces invoicing time by 40%" (job framing) lands harder than "advanced invoice automation features." Lead with the job.

Pricing: Customers pay based on the value of the job, not the cost of the product. A tool that eliminates a $50,000 problem can price higher than a tool that eliminates a $500 problem, regardless of development cost.

Market sizing: Define your market by the job. Produces more honest sizing (you're not all of the category TAM) and reveals adjacent opportunities where the same job applies in different contexts.

---

Common JTBD Mistakes

• Defining the job too broadly ("I want to make progress" is a wish, not a job)
• Confusing the job with the solution ("I need project management software" is not a job)
• Only looking for functional jobs (emotional and social jobs often determine which product wins)
• Assuming all customers hire the product for the same job (segment by job, not just demographic)

---

Understanding what job your customers are actually trying to get done requires deep market intelligence — who they are, what alternatives they're currently using, and what triggers their search for something better. DimeADozen.AI generates a comprehensive competitive and market analysis in minutes, giving you the foundation to identify the real job before you build.

Get yours →