What's the difference between a Job to be Done and a task?

A task describes what you do with a product (store music, organize files). A Job describes how you want to change as a person (become someone who can grow a company beyond 5 employees). Tasks are product-centric; Jobs are person-centric. Pandora and Spotify were designed so customers didn't have to 'store and retrieve music' — they eliminated the task entirely. The Job (evolving your emotional relationship with music) stayed the same.

Are there different types of Jobs (emotional, functional, social)?

No — and trying to categorize them is a waste of time. Practically, each Job is a unique combination of emotional desires (belonging, self-expression, control). Theoretically, no objective test can classify a Job as 'social' vs 'emotional.' If someone buys a Ferrari to impress others, is that social or personal insecurity? The team will debate endlessly and gain nothing. Just describe the Job as it is.

How do you identify a customer's Job to Be Done?

Interview customers about their 'switch story' — don't ask for feature wishlists. Ask: 'Tell me the story of how you came to use our product.' Understand the trigger event, what they were doing before (the old way), what frustrated them (the struggle), and what they imagined becoming (the new me). Then test it: Does it describe a transformation? Does it describe progress from situation A to B? Are there constraints that require a product?

How does JTBD relate to competition and creative destruction?

JTBD incorporates Schumpeter's insight that competition doesn't just come from similar products — it can come from anywhere. Your real competitor might be spreadsheets, email, or the customer's assumption that 'this is just how things work.' Deming added that simply improving your current product isn't enough — happy customers will abandon you the moment someone invents a fundamentally new way to get the Job Done, just as vacuum tube customers abandoned for transistor radios.

Jobs to Be Done (JTBD): The Complete Framework for Building Products People Actually Buy (2025)

Q: What is Jobs to Be Done (JTBD)?

Jobs to Be Done is a theory of consumer action that explains why people buy products. The formal definition: 'A Job to be Done is the process a consumer goes through whenever she aims to change her existing life-situation into a preferred one, but cannot because there are constraints that stop her.' The key insight is that customers don't buy products for features — they 'hire' products to help them become a better version of themselves. It's a process (starts, runs, ends), not a state.

Upgrade Your User, Not Your Product

There's a line that captures the entire Jobs to Be Done philosophy in a single sentence:

"Don't build better cameras — build better photographers."

— Kathy Sierra

This is the foundation of Jobs to Be Done (JTBD) — a theory of consumer action that explains why people buy things. Not what they buy, not how they use it, but why they switch from one solution to another. And understanding this distinction is the difference between building products that sell and products that sit.

Charles Revson, founder of Revlon, understood this intuitively: "In the factory we make cosmetics; in the drugstore we sell hope." Revlon's breakout 1952 "Fire and Ice" campaign barely mentioned the product. One page was provocative questions ("Have you ever wanted to wear an ankle bracelet?"). The other was a glamorous photo. What was being sold? Not lipstick — a "new me."

What Is a Job to Be Done?

JTBD is a theory of consumer action. It describes the mechanisms that cause a consumer to adopt an innovation. Here's the formal definition:

📋 JTBD Defined

"A Job to be Done is the process a consumer goes through whenever she aims to change her existing life-situation into a preferred one, but cannot because there are constraints that stop her."

The key words: process (it starts, runs, and ends), change (from current state to preferred state), and constraints (the reason they need a product to help).

Markets grow, evolve, and renew whenever customers have a Job to be Done and then buy a product to complete it. The critical insight: a JTBD describes how a customer changes or wishes to change — not what features they want or tasks they need to accomplish.

The Bear vs. The Human

Alan Klement, one of the leading JTBD practitioners, uses a powerful analogy to explain the difference between task-based thinking and JTBD thinking:

🐻 The Bear (Task Thinking)

"I wish fishing could be made better, faster, or easier."

The bear thinks only about what is. Today it may find a better way to fish. But tomorrow, it is still a bear that fishes. No transformation. No evolution.

🧠 The Human (JTBD Thinking)

"Fishing is no good. If I could transform that lagoon into a fish breeding place, I'd never have to fish again."

The human thinks about what ought to be. Today she fishes, but tomorrow that can change. She's imagining a new version of herself — one who doesn't fish at all.

The bear never has a Job to be Done. The human does — every time she begins the process of evolving herself and her situation.

A Real JTBD in Action: The Basecamp Story

Here's a real example from JTBD research that shows exactly how a Job to be Done works in practice:

Andreas's Job to Be Done

CURRENT SITUATION

Andreas runs a medical tourism business with 5 employees. He uses Google Sheets, Docs, and email to manage everything. He assumes this is just how companies his size operate.

THE TRIGGER

At a coffee shop, his friend Jamie mentions Basecamp — a project management tool for small businesses. Andreas didn't know such a thing existed. He assumed tools like Microsoft Project were only for big companies.

THE "NEW ME" EMERGES

As Jamie talks, Andreas's mind races: "Basecamp could help my company stay organized as it adds more customers and employees." Until this moment, he assumed his company had hit its growth limit. Now he can imagine a different future.

THE JOB GETS DONE

Andreas researches Basecamp and competitors, chooses Basecamp, signs up, and grows his company beyond 5 employees for the first time.

Notice: the Job wasn't "manage projects" or "organize tasks." The Job was "become the kind of business owner who can grow beyond 5 employees." The product was just the tool that enabled the transformation.

💡 JTBD Is a Process, Not a State

A JTBD isn't something consumers have — it's something they participate in. It starts (trigger), runs (search and evaluation), and ends (adoption and transformation). Compare it to falling in love: you don't "have" falling in love; you participate in it. And just as you can't fall in love by yourself, a customer can't complete a JTBD without a product to help.

