JTBD

Also called Jobs to Be Done, Jobs Theory, JTBD theory. Also in Business, Design, Marketing

Quick answer

JTBD, short for Jobs to Be Done, explains why people choose a product: they use it to make progress in a specific situation. A product manager or designer applies it by interviewing recent buyers about the circumstances of their choice. The aim is to find the real reason people buy, which age or income cannot show.

~20 sec read

012 min

What goes wrong without JTBD

A fast-food chain wanted to sell more milkshakes, and its marketing team started the way most teams start. In a story Clayton Christensen tells in his MBA course, the team described the typical milkshake buyer by traits such as age. It then asked people who fit that description to list what an ideal milkshake would be: thick or thin, fruity or chocolate, smooth or chunky.

The chain changed the milkshake to match the answers, and sales did not improve.

That result is the cost of the usual approach. The team put its effort into a product change that did not move sales, and it learned nothing about why people bought the old product. Splitting a market by product type or by buyer profile is called market segmentation. It tells a team who the buyers are and what they say they want. It does not show the situation each buyer was in when they paid. Without that, a team improves features that nobody needed improved.

Why a buyer profile does not explain a purchase

Christensen argues that neither product categories nor buyer profiles work well for dividing a market. His reasoning is about cause. A profile such as a buyer aged 18 to 35 with a degree can match many buyers without causing any of their purchases. What causes a purchase, he says, is that a person has a job to get done at that moment. A rule for deciding what to build needs the cause, not just the match.

022 min

How JTBD finds the job

The chain therefore asked a researcher who worked with Christensen to look at the question differently. The researcher did not ask what people wanted in a milkshake. He watched. He spent a full day in one restaurant and noted who bought milkshakes, when they bought them, and whether they drank them there. He found that 40 percent of the milkshakes were bought early in the day by commuters who took them to go.

The next morning he came back and interviewed buyers as they left with a milkshake in hand. He asked what job they had hired the milkshake to do. To hire a product, in JTBD, simply means to choose it in order to get something done.

Most of the commuters gave a similar answer. Their commute was long and dull, and they wanted something to keep one hand busy. They were not hungry yet, but they knew they would be by ten o'clock, and they wanted to stay full until noon. They were in a hurry, they wore work clothes, and they had at most one free hand. A bagel or a doughnut was messy. A thick milkshake was tidy, filled them up, and took a long time to drink through a thin straw, which gave them something to do.

So the job was not simply to have a milkshake. It was to make a dull commute easier and stay full until lunch. For that job the milkshake's rivals were a bagel and a doughnut, not other milkshakes. The job, not the product category, sets who the competitors are.

With the job known, the chain could change the product on purpose. The morning milkshake became thicker, so it would last through a long commute, and it got pieces of fruit to make the drink more interesting.

One product, two jobs

The same work found a second job. Some customers bought a milkshake as a treat for a young child. Those parents did not want to wait half an hour while the child worked the milkshake through a straw. That job needed a thinner milkshake. One product, then, had two jobs that called for opposite design changes, and no single ideal milkshake could serve both.

What counts as a job

In the definition Christensen and his coauthors use, a job is the progress a person seeks in a particular circumstance, and it has emotional and social sides as well as practical ones.

The practical side is what must happen. The emotional side is how the person wants to feel. The social side is how the person wants other people to see them. The commuters' job had a practical part (stay full until noon) and an emotional part (make a dull drive less dull).

morning40 percentof milkshakes
Look at the commuter holding a milkshake and at how large the morning group is among all milkshake buyers.

031 min

Where JTBD came from

The researcher's way of looking at the milkshake comes from two people who worked on separate methods. Tony Ulwick built a method he called Outcome-Driven Innovation, which studies the process a person is trying to carry out instead of the product. By his company's own history, Ulwick named the method in 1999 and also introduced it to Christensen at Harvard.

Christensen then gave the idea its wide audience. His 2003 book The Innovator's Solution used the term Jobs-to-be-Done, and Strategyn's account says it cited Ulwick's work. In 2005 Christensen, Scott Cook and Taddy Hall argued in Harvard Business Review that the usual ways to segment markets and build brands are broken. A Harvard Business School article told the milkshake story in 2011. In 2016 Christensen, Hall, Karen Dillon and David Duncan set out the theory in the book Competing Against Luck and in a Harvard Business Review article.

042 min

Two meanings of the word job in JTBD

Those two lines of work use the word job in different ways, and that matters to anyone who reads about JTBD.

Ulwick's company treats a job as a task, goal or objective that a customer wants to accomplish in a certain situation. Its team breaks the job into steps on a job map and records the measures customers use to judge success at each step. It then writes them as measurable outcome statements.

The progress school, which Bob Moesta and Chris Spiek teach, starts from the story of a person who switched. Their switch interview rebuilds a real purchase from the first thought to the buying, and it looks for the forces that moved the person.

