Jobs to Be Done (JTBD)

Understanding Why Customers Really Buy

Summary

Jobs to Be Done (JTBD) is a framework that explains customer behavior by focusing on the progress people want to make in a given situation. Instead of asking who the customer is, it asks what job they are hiring a product to do. This helps teams design, position, and market products around real motivations.

Back

Jobs to Be Done (JTBD) is a theory of customer behavior built on a simple idea: people do not buy products, they "hire" them to make progress in a specific situation. When a product does the job well, customers keep hiring it. When it falls short, they "fire" it and switch to something else, which might be a competitor, a workaround, or doing nothing. The framework was popularized by Harvard professor Clayton Christensen, notably in his 2016 book Competing Against Luck, and developed further by practitioners such as Tony Ulwick and Bob Moesta.

A well-defined job includes several dimensions:

  • Situation: The circumstances that trigger the need, such as a deadline, a life change, or a new responsibility.
  • Functional job: The practical task to be completed.
  • Emotional job: How the person wants to feel, such as confident, in control, or relieved.
  • Social job: How the person wants to be perceived by others.
  • Forces of progress: The push of the current problem and pull of a new solution, balanced against anxiety about change and habits of the present.

Benefits of Jobs to Be Done

  1. Clearer view of competition: Your real competitors are everything customers might hire for the same job, not only similar products.
  2. Sharper messaging: Copy that describes the progress customers want resonates more than feature lists, and it strengthens your unique value proposition.
  3. Better product priorities: Features can be judged by how well they help complete the job.
  4. Stable foundation: Jobs tend to persist even as technologies change, which makes them a reliable basis for strategy.

Real-World Example of Jobs to Be Done

A frequently cited example comes from Christensen’s work with a fast-food chain trying to sell more milkshakes. Demographic research and product tweaks did little. Researchers then observed that many milkshakes were bought early in the morning by commuters who wanted something filling and slow to consume during a long, boring drive. The job was "make my commute more interesting and keep me full until lunch." Seen this way, the milkshake competed with bananas, bagels, and snack bars, which pointed to very different improvements than changing flavors.

How to Apply Jobs to Be Done

Interview recent customers about the moment they decided to switch to your product. Ask what was happening in their lives, what they tried before, what almost stopped them, and what finally tipped the decision. This kind of UX research uncovers the situation and motivations behind a purchase.

Summarize findings as job statements, for example: "When I am preparing for a board meeting, I want to see this quarter’s results at a glance, so I can answer questions confidently." Use these statements alongside a persona or a value proposition canvas to guide design, messaging, and roadmap decisions. Then make sure each stage of your communication speaks to the job, as described in our guide to communicating your product across the customer journey.

Conclusion

Jobs to Be Done shifts attention from who customers are to what they are trying to achieve. That shift helps teams build products people actually need and explain them in words customers recognize.

Need Help With Jobs to Be Done?

Artifact runs research and strategy work that uncovers your customers’ real jobs and turns them into product, brand, and messaging decisions. Tell us about your project