Jobs to Be Done: The Milkshake Dilemma and the Causal Mechanics of Customer Choice

Of the tens of thousands of new consumer products launched every year, between 70 and 90 percent vanish without a trace. This failure does not happen because companies neglect market research. Modern firms assemble focus groups, run exhaustive demographic surveys, and gather terabytes of consumer web browsing logs. When consumers ask for sweeter beverages, companies increase sugar content; when users request more features, developers add buttons. Yet the resulting products, meticulously refined according to direct customer feedback, routinely meet disastrous rejection in the marketplace.
The most pervasive and lethal error in business is mistaking correlation between customer attributes and purchase events for causality. A demographic profile such as a college-educated 30-something male with median income residing in a metropolitan area explains precisely zero reasons why that individual opens his wallet at a particular moment. Human beings do not purchase products because they belong to a demographic cohort. They reach for tools only when seeking to make specific progress within the struggling circumstances of their lives.
Customers do not buy products for their physical specifications or demographic attributes. They hire solutions to make progress against specific struggling circumstances. True competition takes place not within product categories, but across all alternatives hired to perform the same job. The victory of innovation hinges on an experience architecture that eliminates anxiety and inertia so customers can fire their existing habits and adopt a new solution.
The Trap of Feature Optimization and the Milkshake Paradox
A famous study of a major American fast-food chain trying to boost milkshake sales reveals the blind spots of feature-centric thinking. Management initially convened heavy milkshake buyers for in-depth feedback. They asked whether customers preferred richer chocolate flavors, lower prices, or fruit chunks. The chain implemented the responses faithfully, releasing sweeter, chunkier shakes, but sales remained completely flat.
The hidden reality emerged only when researchers stationed themselves inside restaurants for entire days to observe actual purchasing behavior. Nearly half of all milkshakes were sold before 8:30 in the morning. Customers almost always came alone, bought nothing else, and carried the single cup straight back to their cars.
When researchers interviewed these morning commuters, the real story became clear. They were not craving a dessert. The job they were trying to accomplish was staving off hunger until mid-morning while making a long, boring drive more engaging. In this context, the true rivals of the milkshake were not competing milkshakes from rival chains. They were bananas, donuts, and bagels.
A banana disappeared in sixty seconds, leaving the driver hungry again soon after. A donut coated fingers in sticky glaze, staining the steering wheel. A bagel was dry and crumbly, and spreading cream cheese while driving risked ruining a clean dress shirt. A thick milkshake, by contrast, took twenty minutes to sip through a narrow straw, lasting the entire commute. It fit snugly into a cup holder, required only one hand, and left no mess on business clothing. Commuters did not purchase a confection; they hired a milkshake as a durable driving companion.
The afternoon context, however, presented a completely different job. When parents visited the restaurant with young children after school, that same thick milkshake became a nightmare. The parents sought a quick treat to show affection and reward their child before heading home. Yet because the shake was so dense, the child struggled for thirty minutes just to finish half the cup, testing parental patience. For the afternoon job, a thin, fast drink in a small cup was the ideal solution. The exact same physical product performed two completely contradictory jobs depending on the time of day and circumstantial context.
Dimension | Product-Centric Perspective | Jobs to Be Done (JTBD) Perspective |
|---|---|---|
Starting Point | Which features and specifications should we add? | What progress is the customer trying to make in this situation? |
Market Segmentation | Demographics (age, income) and product categories | Specific struggling circumstances faced by the person |
Competitive Scope | Rival products within the same industry category | All alternatives that can be hired to complete the job |
Feedback Collection | Abstract surveys ("Would you like a sweeter taste?") | Contextual observation ("What did you replace right now?") |
Marketing Message | Listing superior product specifications and features | Depicting relief from friction and improved daily life |
Response to Failure | Discounting prices or adding another marginal feature | Redefining the customer circumstance and core job |