Outcome-Driven Innovation (Ulwick)Progress and switching (Christensen, Moesta, Spiek)
A job isA task, goal or objective in a situationThe progress a person seeks in a circumstance
It is found byA job map and customer interviewsSwitch interviews that rebuild a timeline
It producesMeasurable outcome statementsA timeline and the forces behind a switch

Neither meaning is wrong. They answer different questions. Ulwick's gives a team numbers it can rank. The progress school gives a story that explains a switch. When you read a JTBD article, check which meaning it uses before you borrow its results.

052 min

The four forces behind a JTBD switch

A job explains why a person wants progress, but not why they often do nothing about it.

Moesta and Spiek add four forces. Two push a person toward a change. The push is the problem with the current situation, and the pull is the attraction of the new option. Two hold a person back. Anxiety is fear about a new, unproven choice, and habit is the comfort of what the person already does. Moesta and Spiek say people change when the push of their situation and the pull of a new option are stronger than their anxiety and their habit.

Habit is close to what behavioural science calls status quo bias. It is the force a new product most often underestimates, because the old way still works well enough.

The Roomba and the Dyson

In an interview from one of their Switch workshops in Chicago, a man described buying a Roomba, a robot vacuum cleaner. His wife did not like vacuuming and he did it, so the household chores were already divided. She was keen on the Roomba, and he was the one who liked gadgets. He worried that it would not clean well, and he spent about 12 months researching before he bought it.

Six months after he bought the Roomba, he pulled out his old Dyson on a Saturday morning, while his wife was out of town. The interview suggested why. He liked vacuuming with the Dyson and did not want to say so to his wife. Moesta also pointed out that she had wanted the Roomba mainly because the children liked it so much that they picked up the whole room for it. The Roomba and the Dyson did two different jobs.

This shows the force of habit. The Roomba had enough pull to be bought, but it did not replace the old way, because the old way did a job the Roomba did not do.

RoombaDyson
Look at which machine the person reaches toward. The Roomba stays in its frame.

061 min

Writing a JTBD job story

Interviews produce stories, and a team needs a short form to pass them on to the people who build the product.

The most common short form is the job story. Alan Klement and the software company Intercom proposed it as a replacement for the user story, which describes a feature from the point of view of a type of user. Researchers at Utrecht University describe job stories as having three parts: the situation that triggers a problem, the motivation, and the outcome the person expects.

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

For the morning milkshake, the job story would be: when I face a long, dull commute with one free hand, I want something tidy that keeps me full until noon, so I can reach lunch without being hungry. Nothing in it names a milkshake. A bagel or a smoothie could fit the same story, which is the point. The story describes the job and leaves the solution open.

072 min

A second case: one university, two jobs

The idea also works outside a restaurant, as Southern New Hampshire University (SNHU) shows. Christensen and his coauthors tell the story in an essay adapted from their book.

SNHU was a traditional campus for school leavers. It also ran an online program that drew a steady stream of adults who wanted to resume an education they had stopped. Online adult students and school leavers, SNHU's leaders found, wanted such different things from the school that their jobs shared almost nothing. The school leavers were hiring SNHU for a coming-of-age experience.

What the job changed inside the school

The finding changed more than the website. The authors write that very little in SNHU's policies, structures and procedures had been built for online learners. A person who asked for information got a form reply within 24 hours, and a week later the same printed packet that everyone else received. Waiting weeks to learn their own financial aid options was, to a working adult, the same as getting no reply.

SNHU rebuilt the experience around the online learner. For example, it gave each new online student a personal adviser who stays in constant contact and notices warning signs early. The authors report that by the end of fiscal 2016 SNHU was close to $535 million in revenue, a 34 percent compound annual growth rate over five years.

The two cases differ in one variable. The restaurant chain kept one product and changed it for each job. SNHU kept one school and had to change how it works, because the job affected every step from the first inquiry to the degree.

081 min

What teams do with a JTBD job

Once a team has a job, it can use it for decisions it already makes.

  • Roadmap. For each backlog item, a team asks which job story it serves. An item that serves none is a candidate to drop.
  • Competitors. A team lists everything the person might use instead, including things that are not products, as the bagel and the doughnut were for the milkshake.
  • Messaging. Marketing copy describes the situation and the progress, in the words the interviewees used.
  • Discovery. The job story is a starting point for product discovery and for the user-need statement in design thinking.

Naming a product after its job

Christensen calls this purpose branding. In the 2011 Harvard Business School article, he points to Kodak's FunSaver single-use camera, named for preserving fun memories, and to the Sawzall saw from Milwaukee Electric Tool, named for sawing through almost anything. When the name states the job, the buyer needs no explanation of why the product exists.

091 min

How to run JTBD this week

