Concise Summary简洁概述
Customers don't buy products by demographic or feature preference — they 'hire' products to make progress on a specific job defined by circumstance, spanning functional, social, and emotional dimensions.
Correlation-based big data (who bought what) cannot reveal causation (why); only observing struggle in context — active, qualitative data — exposes the mechanism behind a purchase.
客户购买行为并非由人口统计特征或功能偏好驱动，而是「雇用」产品来完成某个由具体情境定义的任务，这个任务同时包含功能、社会、情感三个维度。
基于相关性的大数据（谁买了什么）无法揭示因果（为什么买）；只有在具体情境中观察客户的挣扎——主动的定性数据——才能暴露购买背后的真实机制。
Infographic信息图
The Milkshake Dilemma
奶昔困境
18 hours of observation revealed two unrelated buying occasions for the same product: a viscous, single-hand-friendly shake for bored morning commuters, versus a thin, fast-drinking shake for guilty afternoon dads. Averaging the two designs satisfies neither.
18小时的现场观察揭示同一款产品服务着两个毫不相干的任务：黏稠、单手可饮的奶昔服务无聊的早间通勤者；稀薄、能快速喝完的奶昔服务愧疚的下午父亲。若把两种需求取平均值设计产品，两边都不满意。
The Switching Equation
切换方程式
Adoption = (Push + Pull) − (Habit + Anxiety). The mattress buyer wanted the new mattress and hated his old one, yet stalled — not on price, but on the trivial anxiety of disposing of the old one. Removing that friction, not adding features, closed the sale.
雇用可能性 = (推力+拉力) − (习惯+焦虑)。床垫买家渴望新床垫、厌恶旧床垫，却迟迟不下单——卡点不是价格，而是「旧床垫怎么处理」这个微小焦虑。消除这个摩擦而非增加功能，才促成了成交。
Competitors Beyond the Category
跨品类的真实对手
JTBD dissolves industry boundaries: Netflix's rival is a bottle of wine or sleep, not just HBO; a small business's real competitor to Salesforce is an Excel spreadsheet. The largest competitor is often 'non-consumption' — customers tolerating the problem rather than buying anything.
JTBD打破行业壁垒：Netflix的对手是一瓶红酒或睡眠，而非仅仅HBO；对许多小企业而言，Salesforce的对手是Excel表格。最大的竞争对手常常是「非消费」——客户宁可忍受问题，也不购买任何解决方案。
Active vs. Passive Data
主动数据 vs 被动数据
CRM/ERP systems are built to harvest passive data (clicks, sales totals) that shows 'what happened' but hides context. Active data — messy, narrative accounts of struggle — can only be obtained by leaving the building and observing or interviewing customers directly.
CRM/ERP系统天生只擅长采集被动数据（点击率、销售额），它告诉你「发生了什么」，却掩盖了背景。主动数据——混乱、叙事性的挣扎描述——只能靠走出办公室、亲自观察和访谈获得。
Detailed Summary详细解读
The report opens by naming a paradox: companies have never had more customer data, yet new-product failure rates remain stubbornly high. Christensen's diagnosis is that the 'unit of analysis' is wrong — segmenting by demographics (age, income, city tier) or by product attributes (processor speed, flavor count) both describe surface traits, not the causal reason a purchase happens. A 40-year-old buying a newspaper on Tuesday versus Saturday shares identical demographics but entirely different motives. The fix is to replace 'who' and 'what' with 'why,' using the Job to Be Done — the progress a person is trying to make in a given circumstance — as the analytic unit.
Every job has three intertwined dimensions — functional, social, emotional — and ignoring the latter two is the most common cause of innovation failure. A family SUV purchase is nominally about seating capacity and fuel economy (functional), but is equally driven by wanting to look like a stable, prosperous parent to relatives (social) and to feel like a responsible caregiver (emotional). When functional and emotional needs conflict, the report argues emotional usually wins — a claim borrowed directly from the book's framing rather than independently tested here.
The milkshake case anchors the entire framework: after lab surveys asking customers 'what would make you buy more milkshakes?' failed to move sales, researchers instead logged 18 hours of in-store behavior. Discovering that 40% of shakes sold before 8:30am, to solo commuters who took them straight to their cars, led to interviews revealing a 'keep-my-hand-busy, stay full till 10am, don't stain my clothes' job that beat bananas, donuts, and bagels on every axis. A separate afternoon spike — fathers buying for children — needed a thinner, faster-drinking shake, proving that averaging the two use cases into one product satisfies neither.
The report reframes competition and data strategy around this lens. Netflix's real rivals aren't HBO or Amazon Prime but a glass of wine, a board game, or sleep — whatever else could satisfy the same 'unwind after a long day' job — and the single biggest competitor across categories is often 'non-consumption,' where customers simply tolerate the problem. On data, passive metrics (clicks, sales totals) reveal correlation but hide mechanism; the report insists only active, narrative 'thick data' gathered by leaving the building explains causation, a methodological stance that is asserted rather than empirically benchmarked against data-driven alternatives.
Execution is formalized through the 'Forces of Progress' equation: switching likelihood equals (push + pull) minus (habit + anxiety). The mattress interview is the key illustration — a buyer disliked his old mattress and loved the new one, yet stalled for reasons unrelated to price: anxiety over how to dispose of the old mattress. Once the retailer offered free haul-away, the sale closed immediately without a discount, showing that the cheapest lever for growth is often removing a small, specific friction rather than adding product features or cutting price.
Taken together, the report positions JTBD as a causal alternative to correlation-driven segmentation, but its evidentiary base is almost entirely the same handful of Christensen case studies (milkshake, mattress, Southern New Hampshire University) repeated across sections rather than independent replication — a limitation worth flagging even as the framework's diagnostic value for product teams remains genuinely high.
报告开篇点出一个悖论：企业掌握的客户数据前所未有地丰富，但新产品失败率依然居高不下。克里斯坦森的诊断是「分析单位」选错了——按人口统计（年龄、收入、城市线级）或产品属性（处理器速度、口味数量）切分市场，描述的都是表面特征，而非购买发生的真正原因。同一个40岁的人周二和周六买报纸，人口特征完全相同，但动机可能截然不同。解法是用「待办任务」——一个人在特定情境下试图取得的进步——取代「谁」和「什么」，作为新的分析单位。
每个任务都包含三个交织的维度——功能、社会、情感——忽略后两者是创新失败最常见的原因。购买家用SUV表面上是为了座位数和省油（功能），但同样受「想在亲戚面前显得稳重富足」（社会）和「想感觉自己是负责任的家长」（情感）驱动。报告指出，当功能与情感冲突时，情感往往胜出——这一断言直接沿用了原书的框架，报告本身并未独立给出验证数据。
奶昔案例是整套框架的基石：实验室调研问客户「怎么做才能让你买更多奶昔」并未拉动销量，研究者转而记录了18小时的门店真实行为数据。他们发现40%的奶昔在早8:30前售出，买家多为独自驾车通勤者，直接带走上车；随后的访谈揭示了一个「让手有事做、撑到10点不饿、不能弄脏衣服」的任务，奶昔在这个任务上完胜香蕉、甜甜圈和贝果。而下午另一波由父亲带孩子购买的高峰，则需要更稀薄、能快速喝完的奶昔——证明把两种使用场景的需求取平均值设计产品，注定两头不讨好。
报告以此视角重新定义竞争与数据策略。Netflix真正的对手不是HBO或Amazon Prime，而是一杯红酒、一局棋盘游戏甚至睡眠——任何能满足「结束漫长一天后放松」这一任务的替代品——而跨品类最大的竞争对手往往是「非消费」，即客户干脆选择忍受问题。在数据层面，被动指标（点击率、销售额）只能揭示相关性而掩盖机制；报告坚持只有走出办公室获取的、叙事性的「厚数据」才能解释因果，但这一方法论立场是断言式的，并未与数据驱动方案做实证对比。
执行层面通过「进步的四种力量」方程式形式化：切换可能性 = (推力+拉力) − (习惯+焦虑)。床垫访谈是关键例证——买家讨厌旧床垫、喜欢新床垫，却迟迟不下单，原因与价格无关，而是「旧床垫怎么处理」这一具体焦虑。商家一旦提供免费回收旧床垫的服务，客户立即下单，无需任何折扣——说明促成增长最廉价的杠杆，常常是消除某个具体而微小的摩擦，而非增加产品功能或降价。
总体而言，报告将JTBD定位为对抗相关性驱动细分的因果替代方案，但其论证证据几乎全部依赖同一批克里斯坦森案例（奶昔、床垫、南新罕布什尔大学）在各章节间反复出现，而非独立的复现验证——这是一个值得指出的局限，尽管该框架对产品团队的诊断价值确实很高。
FAQ常见问答
Isn't JTBD just a rebrand of user needs analysis?JTBD不就是「用户需求分析」换了个说法吗？
No — the distinction is the unit of analysis. Needs analysis still segments by who the user is; JTBD segments by the circumstance and progress sought, so the same person can belong to different job segments hour to hour.
不一样，核心区别在分析单位。需求分析仍以「用户是谁」切分市场；JTBD以「情境+寻求的进步」切分，同一个人在不同时段可能属于完全不同的任务细分市场。
Does removing anxiety always beat adding features?消除焦虑是否永远优于增加功能？
Not universally — the report only shows this in cases where habit/anxiety, not push/pull, was the binding constraint. When customers lack any dissatisfaction (no push), no amount of anxiety-removal will trigger a switch.
并非绝对——报告展示的只是「习惯/焦虑」而非「推力/拉力」是主要卡点的场景。若客户对现状毫无不满（缺乏推力），再怎么消除焦虑也无法促成切换。
How do you operationalize 'circumstance' for market segmentation?「情境」这个概念在实际市场细分中如何落地？
The report gestures at structured JTBD interviews and job specification documents but doesn't give a repeatable quantitative method — this is the weakest, most abstract part of the execution module.
报告提到了结构化JTBD访谈和任务规格说明书，但没有给出可重复的量化方法——这是执行模块中最薄弱、最抽象的部分。
Is the milkshake study still valid evidence today?奶昔案例作为证据如今是否依然站得住脚？
It's a single-restaurant, decades-old anecdote never independently replicated at scale; it illustrates the JTBD mechanism vividly but shouldn't be treated as statistically generalizable proof.
这是一家餐厅、几十年前的案例，从未被大规模独立复现；它生动地展示了JTBD机制，但不应被当作具有统计普适性的证据。
How does JTBD handle B2B purchases with multiple stakeholders?面对多方决策者的B2B采购，JTBD如何应对？
The report notes social-dimension weight rises in B2B contexts but doesn't detail how to reconcile competing jobs held by different stakeholders in the same buying committee.
报告提到B2B场景下社会维度权重上升，但没有详细说明如何调和同一采购委员会内不同决策者持有的相互冲突的任务。
In-depth Analysis · Pros & Cons深入解读 · 优缺点
This report deconstructs Christensen's 'Competing Against Luck' into a systematic Jobs-to-Be-Done (JTBD) framework, moving from the theory's foundational logic through its counter-intuitive conflicts with conventional marketing to a concrete execution toolkit. It reorganizes scattered case studies (the milkshake, the mattress interview) into a causal model explaining why customers 'hire' and 'fire' products.
本报告将克里斯坦森《与运气竞争》拆解为一套系统化的「待办任务」（JTBD）框架，从理论基石出发，穿过它与传统营销直觉的正面冲突，最终落到可执行的工具箱。它把书中散落的案例（奶昔、床垫访谈）重新组织成一套解释客户为何「雇用」与「解雇」产品的因果模型。
- Vivid, teachable case anchor生动且可教学的案例锚点The milkshake dilemma compresses an abstract causal theory into a concrete, memorable 18-hour observation study that any reader can retell and apply.奶昔困境把一个抽象的因果理论压缩成一个具体、易记的18小时观察研究，任何读者都能复述并直接套用。
- Formalized adoption mechanics将购买动态公式化The push/pull/habit/anxiety equation gives practitioners an actionable diagnostic checklist instead of a vague 'understand your customer' platitude.推力/拉力/习惯/焦虑方程式为从业者提供了可操作的诊断清单，而非「理解你的客户」这类空泛口号。
- Reframes competition usefully对竞争的重新框定具有实用价值Naming non-consumption and cross-category rivals (Netflix vs. wine) forces teams to look beyond their own industry for the real threat to adoption.点出「非消费」和跨品类对手（Netflix对红酒），迫使团队跳出自己所在行业去审视真正威胁采纳率的对手。
- Distinguishes data types clearly清晰区分数据类型The active/passive data split gives a concrete critique of CRM-only decision-making, explaining why executives drift from ground truth.主动/被动数据的划分对「仅靠CRM决策」给出了具体批判，解释了高管为何逐渐远离一线真相。
- Thin, repeated evidence base证据基础单薄且反复使用Nearly every claim traces back to the same three or four Christensen case studies; there's no independent dataset or replication across industries in this report.几乎所有论断都来自同样的三四个克里斯坦森案例；报告中没有独立数据集或跨行业的复现验证。
- No falsification path缺乏可证伪路径The theory is presented almost entirely through confirming anecdotes; the report doesn't discuss cases where JTBD-guided products still failed, which would test the framework's limits.理论几乎全靠正面案例支撑；报告未讨论按JTBD设计后仍然失败的产品案例，无法检验该框架的边界。
- Execution tools remain qualitative执行工具仍停留在定性层面The 'job specification' and interview toolkit are described conceptually but lack a repeatable, measurable process for teams without deep JTBD training.「任务规格说明书」和访谈工具仅停留在概念层面，缺乏一套没有深厚JTBD训练背景的团队也能照做的可量化流程。
- Underplays scale and cost trade-offs低估规模与成本的权衡Solutions like free mattress haul-away or milkshake redesigns are framed as cheap wins without discussing the operational cost of running two product variants per job segment.免费回收旧床垫、针对不同任务重新设计奶昔等方案被描绘成低成本的胜利，却未讨论为每个任务细分市场维护不同产品版本的运营成本。
A genuinely useful synthesis for product managers and marketers who need a causal alternative to demographic segmentation, best read as a mental model to apply rather than a rigorously validated scientific theory — treat the case studies as illustrative, not statistically representative, and pair the JTBD interview method with your own falsification tests before betting a roadmap on it.
对于需要一套因果替代方案来取代人口统计细分的产品经理和营销人员，这是一份真正有用的综合梳理，但更应把它当作一个可拿来即用的思维模型，而非经过严格验证的科学理论——案例应被视为启发性说明而非统计代表性证据，在把产品路线图押注于此之前，建议自行设计证伪测试来配合JTBD访谈方法。
Original Text原文
The English text on this side is an AI translation provided for convenience; the authoritative version is the source in the other language.
Abstract
This report aims to thoroughly deconstruct and reorganize Clayton Christensen's book Competing Against Luck: The Story of Innovation and Customer Choice. The report adopts the core idea of the "Feynman Technique" — using accessible analogies and deep logical reasoning to transform complex business theory into intuitive cognitive models. The whole piece follows a "cognitive construction" logical sequence, divided into three core modules: Skeleton and Map (theoretical foundations and core definitions), Conflict and Perspective (counterintuitive insights and dispelling misconceptions), and Insight and Transfer (execution frameworks and action guides).
This report is not merely a summary of the book's content, but a comprehensive expansion of the "Jobs to Be Done" (JTBD) theoretical system. By integrating a large number of research excerpts and cases (such as the milkshake experiment, mattress-purchase interviews, the Southern New Hampshire University case, etc.), this report attempts to reveal the causal mechanisms hidden behind consumer purchasing behavior, helping innovators break free from the random gamble of "striking it lucky" and enter the realm of predictable, replicable scientific innovation. At roughly 15,000 words, it aims to provide professional readers with a detailed, rigorous, and highly actionable in-depth research document.
Module One: Skeleton and Map — Reconstructing the Underlying Logic of Innovation
In the vast ocean of the business world, innovation is often seen as a mysterious process akin to alchemy. Companies invest heavily in R&D, market research, and data analysis, yet the success rate of new products remains astonishingly low. The core argument Clayton Christensen puts forward in Competing Against Luck is this: such failure is not due to a lack of effort or intelligence, but because the "map" we are using is wrong. This module will draw a brand-new cognitive map and establish the skeleton of the "Jobs to Be Done" theory.
1.1 The Innovation Maze: Abundant Data, Impoverished Insight
Before delving into the theory, we must first examine the core paradox of today's business environment: because of the proliferation of big data, we seem to know more about customers than ever before, yet the success rate of innovation has not risen accordingly.
1.1.1 The Wrong Unit of Analysis
The core error in traditional marketing and product development lies in the choice of "unit of analysis." The vast majority of companies rely on two main dimensions:
Based on customer attributes: segmenting consumers by demographic traits, such as "ages 18-35, male, holds a bachelor's degree, lives in a tier-1 city."
Based on product attributes: focusing on the product's functional parameters, such as "faster processor, sharper screen, more flavors."
Research shows that neither dimension can explain the underlying reason a purchase occurs. As Christensen put it, a 40-year-old man buying a newspaper on a Tuesday and buying one on a Saturday may share identical demographic traits, yet the motivations behind the two purchases could be completely different. Correlation is not causation. Knowing "who" bought the product, or "what" they bought, does not reveal "why" they bought it.
1.1.2 The Definition of "Job to Be Done"
To capture causality, we need a new unit of analysis: the Job to Be Done.
Within this theoretical framework, the core metaphor is "hiring" and "firing." Customers do not simply "buy" products or services; rather, because some problem or needed progress has arisen in their lives, they "hire" a product into their lives to get that job done. If the product does the job well, the customer will hire it again; if it performs poorly, the customer will "fire" it and look for a new replacement.
Core definition:
A "job" is the progress a person is trying to make in a given circumstance.
This definition contains three crucial keywords:
Progress: A job is not a static state but a movement from the current situation to a desired one. It implies change, growth, or problem-solving.
Circumstance: A job always occurs within its specific context. Circumstance is the core element that defines a job, more important than customer attributes.
Seeking: This is an active process, one that involves intention and struggle.
1.2 The Anatomy of a Job: The Three-Dimensional Structure of Functional, Social, and Emotional
A common misconception is that a "job" refers only to the functional use of a product (such as "drilling a hole" or "cleaning the floor"). In reality, a genuine "Job to Be Done" is an extremely complex structure encompassing three interwoven dimensions. If innovators focus only on the functional dimension while ignoring the social and emotional dimensions, the product will often fail.
1.2.1 Detailed Analysis of the Three Dimensions
| Dimension | Definition | Typical Inner Monologue | Weight Analysis |
| :---- | :---- | :---- | :---- |
| Functional | The specific, practical task the customer wants accomplished. | "I need this software to process Excel data quickly." "I need this car to seat 7 people." | This is the product's baseline, but often not the decisive point of differentiation. |
| Social | The image or recognition the customer wants to project in the eyes of others. | "If I use this brand of phone, my colleagues will think I'm tech-savvy." "As a parent, I need to buy this for my child, or the neighbors will see me as irresponsible." | In B2B procurement or luxury consumption, the social dimension often dominates. |
| Emotional | The inner feeling or psychological state the customer hopes to experience while using the product. | "Wearing this suit makes me feel confident and secure." "After handling this investment, I want to feel at ease, not anxious." | When function and emotion conflict, emotion tends to win out. |
1.2.2 The Dynamic Balance of the Dimensions
Across different jobs, the weighting of these three dimensions shifts dynamically.
Case: Buying a Family SUV
Functional job: Safely drive children to and from school, carry camping gear.
Social job: Show relatives and friends that the family's life is stable and well-off.
Emotional job: Feel like a responsible, caring father/mother.
In this case, if the marketing emphasizes only "spaciousness" and "fuel efficiency" (functional) while ignoring the "sense of solidity" in the vehicle's exterior design (emotional/social), it may fail to trigger the core purchase decision.
1.3 A Core Cognitive Anchor: The Milkshake Dilemma
To make the abstract theory concrete, this report will deeply dissect the cognitive map the book presents through the "milkshake" case. This case is a cornerstone for understanding JTBD theory, because it perfectly demonstrates how to shift from the traditional "product/user perspective" to the "job perspective."
1.3.1 The Failure of the Traditional Perspective
A fast-food giant tried to boost milkshake sales. They followed the standard marketing process:
Market segmentation: Identify the consumer group that buys milkshakes most often (e.g., males aged 18-35).
User research: Bring these consumers into a lab and ask: "What could we do to get you to buy more milkshakes? Make it cheaper? Thicker? More chocolatey?"
Product iteration: Based on the feedback, launch a thicker, sweeter milkshake with richer flavor.
Result: Sales showed no improvement at all.
This failure reveals the blind spot of the traditional approach: customers themselves don't clearly know why they buy milkshakes. Their feedback is based on an "idealized self" or a "general impression of milkshakes," not on the actual purchase context.
1.3.2 Observation from the Job Perspective
Rather than asking customers directly, Christensen's team chose to observe inside the restaurants. They logged 18 hours of sales data, tracking the following variables:
Who bought the milkshake?
What time did they buy it?
Were they alone or with someone?
Did they drink it in the restaurant or take it to go?
What other food did they buy?
The observations revealed a striking pattern: 40% of milkshakes were sold before 8:30 in the morning. These customers were typically alone, took the milkshake straight to their car, and bought almost nothing else.
1.3.3 In-Depth Interviews: Uncovering the "Morning Commute Job"
The team then intercepted these customers in the morning and asked one core question: "When you come here to buy this milkshake, what are you actually trying to use it to replace?" (In other words: if you hadn't bought a milkshake today, what would you have bought?)
This led to the identification of the first specific job — the morning commute job.
Circumstance: A long, boring drive to work.
Struggle:
I'm bored and need something to keep one hand busy.
I'm not hungry right now, but I know I'll be hungry by 10 a.m., so I need something to tide me over.
I'm wearing work clothes and can't get them dirty.
I only have one hand free (the other is on the steering wheel).
Alternatives (competitors):
Banana: Eaten too quickly (gone in 3 minutes), doesn't solve the boredom of a 20-minute drive; and turns black if not eaten right away.
Doughnut: Leaves icing on the hands, dirtying the steering wheel and clothes; often leaves a feeling of guilt afterward.
Bagel: Too dry, needs cream cheese (can't be spread one-handed), scatters crumbs all over the car.
Snickers bar: Feels like eating candy for breakfast — guilt-inducing.
Why the milkshake won:
It's viscous — sipping it through a thin straw takes about 20 minutes, perfectly matching the length of the commute.
It fits neatly in the car's cup holder.
It's filling enough to last until noon.
It's clean and won't dirty the clothes.
Conclusion: In this circumstance, the milkshake gets "hired" because it does a better job than a banana or a doughnut at relieving boredom, staving off hunger, and keeping things tidy.
Action recommendation: To win at this job, fast-food chains should make the milkshake even thicker (extending drinking time), even add fruit chunks (adding a bit of surprise during the boring drive), and set up a fast lane so commuters can buy and go quickly.
1.3.4 A Contrasting Perspective: The "Afternoon Parent-Child Job"
However, the observations also revealed a second purchase peak in the afternoon. This time, it was typically fathers accompanied by their children.
Circumstance: After school or on weekend afternoons.
Job: "Comfort my child, and in doing so feel like a good father."
Struggle: The father has said "no" to his child all day (no buying toys, no running around), and he needs a moment to say "yes," to ease his own guilt and build a bit of closeness in a short amount of time.
The milkshake's failure: The thick, morning-style milkshake completely fails here. The child can't suck it up, and the father waits impatiently. What should be a warm "reward moment" turns into a "long wait," and the father often ends up drinking the leftover half and leaving in frustration.
Action recommendation: For this job, the milkshake should be thinner and half the size, so the child can finish it quickly and everyone is happy.
Core insight: The same product (the milkshake), in different circumstances (morning vs. afternoon), is hired to do completely different jobs. If a company tries to develop a milkshake that "everyone likes" (by averaging), it ends up neither thick enough to satisfy the morning commuters nor thin enough to satisfy the afternoon children, and ultimately loses both markets.
1.4 The Nature of "Progress": A Verb, Not a Noun
In building the cognitive map of JTBD, it must be emphasized that "progress" is a dynamic process.
Progress origin: A state of dissatisfaction or struggle (e.g., a boring commute, a guilty father).
Progress sought: The desired future state (e.g., a fulfilling and filling morning, a harmonious father-child moment).
Progress as a verb: The process of hiring the product.
This requires us to view the product as a vehicle for delivering a service. The product itself is lifeless; value is created only when it is woven into the customer's life flow, helping the customer clear the obstacles between the "starting point" and the "end point."
Module Two: Conflict and Perspective — Counterintuitive Business Truths
Having established the basic skeleton of JTBD, we must now confront the sharp conflicts between this theory and conventional business wisdom. These points of conflict are often the "blind spots" of corporate innovation, and they are also the most difficult yet most valuable part of understanding this book. This module will reveal hidden business truths through a series of binary oppositions.
2.1 Data and Truth: The Correlation Trap of Big Data
In today's business discourse, "data-driven decision-making" is treated as gospel. Yet Christensen puts forward a highly provocative view: data is often misleading, especially passive data that merely describes "correlation."
2.1.1 Attribute Correlation vs. Causal Mechanism
Big data is good at finding correlations. For example, the data might show: "People who buy baby diapers have a high probability of also buying beer."
Traditional interpretation: This is a cross-selling opportunity — put the beer and diapers next to each other.
JTBD interpretation: This does not explain the causal mechanism. Why do they buy both at the same time? Is it because caring for a baby is stressful and they need to unwind (an emotional job)? Or because a trip to the supermarket is inconvenient, so they buy everything at once (a functional job)? Without knowing "why," any marketing based purely on correlation (such as pitching premium red wine to diaper buyers) is likely to fail.
Core view:
"God did not design the world around demographics."
Customer behavior is not driven by who they are (age, gender, ethnicity), but by the circumstance they are in. A 40-year-old banker taking a client to dinner on Friday night (a business-social job) has very different needs from the same man taking his kids to breakfast on Saturday morning (a parenting job) — even though it's the same person. If a system labels him only as a "high-net-worth male" and recommends products on that basis, serious mismatches result.
2.1.2 The Fallacy of Averages
Companies are accustomed to aggregating data in search of the "average user."
In the milkshake case, if you average the morning need (thick) and the afternoon need (thin), you get a medium-thickness milkshake.
Result: Morning customers find it doesn't last long enough; afternoon customers still find it too hard to sip. Designing a product for the "average person" means designing a product that satisfies no one.
Counterintuitive conclusion: Market segmentation should not be based on the person (persona), but on the job. The same user, in different fragments of their life, belongs to entirely different "job segments."
2.2 Reframing Competition: Your Rival Isn't Your Peer
Porter's Five Forces teaches us to focus on competitors within our own industry. Coca-Cola watches Pepsi; BMW watches Mercedes. JTBD theory completely breaks down these industry walls, proposing a cross-dimensional view of competition.
2.2.1 The Category Trap
Companies tend to define competition within a product category.
Traditional view: A milkshake's competitors are ice cream and soda.
JTBD view: A milkshake's competitors are bananas, bagels, Snickers bars, boredom, and the radio (in the morning-commute job).
Case: Netflix's Real Rivals
Netflix CEO Reed Hastings famously pointed out that Netflix's competitors aren't just HBO or Amazon Prime — they're a bottle of wine, a board game, even sleep.
If a user's job is "unwind my brain after a long day," then having a drink or going to sleep are direct substitutes for Netflix.
If a user's job is "kill 10 minutes while waiting for a friend," then Netflix's rival is TikTok or Instagram.
2.2.2 Competing Against Non-consumption
Often, the biggest competitor isn't another company's product — it's doing nothing at all (non-consumption).
In these situations, customers choose to put up with the problem because every existing solution is too complicated, too expensive, or too much of a hassle.
Insight: Products that can compete against — and beat — "non-consumption" often open up enormous blue oceans. For many small businesses, for instance, Salesforce's competitor isn't Oracle, but "a spreadsheet" or "sticky notes."
2.3 The Feature Trap: Overshooting and Surface Growth
Product development is plagued by a pervasive, linear "more is better" mindset.
2.3.1 Overshooting
"Overshooting" happens when a company fixates on performance metrics — pixels, horsepower, number of blades — while losing sight of the underlying job.
Customers are willing to pay to get the job done, but not willing to pay for performance beyond what the job requires.
Counterintuitive point: Adding features can sometimes make a product less competitive.
In the "afternoon milkshake with the kids" case, making the shake thicker (a performance boost) actually caused the job to fail — the child couldn't finish it, and the father grew anxious. Here, the "better" product got fired.
2.3.2 Surface Growth vs. Deep Growth
Surface Growth: Trying to sell existing customers more of what they don't need, or temporarily boosting sales through promotions. This kind of growth is unsustainable because it doesn't address any new job.
Deep Growth: Discovering unmet jobs in customers' lives, or doing an existing job better. This kind of growth builds a durable relationship, because the product becomes an indispensable piece of the customer's life puzzle.
2.4 Active Data vs. Passive Data
Christensen distinguishes between two types of data:
Passive Data: This data is a trace of past behavior — easy to quantify and collect (click-through rates, sales figures). It tells you "what happened," but it obscures the context.
Active Data: This data is a qualitative account of a customer's struggle — messy and narrative. It can only be obtained through observation and conversation.
Conflict: A company's management systems (ERP, CRM) are designed to process passive data. This systemic bias pushes executives further and further away from the "scene of the truth," leaving them dependent on reports that have been filtered and aggregated many times over.
Recommendation: Innovators must get out of the building and gather "thick data" — stories rich with emotion, context, and human complexity.
Module Three: Insight and Migration — From Theory to Precision Execution
Once you understand the skeleton and the conflict, the biggest challenge is execution. How do you turn the abstract concept of "job" into actionable instructions? This module provides a precision toolkit — the "Four Forces of Progress," the "Job Spec," and an interview technique guide — to help readers translate understanding into action.
3.1 The Equation of Change: The Four Forces of Progress
When a customer decides to switch from one solution to another (say, from "tracking finances in Excel" to "using QuickBooks"), a real tug-of-war of forces is playing out in their mind. This isn't a random choice — it can be explained by a model borrowed from physics.
The Switching Equation:
$$\text{Likelihood of switching} = (\text{Push} + \text{Pull}) - (\text{Habit} + \text{Anxiety})$$
For a purchase (a hire) to happen, the forces on the left must outweigh the resistance on the right.
3.1.1 Sources of Momentum
Push:
Definition: The dissatisfaction, pain, or struggle of the status quo. This is the "reason things must change."
Manifestation: "My mattress is so old my back hurts," "This car keeps breaking down and repairs cost too much."
Strategy: Marketing shouldn't only paint a rosy future — it must first amplify the pain of the current situation, so the customer feels "I can't go on like this." Without push, there's no demand.
Pull:
Definition: The appealing vision offered by the new solution. This is "what I want to become."
Manifestation: "If I buy that new mattress, I'll wake up energized every day," "This new car will make me look successful."
Strategy: Paint a picture of the new life the product enables, rather than piling up feature specs.
3.1.2 Sources of Resistance
Habit:
Definition: The inertia of the status quo. "Sure, it's not perfect, but I've already adapted to it."
Manifestation: "I hate Excel, but I know the shortcuts with my eyes closed," "Switching to a new system is such a hassle — I'd have to migrate all my data."
Strategy: Lower the switching cost. Acknowledge the comfort of the status quo, and offer a seamless transition path (like one-click data import).
Anxiety:
Definition: Uncertainty and fear about the new solution.
Types:
Choice anxiety: "What if I buy the wrong one?"
Usage anxiety: "What if I can't figure out how to use it?"
Manifestation: "This looks great, but what if it's not compatible with my old computer?"
Strategy: De-risk the purchase. Offer money-back guarantees, free trials, customer testimonials.
3.1.3 Case: The Psychological Tug-of-War of a Mattress Buyer
21
In a classic JTBD interview, the subject kept putting off buying a new mattress, even though his old one already gave him back pain (push) and he loved how comfortable the new one felt (pull).
The blocker (anxiety): It wasn't the price — it was the seemingly trivial question of "what do I do with the old mattress?" that became a huge source of anxiety. He kept thinking: "I don't have a truck to haul it away. Will I get fined if I leave it on the curb? And it'll take up space if I put it in the basement."
The solution: The retailer didn't just sell mattresses — it also offered a service to haul away and dispose of the old mattress for free.
The result: This service eliminated the key anxiety-driven resistance, and the customer placed the order immediately — even without a price discount.
Insight: Sometimes the cheapest way to drive growth isn't adding product features (pull) — it's removing some small anxiety or habit-based resistance.
3.2 The Big Hire vs. the Little Hire
The relationship between a customer and a product unfolds in two stages, and understanding this distinction is critical to retention.
3.2.1 The Big Hire
This is the moment the customer purchases the product. At this point, the "pull" generated by marketing and the "push" of the status quo have overcome the resistance. The transaction is complete, money for goods.
Focus: Sales conversion, marketing messaging, ease of purchase.
3.2.2 The Little Hire
This is the moment the customer actually uses the product to get the job done. It begins the instant of purchase and repeats with every subsequent use.
Key point: If the "little hire" is full of friction (IKEA furniture too hard to assemble, software interface too complicated, a milkshake too thick to sip), the next "big hire" simply won't happen.
Airbnb case:
Big hire: Booking a room on the website.
Little hire: Dragging your suitcase to the door of the listing. If you can't find the key at that moment, or the room smells bad, or the host didn't provide the toiletries they promised — the little hire has failed.
Airbnb realized that the "arrival moment" is the critical instant of the little hire. They didn't just optimize the website booking flow (big hire) — they also optimized the "walking through the door" experience (little hire) through host education, check-in guides, and more.
Action item: Map out the customer's job timeline. Don't just focus on the point of purchase — pay attention to every "micro-moment" throughout the usage process. Make sure the product delivers on its promise at every single "little hire."
3.3 The Job Spec
Once a job has been clearly defined, how do you communicate the requirements to the R&D team? A traditional "product requirements document" (PRD) tends to just list features. JTBD recommends using a "Job Spec" instead, which includes the following elements:
Functional criteria: The hard requirements the product must meet (e.g., the milkshake must last through a 20-minute drink).
Emotional criteria: The customer's psychological bottom line during use (e.g., the father must not feel rejected by his child).
Social criteria: The signaling role the product plays in a social context.
Trade-offs: What is the customer willing to sacrifice to get the job done? (e.g., morning commuters are willing to sacrifice flavor variety in exchange for convenience and a drink that lasts.)
Obstacles: The specific resistances that must be removed.
3.3.1 Case: Southern New Hampshire University's (SNHU) Online Education
SNHU didn't try to compete with Harvard (Harvard's job is "elite credentialing" and "social networking"). SNHU targeted a different job: "help working adults in their 30s quickly earn a degree to advance their career, without disrupting their lives."
SNHU's Job Spec:
Function: Courses must be fully online, with flexible scheduling.
Emotion/Anxiety: Adults returning to school are filled with fear ("Can I actually do this? Do I even have the time?"). They need extremely fast feedback to sustain their motivation.
Concrete execution:
Traditional universities' financial-aid response time was 24 hours or longer.
SNHU cut that down to 10 minutes.
When a prospective student filled out the form online at night (their only free time), if they didn't hear back until the next day, the impulse to "make a change" (push) could easily get drowned out by the inertia of daily life (habit).
Calling back within 10 minutes caught the customer at the peak moment of "push," dramatically boosting conversion.
Result: This Job-Spec-driven adjustment helped SNHU achieve remarkable growth.
3.4 The Purpose Brand: A Moat Against Competition
When a brand becomes perfectly bound to a specific "job to be done," it becomes a purpose brand.
Definition: The brand name becomes synonymous with the job itself.
Examples:
IKEA: "I need to furnish my whole apartment today, cheaply."
FedEx: "This package absolutely must arrive tomorrow, without fail."
Uber: "I need to get from A to B right now, without cash, without waiting."
Value: Purpose brands occupy a mental shortcut in the customer's mind. When the job arises, the customer triggers "System 1" (intuitive thinking) and hires that brand directly, without even considering competitors. This lets the brand command a premium and resist low-price competition.
3.5 Interviewing Like You're Shooting a Documentary: A Practical Guide to Uncovering the Job
Finally, how do you use interviews to surface these deep, underlying jobs? Christensen recommends interview techniques similar to criminal investigation or documentary filmmaking, to reconstruct the timeline of the purchase.
3.5.1 Timeline Reconstruction
Don't ask "what do you want" — ask "what happened."
| Stage | Core Question | Purpose |
| :---- | :---- | :---- |
| First Thought | "When was the first time the thought 'I need to buy something new' crossed your mind? What were you doing at that moment?" | Capture the initial push. |
| Passive Looking | "After that, did you start noticing related information, even without taking action yet?" | Gauge how strong the habit resistance was. |
| Trigger Event | "What happened later that made you decide 'today's the day, I have to buy it'?" (e.g., the old mattress finally gave out, or the mother-in-law was arriving tomorrow) | Identify the key push that tipped the balance. |
| Active Looking | "What other options did you consider? Why did you rule them out?" | Understand the competitors (including non-consumption) and the anxiety involved. |
| The Big Hire | "At the exact moment you swiped your card, what were you still worried about?" | Surface the last remaining anxiety-based obstacle. |
| Consumption | "Was using it the way you imagined it would be?" | Verify whether the little hire succeeded or failed. |
3.5.2 Techniques for Surfacing Emotional Clues
Look for anomalies: "You said you didn't care about the price — so why did you look at the cheaper one and then put it back down?"
Scene reconstruction: "Tell me what the weather was like that morning. Were you alone?" (Details help jog the memory.)
Alternatives: "If you hadn't bought this, what would you have done instead?" (This surfaces the true competitors.)
Conclusion: From Luck to Causality
The core value of Competing Against Luck isn't a specific marketing trick — it's a shift to a higher plane of understanding. It tells us that business success doesn't have to depend on "high-odds gambling." By shifting the unit of analysis from "the person" and "the product" to "the job to be done," we can see clearly the causal mechanisms hidden beneath the chaotic surface of the market.
Once you put on the JTBD lens, the world looks different:
You no longer see "a 35-year-old male user" — you see "a father trying to relieve boredom on his morning commute."
You no longer see "a competitor's product specs" — you see "if he doesn't hire me, he'll go to sleep instead."
You no longer pile on features blindly — you start carefully designing away every tiny moment of anxiety.
As Christensen put it: "If we can observe the world through the correct lens, innovation is no longer a matter of luck but a science that can be predicted and mastered." This is the greatest gift this book leaves us — a key to unlocking the causal laws of innovation.
Works cited
The 3 types of customer job — Steve Forbes - Innovation | Product Development | Strategy, accessed January 19, 2026, https://www.steveforbes.com.au/blog/2019/8/13/the-3-types-of-customer-job
Jobs to Be Done Framework: The Product Manager's Guide to Building Products Customers Actually Want - Kaizenko, accessed January 19, 2026, https://www.kaizenko.com/jobs-to-be-done-framework-the-product-managers-guide-to-building-products-customers-actually-want/
accessed January 19, 2026, https://www.christenseninstitute.org/theory/jobs-to-be-done/#:~:text=We%20call%20these%20Jobs%20because,their%20lives%20to%20make%20progress.
Jobs to Be Done Theory - Christensen Institute, accessed January 19, 2026, https://www.christenseninstitute.org/theory/jobs-to-be-done/
Competing Against Luck - Clayton M. Christensen, Taddy Hall, Karen Dillon, David Duncan, accessed January 19, 2026, https://manassaloi.com/booksummaries/2017/07/22/competing-against-luck-christensen.html
Know the Two — Very — Different Interpretations of Jobs to be Done | by Alan Klement, accessed January 19, 2026, https://jtbd.info/know-the-two-very-different-interpretations-of-jobs-to-be-done-5a18b748bd89
Clayton Christensen, Jobs-to-be-Done & Competing Against Luck, Part 1 - Thrv, accessed January 19, 2026, https://www.thrv.com/blog/clayton-christensen-jobs-to-be-done
Clay Christensen's Jobs to Be Done framework: How to build better products - Fullstory, accessed January 19, 2026, https://www.fullstory.com/blog/clayton-christensen-jobs-to-be-done-framework-product-development/
Milkshakes in the Morning - The JTBD Story - The Re-Wired Group, accessed January 19, 2026, https://therewiredgroup.com/case-studies/milkshakes/
'Hire' this article about milkshakes if you're struggling to understand customer needs, accessed January 19, 2026, https://uxdesign.cc/hire-this-article-if-you-re-struggling-to-understand-your-customer-needs-3963eff273f8
Book Summary — Competing Against Luck | by Michael Batko | MBReads | Medium, accessed January 19, 2026, https://medium.com/mbreads/competing-against-luck-379fe4b9268a
Case Studies: Milk-Shake - The Triz Journal, accessed January 19, 2026, https://the-trizjournal.com/case-studies-milk-shake/
Understanding Progress, accessed January 19, 2026, https://theprogresseconomy.com/understanding-progress/
Competing Against Luck - Product Management Book Summaries, accessed January 19, 2026, https://andrewclark.co.uk/all-media/competing-against-luck
DEMAND CREATION - AWS, accessed January 19, 2026, https://innodynmedia.s3.amazonaws.com/WSU/DC+Chapters+1-2.pdf
The Ultimate Guide to Jobs To Be Done Theory - Viima, accessed January 19, 2026, https://www.viima.com/blog/jobs-to-be-done
[Pt. 4] The Struggle and the Opportunity! | by Andrea F Hill | Frameplay | Medium, accessed January 19, 2026, https://medium.com/frameplay/pt-4-the-struggle-and-the-opportunity-c67a611db52e
How habits and anxieties keep people from using your product - Adam Amran, accessed January 19, 2026, https://www.amran.cz/how-habits-and-anxieties-keep-people-from-using-your-product/
Uncovering the Jobs That Cause Customers to Hire Products and Services | by Andrej Balaz, accessed January 19, 2026, https://jtbd.info/uncovering-the-jobs-that-customers-hire-products-and-services-to-do-834269006f50
The Forces of Progress. Forces that oppose each other —… | by Alan Klement | Jobs to be Done, accessed January 19, 2026, https://jtbd.info/the-forces-of-progress-4408bf995153
Can an Innovation Get You Into Heaven? Bob Moesta and Brian Walker talk Jobs-to-be-Done, accessed January 19, 2026, https://jobstobedone.org/news/brand-labs-bob-moesta/
The Jobs-to-be-Done Mattress Interview (as seen in Competing Against Luck), accessed January 19, 2026, https://jobstobedone.org/radio/the-mattress-interview-part-one/
Competing Against Luck review - Matt Bjornson, accessed January 19, 2026, https://bjornson.co/2017/09/12/competing-against-luck/
The "Jobs to Be Done" Theory of Innovation - Strategy+business, accessed January 19, 2026, https://www.strategy-business.com/article/The-Jobs-to-Be-Done-Theory-of-Innovation
A book review of Competing Against Luck by Josh Wayne, accessed January 19, 2026, https://joshwayne.com/books/competing-against-luck/
Competing Against Luck by Clayton Christensen (& others) – My Four Lessons and Takeaways | First Friday Book Synopsis, accessed January 19, 2026, https://www.15minutebusinessbooks.com/blog/2016/11/09/competing-against-luck-by-clayton-christensen-others-my-four-lessons-and-takeaways/
Jobs to be Done 101: Your Interviewing Style Primer - Dscout, accessed January 19, 2026, https://dscout.com/people-nerds/the-jobs-to-be-done-interviewing-style-understanding-who-users-are-trying-to-become
How to Interview for JTBD. Here is how we do JTBD interviews at… | by Jess Telford | cete, accessed January 19, 2026, https://medium.com/cete/how-to-interview-for-jtbd-8a4449003667
How to do a Jobs To Be Done Interview - Jason Evanish, accessed January 19, 2026, https://jasonevanish.com/2014/04/23/how-to-do-a-jobs-to-be-done-interview/
摘要
本报告旨在对克莱顿·克里斯坦森（Clayton Christensen）的著作《与运气竞争：创新与客户选择的故事》（Competing Against Luck: The Story of Innovation and Customer Choice）进行详尽的解构与重组。报告采用"费曼技巧"的核心理念，即通过通俗易懂的类比与深度逻辑推演，将复杂的商业理论转化为直观的认知模型。全篇遵循"认知构建"的逻辑顺序，划分为三大核心模块：骨架与地图（理论基础与核心定义）、冲突与观点（反直觉洞察与误区破除）、洞察与迁移（执行框架与行动指南）。
报告不仅仅是对书本内容的摘要，更是对"待办任务"（Jobs to Be Done, JTBD）理论体系的全面扩展。通过整合大量研究片段与案例（如奶昔实验、床垫购买访谈、南新罕布什尔大学案例等），本报告试图揭示隐藏在消费者购买行为背后的因果机制，帮助创新者从"撞大运"的随机博弈中解脱出来，进入可预测、可复制的科学创新领域。字数规模约为 15,000 字，旨在为专业读者提供一份详实、严谨且极具可操作性的深度研究文档。
第一模块：骨架与地图——重构创新的底层逻辑
在商业世界的浩瀚海洋中，创新往往被视为一种类似于炼金术的神秘过程。企业投入巨资进行研发、市场调研和数据分析，但新产品的成功率依然低得惊人。克莱顿·克里斯坦森在《与运气竞争》中提出的核心论点是：这种失败并非因为缺乏努力或智慧，而是因为我们使用的"地图"是错误的。本模块将绘制一张全新的认知地图，确立"待办任务"理论的骨架。
1.1 创新的迷局：数据的丰饶与洞察的贫瘠
在深入理论之前，必须首先审视当前商业环境中的核心悖论：由于大数据的泛滥，我们对客户的了解似乎比以往任何时候都多，但创新的成功率却并未因此提升。
1.1.1 错误的分析单位
传统市场营销和产品开发的核心错误在于其"分析单位"（Unit of Analysis）的选择。绝大多数企业依赖于两种主要的分析维度：
基于客户属性（Customer Attributes）： 将消费者细分为人口统计学特征，如"18-35岁、男性、拥有本科学历、居住在一线城市"。
基于产品属性（Product Attributes）： 关注产品的功能参数，如"更快的处理器、更清晰的屏幕、更多的口味"。
研究表明，这两种维度都无法解释购买行为发生的根本原因。正如克里斯坦森所言，一位40岁的男性在周二购买一张报纸，与他在周六购买一张报纸，虽然人口统计学特征完全一致，但其背后的动因可能截然不同。相关性（Correlation）并不等于因果性（Causality）。知道"谁"买了产品，或者他们买了"什么"，并不能揭示"为什么"购买 1。
1.1.2 "待办任务"的定义
为了捕捉因果关系，我们需要一个新的分析单位：待办任务（Job to Be Done）。
在这个理论框架下，核心隐喻是"雇用"（Hire）和"解雇"（Fire）。客户并不是单纯地"购买"产品或服务，而是因为生活中出现了某种必须解决的问题或必须取得的进步，他们才将产品"雇用"到生活中来完成这项任务。如果产品能够出色地完成任务，客户就会再次雇用它；如果产品表现不佳，客户就会将其"解雇"，并寻找新的替代品 2。
核心定义：
"任务"（Job）是指一个人在特定情境（Circumstance）下，试图取得的进步（Progress）。 5
这个定义包含三个至关重要的关键词：
进步（Progress）： 任务不是静止的状态，而是从现状向理想状态的移动。它意味着改变、成长或解决问题。
情境（Circumstance）： 任务总是发生在其特定的背景之中。情境是界定任务的核心要素，比客户属性更重要。
试图（Seeking）： 这是一个主动的过程，包含着意图和挣扎。
1.2 任务的解剖学：功能、社会与情感的三维结构
一个常见的误区是认为"任务"仅仅指代产品的功能性用途（如"钻一个孔"或"清洁地板"）。实际上，真正的"待办任务"是一个极其复杂的结构，包含三个相互交织的维度。如果创新者只关注功能维度，而忽略了社会和情感维度，往往会导致产品的失败 1。
1.2.1 三维度的详细解析
| 维度 | 定义 | 典型内心独白 | 权重分析 |
| :---- | :---- | :---- | :---- |
| 功能维度 (Functional) | 客户希望完成的具体、实用的操作任务。 | "我需要这个软件能快速处理Excel数据。" "我需要这辆车能容纳7个人。" | 这是产品的基准线，但往往不是差异化的决胜点。 |
| 社会维度 (Social) | 客户希望在他人眼中呈现的形象或获得的认可。 | "如果我用这个品牌的手机，同事们会觉得我很懂科技。" "作为父母，我需要给孩子买这个，以免被邻居视为不负责任。" | 在B2B采购或奢侈品消费中，社会维度常占据主导地位。 |
| 情感维度 (Emotional) | 客户在使用产品时希望获得的内在感受或心理状态。 | "穿上这件西装让我感到自信和安全。" "处理完这笔投资后，我希望能感到安心，不再焦虑。" | 当功能和情感发生冲突时，情感往往胜出 1。 |
1.2.2 维度的动态平衡
在不同的任务中，这三个维度的权重是动态变化的。
案例：购买一辆家用SUV
功能任务： 安全地接送孩子上下学，装载露营装备。
社会任务： 向亲戚朋友展示家庭生活的稳定与富足。
情感任务： 感觉自己是一个负责任、关爱家庭的父亲/母亲。
在此案例中，如果仅仅强调"大空间"和"省油"（功能），而忽视了车辆外观设计的"稳重感"（情感/社会），可能就无法触动购买决策的核心扳机。
1.3 核心认知的锚点：奶昔困境（The Milkshake Dilemma）
为了将抽象的理论具象化，本报告将深度拆解书中通过"奶昔"案例展示的认知地图。这个案例是理解JTBD理论的基石，因为它完美地展示了如何从传统的"产品/用户视角"切换到"任务视角" 8。
1.3.1 传统视角的失败
一家快餐巨头试图提升奶昔的销量。他们遵循了标准的市场营销流程：
细分市场： 找出最常购买奶昔的消费者群体（例如18-35岁男性）。
用户调研： 邀请这些消费者进入实验室，询问："我们要怎么做才能让你们买更多的奶昔？是要更便宜？更浓稠？还是更多巧克力味？"
产品迭代： 根据反馈，推出了更浓、更甜、口味更丰富的奶昔。
结果： 销量毫无起色。
这个失败揭示了传统方法的盲点：客户并不清楚自己为什么要买奶昔。 他们的反馈是基于"理想中的自己"或"对奶昔的一般认知"，而不是基于真实的购买情境。
1.3.2 任务视角的观察
克里斯坦森团队并未直接询问客户，而是选择在餐厅里观察。他们记录了长达18小时的销售数据，关注以下变量：
谁买了奶昔？
是什么时间买的？
他们是独自一人还是有人陪伴？
他们买了奶昔后是在店里喝还是带走？
他们还买了什么其他食物？
观察揭示了一个惊人的模式：40%的奶昔是在早上8:30之前售出的。这些顾客通常是独自一人，买了奶昔后直接上车带走，且几乎没有购买其他食物。
1.3.3 深度访谈：挖掘"早间通勤任务"
团队随后在早上拦截了这些顾客，询问了一个核心问题："当你来买这杯奶昔时，你实际上是想用它来替代什么东西？"（即：如果今天没买奶昔，你会买什么？）
这引出了第一个特定的任务——早间通勤任务。
情境： 漫长而无聊的开车上班路途。
挣扎（Struggle）：
我很无聊，需要一只手有点事做（Keep the hand busy）。
我现在不饿，但我知道10点钟会饿，我需要东西垫肚子。
我穿着工作服，不能弄脏衣服。
我只有一只手有空（另一只手在方向盘上）。
竞争对手（Alternatives）：
香蕉： 吃得太快（3分钟就没了），无法解决20分钟车程的无聊问题；而且如果不立刻吃完会变黑。
甜甜圈： 手上会粘糖霜，弄脏方向盘和衣服；吃完后容易感到罪恶感。
贝果（Bagel）： 太干了，需要涂抹奶酪（无法单手操作），弄得车里到处是碎屑。
士力架： 感觉像是在早餐吃糖果，有负罪感。
奶昔的胜出原因：
它很粘稠（Viscous），用细吸管吸完需要20分钟，完美覆盖通勤时间。
它刚好能放在汽车杯架里。
它能提供足够的饱腹感直到中午。
它很干净，不会弄脏衣服。
结论： 在这个情境下，奶昔被"雇用"是因为它比香蕉或甜甜圈更好地完成了"排解无聊、垫饥、保持整洁"的任务。
行动建议： 为了在这个任务中胜出，快餐店应该把奶昔做得更浓稠（增加饮用时间），甚至加入果肉粒（增加无聊驾驶中的惊喜感），并设立快速通道让通勤者能迅速买完即走 10。
1.3.4 对比视角："下午的亲子任务"
然而，观察还发现了另一波购买高峰在下午。这一次，通常是父亲带着孩子。
情境： 放学后或周末下午。
任务： "安抚孩子，并以此感觉自己是个好父亲。"
挣扎： 父亲整天都在对孩子说"不"（不准买玩具，不准乱跑），他需要一个时刻说"是"，来缓解内心的愧疚感，并在短时间内构建亲密关系。
奶昔的失败： 早上的那种"浓稠"奶昔在这里完全失效了。孩子吸不动，父亲等得不耐烦。原本温馨的"奖赏时刻"变成了"漫长的等待"，最后往往是父亲喝掉了剩下的一半，带着一肚子气离开。
行动建议： 针对这个任务，奶昔应该变稀，且份量减半，以便孩子能快速喝完，皆大欢喜。
核心洞察： 同样的产品（奶昔），在不同的情境下（早上 vs 下午），被雇用通过来完成完全不同的任务。如果企业试图开发一款"所有人都喜欢"的奶昔（取平均值），那么它既不够浓稠以满足早上的通勤者，又不够稀薄以满足下午的孩子，最终将失去两个市场。
1.4 "进步"的本质：动词而非名词
在构建JTBD的认知地图时，必须强调"进步"（Progress）是一个动态过程 13。
进步起点（Progress Origin）： 某种不满意或挣扎的状态（如：无聊的通勤、愧疚的父亲）。
寻求的进步（Progress Sought）： 理想的未来状态（如：充实而饱腹的早晨、和谐的父子时刻）。
作为动词的进步（Progress as a Verb）： 雇佣产品的过程。
这要求我们将产品视为服务的载体。产品本身是没有生命的，只有当它被整合进客户的生活流程中，帮助客户消除从"起点"到"终点"的阻碍时，价值才产生。
第二模块：冲突与观点——反直觉的商业真相
在建立了JTBD的基本骨架后，我们必须面对该理论与传统商业智慧之间的剧烈冲突。这些冲突点往往是企业创新的"盲区"，也是理解本书最困难但最有价值的部分。本模块将通过一系列的二元对立，揭示被掩盖的商业真相。
2.1 数据与真相：大数据的相关性陷阱
在当今的商业语境中，"数据驱动决策"被奉为圭臬。然而，克里斯坦森提出了一个极具挑衅性的观点：数据往往具有误导性，尤其是那些仅仅描述"相关性"的被动数据。
2.1.1 属性相关性 vs. 因果机制
大数据擅长发现相关性。例如，数据可能显示："购买婴儿尿布的人有高概率购买啤酒"。
传统解读： 这是一个交叉销售的机会，应该把啤酒和尿布摆在一起。
JTBD解读： 这没有解释因果机制。为什么他们会同时买？是因为照顾婴儿压力大需要放松（情感任务）？还是因为去超市不方便只能一次性买齐（功能任务）？如果不知道"为什么"，任何基于相关性的营销（如推销高档红酒给尿布买家）都可能失败。
核心观点：
"上帝不会根据人口统计学特征来设计世界。"
客户的行为不是由他们的身份（年龄、性别、种族）驱动的，而是由他们所处的情境驱动的。一个40岁的银行家在周五晚上带客户吃饭（商务社交任务），与他在周六早上带孩子吃早餐（亲子任务），虽然由于同一个人，但其需求截然不同。如果系统只标记他为"高净值男性"，并据此推荐产品，就会出现严重的错配 5。
2.1.2 均值谬误（The Fallacy of Average）
企业习惯于聚合数据以寻找"平均用户"。
在奶昔案例中，如果将早上的需求（浓稠）和下午的需求（稀薄）取平均值，得到的是一种中等浓度的奶昔。
结果： 早上的顾客觉得它不够耐喝，下午的顾客觉得它还是太难吸。为"平均人"设计产品，意味着没有人会满意。
反直觉结论： 细分市场不应基于人（Persona），而应基于任务（Job）。同一个用户在其生活的不同片段中，会属于完全不同的"任务细分市场"。
2.2 竞争的重构：你的对手不是你的同行
波特五力模型教导我们关注行业内的竞争对手。可口可乐盯着百事可乐，宝马盯着奔驰。JTBD理论彻底打破了这种行业壁垒，提出了跨维度的竞争观。
2.2.1 类别陷阱（Category Trap）
企业倾向于在产品类别内定义竞争。
传统视角： 奶昔的竞争对手是冰淇淋、苏打水。
JTBD视角： 奶昔的竞争对手是香蕉、贝果、士力架、无聊、收音机（早间通勤任务）。
案例：Netflix的真正对手
Netflix CEO 里德·哈斯廷斯（Reed Hastings）曾著名地指出，Netflix的竞争对手不仅仅是HBO或Amazon Prime，而是一瓶红酒、棋盘游戏，甚至是睡眠。
如果用户的任务是"在漫长的一天后放松大脑"，那么喝一杯酒或睡觉都是Netflix的直接替代品。
如果用户的任务是"打发等待朋友的10分钟"，那么Netflix的对手就是TikTok或Instagram。
2.2.2 非消费（Non-consumption）的竞争
很多时候，最大的竞争对手不是另一家公司的产品，而是**"什么都不做"**（Non-consumption）。
在此情境下，客户选择忍受问题，因为现有的解决方案都太复杂、太昂贵或太麻烦。
洞察： 能够与"非消费"竞争并胜出的产品，往往能开启巨大的蓝海市场。例如，对于许多小型企业来说，Salesforce的竞争对手不是Oracle，而是"Excel表格"或"便利贴"。
2.3 功能的误区：过度满足与表面增长
在产品开发中，普遍存在一种"更多就是更好"的线性思维。
2.3.1 过度满足（Overshooting）
当企业过度关注产品性能指标（如像素、马力、刀片数量）而忽略了任务本身时，就会发生"过度满足"。
客户愿意为完成任务付费，但不愿意为超出任务需求的性能付费。
反直觉观点： 增加功能有时会降低产品的竞争力。
在"下午亲子奶昔"的案例中，让奶昔变得更浓（性能提升）反而导致了任务失败（孩子喝不完，父亲焦虑）。这里，"更好"的产品反而被"解雇"了。
2.3.2 表面增长 vs. 深度增长
表面增长（Surface Growth）： 试图向现有客户兜售更多他们不需要的产品，或者通过促销手段暂时拉动销量。这种增长是不可持续的，因为它没有解决新的任务。
深度增长（Deep Growth）： 发现客户生活中尚未被满足的任务，或者将现有任务完成得更好。这种增长建立了牢固的客户关系，因为产品成为了客户生活拼图中不可或缺的一块 11。
2.4 主动数据与被动数据
克里斯坦森区分了两种数据类型：
被动数据（Passive Data）： 这种数据是过去行为的痕迹，易于量化和采集（如点击率、销售额）。它告诉你"发生了什么"，但掩盖了背景。
主动数据（Active Data）： 这种数据是关于客户挣扎的定性描述，是混乱的、叙事性的。它只能通过观察和对话获得。
冲突： 企业的管理系统（ERP, CRM）是为了处理被动数据而设计的。这种系统性的偏见使得企业高管越来越远离"真相的现场"，而迷信于经过层层过滤和聚合的报表。
建议： 创新者必须走出大楼，去搜集"厚数据"（Thick Data）——那些包含情感、语境和复杂人性的故事 5。
第三模块：洞察与迁移——从理论到执行的精密机械
理解了骨架和冲突之后，最大的挑战在于执行。如何将"任务"这一抽象概念转化为可操作的指令？本模块将提供一套精密的工具箱，包括"进步的四种力量"、"任务规格说明书"以及"访谈技术指南"，帮助读者将认知转化为行动。
3.1 变革的方程式：进步的四种力量（The Forces of Progress）
当客户决定从一种解决方案切换到另一种时（例如，从"用Excel记账"切换到"使用QuickBooks"），其内心实际上正在进行一场力量的博弈。这并非随机的选择，而是可以通过物理力学模型来解释的。
切换方程式：
$$\text{切换的可能性} = (\text{推力} + \text{拉力}) - (\text{习惯} + \text{焦虑})$$
要促成购买（雇用），左边的动力必须大于右边的阻力 15。
3.1.1 动力的来源
- 推力（Push）：
定义： 现状中的不满、痛苦或挣扎。这是"必须改变"的理由。
表现： "我的床垫太旧了，睡得背痛"、"这辆车总是坏，修理费太贵"。
策略： 营销不应只展示美好未来，必须首先放大现状的痛点，让客户意识到"不能再这样下去了"。没有推力，就没有需求。
- 拉力（Pull）：
定义： 新解决方案带来的美好愿景。这是"想要变成的样子"。
表现： "如果买了那个新床垫，我每天醒来都会精力充沛"、"这辆新车能让我看起来像个成功人士"。
策略： 描绘产品使用后的新生活图景，而非堆砌功能参数。
3.1.2 阻力的来源
- 习惯（Habit）：
定义： 现状的惯性。"虽然现在的不完美，但我已经适应了"。
表现： "我虽然讨厌Excel，但我闭着眼睛都知道快捷键"、"换新系统太麻烦，还得迁移数据"。
策略： 降低迁移成本。承认现状的舒适性，并提供无缝的过渡方案（如一键导入数据）。
- 焦虑（Anxiety）：
定义： 对新解决方案的不确定性和恐惧。
类型：
选择焦虑： "万一买错了怎么办？"
使用焦虑： "万一我学不会怎么用怎么办？"
表现： "这看起来很棒，但如果它不兼容我的旧电脑怎么办？"
策略： 风险通过。提供退款保证、免费试用、用户证言。
3.1.3 案例：床垫购买者的心理博弈
21
在一次经典的JTBD访谈中，受访者迟迟不愿购买新床垫，尽管旧床垫已经让他背痛（推力）且他很喜欢新床垫的舒适（拉力）。
阻碍因素（焦虑）： 并不是价格，而是"旧床垫怎么处理？"这看似微不足道的问题成为了巨大的焦虑源。他在想："我没有卡车运走它，如果放在路边会被罚款吗？放在地下室又占地方。"
解决方案： 商家不仅仅卖床垫，还提供"免费回收旧床垫并处理"的服务。
结果： 这一服务消除了关键的焦虑阻力，即使没有价格折扣，客户也立即下单了。
洞察： 有时候，促进增长的最廉价方式不是增加产品功能（拉力），而是消除微小的焦虑或习惯阻力。
3.2 大雇用与小雇用（Big Hire vs. Little Hire）
客户与产品的关系分为两个阶段，理解这一区别对于留存至关重要 5。
3.2.1 大雇用（The Big Hire）
这是客户购买产品的时刻。此时，营销产生的"拉力"和现状的"推力"战胜了阻力。交易完成，钱货两清。
- 关注点： 销售转化、营销信息、购买便利性。
3.2.2 小雇用（The Little Hire）
这是客户真正使用产品来完成任务的时刻。这是从购买那一刻开始，并在每次使用中重复发生的过程。
关键点： 如果"小雇用"充满了摩擦（例如：宜家家具组装太难、软件界面太复杂、奶昔太稠吸不动），那么下一次"大雇用"就不会发生。
Airbnb案例：
大雇用： 在网站上预订房间。
小雇用： 拖着行李箱到达房源门口。如果此时找不到钥匙，或者房间有异味，或者房东没有像承诺的那样提供洗漱用品，小雇用就失败了。
Airbnb意识到，"到达时刻"是小雇用的关键瞬间。他们不仅要优化网站预订流程（大雇用），更要通过房东教育、入住指南等方式优化"进门体验"（小雇用）。
行动建议： 绘制客户的任务时间轴，不仅要关注购买点，更要关注使用过程中的每一个"微时刻"。确保产品在每一次"小雇用"中都能兑现承诺。
3.3 任务规格说明书（The Job Spec）
一旦明确了任务，如何向研发团队传达需求？传统的"产品需求文档"（PRD）往往罗列功能。JTBD建议使用**"任务规格说明书"**，它包含以下要素 7：
功能性标准： 产品必须达到的硬性指标（如：奶昔必须能喝20分钟）。
情感性标准： 客户在使用过程中的心理底线（如：父亲不能感到被孩子拒绝）。
社会性标准： 产品在社交环境中的信号作用。
权衡（Trade-offs）： 客户愿意为了完成任务而牺牲什么？（如：早间通勤者愿意牺牲口味的多样性来换取饮用的便利性和持久性）。
障碍（Obstacles）： 必须移除的具体阻力。
3.3.1 案例：南新罕布什尔大学（SNHU）的在线教育
SNHU没有试图与哈佛竞争（哈佛的任务是"精英认证"和"社交网络"）。SNHU锁定的任务是："帮助30多岁的在职成年人快速获得学位以提升职业前景，同时不干扰他们的生活。"
SNHU的任务规格说明书：
功能： 课程必须完全在线，时间灵活。
情感/焦虑： 成年人重返校园充满了恐惧（我能行吗？我有时间吗？）。他们需要极速的反馈来维持动力。
具体执行：
传统大学的经济援助回复时间是24小时甚至更久。
SNHU将其缩短为10分钟。
当潜在学生在晚上在网上填写表格时（这是他们唯一的空闲时间），如果第二天才能收到回复，那种"想要改变"的冲动（推力）可能就被日常生活的惯性（习惯）淹没了。
10分钟内的电话回复抓住了"推力"最强的时刻，极大地提高了转化率。
结果： 这一基于任务规格的调整，帮助SNHU实现了惊人的增长。
3.4 目的品牌（Purpose Brand）：竞争的护城河
当一个品牌与一个特定的"待办任务"完美绑定时，它就成为了目的品牌。
定义： 品牌名称成为了任务的代名词。
案例：
IKEA： "我今天就需要以低廉的价格布置好整个公寓。"
FedEx： "这件包裹必须在明天绝对无误地送达。"
Uber： "我现在就要从A点去B点，不想掏现金，不想等待。"
价值： 目的品牌占据了客户的心智快捷方式。当任务出现时，客户会启动"系统1"（直觉思维），直接雇佣该品牌，而不再考虑竞争对手。这使得品牌能够获得溢价，并抵御低价竞争 5。
3.5 像拍摄纪录片一样访谈：挖掘任务的实战指南
最后，如何通过访谈挖掘出这些深层的任务？克里斯坦森建议采用类似于刑事侦查或纪录片拍摄的访谈技巧，重建购买的时间轴 27。
3.5.1 时间轴重建法
不要问"你想要什么"，要问"发生了什么"。
| 阶段 | 核心问题 | 目的 |
| :---- | :---- | :---- |
| 第一念头 (First Thought) | "你第一次冒出'我需要买个新东西'这个念头是在什么时候？当时你在做什么？" | 捕捉最初的推力（Push）。 |
| 被动浏览 (Passive Looking) | "在那之后，你有没有留意过相关的信息？但还没有采取行动？" | 了解习惯（Habit）的阻力有多大。 |
| 触发事件 (Trigger Event) | "后来发生了什么事，让你决定'就是今天，我必须买了'？"（例如：旧床垫彻底坏了，或者明天丈母娘要来住） | 识别打破平衡的关键推力。 |
| 主动寻找 (Active Looking) | "你考虑了哪些其他选择？你为什么排除了它们？" | 了解竞争对手（包括非消费品）和焦虑（Anxiety）。 |
| 购买时刻 (The Big Hire) | "当你刷卡的那一瞬间，你还在担心什么？" | 挖掘最后的焦虑障碍。 |
| 使用体验 (Consumption) | "用起来和你想象的一样吗？" | 验证小雇用的成败。 |
3.5.2 挖掘情感线索的技巧
寻找异常： "你说你不在乎价格，但为什么看了那款便宜的之后又放下了？"
场景还原： "告诉我那天早上的天气怎么样？只有你一个人吗？"（细节能唤起记忆）。
替代方案： "如果你没买这个，你会怎么办？"（挖掘真正的竞争对手）。
结语：从运气到因果
《与运气竞争》这本书的核心价值，不在于提供一个具体的营销技巧，而在于认知的升维。它告诉我们，商业成功不必依赖于"大概率的赌博"。通过将分析单位从"人"和"产品"切换到"待办任务"，我们能够看清隐藏在混乱市场表象下的因果机制。
当你戴上JTBD的眼镜，世界将焕然一新：
你不再看到"35岁的男性用户"，你看到的是"早间通勤排解无聊的父亲"。
你不再看到"竞争对手的产品参数"，你看到的是"如果不买我，他会去睡觉"。
你不再盲目堆砌功能，你开始精心设计消除焦虑的每一个微小体验。
正如克里斯坦森所言："如果我们能够通过正确的镜头观察世界，创新就不再是撞大运，而是可以预测、可以掌握的科学。" 这就是这本书留给我们的最大财富——一把解开创新因果律的钥匙。
Works cited
The 3 types of customer job — Steve Forbes - Innovation | Product Development | Strategy, accessed January 19, 2026, https://www.steveforbes.com.au/blog/2019/8/13/the-3-types-of-customer-job
Jobs to Be Done Framework: The Product Manager's Guide to Building Products Customers Actually Want - Kaizenko, accessed January 19, 2026, https://www.kaizenko.com/jobs-to-be-done-framework-the-product-managers-guide-to-building-products-customers-actually-want/
accessed January 19, 2026, https://www.christenseninstitute.org/theory/jobs-to-be-done/#:~:text=We%20call%20these%20Jobs%20because,their%20lives%20to%20make%20progress.
Jobs to Be Done Theory - Christensen Institute, accessed January 19, 2026, https://www.christenseninstitute.org/theory/jobs-to-be-done/
Competing Against Luck - Clayton M. Christensen, Taddy Hall, Karen Dillon, David Duncan, accessed January 19, 2026, https://manassaloi.com/booksummaries/2017/07/22/competing-against-luck-christensen.html
Know the Two — Very — Different Interpretations of Jobs to be Done | by Alan Klement, accessed January 19, 2026, https://jtbd.info/know-the-two-very-different-interpretations-of-jobs-to-be-done-5a18b748bd89
Clayton Christensen, Jobs-to-be-Done & Competing Against Luck, Part 1 - Thrv, accessed January 19, 2026, https://www.thrv.com/blog/clayton-christensen-jobs-to-be-done
Clay Christensen's Jobs to Be Done framework: How to build better products - Fullstory, accessed January 19, 2026, https://www.fullstory.com/blog/clayton-christensen-jobs-to-be-done-framework-product-development/
Milkshakes in the Morning - The JTBD Story - The Re-Wired Group, accessed January 19, 2026, https://therewiredgroup.com/case-studies/milkshakes/
'Hire' this article about milkshakes if you're struggling to understand customer needs, accessed January 19, 2026, https://uxdesign.cc/hire-this-article-if-you-re-struggling-to-understand-your-customer-needs-3963eff273f8
Book Summary — Competing Against Luck | by Michael Batko | MBReads | Medium, accessed January 19, 2026, https://medium.com/mbreads/competing-against-luck-379fe4b9268a
Case Studies: Milk-Shake - The Triz Journal, accessed January 19, 2026, https://the-trizjournal.com/case-studies-milk-shake/
Understanding Progress, accessed January 19, 2026, https://theprogresseconomy.com/understanding-progress/
Competing Against Luck - Product Management Book Summaries, accessed January 19, 2026, https://andrewclark.co.uk/all-media/competing-against-luck
DEMAND CREATION - AWS, accessed January 19, 2026, https://innodynmedia.s3.amazonaws.com/WSU/DC+Chapters+1-2.pdf
The Ultimate Guide to Jobs To Be Done Theory - Viima, accessed January 19, 2026, https://www.viima.com/blog/jobs-to-be-done
[Pt. 4] The Struggle and the Opportunity! | by Andrea F Hill | Frameplay | Medium, accessed January 19, 2026, https://medium.com/frameplay/pt-4-the-struggle-and-the-opportunity-c67a611db52e
How habits and anxieties keep people from using your product - Adam Amran, accessed January 19, 2026, https://www.amran.cz/how-habits-and-anxieties-keep-people-from-using-your-product/
Uncovering the Jobs That Cause Customers to Hire Products and Services | by Andrej Balaz, accessed January 19, 2026, https://jtbd.info/uncovering-the-jobs-that-customers-hire-products-and-services-to-do-834269006f50
The Forces of Progress. Forces that oppose each other —… | by Alan Klement | Jobs to be Done, accessed January 19, 2026, https://jtbd.info/the-forces-of-progress-4408bf995153
Can an Innovation Get You Into Heaven? Bob Moesta and Brian Walker talk Jobs-to-be-Done, accessed January 19, 2026, https://jobstobedone.org/news/brand-labs-bob-moesta/
The Jobs-to-be-Done Mattress Interview (as seen in Competing Against Luck), accessed January 19, 2026, https://jobstobedone.org/radio/the-mattress-interview-part-one/
Competing Against Luck review - Matt Bjornson, accessed January 19, 2026, https://bjornson.co/2017/09/12/competing-against-luck/
The "Jobs to Be Done" Theory of Innovation - Strategy+business, accessed January 19, 2026, https://www.strategy-business.com/article/The-Jobs-to-Be-Done-Theory-of-Innovation
A book review of Competing Against Luck by Josh Wayne, accessed January 19, 2026, https://joshwayne.com/books/competing-against-luck/
Competing Against Luck by Clayton Christensen (& others) – My Four Lessons and Takeaways | First Friday Book Synopsis, accessed January 19, 2026, https://www.15minutebusinessbooks.com/blog/2016/11/09/competing-against-luck-by-clayton-christensen-others-my-four-lessons-and-takeaways/
Jobs to be Done 101: Your Interviewing Style Primer - Dscout, accessed January 19, 2026, https://dscout.com/people-nerds/the-jobs-to-be-done-interviewing-style-understanding-who-users-are-trying-to-become
How to Interview for JTBD. Here is how we do JTBD interviews at… | by Jess Telford | cete, accessed January 19, 2026, https://medium.com/cete/how-to-interview-for-jtbd-8a4449003667
How to do a Jobs To Be Done Interview - Jason Evanish, accessed January 19, 2026, https://jasonevanish.com/2014/04/23/how-to-do-a-jobs-to-be-done-interview/