JazmineN
ServiceNow Employee

Overview

Jobs-to-be-done (JTBD) is a framework for understanding the underlying goal your customers are trying to achieve, not the feature they asked for or the tool they're using today. Across industries and enterprises, JTBD helps teams step back from individual requests and focus on the needs and outcomes that matter most. It's for anyone who wants to build the right thing instead of just more things. If you've got a backlog full of feature requests and no clear sense of what actually matters most, JTBD gives you a way to find out. That understanding gives teams a stronger foundation for making decisions about what to prioritize and where to invest. One way teams can apply JTBD is to inform ServiceNow product and implementation decisions, helping determine what to build, improve, or configure based on real customer needs. 

 

The job is the goal, not the task or the tool 

 

People don't buy products. They hire them to get a job done. 

 

A job is the underlying goal someone is trying to accomplish. While products, features, and technology change over time, the job itself often stays the same. 

 

JTBD helps you focus on the outcome people want, not the tool they use to achieve it. 

 

Imagine an HR leader who wants to improve the new-hire onboarding experience. The initial requests are familiar: 

  • Create a better onboarding checklist
  • Send fewer emails
  • Improve the new-hire portal
  • Add more training content

But those solutions focused on the tools and touchpoints. When viewed through a JTBD lens, the underlying goal is broader: new employees are trying to understand what they need to do, get access to what they need, and feel ready to contribute. 

 

The opportunity shifts from “How do we build a better onboarding checklist?” to “How do we help new hires become productive and confident?” 

 

The JTBD Mindset

JTBD encourages you to stop asking: "What features do you want?"  And start asking: "What are you trying to get done?" 

 

Why JTBD is impactful

Three things make this framework worth the effort: 

  • It focuses on the problem, not the solution — so you can get to the root of what customers are trying to accomplish instead of chasing individual feature requests. That means clearer priorities and fewer wasted builds. 
  • It has a concrete, measurable outcome so you can move beyond vague user needs and define what success actually looks like. That gives you a way to tell whether a change meaningfully helped customers get the job done. 
  • It's evergreen because the solutions that support a job may change entirely, while the underlying job remains more stable. That gives you a durable foundation for making decisions even as technology evolves. That's exactly why it's a useful lens for AI-native thinking: the tools are changing fast, but the jobs your customers need done aren't. 

 

Getting started with JTBD

You don't need a full research study to get value from a JTBD mindset. Here's how to try a lightweight version yourself: 

 

1. Select a product or service area

Start with a product or service you provide today, ideally one where customers have run into problems. Or pick one you want to improve, just like in the milkshake example. 

 

2. Write three jobs related to that product/service to focus on

Writing a job statement helps you articulate what your customers are using your product or service to accomplish while also keeping you focused when you go to learn more from your customers. When we say “job” here, we do not mean the title or role a person has. A job in this context means the outcome your customer is trying to accomplish. 

A job statement can follow a simple formula: verb + object + context. The point here is to write out what someone is trying to accomplish, not how they'd do it. Aim for 3 candidate jobs to evaluate with customers. Don't overthink it; you can refine them later as you learn. 

 

Example Level
“Run the compliance report”  Task (too narrow) — describes an action, not a goal 
“Schedule automated compliance scans”  Feature (a solution) — describes a tool, not the underlying need 
“Enforce compliance with security & privacy requirements” 

Job (the goal) — describes what they're actually trying to accomplish 

 

Keep in mind when writing job statements: 

  • Getting the right level matters. Too narrow, and you're just describing today's task. Too broad, and it's not actionable. 
  • Focus on the customer's perspective. Describe what customers are trying to accomplish, not what they are doing to accomplish it. And not what product or service they’re using to accomplish their goal. 

 

3. Collect data from your customers about your jobs 

Once you've got a list of jobs, run a short survey asking customers to rate each job on a 5-point scale (1 = lowest, 5 = highest). At minimum, rate importance and satisfaction. 

 

What to measure 

What measuring it can tell you 

Importance 

Which jobs matter most to your customers. 

Satisfaction 

Where expectations aren't being met 

Confidence (recommended) 

Whether people feel capable of doing the job well, even if they're “satisfied” 

Frequency (optional) 

How often the job gets done 

 

Consider adding a metric for confidence if your customers typically report high satisfaction. This can help you spot jobs with hidden struggles that satisfaction may not reveal. You can also consider measuring frequency as supporting data to help understand how often this job shows up for your customers. 

Don’t have enough customers to survey, or already know which job to focus on? Skip to step 5 and start with interviews. 

 

4. Calculate your opportunity score 

When you have your responses from customers, look for jobs with high importance and low satisfaction (or low confidence). The gap between them is your opportunity signal to prioritize which job(s) to focus on. 

