Launch & Validation

Jobs to Be Done: The Framework That Reveals What Your Customers Are Really Buying

A fast food chain wanted to sell more milkshakes. They did what companies always do. They segmented the market by demographics, ran focus groups, tweaked the recipe. Thicker. Thinner. Sweeter. More chocolate chips. Sales didn't move. So they hired Clayton Christensen's team at Harvard Business School, and a researcher stood inside the restaurant for eighteen hours and watched. Who bought milkshakes? When? Were they alone? Did they buy anything else? The pattern was immediate: nearly half the milkshakes sold before 8:30 in the morning to solo commuters who walked in, bought nothing else, and drove away. The milkshake's real competitors weren't other milkshakes. They were bagels, bananas, and boredom. The "job" was filling a long, empty commute, not satisfying a dessert craving.

When the team went back and interviewed those morning buyers, the story sharpened. These were people facing thirty or forty minutes of nothing. They'd tried the alternatives. A banana was gone in sixty seconds. A donut left crumbs on their shirt and a sugar crash by ten. A bagel required cream cheese, which required steering with their knees. A Snickers bar triggered guilt before they reached the highway on-ramp.

The milkshake was thick enough to last twenty minutes through a thin straw. It was filling enough to suppress hunger until lunch. It was neat enough to manage with one hand. When the company made the morning milkshake thicker, added chunks of fruit for texture and interest, and moved the dispensers to the front of the counter so commuters could grab one without waiting in a food line, sales climbed. Not because the milkshake improved as a milkshake. Because it improved as a commute companion.

The afternoon milkshake, it turned out, had a completely different job. Parents bought them for kids after school. In that context, the milkshake competed against a trip to the toy store, against saying "no" one more time at the end of a long day. Same product, two entirely different jobs, different competitors, and different criteria for success. A thicker milkshake would serve the morning job better and the afternoon job worse. No amount of demographic profiling would have revealed this, because the job doesn't live inside the customer. It lives in the situation.

What Is the "Job" Your Customer Is Actually Hiring Your Product to Do?

The framework Christensen built from studies like the milkshake has a name: Jobs to Be Done. Its central claim is both obvious and radical. People don't buy products. They hire them to make progress in a specific circumstance. The "job" isn't a task on a checklist. It's the full context of what someone is struggling with, what they hope to feel when it's resolved, and what they need the world to see about them when they're done.

Every job has three layers. The functional job is the practical task: get me to work, store my files, clean my house. It's the layer that shows up in product requirement documents and feature comparison charts. It's also the layer most visible and least differentiating, because functional jobs are the easiest to copy. If your only advantage is functional, someone with more resources or better engineers will match you within eighteen months.

The emotional job is how the customer wants to feel during and after using the product. The morning commuter wasn't hungry at 6:45 AM. They wouldn't be functionally hungry for hours. The emotional job was: make this drive feel less empty. Give me something to anticipate between my driveway and my parking garage. When Bob Moesta, one of Christensen's closest collaborators, studied retirement condo buyers in Detroit, he discovered that the number one barrier to purchase wasn't price, location, or floor plan. It was the dining room table. Buyer after buyer agonized over whether their family's table would fit in the new unit. Thirty years of birthdays, Thanksgivings, and report card conversations compressed into a piece of furniture. The emotional job had nothing to do with buying a smaller home. It was about starting the next chapter without losing the life they'd built. When Moesta told the architect to shrink the second bedroom and make room for the table, sales jumped twenty-seven percent.

The social job is how the customer wants to be perceived by others. Most founders ignore it. Most consumers can't articulate it. Nobody says "I bought this truck because I want my neighbors to see me as capable and self-reliant." But the manufacturers who understand that social job outsell the ones who advertise towing capacity. Nobody says "I chose Airbnb because I want my friends to see me as an adventurous traveler." But that social job explains why Airbnb disrupted hotels that were functionally superior in almost every measurable dimension. The hotel had cleaner rooms, more reliable Wi-Fi, and 24-hour room service. Airbnb had a story you could tell at brunch.

The unique value proposition that actually drives retention isn't "we have better features." It's the one that nails all three layers: the functional task, the emotional relief, and the social identity the customer is hiring you to deliver.

Why Features Lists Kill Products

