Why does someone buy a drill? A product team might answer with specs: torque, battery life, price. But the person standing in the hardware store doesn’t want a drill. They want a hole in the wall so they can hang a shelf, so the room feels finished. The drill is just the tool they hire to get there.

That shift in thinking is the heart of Jobs to Be Done (JTBD), a framework that helps teams understand what customers are really trying to accomplish. This guide explains what JTBD is, its core concepts, examples, and best practices for applying it.

What Is Jobs to Be Done?

Jobs to Be Done is a framework for understanding customer motivation. Its central idea is that people “hire” products and services to make progress in a particular situation. The “job” is that progress: the change someone wants in their life or work.

The idea was popularized by Harvard professor Clayton Christensen, and shaped by practitioners such as Tony Ulwick and Bob Moesta. A well-known example from Christensen’s work involves a fast-food chain trying to sell more milkshakes. Demographic analysis went nowhere, but interviews revealed that many morning customers were hiring the milkshake to make a long, boring commute more interesting and to keep them full until lunch. Once the team understood that job, they knew what to improve.

JTBD shifts the focus from who the customer is to what they are trying to get done.

Why JTBD Matters

Traditional segmentation groups people by age, income or job title. The trouble is that people with identical profiles often behave very differently, while very different people may share the same goal. Demographics describe customers; they rarely explain their choices.

JTBD helps teams:

• Understand real motivations rather than guessing from surface traits
• Find unmet needs that competitors overlook
• See the true competition, which includes anything that gets the job done, not just similar products
• Prioritize features based on progress delivered rather than opinion
• Align teams around a shared view of customer value

The Core Concepts of JTBD

The job

A job is the progress a person seeks in a given circumstance. It is solution-agnostic: it describes the goal, not the product. “Get to work on time without stress” is a job. “Use a ride-hailing app” is not.

Functional, emotional and social dimensions

Every job has multiple layers:

• Functional: the practical task, such as transferring money or scheduling a meeting
• Emotional: how the person wants to feel, such as confident, relaxed or in control
• Social: how they want to be perceived, such as competent, responsible or modern

Great products address all three. A banking app that moves money quickly (functional) but makes users anxious (emotional) is only half-successful.

Context and circumstance

Jobs arise in specific situations. The same person may hire different solutions at different times: a quick snack on a commute, a proper meal with family. Understanding context is often more useful than understanding the person.

Desired outcomes

Outcomes are the measurable criteria people use to judge how well a job is done, such as “minimize the time it takes to find a document” or “reduce the likelihood of making an error.” These make jobs concrete enough to design and test against.

Forces of progress

Moesta’s framework describes four forces that influence whether someone switches to a new solution:

• Push: frustration with the current situation
• Pull: attraction toward a new solution
• Anxiety: fears and doubts about changing
• Habit: comfort with the existing way

Teams often focus only on pull (features and benefits) and ignore anxiety and habit, which are frequently what stop people from adopting a product.

How to Write a Job Statement

A common format for job statements is:

When [situation], I want to [motivation], so I can [expected outcome].

Examples:

• When I’m preparing for a client meeting, I want to see all past conversations in one place, so I can walk in confident and informed.
• When I’m traveling for work, I want to submit expenses quickly, so I can avoid chasing receipts later.
• When I run out of ideas for dinner, I want a simple recipe based on what I already have, so I can avoid another takeaway order.

Notice that none of them mention a product or a feature. That is intentional. Solution-free statements leave room for creative thinking.

Examples of JTBD in Action

Milkshakes at breakfast. The job was not “enjoy dessert.” It was “make my commute less boring and keep me full.” That insight pointed to thicker shakes and faster service, not new flavors.

Music streaming. People were not hiring music services merely to “listen to songs.” Many were hiring them to “set the mood for a workout” or “focus while working.” Curated playlists emerged from understanding those jobs.

A project management tool. A team discovers customers are not trying to “manage tasks.” They are trying to “stay calm when a deadline is near and everyone is asking for updates.” That insight shifts the product toward clear status visibility and fewer notifications, rather than more features.

A fintech app. Users who open a budgeting tool may actually be trying to “feel in control of money after an unexpected expense.” The emotional job drives design choices such as reassuring language, simple visuals and small wins.

Best Practices for Applying JTBD

1. Start with customer interviews focused on switching

The most revealing JTBD research asks about real decisions customers recently made: what prompted them to look for something new, what alternatives they considered, what nearly stopped them, and what finally made them switch. Specific stories beat opinions. Our guide to UX research interview questions offers practical advice on asking questions that uncover real behavior.

2. Focus on the situation, not the person

Ask what was happening when the person decided to act. Triggers such as a new job, a missed deadline or a frustrating experience often reveal the real job behind the purchase.

3. Map the job into steps

Break a job into stages, for example: define the goal, gather what is needed, prepare, execute, monitor and conclude. Identify where people struggle at each step. These friction points become your opportunities. Pairing job maps with a customer journey view helps you see how the job unfolds across touchpoints.

4. Identify the real competition

If the job is “relax after a long day,” your competitors include streaming services, games, books and a walk outside. Looking beyond direct rivals can reveal both threats and openings.

5. Quantify and prioritize

Once you have a list of desired outcomes, ask customers how important each is and how satisfied they are with current solutions. Outcomes that are highly important but poorly satisfied are your best opportunities.

6. Use jobs to shape your value proposition

A strong value proposition describes how your product helps people complete a job better than the alternatives. If you are refining positioning, our article on what a product value proposition is and how to create one is a useful companion.

7. Combine JTBD with personas, don’t replace them

Personas capture who users are; JTBD captures what they are trying to do. Used together, they give a richer picture. Teams that already work with user personas can enrich them by adding the key jobs each persona is trying to accomplish.

8. Embed jobs in everyday product work

Write user stories and feature briefs in job language. Review roadmap items by asking which job they serve and how they improve the outcome. Share job statements across design, engineering, marketing and support so everyone works from the same understanding.

9. Validate with prototypes and testing

Jobs are hypotheses until tested. Build prototypes that address a specific job and see whether users complete it faster, with less effort or more confidence. Our user research and persona development service shows how research and validation fit together.

Common JTBD Mistakes to Avoid

• Describing solutions instead of jobs, such as “use a dashboard”
• Making jobs too broad (“be happy”) or too narrow (“click the export button”)
• Ignoring emotional and social jobs
• Relying on surveys alone, which capture opinions rather than behavior
• Interviewing only existing customers, missing non-users and people who switched away
• Collecting jobs without acting on them
• Treating JTBD as a replacement for all other methods rather than a lens that complements them

When to Use JTBD

JTBD is useful at many stages: exploring new product ideas, improving an existing product, repositioning in the market, writing messaging, or deciding what to build next. It is especially powerful when feature requests are piling up and the team needs a way to separate what customers say from what they truly need.

Bringing It All Together

Jobs to Be Done reframes product thinking around a simple question: what progress is the customer trying to make? By understanding the situation, the functional and emotional dimensions of the job, and the forces that help or hinder change, teams can design products that fit real lives rather than assumed preferences.

Start with a handful of customer interviews, write a few job statements, and test them against your current roadmap. You may find that the most valuable improvement is not a new feature at all, but a better way of helping people get their job done.

If you want to build products grounded in real customer needs, our UI/UX design services can help you turn research into experiences that make a difference.