What those gaps could mean: 

  • A job has high importance and low satisfaction: Customers are feeling pain when they are trying to accomplish the job. Example: I can't program my security requirements into the system. 
  • A job has high Importance and low confidence: Customers may be able to accomplish the job, but unsure if they were successful or not. Example: I can configure my security policies, but I’m not sure they’re working as intended. 

You can use the formula below to calculate an opportunity score for each job. The “Top-2-Box" here just means you use the percentage of customers who selected the top two positive responses in your 5-point scale. 

 

Score = 10 × (Top-2-Box Importance + MAX(0, Top-2-Box Importance − Top-2-Box Satisfaction)) 

 

Here's an example with some hypothetical numbers: say 92% of customers rate a job's importance at a 4 or 5, and only 43% rate their satisfaction at a 4 or 5. The score for that job would be 10 × (0.92 + (0.92 − 0.43)) = 14.1, which lands in the under-served range. 

 

A high score means a job that matters a lot but isn't being done well or confidently. You can replace “Satisfaction” in the formula with the “Confidence” metric to identify the opportunity score there. When reviewing the scores, use the range below as a guide. Based on your context and resulting job scores, you can adjust the ranges if needed. 

 

Score range 

What it means 

Above 12 

Under-served — high importance, low satisfaction. Innovate here. 

10–12 

Balanced — monitor, but lower priority. 

Under 10 

Over-served — low importance relative to satisfaction. Consider simplifying. 

 

5. Go deeper with follow-up interviews 
Once you've spotted a high-opportunity job (from your scores, or your best guess if you skipped the survey), talk to five customers about how they do it today. It’s okay to start small. You don’t need a full research team or a formal research program to have useful conversations with customers.  Ask about their goals, the outcome they want, and who or what they lean on to get it done. Ask what's painful and what workarounds they've built. If you're not sure what to ask, start here: 

  • "How important is [job] to you, and why?" 
  • "Walk me through the last time you tried to [job]. What happened?" 
  • "What's frustrating or difficult about doing this today?" 
  • "How confident are you that you're doing this well? What makes you say that?" 
  • "If this were solved perfectly, what would be different for you?" 

Listen for phrases like "I wish," "I always have to," or "I'm not sure if" — these point to unmet importance or low confidence, even without a number attached. Use what you learn to shape what you build next. 

 

Common use cases 

Reach for JTBD when: 

  • You've got a long backlog and aren't sure which problems matter most. JTBD gives you a data-driven way to prioritize instead of guessing. 
  • Different teams in your organization are building for similar customers with no shared language for their needs. A job statement list gives everyone a common reference point. 
  • Feature requests keep piling up, but adoption doesn't move. That's often a sign you're solving tasks, not jobs. 
  • Users report satisfaction, but something still feels off. The satisfaction/confidence gap is built to catch exactly this. 
  • You're exploring where AI could genuinely help, not just where it could be bolted on. Jobs with a clear opportunity gap are a strong place to start. 

JTBD is not the right tool if you already have a clear spec and just need usability feedback, or if your question is about visual design and UI polish rather than underlying customer goals. Those needs are better served by other research methods. 

 

Bringing JTBD to life: The milkshake example 

The best-known JTBD example shows how focusing on the underlying job can reveal opportunities that traditional customer feedback may miss. 

 

A fast-food company wanted to sell more milkshakes. It initially asked customers how the product could be improved: 

  • Should it be sweeter?
  • Should it be thicker?
  • Should it cost less?

The company made changes based on this feedback, but sales did not increase. 

 

Researchers then approached the problem differently. Instead of asking customers what they wanted changed, they observed and interviewed people who were buying milkshakes. They discovered that many morning commuters were choosing a milkshake to make a long commute more enjoyable, stay full until later in the day, and have something convenient to consume without making a mess. 

 

From that perspective, the milkshake was not competing only with other drinks. It was competing with bananas, donuts, bagels, and anything else customers might choose to accomplish the same job. 

 

The example illustrates the central idea behind JTBD: customers may ask for changes to a product, but understanding what they are ultimately trying to accomplish can reveal a different and more valuable opportunity. 

 

Resources

If your organization has a UX Research team, talk with them about JTBD and running a full JTBD study for the set of jobs you support. If you don’t have a UX research team or they aren’t available, you can still make use of this framework and the following resources to find some early wins for your customers and your organizations. You may also consider engaging with your vendors and partners to explore how they can support you in applying JTBD to the products and services you use. 

 

You don’t need advanced tools to get started. What matters is engaging with your customers, understanding what they’re trying to accomplish, and using what you learn to guide your decisions. Find these resources attached below.

  • Check out the one-page, hands-on worksheet to help you get started.
  • After you’ve surveyed your customers, you can use this Opportunity Score Calculator to help you quickly calculate your scores. 

If this article helps you put JTBD into practice, our UX Research team would love to hear how it goes, what you learn, and where additional guidance or support could help. Let us know in the comments!

Version history
Last update:
8m ago
Updated by:
Contributors