The 'Jobs to be Done' framework is a powerful tool for innovation that shifts focus from demographics to customer motivation. This lesson teaches you to stop focusing on what your product is and start understanding the 'job' a customer is 'hiring' it to do. Learn how to uncover deep customer needs, improve product development, and create marketing that truly resonates by asking not 'who is the customer?' but 'what progress are they trying to make?'.
Let’s begin with a mystery. A fast-food chain wants to sell more milkshakes. They do what any sensible company would do: they study their customer. They assemble focus groups, they analyze demographic data, they identify their target milkshake buyer. They ask these customers, “How can we make this milkshake better for you?” The feedback is clear and consistent. Make it chocolatier. Make it cheaper. Make it thicker, or maybe thinner. The company’s food scientists get to work, reformulating the product based on this direct feedback. They launch the new, “improved” milkshakes. And… nothing happens. Sales are flat. The project is a failure. Why? The company did everything right, according to the old rules. They listened to their customers. They improved their product. Yet the result was indifference. This is the exact puzzle that the late Harvard Business School professor Clayton Christensen and his colleagues were asked to solve. What they uncovered would change the way we think about products, innovation, and the fundamental motivations of the people we call customers. The answer wasn't in the milkshake's ingredients; it was in the job the milkshake was being hired to do.
Christensen’s team took a different approach. Instead of asking customers what they wanted in a milkshake, they asked a deeper, stranger question: What job did you hire that milkshake to do? They didn't conduct focus groups. They stood in a restaurant for 18 hours and simply observed. A pattern quickly emerged. A surprising number of milkshakes were sold before 8:30 in the morning. The buyers were almost always alone. They never drank the milkshake in the store. They got in their car and drove away with it. The researchers went out and talked to these morning commuters. They asked them about their journey. “Tell me about your commute,” they’d say. “What’s that like for you?” The story was always the same: it’s long, it’s tedious, it’s boring. They weren't particularly hungry yet, but they knew they would be by 10 a.m. They needed something to make the drive more interesting and to stave off mid-morning hunger. This was the job: “Help me stay engaged during my boring commute and keep me full until lunch.” When you look at the world through this lens, the milkshake’s true competitors come into focus. It wasn’t another restaurant’s milkshake. It was a banana—but that was gone in a minute and didn’t solve the boredom. It was a donut—but that was messy, leaving crumbs and sticky glaze on the steering wheel. It was a bagel—but trying to spread cream cheese while navigating traffic is a recipe for disaster. Suddenly, the humble milkshake looks like a genius solution. It’s thick, so it takes a long time to drink through a thin straw, giving the driver something to do for 20 minutes. It’s tidy. It fits in a cup holder. It’s substantial enough to quiet a rumbling stomach. It did the job better than any of its competitors. The fast-food chain wasn't in the milkshake business. It was in the business of making commutes more bearable. Understanding this changed everything. To improve the product, you don’t make it chocolatier. You make it *thicker* so it lasts longer. You add tiny bits of fruit to create moments of discovery and interrupt the monotony. You move the dispenser in front of the counter and create a self-service kiosk with a prepaid card, so commuters can get in and out fast. You solve for the *job*, not the product.
This is the core of the Jobs to be Done framework, often abbreviated as JTBD. It proposes a fundamental shift in perspective. Customers don't buy products; they "hire" them to make progress in their lives. This idea, developed and popularized by thinkers like Christensen, Tony Ulwick, and Bob Moesta, argues that the unit of analysis for innovation shouldn't be the customer or the product, but the "job." We are all constantly trying to make progress. We want to feel more connected, more competent, more secure, to get from point A to point B. This struggle for progress is what creates the demand for new solutions. A "job" is simply the progress a person is trying to achieve in a particular circumstance. Think about the last time you bought a piece of software. Did you hire it to "own a spreadsheet program," or did you hire it to "organize complex information and feel in control of my project"? The first is about a feature; the second is about a job. The first leads to incremental improvements. The second leads to breakthroughs. This framework explains why simply looking at demographics—a 35-year-old suburban male—is so often misleading. That same man might hire a fancy restaurant for a "celebrate a special anniversary" job one night, and a frozen pizza for a "get a hot meal on the table for the family with zero effort" job the next. The circumstances and the job, not the person, dictate the best solution.
So how do you find the job? You can't just ask people. As the milkshake story shows, customers are often poor at articulating their deeper needs and tend to suggest superficial improvements to existing solutions. Instead, you have to become a detective. You have to investigate the story behind the purchase. The most powerful tool for this is the Jobs to be Done interview. The goal isn't to get feedback on your product; it's to reconstruct the chain of events that led to someone "hiring" it. You want to talk to people who have recently made a purchase or switched from one solution to another. Their memory of the struggle is fresh. You start by building a timeline. Ask them: “Take me back to the day you decided you needed something to solve this problem. Where were you? What was happening?” You're looking for the initial spark, the first thought that "maybe there's a better way." Listen for two key forces at play: the "push of the situation" and the "pull of the new solution." * **The Push:** What was so frustrating about their old way of doing things that it pushed them to seek something new? This is where the energy for change comes from. * **The Pull:** What was it about your solution that pulled them toward it? What progress did they envision it helping them make? At the same time, you listen for the counter-forces: the "habits of the present" that create inertia, and the "anxieties about the new solution" that cause hesitation. Was it too expensive? Would it be hard to learn? You're essentially making a documentary about a decision. Your questions should be specific and chronological: * "What solutions did you try before this one?" * "What was the moment you realized the old way wasn't working anymore?" * "When you were looking for an answer, what else did you consider?" * "Describe the conversation you had with your partner or team about making this purchase." By piecing together this story, you move past the sterile, feature-level analysis and into the rich, emotional, and contextual world where real decisions happen. You stop seeing your product as an object and start seeing it as a service that helps someone make progress.
The Jobs to be Done lens can be applied anywhere. It is not limited to consumer products. Consider the rise of Airbnb. For decades, the hotel industry focused on optimizing its product: cleaner rooms, faster check-in, better amenities. They were trying to build a better hotel. Airbnb understood that for many travelers, the job wasn’t just “find a place to sleep.” It was “experience a destination like a local.” Suddenly, staying in a stranger’s apartment in a real neighborhood wasn’t a bug; it was the central feature. Hotels weren't competing with Airbnb on the quality of their beds; they were competing with a fundamentally different way of fulfilling a job. Or think of software for remote teams. Before 2020, many companies saw videoconferencing as a niche tool. But when the world went remote, the job became urgent: "Help me manage, connect with, and engage my team when we can't be in the same room." Zoom won, not because it had the most features, but because it was the easiest and most reliable solution to hire for that specific job in that specific circumstance. In each case, the innovation came not from improving an existing product, but from deeply understanding the progress a person was trying to make. The product is the means, not the end. The job is the star of the show. Stop looking at who your customers are. Stop obsessing over what your competitors are doing. Instead, ask a better question: In a moment of struggle, what progress is someone trying to make, and how can we build something that they will be delighted to hire for that job? The answer won’t be in your spreadsheets. It will be in their story.