What is jobs-to-be-done theory?

Jobs-to-be-done (JTBD) theory is a framework for understanding why customers choose the products and services they use. Rather than focusing on who the customer is, JTBD focuses on what the customer is trying to accomplish — the "job" they are trying to get done — and the circumstances that drive them to seek a solution.

The theory was popularized by Harvard Business School professor Clayton Christensen and expanded in his 2016 book Competing Against Luck, co-authored with Taddy Hall, Karen Dillon, and David Duncan. At its core, the framework argues that customers don't buy products — they hire them to make progress in their lives.

The core idea: customers "hire" products to do a job

The central metaphor of JTBD is that of hiring. When a customer chooses a product, they are hiring it to fulfill a specific need at a specific moment. When the product stops fulfilling that need — or a better alternative comes along — they fire it and hire something else.

Christensen's most famous illustration of this is the milkshake story. A fast food chain wanted to increase milkshake sales. Traditional market research (segmenting by demographics, asking customers what improvements they wanted) produced little insight. When researchers instead asked what job customers were hiring a milkshake to do, a pattern emerged: many customers bought milkshakes in the morning for their commute. The job was to keep them full and give them something to do during a long, boring drive. The competition wasn't other milkshakes — it was bananas, bagels, and coffee. This reframe completely changed how the company thought about the product.

Three types of jobs

Every job has multiple dimensions. Understanding all three helps teams design more complete solutions.

Functional jobs

The practical, task-oriented goal the customer wants to accomplish. "Get from point A to point B" is a functional job. "Consolidate customer feedback from five different sources into one place" is a functional job. These are the most straightforward to identify and address.

Emotional jobs

How the customer wants to feel — or not feel — as a result of getting the job done. A user doesn't just want to complete a research report; they want to feel confident presenting it to leadership. Emotional jobs shape what "good enough" looks like and explain why technically superior products can lose to ones that feel better.

Social jobs

How the customer wants to be perceived by others. A product manager who presents data-backed recommendations wants to be seen as rigorous and trustworthy. A designer who surfaces user insights wants to be recognized as an advocate for the user. Social jobs influence which solutions feel worth the effort.

How JTBD differs from traditional segmentation and personas

Traditional market research segments customers by who they are: age, industry, company size, role. JTBD segments them by what they are trying to accomplish and under what circumstances.

The distinction matters because demographics don't predict behavior as reliably as we assume. Two 40-year-old product managers at similarly sized companies might have completely different jobs to be done depending on their organizational context, their team's maturity, and the specific decision they're trying to make today.

JTBD doesn't replace personas — it complements them. Personas humanize the user and build empathy; JTBD explains the underlying motivation behind their behavior and the criteria they use to evaluate solutions.

The JTBD interview method

The most direct way to uncover jobs is through interviews, specifically the "switch interview" or "timeline interview" technique developed by Bob Moesta and Chris Spiek.

The approach focuses on a specific moment in time: the day a customer decided to use your product or switch from a competitor. By reconstructing the sequence of events, thoughts, and feelings leading up to that decision, researchers surface the real job that drove the switch.

Key questions include:

• "Walk me through the day you first decided to look for a solution. What was happening?"
• "What were you using before? What made you start thinking about switching?"
• "When did you first start to feel like your old approach wasn't working?"
• "What almost stopped you from making the change?"
• "After you started using this, when did you first feel like it was working?"

The goal is to understand the full timeline — the struggling moment, the passive and active search, the decision, and the first moment of progress — rather than just the point of purchase.

How to write a job statement

A well-formed job statement makes the customer's goal explicit and actionable. The standard format is:

[Action verb] + [object of the action] + [contextual clarifier]

Examples:

• "Minimize the time it takes to synthesize interview data so I can share findings while they are still relevant."
• "Increase confidence in my product roadmap decisions without needing to run a major research project every quarter."
• "Reduce the risk of building the wrong feature by validating assumptions before engineering investment."

Job statements are most useful when they describe the outcome the customer is seeking — not the feature or solution they think they need.

Applying JTBD in product research and development

JTBD has practical applications across the product development lifecycle.

Roadmap prioritization. When evaluating which problems to solve, JTBD helps teams assess whether a proposed feature addresses a real, frequent, and underserved job — rather than a nice-to-have.

Go-to-market messaging. Understanding the job reveals the language customers use to describe their struggle. The most effective product messaging speaks to the job in the customer's own words, not the product team's terminology.

Competitive analysis. JTBD reframes who your real competitors are. The alternatives customers consider when hiring your product include not just direct competitors but workarounds, manual processes, and doing nothing. Understanding the full competitive set sharpens positioning.

Product-market fit. A product achieves strong fit when it reliably gets the job done better than any available alternative. JTBD gives teams a concrete way to define and measure fit beyond surface-level satisfaction scores.

Getting started with JTBD

The fastest way to start applying JTBD is to run five to ten switch interviews with recent customers — people who adopted your product in the last three to six months. Focus on the circumstances that led to their decision, not their opinions about features.

Look for patterns in the struggling moment: the specific situation that made the status quo unacceptable. That struggling moment is where the job lives, and it is where the most valuable product opportunities are found.