What Is Jobs-to-be-Done? (And Why the History Is Older Than You Think)

What Jobs-to-be-Done actually means

Open any product-management textbook from the last decade and you will run into Jobs-to-be-Done in the first few chapters. Most people know it through one story.

In the early 2000s, Clayton Christensen, a professor at Harvard Business School, was hired by a fast-food chain with a milkshake problem. Sales were flat. The company had tried everything: thicker milkshakes, sweeter milkshakes, milkshakes with fruit. Nothing moved. Christensen's team did something different. They stood in the car park at seven in the morning and watched who actually bought the milkshakes.

It turned out half the sales happened before 8am, almost always to a solo driver on the way to work. Those customers were bored in traffic, needed something to do with their free hand, needed something to chew on for the next twenty minutes, and wanted it not to leave crumbs in the lap. A traditional marketer looks at that and sees a demographic: working adults, 25–45. Christensen saw a job. The milkshake was being hired to get a bored commuter through rush hour, and it was competing with bananas, bagels, and cans of Red Bull — not with other milkshakes.

That is the whole framework. Customers don't really buy products. They hire products to get a job done in their life. Your competition is not other products in your category. Your competition is whatever else the customer might hire for the same job.

It sounds obvious once you read it. That is a sign of a good framework, not a sign of a trivial one. Physics also sounds obvious once someone explains it.

Why it matters in practice

Most product research is built around personas: "Sarah, 32, working mother, household income £85k, shops at Marks & Spencer." A persona is a description of a type of person. The problem is that Sarah will hire a Snickers bar, a latte, or a milkshake at different moments of the same day, for different jobs, and no amount of demographic data tells you which she will pick on any given morning.

Jobs-to-be-Done replaces the question "who is the customer?" with "what is the customer trying to get done?". Sarah-in-traffic-at-7am is a different customer to Sarah-at-her-daughter's-party-at-4pm, even though she is the same woman. The milkshake is fighting different competition in each situation, and the winning rival is different each time.

This is the practical unlock. You stop fighting for share of consumer. You start fighting for share of situation.

Once you see the world this way, strategy gets simpler. Nintendo famously survived Sony's PlayStation by refusing to compete for the hardcore gamer and building for a different job altogether, "entertain this family at this gathering", which Sony's PS3 could not serve. Airbnb did not beat Marriott on amenities; it won the different job of "feel at home in a city I don't live in". Every good strategy you admire, when you look closely, is usually a good answer to the question what job are we actually being hired to do?

A warning. Jobs-to-be-Done is a useful lens. It is not a research method on its own. You still have to do the watching-people-in-car-parks part. Most of the "3-minute JTBD explainers" floating around the internet skip that part, which is why they do not work.

Now, the interesting bit.

The framework is sixty years older than you think

Christensen, milkshakes, Harvard Business School. That is how Jobs-to-be-Done reached the product-management world. It is not how the idea reached the world.

In 1954, fifty-three years before Christensen ever walked into a McDonald's, Peter Drucker published The Practice of Management. Chapter 7 opens with four lines that have never been beaten for clarity: "There is only one valid definition of business purpose: to create a customer." "It is the customer who determines what a business is." "What the customer thinks he is buying, what he considers 'value', is decisive." "Any business enterprise has two — and only these two — basic functions: marketing and innovation." Drucker's whole argument, compressed, is that companies exist to solve customer jobs. Value lives outside the firm. Everything else is noise.

Six years later, in the July–August 1960 issue of Harvard Business Review, Theodore Levitt published Marketing Myopia. The argument was simple and rude: American railroads were dying because their executives thought they were in the railway business. The customers, freight shippers and passengers, were hiring a job called "move my cargo, or me, across the country". When trucks and aeroplanes became a better hire for that job, the railways lost. Same idea, angrier delivery. Levitt's article still holds the record for the best-selling piece HBR has ever published: 35,000 reprints in the first year, more than 850,000 over the next four decades.

Behind Drucker and Levitt, there is a longer shelf. In 1942, Joseph Schumpeter wrote about creative destruction, the idea that better solutions to jobs displace worse ones. That is JTBD with the politics left in. In 1890, Alfred Marshall introduced "derived demand" in his Principles of Economics: the demand for bricks is not really for bricks, it is for houses. Nobody hires a brick-maker for the sake of bricks. That is, in outline, the milkshake argument — published 121 years before Christensen.

What Christensen and his collaborators did add, when they arrived in the 2000s, was genuinely useful. They gave the framework a verb that the business world could actually repeat: hire. They produced a repeatable interview method; the "mattress interview" transcript in Competing Against Luck is still the cleanest demonstration I have seen of how to walk a customer backwards from purchase to first dissatisfaction. And they packaged the whole thing into a single memorable story. The milkshake detail made the idea stick.

None of that is nothing. But it is a better user-manual for an old idea, not a new idea.

Why the history is interesting

The point is not that Christensen owes Drucker a royalty. Business books borrow from each other constantly, and that is fine. The point is this: the frameworks you meet in your career are almost never inventions. They are re-expressions of older ideas, dressed up for the current generation.

Three practical implications.

First, reading the originals saves you money and time. The foundational books in this one lineage were published in 1890, 1942, 1954, and 1960. You can work through all four in a month of commutes. They will make you sharper than any paid JTBD masterclass, at a fraction of the cost.

Second, the history helps you spot fakes. Walk up to anyone who claims JTBD fluency and ask them three questions, no Googling allowed. What year was "Marketing Myopia" published? What are Drucker's two basic functions of a business? What did Alfred Marshall mean by derived demand? If they cannot answer any of the three, the framework in their hands is decoration, not method.

Third, and this is where it matters most, in an interview room or a strategy meeting, depth of reading is visible. When a consultant asks you to "think about the customer", most candidates reach for whichever book is fashionable that year. The candidate who answers in Drucker's language signals something different. They know where the framework came from, which means they know where it breaks. In my experience as an interview panelist, that hire-decision is almost automatic.

Here is one small parable that ties all of it together.

The most-cited line in marketing writing is "People don't want a quarter-inch drill, they want a quarter-inch hole." It is usually credited to Theodore Levitt. It was not Levitt's. It was written by a man called Leo McGivena, a publicity manager at the New York Daily News, and published in 1947 inside a sales manual by Percy Whiting. Levitt, to his credit, credited McGivena in 1969. Christensen, writing in HBR in 2005, credited Levitt and dropped McGivena. Thirty-six years of polite attribution drift, and an idea written by a 1947 advertising hack ended up credited to a Harvard Business School giant.

Jobs-to-be-Done is that quote at framework scale. The insight is real. The origins have been rubbed off by thousands of careless retellings. Knowing where it actually came from is what separates the person using the framework from the person performing it.

One last thing

Understanding where a framework comes from is the difference between using it in an interview and performing it. Rehearsal's briefs work that muscle: fifteen minutes on one concept, taken seriously. That is all.