What Is NOT a Job to Be Done

This is where most people get JTBD wrong. The biggest and most common mistake:

⚠️ The #1 JTBD Mistake: Confusing Jobs with Tasks

Examples of things people incorrectly call "Jobs":

❌ "Store and retrieve music"

This is a task. Pandora and Spotify were designed so customers didn't have to store and retrieve music at all.

❌ "Listen to music"

This is an activity. Humans listened to music 10,000 years ago and will in 10,000 more. What changes is how they evolve themselves through music.

Tasks and activities describe how you use a product or what you do with it. A Job to be Done describes how you want to change.

There Are No "Types" of Jobs

Another common mistake: categorizing Jobs into "emotional," "functional," and "social" types. Klement explains why this is both practically and theoretically wrong:

Practically wrong

Each Job is unique — a unique combination of core emotional desires (belonging, self-expression, control). Facebook taps into control, self-expression, and belonging, but does so in its own unique way. Categorizing Jobs into types creates false boundaries.

Theoretically wrong

No objective test exists to classify Jobs. If someone buys a Ferrari to impress others, is that a "social" Job or a "personal/emotional" Job rooted in insecurity? The team will endlessly debate categories — gaining nothing. Knowing why the customer bought the Ferrari is enough.

The JTBD Decision Tree

When evaluating whether something is truly a Job to be Done, use this simple test:

🌳 Is It a Job to Be Done?

Does it describe a "new me" — a transformed state?

It must answer: "How are you better since you started using [product]?" If it describes an activity (listen to music) or a task (store files), it's not a Job.

Does it describe progress — moving from situation A to situation B?

Psychologist Albert Bandura described humans as "proactive, aspiring organisms." JTBD carries this into markets: we buy and use things to improve ourselves, to make progress.

Are there constraints preventing the change without a product?

If the customer could achieve the transformation on their own (by snapping their fingers), there's no Job. The need for a product to enable the change is what creates the market.

The Intellectual Roots of JTBD

JTBD isn't a single person's invention — it's the product of decades of work across economics, systems thinking, and psychology. Understanding the lineage helps you apply the theory more effectively:

Joseph Schumpeter: Creative Destruction

Going back 75+ years, Schumpeter observed that new innovations steal customers from incumbents and eventually replace them. Horses → trains → cars → airplanes. Two insights JTBD incorporates:

• Customers switch solutions — and understanding why they switch is the key to innovation
• Competition can come from anywhere — not just products of the same "type." Your real competitor might be something you've never considered

W. Edwards Deming: Systems Thinking

Deming's most important contribution: producers and customers are connected by systems. "The customer and producer must work together as a system."

"Makers of vacuum tubes improved year by year the power of vacuum tubes. Customers were happy. But then transistor radios came along. Happy customers of vacuum tubes deserted vacuum tubes and ran for the pocket radio."

Simply making your product better isn't enough. Someone else can invent an entirely new way to get the Job Done.

Behavioral Economics: Irrational Customers

Influences from Kahneman, Tversky, Loewenstein, and Klein help JTBD account for the fact that customers don't make rational decisions. They're inconsistent in their opinions, don't always act in their self-interest, and are driven by emotional forces. If you want to make a great product, you have to understand the emotional forces shaping customer motivation.

Palmer, Pedi & Moesta: The Language of "Jobs"

In the 1990s, John B. Palmer, Rick Pedi, and Bob Moesta combined their experiences into the first JTBD principles — including the language that customers have "Jobs" they're trying to get "Done." This framing gave the theory its accessible, actionable vocabulary.

How to Apply JTBD to Your Startup

Understanding JTBD theory is one thing. Applying it to build products people actually buy is another. Here's a practical framework:

Interview customers about their switch — not their wish list

Don't ask "what features do you want?" Ask "tell me the story of how you came to use our product." Understand the trigger, the old way, the struggle, and the new me they imagined. Andreas didn't want "project management features" — he wanted to grow beyond 5 employees.

Describe the Job as a transformation, not a task

Instead of "organize projects" → "become the kind of company that can scale beyond its current limits." Instead of "send emails" → "maintain relationships with people I care about without it consuming my day." The Job is always about the person changing, not the tool working.

Identify the real competition

Your competitors aren't just similar products. They're everything the customer is currently doing to get the Job Done — including doing nothing. Andreas's competition wasn't other project management tools. It was Google Sheets, email, and the assumption that "this is just how small companies work."

Design your marketing around the "new me"

Like Revlon, sell the transformation — not the ingredients. Your landing page, ads, and pitch should help customers imagine the "new me" they'll become. Feature lists are the bear's way of thinking. Transformation stories are the human's way.

Remember: "A dissatisfied customer does not complain; he just switches"

Deming's warning applies directly. Your happiest customers could leave tomorrow if someone invents a fundamentally better way to get the Job Done. Don't just improve what exists — keep asking: "What will we be making five years from now?"

The Bottom Line

JTBD reframes every product decision around a single question: "How does our customer want to change?" Not what features they want. Not what tasks they need to complete. But what "new me" they're trying to become — and what constraints are stopping them.

When you build products through this lens, you stop competing on features and start competing on transformation. And as Revlon proved 70 years ago: people don't buy products. They buy better versions of themselves.

🚀 Find Investors Who Understand Your Customer's Job

The best investors evaluate startups through the JTBD lens — they ask "what Job does this solve?" not just "what's the TAM?" Search 100K+ verified VC and angel profiles on Datapile to find investors aligned with your approach to building products.

Search Investors →