Jobs-to-be-done research: How to apply JTBD in user interviews

Most user research collects feedback on what users think about a product or how they use it. Jobs-to-be-done research asks a different question: why did users decide to change their behavior, and what are they ultimately trying to accomplish? That shift in framing produces a fundamentally different type of insight, one that is more useful for product strategy, positioning, and identifying where a product genuinely creates value.

This article covers the JTBD framework, how to apply it in research interviews, and what to do with the findings once you have them.

The core idea behind JTBD

Clayton Christensen introduced the jobs-to-be-done concept to explain why customers choose products. His argument: customers do not buy products for their features. They “hire” products to accomplish a job, a specific goal in a specific context. Understanding the job, what the customer is trying to accomplish, in what situation, under what constraints, produces more durable insight than asking about feature preferences.

The classic illustration is the drill bit. People who buy a quarter-inch drill bit do not want a drill bit. They want a hole. More specifically, they want to hang a shelf, attach a fixture, or complete a home project. The drill bit is just the current best tool for accomplishing that job.

Applied to software, the insight becomes more significant. Users do not want CRM features. They want to maintain client relationships, hit revenue targets, and demonstrate performance to their leadership. They do not want project management software. They want their team to finish work on time without constant manual coordination. Products that understand the underlying job, and design everything from features to onboarding to messaging around it, consistently outperform products that optimize for feature satisfaction.

JTBD research is the practice of uncovering those underlying jobs from the people who have made the decision to hire or fire a product.

Three types of jobs

Not all jobs are functional tasks. Understanding the full job requires recognizing that customers are trying to accomplish things at multiple levels simultaneously.

Functional jobs are the practical outcomes a customer is trying to achieve. Complete the quarterly financial report. Onboard a new team member. Ship a product update before the deadline. These are the direct, task-level goals that are easiest to identify in research because customers can articulate them without much probing.

Emotional jobs describe how the customer wants to feel as a result of using the product. Feel confident the data is accurate before presenting it to leadership. Stop worrying about whether a compliance deadline has been missed. Feel in control of a process that previously felt chaotic. Emotional jobs are often more influential than functional jobs in driving product adoption and loyalty, but they are rarely what customers mention first. You have to ask for them.

Social jobs reflect how the customer wants to be perceived by others. Be seen as a strategic thinker rather than a tactical executor. Demonstrate technical sophistication to a team. Show leadership that the function is under control. Social jobs are particularly relevant in B2B contexts where product choices affect organizational status and where the decision to adopt a product often requires internal persuasion.

Products that address only functional jobs compete primarily on features and price. Products that address functional, emotional, and social jobs together are harder to displace because switching means giving up benefits that users cannot easily quantify or articulate.

The switch interview structure

The most effective way to surface JTBD insights is through a specific interview structure focused on the switch moment: the point when a customer decided to change their approach, either by adopting a new product, abandoning an existing one, or making any significant behavioral change. That moment contains the job with all its context.

Start with the event that triggered the search (about ten minutes). Ask the participant to think back to when they first started looking for a different approach to the problem. What was happening at that point? What made the status quo unacceptable at that specific moment rather than earlier?

You are looking for the specific situational trigger, the emotion associated with it, and what changed that made action necessary now. Participants often describe triggers they have never articulated before because no one has asked. The trigger reveals the job at its most specific and most emotionally charged point.

Explore the search and evaluation process (about ten minutes). Ask what they looked for, how they evaluated options, and what mattered most in the decision. What sources of information did they consult? What alternatives did they seriously consider? What criteria did they apply?

This stage reveals the purchase criteria, the competitive landscape as the customer experienced it, and the trade-offs they were willing to make. That information is more useful for positioning and messaging than any customer survey asking which features are important.

Understand the decision (about five minutes). Ask what ultimately led them to choose the solution they chose, and what almost stopped them. What was the deciding factor? What concerns needed to be resolved before they committed?

The answer to the second question, what almost stopped them, often reveals the anxieties that your product’s onboarding, messaging, and early experience need to address for new users who have not yet committed.

Explore the job in use (about ten minutes). Ask them to walk you through how they use the product in a typical week. What are they trying to accomplish when they use it? What does a successful session look like?

This is where the functional job becomes fully visible. Most customers can articulate it clearly at this stage because they are describing their own ongoing experience. Follow up by asking about the emotional outcome when things go well. How do they feel after a successful session? What does it let them do or stop worrying about?

Define their measure of success (about five minutes). Ask how they know the product has done its job well. What does success look like? How has it changed anything for them?

The answers here reveal the outcome metrics the customer uses internally, often different from the metrics your team tracks, and how the product affects their standing or capability within their organization.

Writing a job statement

A well-formed JTBD job statement captures the situation, the motivation, and the expected outcome in a single sentence that can anchor product decisions.

The structure is: when [situation], I want to [motivation], so that [expected outcome].

