Jobs to Be Done:A Practical Framework for Solving Product Problems

Jobs to Be Done: A Practical Framework for Solving Product Problems
Product Management • Customer Research • Innovation

Customers do not simply buy products. They “hire” products and services to make progress in a particular situation. Jobs to Be Done helps product teams understand that situation—and design around the real problem rather than the product they happen to be building.

Imagine you are a product manager. Your product has thousands of users, plenty of analytics, and a long list of feature requests. Yet growth has stalled.

Your team responds in the obvious way: add features, improve the interface, change the pricing, run surveys, and ask customers what they want.

Sometimes this works. But sometimes the team is solving the wrong problem.

This is where Jobs to Be Done (JTBD) becomes useful. Instead of starting with the product, JTBD starts with the customer’s situation and asks:

“What is the customer actually trying to accomplish when they choose this product?” — The central idea behind Jobs to Be Done

The shift sounds subtle, but it can fundamentally change how a product team researches customers, defines problems, identifies competitors, prioritizes opportunities, and designs solutions.

1. What Is Jobs to Be Done?

Jobs to Be Done is a framework for understanding the circumstances and motivations that cause people to choose one solution over another. The Christensen Institute describes JTBD as a lens for understanding the circumstances—or forces—that drive people and organizations toward and away from decisions.

The important idea is that a customer is not necessarily buying a product for the product itself. They are using it to make progress toward something they want to accomplish.

Customer + Situation + Desired Progress = Job to Be Done

For example, saying:

  • “People buy project-management software.”
  • “Our customers are small businesses.”
  • “Users want more dashboard features.”

does not tell you very much about the actual job.

A JTBD-oriented statement might instead be:

“When my team is working across multiple projects, help me quickly understand what needs my attention so I can feel confident that nothing important is being missed.”

Now the product team has something much more useful to investigate.

2. A Job Is More Than a Functional Task

One common mistake is to interpret “job” too narrowly. A job is not simply a functional task such as “upload a document” or “send a payment.”

Jobs can contain functional, emotional, and social dimensions.

Functional

What does the customer practically need to accomplish?

Emotional

How does the customer want to feel before, during, or after the job?

Social

How does the customer want to be perceived by other people?

Consider someone choosing a premium accounting service.

The functional job might be: “Help me prepare my taxes correctly.”

But there may also be an emotional job: “Help me stop worrying that I have made a costly mistake.”

And potentially a social job: “Help me appear financially responsible to my business partners.”

The same product can therefore satisfy multiple dimensions of a customer’s job.

3. The Classic JTBD Case Study: McDonald’s Milkshake

One of the most famous examples of Jobs to Be Done comes from research into McDonald’s milkshake sales, discussed extensively by Clayton Christensen and the Christensen Institute.

The company wanted to increase milkshake sales. The conventional approach was to study the product and its customers.

Researchers asked customers about things such as taste, thickness, price, and product characteristics. Customers gave useful feedback, and the product was improved.

But the improvements did not meaningfully improve sales.

The problem was not necessarily the quality of the research. The problem was the question being asked.

The Wrong Question

The traditional question was essentially:

“How can we make the milkshake better?”

JTBD reframed the question:

“What job causes someone to hire a milkshake in the first place?”

The Researchers Changed Their Observation

Instead of only asking people what they liked about milkshakes, researchers observed when, where, and how people purchased them.

They discovered an interesting pattern: a substantial portion of milkshake purchases occurred in the morning. Those customers were often alone, bought little else, and took the milkshake with them in their cars.

That observation led to a deeper investigation into the circumstances surrounding the purchase.

According to Christensen’s account, these customers often had a long, boring commute. They wanted something that would make the journey more interesting while also keeping them satisfied until later in the morning. They were also dealing with practical constraints: they were in a hurry, wearing work clothes, and effectively had only one free hand.

Suddenly, the competitive landscape looked completely different.

The Real Competition Was Not Just Other Milkshakes

If the job is:

“Help me make my boring morning commute more interesting while keeping me satisfied until lunch.”

then the competitors are not limited to other milkshakes.

The customer could potentially hire:

  • A banana
  • A bagel
  • Coffee
  • Another breakfast food
  • Or even something else that helps make the commute more tolerable