In December 2001, Dean Kamen unveiled the Segway to a wave of media coverage that bordered on hysteria. Steve Jobs had reportedly said it was "as big a deal as the PC." John Doerr predicted it would reach $1 billion in revenue faster than any company in history. Time magazine put it on the cover. Kamen himself had already revolutionized medical technology with the portable insulin pump and the iBOT wheelchair, a stair-climbing device so advanced that the FDA regulated it as a medical robot. His engineering credentials were beyond question.

The Segway was, by every technical measure, remarkable. Self-balancing on two wheels using five gyroscopes and a cluster of microprocessors. A tilt sensor that sampled body position a hundred times per second. Top speed of 12.5 miles per hour. Zero emissions. It could carry a rider and cargo across a campus, a warehouse floor, or a downtown sidewalk with the turning radius of a human body.

Kamen projected sales of 50,000 units in the first year and eventually ten million annually. The company sold approximately 30,000 units in its first six years.

The Segway was a feature looking for a job. It solved a transportation problem that almost nobody experienced as a problem. Walking short distances isn't painful for most people. Driving short distances isn't particularly inconvenient. The gap between walking and driving, the exact gap the Segway was engineered to fill, wasn't a gap that caused enough struggle to generate a hiring decision. There was no push. The current situation, walking and driving, worked well enough.

Worse, the Segway created social costs its engineers never modeled. The rider stood elevated above pedestrians, tilted forward, gliding silently at a pace that felt aggressive on a sidewalk and sluggish on a road. Early adopters reported feeling conspicuous in exactly the wrong way. The social job wasn't just neutral. It was negative. Riding a Segway in 2002 communicated something most people didn't want to communicate. Security guards and tour groups eventually adopted it, because in those contexts the elevated visibility was a feature, not a liability. But the mass market Kamen envisioned never materialized.

This is the curse of knowledge applied to product development. Elizabeth Newton demonstrated the phenomenon in a famous 1990 Stanford experiment. She asked one group of participants to tap out the rhythm of a well-known song on a table. Before tapping, the tappers predicted that listeners would identify the song about fifty percent of the time. The actual success rate was 2.5 percent. The tappers could hear the full melody in their heads. The listeners heard disconnected knocking.

Founders do the same thing with features. They hear the melody of their product, the elegant engineering, the clever design decisions, the technical sophistication. Customers hear tapping. They don't experience the product through the lens of how it was built. They experience it through the lens of whether it resolves a struggle they already have. When no struggle exists, no amount of technical elegance creates demand. Features describe what a product is. Jobs describe why a person reaches for it.

Napkin version: your customer doesn't care how the thing works. They care whether it makes progress on the problem that's been nagging them since Tuesday.

The Emotional Job Nobody Talks About

In the early 2000s, psychologists Daniel Gilbert and Timothy Wilson developed a research program around a term that would reshape how psychology understood decisions: affective forecasting. The idea was simple. Before every decision, the brain runs a simulation. It imagines the future state, predicts how that state will feel, and uses that prediction to choose. Buy the house or keep renting. Take the job or stay put. Switch to the new product or stick with the old one. The prediction of feeling is the engine of the decision.

The problem Gilbert and Wilson documented across more than a decade of studies was that people are remarkably bad at it. They overestimate how long good feelings will last and how intensely bad ones will hurt. They fixate on the most vivid feature of the imagined future and neglect everything surrounding it. Gilbert called this "focalism," and it operates like a spotlight on a dark stage: whatever the light hits seems like the whole show, while everything in shadow disappears.

This has a direct consequence for how customers hire products. When a commuter imagines buying the milkshake, their brain doesn't run a nutritional analysis. It simulates twenty minutes of something interesting in the cup holder and predicts: that will feel better than silence. When a retiree imagines moving into a smaller condo, their brain doesn't calculate price per square foot. It simulates Thanksgiving without the table and predicts: that will feel like loss. The simulation is the decision. And the simulation runs on feelings, not specifications.

Brian Knutson, a neuroscientist at Stanford, demonstrated the neural mechanics in a 2007 study. He put participants in an fMRI scanner and had them make real purchasing decisions. When someone saw a product they wanted, the nucleus accumbens lit up, the same region activated by anticipated rewards. When the price felt too high, the insula fired, the brain's pain and disgust center. The prefrontal cortex then arbitrated between the two signals. Critically, the brain's response preceded and predicted the purchasing decision more accurately than the participants' own self-reported preferences. The brain had already voted before the conscious mind weighed in.

