Jobs to Be Done (JTBD) is a product development framework arguing that people “hire” products to accomplish specific “jobs” in their lives. Popularized by Clayton Christensen (Harvard Business School) through his milkshake marketing case study, the theory shifted focus from customer demographics to underlying motivations. The framework gained startup traction in 2010s as alternative to traditional market segmentation.

The Milkshake Story

Christensen’s team studied a fast-food chain’s milkshake sales. Traditional research asked: “How can we improve milkshakes?” (flavor, texture, size). JTBD research asked: “What job is the milkshake doing?”

Insights:

• Morning commuters: Hired milkshakes to make boring commutes interesting and stave off hunger until lunch (thick = lasts longer)
• Parents: Hired milkshakes to appease kids demanding treats (thin = consumed quickly, less mess)

Two different jobs → two different product needs. The chain created morning (thicker, chunks) and afternoon (thinner, faster) milkshakes.

The Framework

JTBD format: “When [situation], I want to [motivation], so I can [outcome].”

• “When I’m bored on my commute, I want something engaging, so I can arrive at work alert.”
• “When my kid nags for treats, I want to say ‘yes’ without hassle, so I can be seen as a good parent.”

The theory argues features don’t matter — progress toward desired outcomes does. Users don’t want a drill; they want a hole in the wall.

Product Development Applications

JTBD influenced how startups build products:

• Interview focus: Ask about last time user switched products, what they were trying to accomplish (not hypothetical future behavior)
• Competitor redefinition: A morning milkshake competes with bagels, bananas, energy bars, coffee — not just other milkshakes
• Feature prioritization: Build what helps users make progress, not what they explicitly request

Example: Intercom realized customers didn’t want “better live chat” — they wanted to “reduce support ticket volume.” This led to self-service knowledge bases, chatbots, proactive messages.

Criticisms

• Overcomplication: Sometimes users want faster horses, and giving them faster horses is fine (not every product needs deep JTBD analysis)
• Interview skill required: Extracting real jobs requires expert interviewing (bad interviews yield garbage insights)
• Backward-looking: JTBD interviews analyze past behavior, missing breakthrough innovations users can’t articulate (iPhone didn’t emerge from JTBD research)

Clayton Christensen himself noted: JTBD works for incremental innovation, less useful for disruptive breakthroughs.

Cultural Impact

#JobsToBeDone shaped product management culture:

• User story formats: “As a [role], I want [feature], so that [benefit]” (Agile user stories influenced by JTBD)
• Outcome-based metrics: Track progress toward goals (time saved, anxiety reduced) not feature usage
• Product-market fit conversations: “What job does your product do?” became common investor question

The framework gave product teams shared language for customer-centric thinking, even if purists argue most companies misapply it.

References

• Competing Against Luck by Clayton Christensen - Book, 2016
• The Jobs to Be Done Playbook - Intercom, 2016