The Christensen Institute explicitly describes this insight: the competitive set for the morning milkshake job extended beyond milkshakes to alternatives such as bananas and bagels.

The Product Was Reframed Around the Job

Once the job became clearer, the relevant product attributes changed.

A thicker milkshake could take longer to consume. That could be valuable if the customer needed something that lasted through a long commute. Convenience also became much more important.

The question was no longer:

“How do we make a better milkshake?”

It became:

“How do we design the experience around the customer’s morning job?”

The key lesson: The customer was not simply buying a milkshake. The customer was hiring the milkshake to make progress in a particular situation.

This is the fundamental power of JTBD.

4. What the Milkshake Case Teaches Product Managers

The case demonstrates several important principles.

1. The Product Is Not the Unit of Analysis

A product manager naturally thinks about products, features, users, funnels, and competitors.

JTBD asks you to move one level deeper:

Traditional Product Thinking JTBD Thinking
Who buys our product? Who experiences this job?
What features do customers want? What progress are customers trying to make?
Who are our competitors? What alternatives can customers hire?
Why do people like our product? What circumstances cause them to choose it?
How can we improve the product? How can we help customers accomplish the job better?

2. Context Matters

The same person can have completely different jobs at different times.

Someone might hire a coffee shop to:

  • Get caffeine before work.
  • Have a quiet place to work.
  • Meet a client.
  • Spend time with a friend.
  • Take a break from a stressful day.

Demographically, these customers could look identical. Their circumstances are completely different.

5. The JTBD Framework for Solving Product Problems

JTBD becomes especially valuable when a product team has a problem but does not yet understand the underlying cause.

Here is a practical six-step process you can use.

1

Define the Product Problem Without Jumping to a Solution

Start with the observed problem, not your proposed feature.

Bad: “We need to build an AI recommendation engine.”

Better: “Users are struggling to decide what action to take next.”

Even better: “Users who have completed their first project often stop using the product because they are uncertain about what to do next.”

The objective is to describe the problem before deciding what the solution should be.

2

Find the Situation Where the Problem Happens

JTBD is highly contextual.

Ask:

  • When does this problem occur?
  • What happened immediately before it?
  • What is the customer trying to accomplish?
  • What constraints are present?
  • What alternatives are available?
  • What happens if they do nothing?

You are looking for a specific situation rather than a generic customer profile.

3

Study the Customer’s Actual Behavior

Do not rely entirely on what customers say they want.

Study what they actually did.

For example, instead of asking:

“Would you use a feature that automatically creates your weekly report?”

ask about the last time they created a report:

  • When did you realize you needed the report?
  • What did you do first?
  • What tools did you use?
  • What was frustrating?
  • What did you try before using our product?
  • What happened after you finished?

This turns a hypothetical conversation into a reconstruction of a real decision.

4

Identify the Job

Now translate the research into a job statement.

A useful format is:

When [situation], help me [make progress], so I can [desired outcome].

For example:

Example: Personal Finance App

Weak statement: “Users want budgeting features.”

JTBD statement: “When I get paid and have multiple upcoming expenses, help me understand how much I can safely spend so I can enjoy my money without worrying that I will run out before payday.”

Notice how much more information is contained in the second statement.

5

Map the Alternatives

Once you understand the job, ask:

“What would this customer do if our product did not exist?”

This is one of the most important questions in JTBD.

Alternatives can include:

  • A competing product
  • A spreadsheet
  • A manual process
  • A colleague
  • A physical product
  • Doing nothing
  • Using a completely different category of product

Your real competitor may not look anything like your product.

6

Design Against the Job, Not Against Competitors

Once you understand the job and the alternatives, identify the dimensions that determine whether the job is successfully completed.

Ask:

  • What makes the job difficult?
  • What takes too long?
  • What creates anxiety?
  • What requires too much effort?
  • Where does the current solution fail?
  • What does the customer have to do manually?
  • What would make the job dramatically easier?

6. The Four Forces Behind a Product Decision

Another useful JTBD concept is the idea that several forces influence whether someone switches from their current solution to a new one.

The Christensen Institute describes four forces of progress.

Push

Dissatisfaction or frustration with the current situation.

Pull

The attraction of the new solution and the progress it promises.

Habit

Existing behaviors and routines that keep people using the current solution.

Anxiety

Concerns about whether the new solution will actually work or create new problems.

