A fast-food chain wanted to sell more milkshakes. They improved the recipe. They added flavors. They ran promotions. Sales barely moved.
Then a researcher named Clayton Christensen asked a different question. Instead of “How do we make a better milkshake?”, he asked “What job is the milkshake being hired to do?”
The answer was surprising. Nearly half of all milkshakes were purchased before 8 AM, by commuters, alone. The milkshake was not competing against other milkshakes. It was competing against bananas, bagels, and boredom. Commuters hired the milkshake for a specific job: make my long drive to work slightly less boring, keep one hand free for the steering wheel, and keep me full until lunch.
Understanding the job changed everything. The chain made the milkshake thicker (lasts longer during the commute), added chunks of fruit (occasional surprise), and moved the dispenser in front of the counter (faster purchase for people in a hurry).
Sales went up. Not because the milkshake was better. Because the job was better understood.
What “Jobs-to-be-Done” Actually Means
People do not buy products. They hire products to make progress in their lives. The product is the employee. The progress is the job.
This reframe changes how you think about your business in three fundamental ways.
You stop competing with similar products and start competing with whatever currently does the job. The milkshake’s competitors were not other milkshakes — they were bananas and coffee. Your SaaS tool’s competitors might not be other SaaS tools — they might be spreadsheets, sticky notes, or “I just try to remember.”
You stop designing features and start designing outcomes. Features are what the product does. Outcomes are what the customer achieves. A drill bit is a feature. A hole in the wall is an outcome. Nobody wants a drill bit. Everyone wants to hang a picture.
You stop asking “What does our customer want?” and start asking “What is our customer trying to accomplish?” Wants are vague and shifting. Jobs are concrete and consistent. The commuter’s want might change from milkshake to smoothie to protein bar. Their job stays the same: make the commute bearable and keep me full.
The Three Dimensions of a Job
Every job has three dimensions. Understanding all three is what separates a product that works from a product that sells.
Functional dimension: The practical task. Track my expenses. Get from A to B. Learn a new skill. This is the surface-level job that most founders focus on.
Emotional dimension: How the person wants to feel. Confident about my finances. In control of my schedule. Smart and capable. This is the dimension that drives most purchasing decisions. People pay more for products that make them feel good than for products that merely work well.
Social dimension: How the person wants to appear to others. Organized and professional. Successful. Not behind the times. This is the dimension that creates brand loyalty — when using a product signals something about who you are.
When you design for all three dimensions, you build something people love, not just something people use.
A bookkeeping tool that works (functional) and is so simple it makes the founder feel competent (emotional) and generates reports that impress investors (social) is three times more compelling than a bookkeeping tool that just works.
Finding Your Customer’s Job
The Jobs-to-be-Done framework is not something you brainstorm at your desk. It is something you discover through customer interviews. Specifically, through a particular type of interview called the Switch Interview.
The Switch Interview focuses on people who recently switched from one solution to another. They switched from a spreadsheet to a software tool. From doing it manually to hiring someone. From one product to a competitor.
The switch reveals the job because the moment of switching is when all three dimensions are visible:
What triggered the switch? Something happened that made the old solution inadequate. A missed deadline. An embarrassing moment. A frustrating evening wasted on manual work. The trigger reveals the functional job that was not getting done.
What did they hope would change? The expected improvement reveals the emotional job. “I hoped I’d stop dreading Sunday evenings.” “I wanted to feel like I had my finances under control.”
What did they tell others? How they described the switch to friends or colleagues reveals the social job. “I told my partner I’m finally getting organized.” “I showed my accountant the new reports.”
Interview five people who recently switched solutions for the problem you are addressing. Their switching stories contain your entire product strategy.
Applying JTBD to Your Business
Here is the practical application, in four steps.
Step 1: Write the job statement. Use this format: “When [situation], I want to [motivation], so I can [expected outcome].”
“When I’m closing out my monthly finances, I want to see exactly where my money went, so I can feel confident about my tax filing.”
This single sentence becomes your north star. Every feature, every marketing message, every pricing decision should serve this job.
Step 2: Map the job chain. The job is not a single action — it is a sequence of smaller jobs. Map them in order:
- Collect all income data
- Categorize expenses
- Identify unusual entries
- Generate a summary
- Send to accountant
- Feel relieved until next month
Each step in the chain is a potential pain point and a potential product feature. Your minimum viable product should address the most painful step first.
Step 3: Identify the competition. List everything that currently does this job — not just similar products, but every alternative. Spreadsheets. Accountants. Shoeboxes full of receipts. Ignoring the problem entirely.
Each alternative is a competitor. Your product needs to beat the best alternative on at least one dimension (faster, cheaper, less stressful, more accurate) to get hired.
Step 4: Design for the job, not the product. Instead of asking “What features should we build?”, ask “What would make this job easier at each step?”
The answer might not be more features. It might be fewer steps. It might be better instructions. It might be a reassuring email after the task is complete. The best JTBD-informed products often have fewer features than their competitors — because they focus on the job rather than the product.
The JTBD Pricing Principle
Jobs-to-be-Done changes how you think about pricing.
Traditional pricing is cost-based or competitor-based. JTBD pricing is value-based — specifically, it is based on the value of getting the job done.
If the job is “file my quarterly taxes without stress,” and the alternative is hiring an accountant for EUR 400 per quarter, then a software tool that does the job for EUR 50 per quarter is priced against the alternative, not against competing software.
The question is not “What do other apps charge?” The question is “What is the customer currently paying — in money, time, and stress — to get this job done?” Your price should be a fraction of that total cost, making the switch an obvious win.
Common JTBD Mistakes
Defining the job too broadly. “Help people be more productive” is not a job. It is a category. A job is specific: “Help freelance copywriters track billable hours across five client projects without manual logging.” Specificity is where the value lives.
Confusing the solution with the job. “People need a better time-tracking app” describes a solution, not a job. The job is “Know at the end of each day that my billable hours are accurately recorded.” The solution could be an app, a timer, a habit, or a trained assistant.
Ignoring the emotional and social dimensions. Most founders build for the functional job and wonder why users churn. Users do not churn because the product stops working. They churn because it stops making them feel good. Build for the emotional job and retention improves.
Assuming you know the job without asking. Talk to customers. Your assumptions about the job are wrong. They are always wrong. The job lives inside the customer’s experience, not your imagination.
The Framework in Practice
The Jobs-to-be-Done framework is not academic theory. It is a decision-making tool that answers specific questions:
“Should we add this feature?” Does it help get the job done? Yes: add it. No: subtract it.
“How should we market this?” Describe the job, not the product. “Stop dreading tax season” sells better than “Automated expense categorization.”
“Why are customers leaving?” They found something that does the job better. Find out what, and find out why.
“What should we build next?” What adjacent jobs does our customer need done? The freelancer who tracks time also needs to invoice, also needs to manage contracts, also needs to track expenses. Each adjacent job is a potential product extension.
People do not buy products. They hire them to do a job. Understand the job, and everything else — your product, your price, your marketing, your competitive advantage — falls into place.
