In the late 1990s, a fast-food chain wanted to sell more milkshakes. The company followed the standard playbook: survey customers, segment by demographics, ask what improvements would make the milkshake better. Thicker? Thinner? More chocolate? Cheaper? The feedback was clear and actionable. The company made every requested change. Sales didn't move.
Clayton Christensen's research team at Harvard Business School took a different approach. Instead of asking customers what they wanted in a milkshake, they asked a different question entirely: what job are you hiring this milkshake to do?
They stationed researchers in a restaurant for eighteen hours, recording every milkshake purchase — who bought it, when, what else they bought, whether they consumed it in the store or carried it out. The data revealed something no demographic survey had captured: nearly half the milkshakes were sold before 8:30 AM, to solo customers who bought nothing else and carried them to their cars.
The follow-up interviews exposed the job. These customers faced a long, boring commute. They needed something to do with one hand while driving. They needed something that would keep them full until lunch. They'd previously hired bananas for the job — finished too quickly. Donuts — crumbs everywhere, greasy fingers on the steering wheel. Bagels — dry, required two hands. The milkshake was the best candidate: thick enough to last a twenty-minute drive, consumed through a straw with one free hand, and calorie-dense enough to suppress hunger until noon.
The afternoon milkshake served an entirely different job. Parents bought them for children as a concession — a small "yes" to compensate for the many "no"s of the day. These customers wanted a thinner milkshake their child could finish before patience ran out.
Same product. Two completely different jobs. Making the milkshake thicker would improve the morning hire and sabotage the afternoon one. Making it thinner would do the reverse. The demographic data — age, income, visit frequency — predicted nothing. The job predicted everything.
This is the core of Jobs to Be Done: customers don't buy products. They hire them to make progress in specific circumstances. The unit of analysis isn't the customer or the product. It's the job — the underlying struggle for progress that exists independently of any solution.
Theodore Levitt, the Harvard marketing professor, captured the principle decades earlier: "People don't want to buy a quarter-inch drill. They want a quarter-inch hole." Christensen extended that observation into a complete theory of competitive analysis. The drill is one candidate for the job. So is a nail already embedded in the wall. So is a picture hook with adhesive backing. The competitors aren't other drill manufacturers. The competitors are every solution that gets a hole in the wall — including the decision not to hang the picture at all.
The framework separates every job into three dimensions. Functional: what the customer needs to accomplish. Emotional: how the customer wants to feel. Social: how the customer wants to be perceived. A luxury watch tells time — functional. It provides a sense of personal reward and achievement — emotional. It signals status and taste to others — social. The functional job is trivially served by a $15 Casio. The emotional and social jobs explain why people pay $10,000 for an Omega.
IKEA understood all three dimensions. The job wasn't "buy furniture." The job was "make this apartment feel like home today" — for a young person furnishing a first apartment on a limited budget. The functional requirement was immediate availability and low price. The emotional requirement was feeling capable and independent. The social requirement was having a space that didn't look temporary. IKEA's flat-pack model, in-store room displays, and same-day availability served all three dimensions simultaneously. The competition wasn't other furniture retailers. It was leaving the apartment unfurnished, borrowing from parents, or buying secondhand online.
The inverse reveals the framework's diagnostic power. A company can dominate its product category and still lose — because the job migrates to a different solution. Encyclopaedia Britannica commanded the reference market for over two centuries. The job was "answer a factual question reliably." Wikipedia did the functional job with less authority but dramatically more convenience and zero cost. Google did it with even less depth but even more speed. By 2012, Britannica had ceased print publication. The product was excellent. The job had moved.
The framework's most counterintuitive implication: your real competitors are often not in your industry. When Netflix asked what job its evening viewers were hiring the service to do, the answer wasn't "watch a specific show." The answer was "help me relax for an hour without having to make a bunch of decisions first." The competition for that job included wine, social media, video games, and going for a walk. A film studio analyzing Netflix's competitive threat by comparing content libraries was measuring the wrong dimension entirely.
The practical consequence for founders: if you define your market by your product category, you will be blindsided by competitors who don't look like competitors. If you define your market by the job, you will see the full competitive landscape — including the threats that product-category analysis structurally conceals.
Section 2
How to See It
Jobs to Be Done becomes visible when you shift attention from what people buy to why they buy it — and especially when the "why" reveals competitors you wouldn't have identified through traditional industry analysis.
Technology
You're seeing Jobs to Be Done when a product succeeds despite being objectively inferior on traditional feature comparisons. Early Dropbox was worse than USB drives on storage capacity, worse than email for sharing small files, and worse than external hard drives on reliability. It succeeded because the job wasn't "store files." The job was "access my stuff from anywhere without thinking about it." No USB drive could be hired for that job. Feature comparisons missed the point entirely because they measured the wrong dimensions of competition.
Business
You're seeing Jobs to Be Done when customer segmentation by demographics fails to predict purchasing behavior. The morning milkshake buyers ranged from construction workers to commuting professionals — no demographic cohort explained the purchase. The explaining variable was circumstance: long commute, one free hand, hunger until lunch. When demographics don't predict behavior but circumstances do, you're looking at a job.
Investing
You're seeing Jobs to Be Done when a company captures market share from unexpected directions — taking revenue from products in entirely different categories. When the iPhone launched in 2007, it didn't just take share from Nokia and Motorola. It took share from point-and-shoot cameras, GPS devices, MP3 players, handheld gaming consoles, alarm clocks, and pocket calculators. Each of those categories represented a job the iPhone could be hired to do. Investors watching only the smartphone market missed the total addressable opportunity by an order of magnitude.
Markets
You're seeing Jobs to Be Done when customer satisfaction scores are high but growth has stalled. The company is doing the current job well — but the job itself is shrinking, or a new solution has emerged that does the job so differently it doesn't register as competition. BlackBerry had the highest customer satisfaction scores in smartphones as late as 2008. Its customers were deeply satisfied with how it performed the job of "manage professional email on the go." They switched to iPhone anyway because the job had expanded to include mobile tasks that BlackBerry's architecture couldn't serve.
Section 3
How to Use It
Decision filter
"What is the customer struggling to accomplish in this specific circumstance? What are they hiring my product to do — and what were they using before they found it? If I can't answer both questions with precision, I don't yet understand the competitive landscape."
As a founder
Start every product decision by articulating the job, not the feature. The most common failure mode in product development is building what customers say they want rather than understanding what they're struggling to accomplish. Henry Ford's apocryphal quote — "If I had asked people what they wanted, they would have said a faster horse" — captures the distinction. The job was "get from A to B faster and more reliably than a horse." The Model T addressed the job. A faster horse addressed the stated preference.
Interview customers about their last purchase in the category. Ask them to walk through the timeline: when did they first realize they had a problem? What did they try before your product? What finally triggered the switch? These "switching stories" reveal the job with far more precision than any feature request. When Intercom's product team adopted JTBD interviews in their early years, they discovered that many customers had switched from email — not from a competing chat tool. The job wasn't "better customer chat software." The job was "respond to customers faster without losing conversations in my inbox." That reframe changed their competitive positioning, marketing language, and product roadmap.
As an investor
The JTBD framework reveals whether a company's addressable market is larger or smaller than traditional analysis suggests. If the job crosses industry boundaries, the market is bigger. If the job is narrower than the product category implies, the market is smaller.
When Peloton launched, industry analysts sized the market as "connected fitness equipment" — a small niche. JTBD analysis sized it differently: the job was "make me feel like I got a great workout without the inconvenience of going to a gym." That job was being served by gym memberships, personal trainers, workout DVDs, running outdoors, and doing nothing. The relevant market was the $94 billion global fitness industry, not the $2 billion home equipment segment. The inverse applies too. A company selling project management software might claim its market is "enterprise software," but if the job is "keep a five-person team aligned on weekly tasks," the relevant competition includes shared Google Docs, Slack channels, and weekly standup meetings — not Jira or SAP.
As a decision-maker
Use JTBD to diagnose why products lose customers. Churn analysis typically examines feature gaps, pricing, and competitive offerings. JTBD asks a prior question: has the job changed? A customer who cancels a meal-kit subscription may not have switched to a competitor. The job — "feed my family a healthy dinner without the cognitive load of planning" — may have been replaced by a different priority entirely: "spend less money this month." The meal kit didn't fail at its job. The job lost priority. This diagnostic prevents the most expensive error in retention strategy: improving a product that customers aren't leaving because of.
Common misapplication: Treating JTBD as a rebranding exercise rather than a research methodology. The framework's power comes from rigorous interview technique — the "switching stories" developed by Bob Moesta and Christensen that uncover the actual push and pull forces behind a purchase decision. Founders who rename their feature list as "jobs" without conducting the underlying research are applying marketing vocabulary to an unchanged analytical process. The milkshake insight didn't emerge from a brainstorming session. It emerged from eighteen hours of observation and dozens of structured interviews. The methodology is the model.
Section 4
The Mechanism
Section 5
Founders & Leaders in Action
The founders below didn't use the phrase "Jobs to Be Done" in their strategic planning. Most of them built their companies before Christensen published the theory. What they shared was an instinct — an ability to see past the product to the underlying struggle their customers were trying to resolve. They designed for the job, not the feature comparison chart.
The pattern across these cases is consistent: the founder who understood the job built something that looked irrational by industry standards. A shoe company that sold aspiration more than footwear. A bookstore with no physical books. A streaming service that deliberately reduced the viewer's burden of choice. Each decision confused industry analysts precisely because those analysts were evaluating the product, not the job.
What separates these founders from competent product managers is the depth of the insight. A product manager might survey customers and learn they want "more features." These founders watched what customers actually did — when, where, and instead of what — and derived the job from behavior rather than testimony. The methodology is ethnographic, not statistical. The output is a causal story, not a preference ranking.
In 2001, the portable music market was crowded with MP3 players. Creative, Diamond Multimedia, and a dozen other manufacturers competed on storage capacity, file format support, and price. Jobs ignored all of those dimensions.
The job wasn't "store music files on a portable device." The job was "take my entire music library with me everywhere, and find any song instantly." The iPod's 5 GB hard drive held 1,000 songs — less than some competitors on a per-dollar basis. But the click wheel interface and iTunes integration meant a user could navigate their library in seconds rather than scrolling through file directories. The competitors were solving a storage problem. Jobs was solving an experience problem. The tagline — "1,000 songs in your pocket" — described the job, not the spec sheet.
The iPhone extended the insight. When Jobs introduced it in January 2007, he described three products: a widescreen iPod, a revolutionary phone, and a breakthrough internet device — then revealed they were the same product. The framing was deliberate. Each "product" was actually a job. Consumers were carrying three separate devices for music, communication, and web browsing. The iPhone consolidated three jobs into one hire. Nokia engineers who analyzed the iPhone's specifications were baffled by its limitations: no 3G, no MMS, no copy-paste, a 2-megapixel camera. On a feature comparison, it lost to a $200 Nokia N95 on nearly every technical dimension. But the job comparison wasn't close. The iPhone did three jobs well enough that carrying three devices became irrational. Within five years it had collapsed entire product categories — GPS units, point-and-shoot cameras, MP3 players, PDAs — because each category was a job the iPhone could be hired to do.
Amazon's early pitch — "Earth's Biggest Bookstore" — sounded like a product description. It was a job description disguised as a tagline. The job wasn't "buy a book." The job was "find exactly the book I'm looking for, no matter how obscure, and get it without visiting three stores."
Barnes & Noble carried 175,000 titles in a superstore. Amazon listed 1.1 million. For the reader searching for an out-of-print academic text or a niche hobbyist guide, Barnes & Noble couldn't be hired for the job at any price. The physical constraint of shelf space meant the store could never serve the long tail of demand. Amazon's digital catalog eliminated the constraint entirely.
The insight extends to Amazon Prime, launched in 2005. The conventional analysis: an annual subscription for free shipping. The JTBD analysis: the job was "remove every reason not to buy." Before Prime, each purchase required a friction-laden mental calculation — is this item worth the shipping cost? Should I batch orders? Should I drive to the store instead? Prime eliminated the calculation. The job shifted from "decide whether to buy online" to "click and stop thinking about it." Prime members spent more than twice as much as non-members not because the subscription created irrational behavior but because it removed the friction that had been preventing rational behavior. The job of frictionless procurement was always there. Prime was the first product hired to do it completely.
Bezos's internal practices reinforced job-centric thinking at organizational scale. The famous "empty chair" in meetings — representing the customer — was a structural reminder to evaluate decisions from the job perspective. Amazon's internal press release format for new products required teams to describe the customer problem before proposing the solution, enforcing a JTBD-first discipline across thousands of product decisions.
Netflix's most revealing JTBD insight wasn't about content or technology. It was about decision fatigue.
When Hastings's team studied viewing behavior in the early streaming era, they found that users spent an average of eighteen minutes browsing before selecting something to watch. For many viewers, the browsing itself became aversive — an unwanted job layered on top of the actual job. The product was being hired for one thing ("relax me tonight") while forcing the user through a different, unwanted task ("choose what to watch"). Autoplay, the "continue watching" row, and the increasingly assertive recommendation algorithm were all responses to this tension. Netflix wasn't optimizing for content discovery. It was minimizing the distance between the internal trigger ("I want to unwind") and the reward (content playing on screen).
The JTBD lens also explains Netflix's $17 billion annual content spend. The company wasn't trying to have the best library — an objective, feature-comparison frame. It was ensuring that for any viewer, in any mood, at any time, there was something good enough to hire. The job specification wasn't "the best content." It was "something that works for me right now." That distinction drove the investment in breadth over depth — hundreds of original titles across dozens of genres rather than a small number of prestige productions. HBO served the job of "watch the best show on television." Netflix served the job of "give me something decent before I give up and open Instagram."
The competitive reframe was the sharpest in the industry. Hastings said publicly in 2017 that Netflix's biggest competitor was sleep — a statement that only makes sense through a JTBD lens. No traditional industry analysis would list sleep as a competing product. The job framework makes the competition obvious: anything else the customer might hire to fill the hours between dinner and bed.
Nike's founding mythology centers on waffle irons and running shoes, but the company's dominance was built on a JTBD insight about identity, not footwear.
In the early years, Blue Ribbon Sports (Nike's predecessor) competed on functional performance — lighter, better-cushioned shoes for serious runners. That addressed a clear functional job. Knight's pivotal decision came in 1988 with the "Just Do It" campaign, which reframed the job entirely. The campaign didn't describe shoes. It described a feeling. The job shifted from "improve my running performance" to "feel like an athlete — whether I run or not."
This emotional and social job expanded Nike's addressable market by orders of magnitude. Serious runners were a niche. People who wanted to feel athletic, capable, and aspirational were everyone. A teenager buying Air Jordans wasn't hiring the shoe for basketball performance. The shoe was hired for social signaling — belonging, status, cultural participation. Michael Jordan's deal with Nike in 1984 was a JTBD bet: the job of "be associated with greatness" was worth more than the job of "play better basketball." Jordan never designed a shoe. He provided the emotional and social value that the shoe was hired to deliver.
Knight's insight explains an otherwise puzzling fact: Nike sells billions of dollars worth of athletic shoes to people who don't exercise. The product-centric analyst sees an overpriced commodity. The JTBD analyst sees a product calibrated to the emotional and social dimensions of the job — looking athletic, signaling taste, belonging to a culture. The functional dimension is almost irrelevant for the majority of Nike's customers. The company's competitors aren't just Adidas and New Balance. They're any brand or product hired to express identity and aspiration.
Tesla's Roadster launched in 2008 at $109,000 — a two-seat sports car with a 245-mile range. Traditional automotive analysis classified it as an electric vehicle competing against the emerging Nissan Leaf and Chevy Volt. That framing missed the actual hiring decision entirely.
The Roadster wasn't hired to "drive electric." It was hired to do a job that no existing car could perform: "drive something exhilarating and feel virtuous about it simultaneously." Prior to Tesla, environmentally conscious performance car buyers faced an impossible compromise. A Porsche 911 did the exhilaration job but created environmental guilt. A Toyota Prius addressed the virtue job but offered no driving pleasure whatsoever. The two jobs were mutually exclusive — hiring one meant firing the other. The Roadster collapsed the compromise. Its competitive set wasn't other electric vehicles. It was the guilt that accompanied every high-performance car purchase.
The Model 3, launched in 2017 at $35,000, addressed a completely different job for a completely different circumstance. The buyer wasn't a wealthy enthusiast. The buyer was a mid-career professional whose existing car was aging, whose commute was routine, and whose self-image increasingly included "the kind of person who makes responsible choices." The job: "replace my car with something that feels like an upgrade in every dimension — technology, driving experience, operating cost, identity — without the old trade-offs." Tesla's over-the-air updates, minimalist interior, and Supercharger network weren't features on a spec sheet. They were answers to specific dimensions of that job: the technology dimension, the experience dimension, the convenience dimension.
The competition for the Model 3 wasn't other electric vehicles. It was every car a buyer in that circumstance would consider — the BMW 3 Series, the Audi A4, the loaded Honda Accord. Tesla's achievement was making the electric powertrain invisible as a category distinction and visible only as a benefit: faster acceleration, lower fuel cost, less maintenance. The job defined the competitive set. The powertrain was incidental.
Section 6
Visual Explanation
Section 7
Connected Models
Jobs to Be Done operates at the intersection of innovation theory, product design, and competitive strategy. It reshapes how several adjacent frameworks are applied — reinforcing some, creating productive tension with others, and serving as a natural precursor to strategic questions that other models address. The connections below map the most important interactions.
Reinforces
Disruptive Innovation
Christensen developed JTBD partly to strengthen the predictive power of his earlier disruption theory. Disruptive Innovation explains the trajectory — entrants start below market requirements and improve until they're good enough. JTBD explains the mechanism of switching — why customers adopt the disruptive product despite its apparent inferiority. The answer: the disruptive product does a different job, or serves the same job in a circumstance the incumbent doesn't address. Netflix's early subscribers weren't hiring Netflix for Blockbuster's job (Friday night impulse rental). They were hiring it for a different job — curated access to a deep catalog for serial viewers. When Netflix eventually became good enough at the mainstream job, the switch accelerated. JTBD predicts which disruptions will gain traction; disruption theory predicts the competitive dynamics once they do. Together, they form the most complete framework for understanding why incumbents fall.
Reinforces
First Principles Thinking
Jobs to Be Done is first principles thinking applied to customer behavior. Instead of accepting the industry's inherited definition of the product category, JTBD decomposes the customer's situation to its fundamental elements: what progress are they seeking, in what circumstance, against what alternatives? The milkshake study is a first principles decomposition of a purchase decision — stripping away demographic assumptions, survey-based preference data, and product-category conventions to find the irreducible causal mechanism. The drill-and-hole insight is the same move: refuse the inherited frame (the product) and find the fundamental truth (the job). Founders who practice both models develop a distinctive analytical habit: decomposing simultaneously from the technology side (first principles on cost and capability) and the demand side (JTBD on what progress customers actually seek).
Tension
Section 8
One Key Quote
"When we buy a product, we essentially 'hire' something to get a job done. If it does the job well, when we are confronted with the same job, we hire that same product again. If the product does a crummy job, we 'fire' it and look around for something else we might hire to solve the problem."
— Clayton Christensen, Competing Against Luck (2016)
Section 9
Analyst's Take
Faster Than Normal — Editorial View
Jobs to Be Done is the single most underused framework in product strategy relative to its explanatory power. Every year, billions of dollars in R&D spending are allocated based on customer surveys that ask the wrong question — "what features do you want?" — instead of the right one — "what are you struggling to accomplish?" The milkshake study is over twenty-five years old. The insight has been validated across dozens of industries. And the majority of product teams still define their roadmaps around feature comparisons with competitors rather than job specifications derived from actual customer behavior.
The framework's deepest contribution is redefining competition. Traditional competitive analysis draws industry boundaries and evaluates rivals within those boundaries. JTBD erases the boundaries entirely. The competitors for any product are every alternative the customer considers when the job arises — including doing nothing, using a workaround, or hiring a product from an entirely different category. When Christensen's team asked morning milkshake buyers what they'd do if milkshakes disappeared, the answers included bananas, bagels, coffee, and "just be bored." None of those are in the milkshake industry. All of them are in the competitive set for the job.
The dimension most teams neglect: the emotional and social jobs. It's comfortable to focus on functional requirements — they're measurable, buildable, and defensible in product reviews. The emotional and social dimensions are harder to quantify and easier to dismiss. But they explain the price premium in nearly every premium category. Apple charges $1,200 for a phone that does the same functional job as a $300 Android device. The delta is entirely emotional and social — the feeling of using a beautifully designed product, the status of owning one, the identity signal of being "an Apple person." Founders who design only for the functional job build commodities. Founders who design for all three dimensions build brands.
The methodology matters more than the framework. I've seen dozens of teams claim to practice JTBD while actually practicing repackaged feature prioritization. They rename their feature list as "jobs" without conducting the switching interviews, the behavioral observation, or the circumstance mapping that the methodology requires. The result looks like JTBD but produces the same outputs as traditional product management. Bob Moesta's interview technique — reconstructing the timeline of a switching decision to identify the push, pull, anxiety, and habit forces — is specific, learnable, and irreplaceable. Skip the methodology and you've adopted the vocabulary without the insight.
Section 10
Test Yourself
Jobs to Be Done sounds intuitive — customers hire products for jobs. The difficulty is in application: correctly identifying the job, distinguishing it from the product feature, and mapping the competitive set that the job reveals rather than the one the industry defines. These scenarios test whether you can separate product-centric thinking from job-centric analysis.
Is this mental model at work here?
Scenario 1
A furniture company surveys customers and learns they want sofas in more colors, faster delivery, and lower prices. The company expands its color palette, negotiates better shipping rates, and reduces margins. Customer satisfaction scores improve but market share remains flat.
Scenario 2
A streaming music service notices that its fastest-growing playlist category is 'focus' and 'study' music — ambient, lo-fi, and instrumental tracks. Usage peaks during work hours, not evenings. The service redesigns its home screen to prominently feature these playlists for users who typically listen during the workday.
Scenario 3
A luxury car brand conducts focus groups with potential buyers. Participants describe wanting better horsepower, advanced safety features, and premium interior materials. The company invests $2 billion in engine performance, crash testing, and leather sourcing. Sales improve 4% — well below the projected 15%.
Section 11
Top Resources
The JTBD literature splits between Christensen's theoretical framework and the practitioner methodology developed by Bob Moesta and others. Start with Christensen for the theory and Moesta for the interview technique. The Levitt article is the intellectual ancestor. Ulwick provides the most structured process for converting job insights into product specifications.
The definitive text on Jobs to Be Done theory. Christensen's full articulation of the framework, including the three job dimensions, the milkshake case study, and the concept of non-consumption as the largest source of innovation opportunity. The IKEA and Intuit case studies demonstrate the framework applied to companies that built durable advantage around job understanding. Read this before anything else in the JTBD literature.
Moesta, who co-developed the JTBD interview methodology with Christensen, provides the practitioner's guide to uncovering jobs through customer interviews. The "switching timeline" technique — reconstructing the sequence from first thought to final purchase — is the most reliable method for identifying the push, pull, anxiety, and habit forces that drive hiring and firing decisions. More practical and interview-focused than Competing Against Luck.
The intellectual origin of job-centric thinking. Levitt's argument — that companies fail when they define themselves by their product rather than by the customer need they serve — laid the foundation for everything Christensen later formalized. The railroad example (they thought they were in the railroad business, not the transportation business) remains the clearest illustration of why product-category thinking leads to decline. Published in Harvard Business Review, it has been reprinted more than any other HBR article in history.
Ulwick developed Outcome-Driven Innovation (ODI), a structured methodology for converting JTBD insights into product requirements. Where Christensen provides the theory and Moesta provides the interview technique, Ulwick provides the process for translating jobs into quantified outcome statements that can be systematically prioritized. The most rigorous operationalization of the framework for product management teams.
The book where Christensen first introduced the Jobs to Be Done concept, before it was fully developed in Competing Against Luck. Chapter 3 ("What Products Will Customers Want to Buy?") presents the initial formulation and connects it directly to disruption theory. Reading this alongside the 2016 book shows the evolution of the framework from supporting concept to standalone theory over thirteen years.
Jobs to Be Done reframes competition — the unit of analysis is the job, not the product category, revealing competitors invisible to traditional industry analysis
Marc Andreessen's concept of product/market fit — the moment when a product satisfies a strong market demand — is one of the most used frameworks in startup strategy. JTBD creates a productive tension by challenging the definition of "market." In the Andreessen formulation, a market is a group of customers who will pay for a solution. In the JTBD formulation, a market is a job — and the same job can span customer segments, industries, and product categories that traditional market analysis would never group together. A startup can achieve product/market fit as conventionally measured (growing revenue, organic demand) while serving only one dimension of the job — and remain vulnerable to a competitor that addresses the full job spec including emotional and social dimensions. Peloton found product/market fit in connected fitness. But the full job — "make me feel like I'm making progress on my health without reorganizing my life" — was also being served by Apple Watch, Weight Watchers, and meditation apps. Product/market fit tells you you've found demand. JTBD tells you whether you've found the whole job or just a corner of it.
Tension
[Hook](/mental-models/hook) Model
Nir Eyal's Hook Model describes how products create habitual engagement through a cycle of trigger, action, variable reward, and investment. JTBD describes why customers initially hire a product. The tension is fundamental: JTBD assumes purposeful progress-seeking; the Hook Model describes behavior that has become automatic and operates below conscious deliberation. A user "hires" Spotify to discover new music (JTBD). That same user opens Spotify reflexively when putting on headphones, regardless of whether music discovery is the current need (Hook). The models describe different phases of the product relationship — JTBD governs adoption and initial hiring; the Hook governs retention and habitual return. The strongest products connect both: they solve a genuine job (which provides the motivation to begin the Hook cycle) and build a habit (which ensures the product remains hired even when alternatives emerge). Products that Hook without solving a real job are addictive but shallow. Products that solve a job without building a Hook are useful but replaceable.
Leads-to
Founder-Market Fit
Once you've identified the job, the next strategic question is whether the founding team has a distinctive ability to serve it. Founder-Market Fit evaluates whether the founder's experience, obsession, and insight give them an advantage in understanding the job that competitors lack. JTBD defines the target; Founder-Market Fit evaluates the team's right to pursue it. Phil Knight's background as a competitive runner gave him founder-market fit for the functional job of athletic performance. His instinct for aspirational branding gave him fit for the emotional job. Reed Hastings's personal frustration with Blockbuster late fees — the origin story of Netflix — was a founder experiencing the job firsthand. The most durable companies are built by founders whose personal experience of the job creates insight that cannot be replicated through market research alone.
Leads-to
[Distribution](/mental-models/distribution)
Identifying the job is necessary but insufficient. The product must reach customers in the circumstance where the job arises — which means distribution strategy must be designed around the job context, not the product category. The milkshake's job arose during the morning commute, which meant the distribution channel was the drive-through window before 8:30 AM. A milkshake optimized for the job but sold only inside sit-down restaurants would fail despite being the superior product. Slack's distribution through bottom-up team adoption rather than enterprise IT procurement reflected a JTBD insight: the job ("stay connected to my team's conversation") was experienced by individual team members, not by CIOs. Distribution through viral, team-level adoption matched the circumstance where the job arose. JTBD defines what the customer needs. Distribution determines whether the product reaches them in the moment they need it.
The framework's limitation that practitioners understate: it diagnoses demand but doesn't prescribe supply. JTBD will tell you what job the customer is hiring for. It will not tell you how to build the product that does the job best, how to price it, how to distribute it, or how to defend it against competitors who identify the same job. The milkshake study revealed the morning commute job but didn't specify whether to make the shake thicker, add protein, change the cup size, or redesign the drive-through window. Those are engineering and design decisions that require complementary frameworks. JTBD is the diagnostic. It is not the complete treatment plan.
Where the framework produces the largest returns: non-consumption. The most valuable jobs aren't the ones where customers switch between competing products. They're the ones where customers have no good solution at all — where the current "hire" is a workaround, a compromise, or going without. M-Pesa in Kenya didn't take customers from banks. It served 17 million people who had no financial services whatsoever. The job — "transfer money safely to a family member in another city" — was being done through bus drivers carrying cash envelopes. The workaround was the signal that a massive job existed without an adequate solution. Founders who focus JTBD analysis on non-consumption rather than competitive switching consistently find larger opportunities with less initial competition.
One underappreciated pattern: the best JTBD insights come from studying firing events, not hiring events. When a customer stops using a product, the reason they give is almost never the real reason. "Too expensive" usually means "I stopped getting enough value to justify the cost." "Found a better alternative" usually means "the job changed and this product no longer fits the new circumstance." Firing interviews — conducted with the same rigor as switching interviews — reveal job drift, unmet emotional dimensions, and competitive threats that satisfaction surveys systematically miss. Companies that only study why customers arrive will never understand why customers leave.
The current frontier: JTBD applied to AI products. Most AI tools are being positioned as feature improvements to existing software — "like X, but with AI." That's product-category thinking, not job thinking. The more revealing question: what jobs were previously impossible or impractical that AI now makes feasible? A small business owner who couldn't afford a marketing team can now hire an AI tool for the job of "create professional marketing materials without specialized skills." That's not a feature improvement to existing design software. It's a new hire for a job that was previously unserved below a certain budget threshold. The largest AI opportunities will come from JTBD analysis of non-consumption — identifying the jobs that people have been unable to hire for because no affordable, accessible solution existed until now.
My honest read: JTBD is the framework that makes every other product framework more useful. It doesn't replace competitive analysis, pricing strategy, or distribution planning. It gives those frameworks the correct input — the actual job — rather than the inherited input that most companies use: the product category. Get the job right and the downstream decisions become clearer. Get it wrong and no amount of execution excellence will compensate, because you'll be building the best solution to a problem that isn't the one your customers actually have.
Scenario 4
A meal-kit startup finds that 40% of cancellations cite 'too expensive' as the reason. Instead of lowering prices, the company interviews churned customers about the full timeline leading to cancellation. They discover most cancellations occur after three months, when the novelty of cooking new recipes has worn off and the original job — 'learn to cook interesting meals' — has been accomplished. The customers didn't fire the product for being expensive. They fired it because the job was done.