In simplified form:

Change becomes attractive when Push + Pull outweigh Habit + Anxiety.

This explains why building a better product does not automatically produce adoption.

A customer can recognize that your product is better and still refuse to switch because the existing solution is familiar and the perceived risk of change is high.

7. A Worked Product Example

Imagine you are building a project-management application.

Your analytics show that many new users create a project, invite their team, and then stop using the product.

The initial product hypothesis might be:

“Users need more onboarding features.”

But that is already a solution.

Instead, use JTBD.

Step 1: Find the Circumstance

Interviews reveal that many users are starting a project after receiving a new client or internal initiative.

Step 2: Reconstruct the Story

They need to get their team organized quickly. They create the project, invite everyone, and then encounter a problem:

“I don’t know how to turn this project into a concrete plan.”

Step 3: Identify the Job

Job Statement

“When I receive a new project, help me quickly turn the initial information into a clear plan that my team can act on, so I can confidently get everyone moving in the same direction.”

Step 4: Identify the Existing Alternative

The customer might currently:

  • Create a spreadsheet.
  • Write a document.
  • Hold a meeting.
  • Ask an experienced colleague for help.
  • Use a template from another project.

Now the product team understands what it is actually competing against.

Step 5: Find the Opportunity

Instead of building ten more project-management features, the team might focus on reducing the time between:

“I have a project” → “My team has a clear plan”

That could lead to templates, guided project setup, intelligent task decomposition, example plans, or other solutions.

The specific solution should come after understanding the job—not before.

8. How to Conduct a JTBD Interview

Good JTBD research is less about asking people to design your product and more about reconstructing a real decision.

A useful interview structure is:

Start With a Real Event

Ask the customer to describe the last time they:

  • Bought the product.
  • Started using it.
  • Switched from another product.
  • Considered buying but decided not to.
  • Stopped using it.

Walk Backward Through the Story

Ask:

  • What was happening at the time?
  • What triggered the need?
  • What were you doing before?
  • What alternatives did you consider?
  • What made you start looking for something else?
  • What concerned you about changing?
  • What finally made you choose the product?
  • What happened after you started using it?

Avoid Leading Questions

Instead of:

Leading: “Would an automated dashboard save you time?”

ask:

“Tell me about the last time you needed to understand what was happening across your projects.”

The second question allows the customer to reveal their existing behavior rather than confirming your hypothesis.

9. How to Turn Research Into a Product Opportunity

Once interviews are complete, do not immediately start brainstorming features.

First, synthesize the research.

Look for patterns across:

  • Situations
  • Triggers
  • Desired progress
  • Barriers
  • Existing alternatives
  • Emotional concerns
  • Social considerations
  • Moments of switching
  • Moments of abandonment

Then create an opportunity statement.

When [circumstance], customers struggle to [make progress] because [barrier].

For example:

Opportunity Statement

“When new customers receive their first large project, they struggle to create an actionable plan because translating unstructured information into tasks requires significant effort and experience.”

That is a much stronger foundation for product discovery than:

“We should build an AI project planner.”

10. JTBD Changes How You Think About Competition

Traditional competitive analysis usually asks:

  • Who sells a similar product?
  • What features do they have?
  • How much do they charge?
  • Where are we better?

JTBD asks a different question:

“What else could the customer hire to accomplish this job?”

This can dramatically expand your competitive landscape.

Product Possible Job Potential Alternatives
Project-management software Keep a team aligned Meetings, spreadsheets, chat, documents
Food-delivery app Get dinner without spending time cooking Cooking, takeaway, meal kits, supermarket food
Fitness app Stay accountable to an exercise routine Gym, trainer, friend, calendar, classes
Note-taking app Capture information so it can be found later Paper, email, documents, memory, messaging apps

Your most dangerous competitor may therefore be a spreadsheet, a notebook, a meeting, or simply the customer’s existing habit.

11. Common JTBD Mistakes

Mistake 1: Defining the Job as a Feature

Wrong: “The job is to create an automated report.”

That describes a solution.

Better: “Help me quickly understand what changed so I know where I need to take action.”

Mistake 2: Defining the Job Too Broadly

Too broad: “Help me be successful.”

Almost anything could satisfy that job, which makes it difficult to design against.

Add the situation and desired progress.