For example: “When I am preparing for a board presentation, I want to consolidate financial data from multiple systems quickly so that I can present accurate figures without spending my weekend on it.”

That job statement says more about what the product needs to do than any feature list. It defines the context of use, the urgency, the functional need, and the emotional stakes simultaneously. Features, messaging, onboarding, and pricing can all be evaluated against whether they help users accomplish the job expressed in the statement.

Extract job statements from interview data by looking for repeated situations across multiple participants, the triggers that preceded their decisions, and the definitions of success they use to evaluate the product. Job statements that appear consistently across different participants in a segment represent genuine, durable product requirements.

Analyzing JTBD research findings

Surface the job behind the feature request. When participants say “I wish I could export this to Excel,” the literal request is an export feature. The underlying job might be “share data with colleagues who do not use this software” or “satisfy the expectation of my manager who works primarily in spreadsheets.” The feature request and the job often suggest entirely different solutions. Identifying the job prevents teams from building the requested feature when a more fundamental solution would serve users better.

Map forces for and against switching. JTBD analysis identifies two types of forces operating on customers: forces pushing them toward change (dissatisfaction with the current approach, attraction toward a better solution) and forces creating inertia (anxiety about switching costs, habit and comfort with the current approach). Mapping these forces informs adoption strategy, messaging, and onboarding design. If anxiety about data migration is a significant inertia force, the product’s onboarding needs to address that directly.

Segment customers by job, not demographics. One of the most practically valuable insights from JTBD research is that customers in very different demographic groups often share the same job, and customers in the same demographic group often have very different jobs. Job-based segmentation typically produces more actionable product strategy than age, company size, or industry segmentation alone because the job is what determines whether the product creates genuine value for the user.

Identify underserved jobs. Jobs that are important to customers but poorly served by current solutions represent genuine product opportunities. The combination of high importance and high dissatisfaction marks the areas where new product investment is most likely to create switching behavior. JTBD research produces a map of the competitive landscape as users experience it, not as your marketing team frames it.

Applying JTBD in B2B research

B2B JTBD research involves multiple stakeholders who have different jobs. A procurement manager evaluating a research platform has a different job than the researcher who will use it daily. An IT administrator has a different job than both. An executive sponsor approving the budget has a different job than all three.

B2B JTBD research requires conducting switch interviews across all the roles involved in the adoption decision and in ongoing use. A product that accomplishes the researcher’s job while creating significant friction for IT administration faces an adoption obstacle that will not appear in interviews with researchers alone.

For recruiting qualified B2B participants across multiple roles and seniority levels, CleverX’s panel of 8 million verified professionals with filtering by job function, industry, seniority, and company size provides access to the specific practitioner profiles JTBD research requires. Multi-stakeholder B2B research can be fielded through a single recruitment source rather than managing separate channels for each role. See what is generative research for how JTBD research fits within the broader user research in product management category.

Using JTBD findings in product strategy

JTBD research findings are most powerful when they are actively used to evaluate product decisions rather than filed as a reference document.

Product roadmap decisions can be evaluated against the primary job: does this feature help customers accomplish the job, or does it address a secondary concern that is less critical to the job’s completion? Features that do not clearly connect to the primary job are candidates for deprioritization.

Onboarding design should be structured around the path to first job completion, not the product’s full feature set. Users who experience the job being accomplished early in their first session are significantly more likely to continue using the product. See how to conduct user interviews for the interview techniques that underpin JTBD research.

Messaging and positioning benefit directly from job statement language. When product messaging uses the vocabulary customers use to describe their job, it resonates in a way that feature-list messaging does not. Analyzing user interview data from JTBD research produces the exact language that customer acquisition and retention efforts should be built around.

Frequently asked questions

How is JTBD different from standard user interviews?

Standard user interviews can focus on behavior, usability, preferences, or any research question. JTBD interviews are specifically structured around the switch moment to surface the underlying job and the forces that drove the decision to change. The distinction is in the framing and the specific probes used: JTBD interviews ask about triggers, evaluation criteria, anxieties, and success definitions in a sequence designed to reconstruct the full context of the hiring decision. See customer discovery interview guide for a related method focused on pre-product discovery.

How many JTBD interviews do you need?

Ten to fifteen switch interviews with your primary customer segment typically surfaces the major jobs and the forces driving them. Saturation occurs when new interviews stop revealing new jobs, new triggers, or new forces, usually within fifteen to twenty interviews for a well-defined segment. If you are researching multiple distinct customer segments, plan for ten to fifteen interviews per segment. See how to calculate research sample size for the reasoning behind these numbers.

Can JTBD research be done with existing customers only?

Interviewing existing customers is the most common approach because the switch moment is recent and memorable. Former customers who churned are also valuable: they fired the product to hire something else, and understanding that switch reveals the job the product failed to accomplish adequately. Both populations contribute to a complete picture of the job landscape. If you have access to recent churned customers alongside active ones, prioritize getting both groups into the research.