The emotional job outweighs the functional one in almost every real purchasing decision, even when the customer frames it in purely functional language. "I need a faster computer" means "I need to stop feeling frustrated every time I open a file." "I need a better CRM" means "I need to stop feeling like I'm losing track of relationships that matter."

There's a famous line in marketing: people don't buy drills, they buy holes. But even that doesn't go deep enough. They don't buy holes either. They buy the feeling of competence that comes from hanging a shelf on Saturday morning and standing back knowing they did it themselves. The function is the vehicle. The feeling is the destination.

The elevator mirror principle illustrates the same truth from a different angle. When building managers installed mirrors in elevator lobbies, complaints about slow elevators dropped to nearly zero. The elevators didn't speed up. The mirrors changed how the wait felt. The emotional job, make this wait less unpleasant, was solved without touching the functional reality at all.

Anthony Ulwick, who developed the Outcome-Driven Innovation method as a quantitative extension of Jobs to Be Done, found that when companies mapped both functional and emotional desired outcomes, the emotional outcomes predicted commercial success more reliably. Products that nailed the functional job but missed the emotional one underperformed. Products that nailed the emotional job with merely adequate functional performance often dominated their category. Alan Klement, in his book When Coffee and Kale Compete, pushed this further: the job is never really about the task. It's about the person the customer is trying to become.

Try This: The Job Interview

Most product teams have never conducted a proper job interview, and it is the single highest-leverage research activity available to an early-stage founder. The technique comes from Bob Moesta and Chris Spiek's switch interview method, refined across thousands of customer conversations. Here is the five-step protocol.

First, find the right people. You need five to ten individuals who recently bought your product, switched to your product from a competitor, or stopped using your product. Recent means within the last ninety days. Memory degrades fast, and you need the emotional texture intact, not a cleaned-up narrative the person has been telling themselves for six months.

Second, reconstruct the timeline. Don't ask "Why did you choose us?" Ask "Take me back to the moment you first realized the old way wasn't working. Where were you? What time of day was it? What had just happened?" The goal is to rebuild the full emotional sequence from first thought to final purchase. Push for sensory detail. You want the scene, not the summary. The moment someone says "I was sitting at my desk and I just thought, I can't do this anymore," you've found the push. That's the circumstance the job lives inside.

Third, map the four forces. Moesta identified four forces that govern every switching decision. The push is what's wrong with the current situation, the frustration or failure that starts the search. The pull is what's attractive about the new option, the imagined better future. The anxiety is what could go wrong if the person switches, the fear of making a bad choice or losing what's familiar. And the habit is what's comfortable about staying put, the gravitational pull of the status quo. Every purchase happens when push plus pull exceeds anxiety plus habit. If you don't understand all four, you're building blind. If you only hear the pull ("I liked your features"), you're missing the push that started the search and the anxiety that almost killed it.

Fourth, find the pattern. After five interviews, write down what they share. Not the demographics. Not the feature requests. The situation, the struggle, and the desired feeling. If three different people describe the same underlying frustration using three different sets of words, you've found a job. If every interview sounds completely different, you either have a market too fragmented to serve or you're asking the wrong questions.

Fifth, write the job in one sentence using this format: "When I [situation], I want to [motivation], so I can [desired outcome]." For the morning commuters: "When I face a long boring drive with nothing to do, I want something that lasts and keeps me occupied, so I can arrive at work feeling like the morning wasn't wasted." For Moesta's condo buyers: "When I realize this house is too much for just the two of us, I want to move somewhere simpler, so I can start my next chapter without losing the life I built." That sentence becomes your product compass. Every feature decision, every marketing message, every pricing choice should serve it. If a proposed feature doesn't make progress on that sentence, it doesn't ship. This is the foundation for building a minimum viable product that tests the right thing from the start.

Napkin version: don't ask customers what they want. Ask them what they were struggling with the moment before they went looking.


The milkshake didn't need better chocolate. The Segway didn't need a sixth gyroscope. The condo didn't need a bigger kitchen. Each needed someone to stop staring at the product and start watching the person holding it.

Clayton Christensen passed away in January 2020, but the framework he spent three decades building has only grown sharper. Every product that succeeds beyond its feature set, every startup that wins against a better-funded competitor, every conversion rate that jumps after a positioning change rather than a product update, is evidence that the job was there all along, waiting for someone to notice it. The question isn't whether your customers have jobs to be done. It's whether you've identified the real one or just the one that's easiest to see.