Mistake 3: Treating Demographics as the Job

“Our job is to serve millennials” is not a JTBD statement.

A demographic describes who someone is. A job describes what they are trying to accomplish in a particular circumstance.

Mistake 4: Asking Customers to Invent the Solution

Customers are valuable sources of evidence about their problems and behavior. That does not mean every feature request should become a product requirement.

Your job is to understand the underlying progress they are trying to make.

Mistake 5: Ignoring the Status Quo

If customers already have a solution—even an ugly one—you must understand why they continue using it.

Existing habits are powerful.

12. A Practical JTBD Worksheet

Use the following worksheet whenever your team faces an ambiguous product problem.

1. What product problem are we observing?

Describe the behavior without proposing a solution.

2. In what situation does it happen?

Identify the specific circumstance or trigger.

3. What progress is the customer trying to make?

What are they ultimately trying to accomplish?

4. What is the functional job?

What practical outcome are they trying to achieve?

5. What is the emotional job?

How do they want to feel?

6. What is the social job?

How do they want to be perceived?

7. What alternatives do they currently use?

Include products, manual processes, people, and doing nothing.

8. What pushes them away from the current solution?

Identify frustration, limitations, costs, or changing circumstances.

9. What pulls them toward a new solution?

What improvement makes change attractive?

10. What keeps them with the current solution?

Identify habits, switching costs, familiarity, and workflows.

11. What creates anxiety about switching?

What could make the new solution feel risky?

12. How could we help customers accomplish the job better?

Only now should you begin exploring solutions.

13. From JTBD to Product Strategy

JTBD is not simply a customer-interview technique. It can become a product strategy tool.

Once you understand the job, you can use it across the product lifecycle.

Product Activity JTBD Application
Discovery Understand the circumstances that create demand.
Research Reconstruct real customer decisions and switching events.
Segmentation Segment around jobs and circumstances, not only demographics.
Competitive analysis Identify every alternative customers can hire.
Prioritization Prioritize opportunities where important jobs are poorly served.
Product design Design around the desired progress and constraints.
Marketing Communicate the progress the product helps customers make.
Growth Reduce friction between the customer’s trigger and successful job completion.

14. The Most Important Mindset Shift

The deepest lesson of JTBD is not a template or interview script.

It is a change in how you look at products.

Instead of seeing:

Users → Products → Features

start thinking:

Circumstance → Struggle → Desired Progress → Alternatives → Choice

The product is part of that story. It is not the story itself.

A customer does not wake up thinking:

“I need a project-management SaaS platform today.”

They wake up with a situation.

They have something they need to accomplish. They have constraints. They have habits. They have anxieties. They have alternatives.

Your product becomes valuable when it helps them make the progress they are already trying to make.

Conclusion

Jobs to Be Done gives product teams a powerful way to move from feature thinking to problem thinking.

The McDonald’s milkshake example illustrates the central idea: understanding the product alone was not enough. Researchers needed to understand the situation in which customers were choosing it, the progress they were trying to make, and the alternatives they could use instead.

For product teams, the practical sequence is:

  1. Start with a real customer problem.
  2. Understand the situation in which it occurs.
  3. Reconstruct what customers actually did.
  4. Identify the progress they were trying to make.
  5. Map functional, emotional, and social dimensions.
  6. Identify the alternatives they could hire.
  7. Understand the forces pushing them away from the current solution.
  8. Understand what attracts them to something new.
  9. Identify habits and anxieties that prevent change.
  10. Only then design and test solutions.

The goal of JTBD is therefore not simply to discover what customers want. It is to understand why a customer needs to make progress in a particular situation—and then design a product that helps them do it better.

Further reading and sources

This article’s explanation of the McDonald’s milkshake case and the core JTBD concepts is based on material from the Christensen Institute and Harvard Business Review, including Christensen’s discussions of Jobs to Be Done and the milkshake research.

  • Christensen Institute — Jobs to Be Done Theory
  • Christensen Institute — The Forces of Progress
  • Harvard Business Review — Revisiting “Jobs to Be Done” with Clayton Christensen
  • Harvard Business Review — The “Jobs to Be Done” Theory of Innovation
Jobs to Be Done — A Practical Product Management Guide

Leave a Reply

Your email address will not be published. Required fields are marked *