You can end the week with a page of job stories and the forces behind each one. You need a document or a spreadsheet, and access to people who recently made a choice.

  1. Pick one choice that people made recently, such as buying your product, cancelling it, or switching to a rival.
  2. Find people who made that choice in the last few weeks. Recent memory holds details, while older memory holds a tidy story.
  3. Run a user interview with each person. Ask them to tell the story from the first moment they thought about the problem, and ask what was happening that day. Do not pitch your product.
  4. After each interview, write the four forces in the person's own words: what pushed, what pulled, what made them anxious, and what habit kept them still.
  5. Write down what else they considered, including things that are not products.
  6. After several interviews, look for situations that repeat. Write one job story per repeating situation.
  7. Test each story. If only one feature could satisfy it, you wrote a feature request. Rewrite the motivation so that two very different products could fit.
  8. Bring the stories to your next planning meeting and tag every backlog item with the story it serves.

102 min

JTBD done badly, and where it is contested

JTBD fails in a few predictable ways, and one of them comes from the way people use the term.

A feature request in job-story form

A common failure is a job story that names the solution. When I open the app, I want a dark mode button, so I can use it at night is a feature request with three clauses added. The tell is that only one design could satisfy it. A real job story would say: when I check my phone in a dark room, I want the screen to avoid lighting up the room, so I can look without waking my partner.

Treating the template as the method

Researchers who studied job stories warn that teams who invent their own version of the template may miss the value the theory promises. A team can fill in the three-part template for every old requirement and learn nothing new, because the learning comes from the interviews and not from the sentence.

Where the evidence stops

The milkshake account is a teaching case. The published write-up names no chain and gives no sales figures after the change. It shows how to look for a job. It does not show how much the change earned.

The second problem is the meaning of the word. Ulwick's company and the Christensen school define a job differently, so a result from one is not proof for the other.

Last, not every purchase has a detailed job behind it. When people choose on price alone, interviews will mostly return the answer it was the cheapest, and the method adds little. Treat that as a limit of the method, not as a failure of the interview.

111 min

JTBD vs user stories, personas and journey maps

JTBD is often mixed up with three tools that describe users, not progress.

ConceptWhat it describesQuestion it answers
This pageJTBDWhy do people choose or leave this?What it describes: The progress a person wants in a situation
ProductUser storiesWhat should the team build next?What it describes: A feature, written from a type of user
DesignPersonasWho are our users?What it describes: A composite profile of a type of user
ResearchJourney mappingWhat happens at each step?What it describes: The steps a person takes with a product

The deciding fact is where each one starts. A persona and a user story start from a type of user. A job story starts from a situation. Two people with different profiles in the same situation want the same progress, and one person in two situations wants different progress.

In practice the tools work in order. Use JTBD to decide which problem matters, write a job story for it, and then write user stories as possible solutions.

?4 questions

Questions people ask

What does JTBD stand for?

JTBD stands for Jobs to Be Done. It is also written Jobs-to-be-Done, and some teams call it jobs theory or JTBD theory.

Who should run JTBD research?

A product manager, designer or researcher who can talk directly to customers. The method needs no special tool, only people who recently made a choice and an interviewer who listens for the situation.

How many interviews are enough?

There is no fixed number. Keep interviewing until new interviews stop adding situations or forces you have not already heard, then write the job stories from what repeats.

Can I use JTBD on a product that already exists?

Yes. Interview people who recently started or stopped using it, then ask which job story each backlog item serves. Items that serve none are candidates to remove.

§8 sources

Sources

Show all 8 sources
  1. Nobel, C. (2011). Clay Christensen's Milkshake Marketing. Harvard Business School Working Knowledge (archived copy).

  2. Strategyn. Jobs to Be Done (JTBD): The Original Framework by Tony Ulwick.

  3. Christensen, C. M., Hall, T., Dillon, K., & Duncan, D. S. (2016). The customer may be king, but he is also the boss (adapted from Competing Against Luck). The Boston Globe.

  4. Christensen, C. M., Hall, T., Dillon, K., & Duncan, D. S. (2016). Know Your Customers' Jobs to Be Done. Harvard Business Review.

  5. Christensen, C. M., Cook, S., & Hall, T. (2005). Marketing Malpractice: The Cause and the Cure. Harvard Business Review.

  6. Moesta, B., & Spiek, C. Jobs to be Done, Taught by Bob Moesta & Chris Spiek (the Forces of Progress).

  7. Moesta, B., & Spiek, C. The Habit of the Present: Forces Friday on Jobs-to-be-Done (JTBD Radio).

  8. Lucassen, G., van de Keuken, M., Dalpiaz, F., Brinkkemper, S., Sloof, G. W., & Schlingmann, J. (2018). Jobs-to-be-Done Oriented Requirements Engineering: A Method for Defining Job Stories. REFSQ 2018, Springer (author copy).

Keep reading

More from Product

All of Product
All of Product

Missing a concept?

Tell us what to write next. We’ll email you when it’s live.

Several? Separate them with commas.

Only to tell you when it’s live.

How we use your email: privacy.