Jobs-To-Be-Done (JTBD)

---

Origins

The Jobs-To-Be-Done framework is most often associated with Clayton Christensen, whose work on disruptive innovation led him to formalize the idea that customers do not buy products; they hire products to do jobs.¹ The intellectual lineage runs deeper: Tony Ulwick had been developing what he called Outcome-Driven Innovation since the 1990s, and the marketing strategist Theodore Levitt had famously written in 1960 that "people don't want to buy a quarter-inch drill, they want a quarter-inch hole."²

Christensen popularized the framework with the milkshake study at McDonald's — discovering that morning milkshake buyers were not hungry; they were lonely commuters hiring the milkshake for entertainment on a boring drive. The implications for product strategy were significant: features designed for "hungry breakfast customer" missed the actual job. The milkshake competed with bagels and bananas, but it also competed with podcasts.

The Core Idea

JTBD asks the team to look past what users do with the product to why they reached for it in the first place. Every product exists to do one or more jobs — units of progress the user is trying to make in their life or work. The job is stable; the products people hire to do it change.

This produces a different way of thinking about competition, prioritization, and feature design:

• Competition is defined by the job, not the product category. Your milkshake competes with podcasts.
• Features matter to the degree they advance the job, not to the degree they are technically impressive.
• Customers can describe the job badly — they tell you what features they want, not the underlying progress they are trying to make.
• The job has emotional and social dimensions, not just functional ones. Users hire products to feel a certain way and to be seen a certain way, as well as to accomplish a task.

The Three Dimensions of a Job

A well-articulated job has three layers:

• Functional: the practical task the user is trying to accomplish. Get a quick breakfast on the commute.
• Emotional: how the user wants to feel during or after. Less bored. More energized for the day.
• Social: how the user wants to be perceived. Like someone who has their morning together. Not the person eating cereal on the train.

Most products that win do so because they handle all three dimensions, not just the functional one. A team that optimizes only the functional dimension is doing half the work.

Writing a Job Statement

The canonical Ulwick form for a job statement:

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

For example: "Get the kids ready for school in the morning without forgetting anything important." The verb is concrete (get ready), the object is specific (the kids, for school), and the clarifier captures the constraints (without forgetting, in the morning).

A weaker job statement: "Be a good parent." Too abstract to guide product decisions. A stronger one: "Help my child remember which gear they need for which day." Specific enough that the team can imagine the product.

Discovering Jobs Through Interviews

The JTBD interview technique — refined by Bob Moesta and the Re-Wired Group — focuses on the moment of switching: when the user first hired the product, what triggered the search, what they had been using before, what made them finally switch.³ The interview reconstructs the timeline of that switch in detail.

The technique is powerful because it reveals the push (what was wrong with the old situation) and the pull (what was attractive about the new option), as well as the anxieties and habits that almost prevented the switch. These four forces — push, pull, anxiety, habit — are the engine of why people change.

How JTBD Shapes the Backlog

When a team takes JTBD seriously, the backlog changes:

• The product strategy is framed in terms of jobs the product does, not features it offers.
• Prioritization debates start with "which job does this advance?", not "who asked for it?"
• Stories carry a job reference, making it explicit which progress the work is meant to enable.
• "Feature requests" are interrogated for the underlying job — the request is the symptom; the job is the cause.
• The team becomes more comfortable saying no, because the test becomes does this advance any job we are hired for?

JTBD and Job Stories

JTBD is the strategic framework; Job Stories are one tactical expression of it at the story level. JTBD identifies the jobs; Job Stories capture the situational moments in which those jobs need to be done. A team can use JTBD without ever writing a Job Story (and vice versa), but the two work well together: JTBD gives the strategic direction, Job Stories give the local context.

Coaching Tips

Run a switch interview.

Pick one user who recently started using your product. Ask: what triggered the search? What were you using before? What almost stopped you? The story is the data.

Catch "feature request" framing.

When someone asks for a feature, ask "what would this let you do that you can't today?" The answer is closer to the job.

Write a one-page job summary.

One page, the top three jobs your product is hired to do. Pin it where the team can see it. Use it to filter incoming requests.

Look at the non-obvious competition.

What does the user reach for instead of your product? The answer is often the actual competition — and not what you'd guess.

Don't forget emotional and social.

The functional job is easy to describe and easy to overweight. The emotional and social dimensions usually decide who wins.

Connect each story to a job.

Even a one-word tag on the ticket is enough. Over time, you'll see which jobs the backlog is actually serving — and which it claims to.

Summary

Jobs-To-Be-Done is less a technique than a perspective. It asks the team to stop thinking about features and users and start thinking about progress and moments. The shift is subtle, but the consequences are not: products designed around jobs tend to compete on different axes, succeed for different reasons, and survive longer than products designed around feature parity. For a team building anything meant to be used voluntarily, JTBD is one of the most reliable frames available.

Back to Story Crafting