What Is Jobs to Be Done?

The Job, Not the Product

When someone buys a drill, they're not really buying a drill. They're buying a hole in the wall. When someone signs up for a productivity app, they're not buying software — they're hiring it to help them feel less overwhelmed at work. Jobs to Be Done (JTBD) is a way of thinking that focuses on what customers are really trying to accomplish, rather than what product they happened to buy.

The idea comes from Clayton Christensen, who noticed that customers don't buy products — they "hire" them to get a specific job done. And just like hiring someone for a task, customers will switch products if a better option comes along that does the job faster, cheaper, or easier.

Here's the key insight: people don't want your product. They want the outcome your product gives them. A fitness app isn't giving you a workout tracker — it's giving you the feeling of being healthier and more confident. A to-do app isn't giving you a list — it's giving you peace of mind that nothing falls through the cracks.

Build the Right Thing

Most products fail because teams build what they think customers want, based on feature comparisons with competitors. JTBD flips that. Instead of asking "what features should we add?" you ask "what job is our customer trying to get done, and what are they currently settling for?"

This changes everything about how you design, market, and improve a product. When you understand the job, you stop fighting over features and start solving the actual problem. You also catch things you'd never see in a survey — like why customers switch away from you despite loving your product.

Finding the Real Job

The JTBD framework asks a simple question: "What job does this customer need to get done in their life?" Not in your app — in their life. The job has to be stated in terms of progress, not in terms of features. Here's how it breaks down:

The job itself has three parts: a functional part (what needs to happen), an emotional part (how the customer wants to feel), and a social part (how they want to be seen by others). A great product addresses all three.

For example, someone "hiring" a running shoe isn't just getting shoes — they want to feel like a runner (emotional), they want shoes that don't hurt their feet (functional), and they want to be seen as athletic (social). Your product doesn't have to solve all three perfectly, but you should know which one you're betting on.

The Fast Food Story

Here's a real example of JTBD thinking in action. A fast food chain noticed customers were ordering more sandwiches but fewer sides. They assumed people wanted fewer sides — so they considered cutting the side menu. But when they asked customers what they were really doing, they found something different.

Customers were ordering sandwiches as meal replacements — quick lunches at work. The problem was they felt guilty about not eating vegetables. So they skipped the sides to feel like they were making a healthier choice, even though the sandwich itself might have been less healthy.

The fix wasn't about the sides. It was about helping customers feel less guilty about their lunch choice. The team redesigned the menu to include a "balanced meal" option with a smaller sandwich and a vegetable side — making it easy for customers to feel like they were making a good choice without giving up their sandwich-for-lunch habit.

BEFORE (feature-focused):
"How do we get customers to order more sides?"

AFTER (job-focused):
"How do we help customers feel less guilty about
skipping vegetables — without changing what they
actually want to eat?"

That small shift in how you frame the problem leads to completely different solutions. The question is never "what feature should we add?" It's always "what job are we hired to do, and are we doing it well?"

Knowledge Check

Test what you learned with this quick quiz.