The Demographic Illusion and the Three Dimensions of a Job
Marketers often assume that demographic data explains customer behavior. Yet age, gender, and zip code never cause a purchase. The same professional requires one beverage during a solo Monday morning commute, an entirely different drink at a Friday evening team dinner, and a third choice while strolling in a park with a toddler on Sunday. The causal unit of analysis is never the identity of the person, but the circumstance they occupy.
Furthermore, the job an individual seeks to get done extends beyond raw physical tasks. Every job possesses functional, emotional, and social dimensions that intertwine.
The functional dimension is the practical, tangible task: curbing hunger on a highway, cutting lawn grass, or sending a document. If functionality were everything, buyers would always choose the cheapest, most bare-bones tool. Real human behavior proves otherwise.
Customers also hire solutions to evoke specific feelings during use. This represents the emotional dimension. It encompasses the sense of calm when slowly sipping a drink in bumper-to-bumper traffic, the relief of finishing a report error-free, and the feeling of competence when operating a well-designed tool.
Finally, the social dimension reflects how individuals wish to be perceived by their peers. A parent buying an after-school snack seeks to project warmth and benevolence. Carrying a reusable branded mug or adopting an enterprise collaboration tool communicates professionalism and environmental mindfulness. Even if a product fulfills functional requirements, customers will reject it if it causes emotional frustration or invites social embarrassment.
Loading diagram.
View diagram source
flowchart TD
A["Customer Encounters Struggling Circumstance"] --> B["Identify 3 Dimensions of the Job"]
B --> B1["Functional Job: Practical Task Completion"]
B --> B2["Emotional Job: Gaining Calm and Control"]
B --> B3["Social Job: Reputation and Identity Signaling"]
B1 --> C{"Tug of War: Four Forces of Progress"}
B2 --> C
B3 --> C
C --> D["Forces for Change: Push of Current Pain + Pull of New Solution"]
C --> E["Forces of Resistance: Anxiety of New Solution + Inertia of Habit"]
D --> F{"Forces for Change > Forces of Resistance?"}
E --> F
F -->|"Change Dominates"| G["Fire Old Solution and Hire New Solution"]
F -->|"Resistance Dominates"| H["Abandon Purchase and Revert to Old Habits"]
G --> I["Align End-to-End Experience Architecture"]
I --> J["Build Defensible Competitive Moat"]The Four Forces of Progress: Hiring and Firing Solutions
Purchasing a new solution never happens in a vacuum. To welcome a new product into daily life, a customer must first displace the entrenched habits or legacy tools already occupying that space. Hiring a new solution always requires firing an existing one.
At this crossroads of decision, four invisible forces clash. Two forces push and pull toward change, while two opposing forces anchor the individual in place.
The first driver is the push of the current situation. This is the mounting frustration caused by existing tools that break down, run slowly, or create bottlenecks. Unless this dissatisfaction breaches a critical threshold, people lack the motivation to seek alternatives.
The second driver is the pull of the new solution. This is the magnetic appeal of a promising future, whether dramatic time savings, elegant craftsmanship, or frictionless convenience.
Yet while most companies pour capital into amplifying this pull through feature expansion, they overlook the twin anchors holding customers back.
The first resistance is the anxiety of the new solution. Questions linger: "What if this expensive software proves too complex?", "What if our vital customer records corrupt during migration?" Steep learning curves and transition risks instantly trigger cognitive defense mechanisms.
The second resistance is the inertia of existing habits. Human psychology favors familiar inefficiency over unfamiliar convenience. Even when current routines are cumbersome, the muscle memory built over years exerts immense gravity.
The mathematical reality of adoption is straightforward: the combined strength of push and pull must decisively exceed the combined weight of anxiety and inertia. Innovations collapse not because their features lack appeal, but because companies fail to engineer safety nets that dissolve customer apprehension and habit resistance.

Blind Spots in Innovation and the Boundaries of Job Theory
While Jobs to Be Done theory revolutionized customer-centric strategy, treating it as an infallible panacea is dangerous. In complex commercial realities, the framework faces clear boundaries.
First, over-indexing on current customer struggles creates an incrementalism trap. Consumers cannot articulate jobs for paradigms they have never experienced. Prior to the smartphone, asking consumers about their jobs would have elicited requests for longer battery life on tactile keypads or lighter personal digital assistants. Relying solely on explicit customer-described jobs risks blinding organizations to radical technological leaps and novel category creation.
Second, in multi-stakeholder enterprise environments, defining a single job becomes exceptionally difficult. When adopting enterprise software, the end-user engineer seeks rapid response times and keyboard shortcuts, the IT security administrator requires rigorous access controls and audit trails, and the chief financial officer prioritizes budget predictability. Optimizing for one stakeholder often degrades the job performance for another, transforming product strategy into a political balancing act of corporate governance.
Third, human consumption cannot always be reduced to rational problem-solving. Conspicuous status signaling, aesthetic delight, impulse spending, and cult brand fandom generate massive economic value without resolving functional friction. Framing the purchase of luxury leather goods or rare collector sneakers as hiring a tool to solve life problems stretches the concept of progress into analytical vagueness.
Experience Architecture: Building an Uncopyable Moat
Despite these boundaries, the most enduring gift of job theory to product leaders is the imperative of experience architecture.
Unassailable market leaders do not obsess over making an isolated feature 10 percent better than a competitor. Instead, they integrate every touchpoint across the journey, from discovery and checkout to unboxing, onboarding, customer support, and disposal, into one unified chain aligned with the job.
A rival can duplicate an isolated feature within months. Replicating the sweetness of a drink or matching the megapixel count of a smartphone camera requires only capital and time. But duplicating an integrated system that expedites drive-through checkout, designs cups that never wobble in holders, and calibrates straw diameters for a twenty-minute commute is extraordinarily difficult.
The same principle governs modern software. Companies peddling disconnected feature checklists face rapid commoditization. But firms that engineer one-click data migration to eliminate switching anxiety, craft guided onboarding flows that dismantle old team habits, and deliver five-minute support resolution construct an enduring moat.
True innovation is not a lab contest to inflate technical specifications. It is the disciplined commitment to observe where people struggle, dissolve their anxiety and inertia, and make daily living slightly more effortless and dignified. Customers never purchase your product for what it is; they purchase who they become when using it.
Further Questions
All Essays
Procedural Humility and the Science of Checklists: Why True Experts Ask About What They Already Know
Contrasting Zhu Xi and Jeong Yak-yong on Confucius asking about every ritual in the Grand Temple with modern ICU and surgical checklist studies to explain how procedural humility prevents failures of ineptitude.

An analysis of how exit, voice, and loyalty interact during institutional decline, explaining why easy alternatives often deplete internal reform capacity.