The Launch System covers the full process for discovering the job your product fills before you invest months building the wrong solution. It includes the switch interview protocol, the four-forces framework for mapping what pushes customers toward change and what holds them back, and the validation sequence for testing whether you've found a real job or just a feature request dressed up as insight. Because the hardest part of launching has never been building the product. It's figuring out which product to build.


FAQ

What is Jobs to Be Done (JTBD)? Jobs to Be Done is a framework developed by Clayton Christensen that reframes product strategy around customer progress rather than product features. The core idea is that people don't buy products for what they are. They "hire" products to make progress in a specific situation. A morning commuter doesn't buy a milkshake because they want a milkshake. They hire it to make a boring drive less empty and keep them full until noon. Identifying the real job changes what you build, how you market it, and who you consider your competition.

How is Jobs to Be Done different from buyer personas? Buyer personas segment customers by demographics and psychographics: age, income, interests, lifestyle. JTBD segments by situation and struggle, regardless of who the person is. Two people with completely different demographic profiles can have the identical job to be done, and two people with identical profiles can hire the same product for entirely different jobs. The morning milkshake buyers varied widely in age, income, and background. What they shared was a circumstance: a long, boring commute with a free hand and an empty cup holder.

What are the three dimensions of a job to be done? Every job has a functional dimension (the practical task the customer wants accomplished), an emotional dimension (how the customer wants to feel during and after using the product), and a social dimension (how the customer wants to be perceived by others). Most companies focus exclusively on the functional layer, which is the most visible and least differentiating. The emotional and social layers are where the actual hiring decision happens. The retirees buying condos in Detroit weren't hiring a floor plan. They were hiring the ability to keep their family's dining room table.

How do you discover the job to be done for your product? Conduct switch interviews with five to ten recent buyers or recent churners. Ask them to reconstruct the full timeline from the first moment they considered a change to the moment they committed. Listen for the four forces: push (dissatisfaction with the current situation), pull (attraction to the new option), anxiety (fear of switching), and habit (comfort with the status quo). The job emerges from the patterns across interviews, specifically the recurring situation, struggle, and desired emotional outcome that multiple customers describe in different words. State it in one sentence: "When I [situation], I want to [motivation], so I can [desired outcome]."

Works Cited

  • Christensen, Clayton M., Hall, Taddy, Dillon, Karen, and Duncan, David S. "Know Your Customers' 'Jobs to Be Done.'" Harvard Business Review, September 2016. https://hbr.org/2016/09/know-your-customers-jobs-to-be-done

  • Christensen, Clayton M., Hall, Taddy, Dillon, Karen, and Duncan, David S. Competing Against Luck: The Story of Innovation and Customer Choice. New York: Harper Business, 2016.

  • Ulwick, Anthony W. Jobs to Be Done: Theory to Practice. Houston: Idea Bite Press, 2016.

  • Klement, Alan. When Coffee and Kale Compete: Become Great at Making Products People Will Buy. NYC Publishing, 2018.

  • Gilbert, Daniel T. and Wilson, Timothy D. "Prospection: Experiencing the Future." Science 317, no. 5843 (2007): 1351-1354. https://doi.org/10.1126/science.1144161

  • Gilbert, Daniel T., Pinel, Elizabeth C., Wilson, Timothy D., Blumberg, Stephen J., and Wheatley, Thalia P. "Immune Neglect: A Source of Durability Bias in Affective Forecasting." Journal of Personality and Social Psychology 75, no. 3 (1998): 617-638.

  • Wilson, Timothy D. and Gilbert, Daniel T. "Affective Forecasting: Knowing What to Want." Current Directions in Psychological Science 14, no. 3 (2005): 131-134.

  • Knutson, Brian, Rick, Scott, Wimmer, G. Elliott, Prelec, Drazen, and Loewenstein, George. "Neural Predictors of Purchases." Neuron 53, no. 1 (2007): 147-156. https://doi.org/10.1016/j.neuron.2006.11.010

  • Newton, Elizabeth L. "Overconfidence in the Communication of Intent: Heard and Unheard Melodies." Doctoral dissertation, Stanford University, 1990.

  • Moesta, Bob and Spiek, Chris. "The Jobs-to-be-Done Switch Interview." JTBD Radio. https://jobstobedone.org/radio/


Reading won't build your business.

The strategies in this post work — but only if you use them. Inside The Launch Pad, you get the frameworks, the feedback, and the accountability to actually execute.

Build Your Exit