PTENES
MODULE 2.5

🎯 Jobs To Be Done

People don’t buy products—they “hire” solutions to solve a specific job in their lives. Discover the real job behind a purchase and design innovations that win market share by meeting human needs.

6
Topics
50
Minutes
Medium
Level
Practice
Type
1

đŸ„€ Jobs Theory and the Milkshake Case

In the mid-1990s, Clayton Christensen — a Harvard professor and author of "The Innovator’s Dilemma" — received an unusual assignment: help a fast-food chain sell more milkshakes. The company had done everything right: market research, focus groups, flavor adjustments. Sales remained stagnant. The problem was the wrong question.

📖 Christensen's Discovery

Instead of asking “What do you think of the milkshake?”, Christensen’s team started asking: "What job did you hire this milkshake to do this morning?" The result was revealing: most morning buyers were alone, in a hurry, and driving a long commute to work. They didn’t want a milkshake—they wanted something that occupied both hands, lasted long enough to get them through the commute, and kept them satisfied without having to stop for food.

Clayton Christensen, "Competing Against Luck" (2016) — with Bob Moesta and others

đŸ‘€ Customer has a job to be done in his life “hire” 📩 Product or service to solve solves The Real Job Functional concrete task Emotional how you want to feel Social how you want to be seen e.g., driver morning milkshake keep your hands busy, last the whole trip, satisfy without stopping

Christensen’s conclusion was radical: the real competitor to the morning milkshake wasn’t another milkshake—it was a banana, a bagel, or a donut. Anything the customer could "hire" to do the same job. This changed how the company should innovate: by making the milkshake thicker (so it lasts longer), more convenient to buy (self-service), and less guilt-inducing (a smaller version for kids at the end of the day—a completely different job).

📊 Why JTBD Changes the Game

  • 95% of new products fail, according to a Harvard study (Christensen, 2016)—generally because they solve the wrong product problem, not the right job
  • Airbnb: the job wasn’t "rent a cheap room" — it was "feel at home, connected to the local culture"
  • Uber: the job wasn’t "cheaper taxi" — it was "reliable transportation without uncertainty about arrival time"
2

đŸ”ș Job Dimensions: Functional, Emotional, Social

Every job has three overlapping layers. Most companies see only the functional dimension — the concrete task the user wants to complete. But Bob Moesta, JTBD framework co-creator with Christensen, showed that emotional and social dimensions often play a greater role in the decision to “hire” or “fire” a product.

⚙

Functional

The concrete, objective, measurable task

What the user literally needs to do. “I need to get from point A to point B.” “I need to store my files.” “I need to communicate with my team.” This is the easiest job to identify and also the most commoditized—when everyone does the functional job well, the emotional and social dimensions decide who wins.

Example: "pay my bills without leaving home"

❀

Emotional

How the user wants to feel while using it

The internal, personal dimension. "I want to feel organized." "I want to feel in control." "I don’t want to be afraid of making mistakes." Emotional jobs are powerful because they create loyalty. When a product makes you feel good about yourself, you "rehire" it even when cheaper alternatives exist.

Example: "feel like a present father"

đŸ‘„

Social

How the user wants others to perceive them

The external dimension, tied to status and identity. "I want to look up-to-date to my colleagues." "I want my clients to see me as a professional." "I want to be seen as someone who cares about the environment." Social jobs explain why people pay more for brands—the brand is the social signal the product delivers.

Example: "be seen as a modern manager"

🎓 Insight from Bob Moesta

"When we studied what leads a family to buy a new house, the functional dimension—more space—was the pretext. The emotional dimension—'I want a room of my own' (the mother)—was the real trigger. The social dimension—'I don't want my daughter to share a room when she has friends over'—was the blocker that prevented the purchase until it was addressed."

Bob Moesta, “Demand-Side Sales 101” (2020)

💡 Practical Tip

For every product you're developing, write out the three dimensions explicitly: "The user needs [FUNCTIONAL]. They want to feel [EMOTIONAL]. They want to be seen as [SOCIAL]." If you can't fill in all three fields, you don't understand the job yet.

3

🔍 How to Discover Jobs: Interviews, Switch Interview, and Timeline

Discovering the real job isn’t intuition—it’s a method. Bob Moesta developed specific interview techniques that work because they explore the past behavior, not future intentions. People lie (unintentionally) when they describe what they would do. When they describe what they did, they reveal the truth.

The Switch Interview — Moesta Method

1

First idea: the first thought

When did you first think about changing?

Identify the initial trigger—the moment when the status quo became unacceptable. It may have been weeks or months before the purchase. This is the "first push": the dissatisfaction that began to build.

2

Decision point: the catalyzing event

What happened the day you decided to look for a solution?

Reveals the “passive event”—the specific moment that turned latent dissatisfaction into action. There’s almost always a concrete event: the meeting that went wrong, the bill that was higher than expected, or a friend who showed them a new product.

3

The search: how you looked

Which alternatives did you consider?

Maps the solution space the customer sees. Reveals real competitors (which often surprise the company). Includes "buy nothing" solutions and workarounds the customer was already using.

4

The purchase: D-day

Tell me about the day you bought it — from beginning to end

Reconstruct the “purchase moment” in narrative detail. Where they were, who they were with, what led them to checkout. It reveals forces of attraction (the pull toward the new) and resistance (anxiety about changing). The devil is in the details of this narrative.

đŸŽ™ïž JTBD Interview Golden Rules

Questions about the past

Never “what would you do if...”. Always “what did you do when...”.

Narrative, not a list

Ask the interviewee to tell a story, not give ratings from 1 to 10.

Productive silence

After a response, wait 5 seconds before speaking. The best answers come in the silence.

Follow the emotion

When the tone changes, dig deeper. “You seemed hesitant there—tell me more.”

4

📝 Job Stories vs. User Stories

Alan Klement—one of the leading modern JTBD evangelists—popularized the format Job Story as an alternative to User Stories in agile development. The difference may seem subtle, but it completely changes the product team’s focus.

User Story (traditional)

Format: "As a [persona], I want [functionality] so that [benefit]"

"How Maria, HR manager, I want to see point reports for control the frequency"

  • ✗Focuses on who the (fictional) persona is
  • ✗Already assumes the solution (report)
  • ✗Ignores the situational context
  • ✗Doesn't capture the emotional/social job

Job Story (JTBD)

Format: "When [situation], I want [motivation] so that I can [expected outcome]"

"When I need to justify overtime to the board, I want to get consolidated data in seconds, so I can focus on the conversation, not the spreadsheet"

  • ✓Focuses on the real situational context
  • ✓Doesn't assume the solution
  • ✓Includes motivation and outcome
  • ✓Reveals the emotional job (“focus on the conversation”)

🔑 The Job Story Structure in Detail

WHEN

Describes the situation—the specific context that triggers the job. It’s the substitute for a persona: instead of asking “who is the user,” it asks “what situation is the user in.” Situations are more stable than personas over time.

I WANT

Describes the motivation—what the user is trying to accomplish. It should be an action or state, not a feature. “Have confidence that the data is correct” is better than “view a report.”

WHAT FOR

Describes the desired outcome—the higher-level job. It often reveals the underlying emotional or social job. “So I can focus on what matters” is almost always the real job.

5

📐 Outcome-Driven Innovation (Ulwick)

Tony Ulwick arrived at JTBD by a different path than Christensen. While Christensen came from sociology and behavioral science, Ulwick was an engineer who wanted a repeatable, measurable process. He created the Outcome-Driven Innovation (ODI) — a methodology that turns JTBD into a quantifiable process, mapping "desired outcomes" prioritized by importance and current satisfaction.

📖 Ulwick's Opportunity Formula

Opportunity = Importance + max(Importance - Satisfaction, 0)

Where customers rate importance and satisfaction on a scale from 0 to 10

An outcome with importance of 9 and satisfaction of 3 has an opportunity score of 9 + (9-3) = 15. An outcome with importance of 5 and satisfaction of 8 has an opportunity score of 5 + 0 = 5. The formula identifies where the market is served, overserved, or has gaps—objectively mapping the innovation landscape.

đŸ—ș The 4 Opportunity Landscape Quadrants

High Importance + Low Satisfaction

High-priority innovation opportunity. The market isn’t serving something that matters a lot very well. This is where disruption happens.

High Importance + High Satisfaction

The market is well served. Incremental improvements here do not create a real competitive advantage.

Low Importance + Low Satisfaction

It's not worth investing. Even if you solve it well, it doesn't matter to the customer.

Low Importance + High Satisfaction

Over-serving. You’re spending resources solving something the customer doesn’t value. Cut back to simplify and reduce costs.

💡 ODI in Practice

Ulwick's ODI process has 5 steps: (1) Define the main job, (2) Identify the desired outcomes (usually 50-150 per job), (3) Survey importance and satisfaction with a representative sample, (4) Calculate opportunities, (5) Prioritize the roadmap based on the landscape. Companies such as Bosch, J&J, and Motorola used ODI to generate high-growth innovations with a success rate above 80% (vs. the market average of 5%).

6

⚠ Pitfalls and Practical Examples

JTBD is a powerful framework that's easy to misapply. The most common pitfalls aren't conceptual errors — they're execution errors that turn the framework into a tool for confirming what the team already believed. See the failure patterns and how to avoid them.

⚠ Classic Pitfalls

  • ✗ Overly generic job: "I want to be more productive" isn't an actionable job. Useful jobs are specific enough to distinguish between solutions.
  • ✗ Confusing the job with the solution: "I want a reminder app" is a solution, not a job. The job is "I want to avoid forgetting important appointments."
  • ✗ Interview the most enthusiastic customers: your biggest fans aren't the most informative. Interview people who almost bought but didn't—or who stopped using it.
  • ✗ Ignore the job of non-consumption: sometimes the competitor is “doing nothing” or “living with the problem.” Don’t underestimate inertia as an alternative.

✓ How to Apply It Well

  • ✓ Do at least 8-12 switch interviews before drawing any conclusions about the job
  • ✓ Record the interviews and transcribe them. Patterns emerge from exact words, not summaries.
  • ✓ Separate the job from the context: the same job can be done in different contexts with different solutions.
  • ✓ Map the four forces from Moesta: push (what pushes you away), pull (what attracts you to the new solution), anxiety (fears about the new), habit (comfort with the current).

🏆 Real Examples of JTBD Well Applied

🍎

iPod (Apple, 2001)

The job wasn’t “carrying MP3 files.” It was “having my entire music library in my pocket, without friction.” “1,000 songs in your pocket” describes the job, not the technology. The competition (Discman, existing MP3 players) did a poor job of meeting the functional need; the iPod met the emotional need (identity, elegance) and the social need (being seen with white headphones was a status symbol).

🏠

Airbnb (2008)

The job Bob Moesta discovered while studying Airbnb’s first users: “When I travel for pleasure, I want to feel like I’m living in the place, not just passing through, so I can have authentic stories to tell.” A hotel solves the functional need (sleeping). Airbnb solved the emotional and social needs—the travel story guests take home.

đŸ“±

LinkedIn (for recruiters)

The job wasn’t “a rĂ©sumĂ© database.” It was “when I need to fill a critical role, I want to find candidates I wouldn’t know how to find, so I can fill the role without relying on good candidates finding me.” The difference is subtle, but it led to a completely different product: LinkedIn Premium Recruiter is the solution to the job, not a rĂ©sumĂ© search tool.

⚠ The Trap of Too Much Theory

The biggest mistake with JTBD is using the framework to create beautiful documents instead of changing product decisions. Christensen, Moesta, and Ulwick agree on one point: JTBD only has value if discovering the job changes what you decide to build. If you conducted 15 interviews, produced a 40-slide report, and the roadmap stayed exactly the same—you used JTBD as a ritual, not as a decision-making tool.

📋 Module Summary

✓
People hire products, they don’t buy them — Christensen: the job is what the product solves in the customer's life, not the product itself
✓
Three dimensions: functional, emotional, social — Moesta: the emotional and social job often dominates the buying decision
✓
Switch Interview: past behavior, not intentions — Reconstructing the buying narrative reveals the real job that questionnaires don't capture
✓
Job Stories replace User Stories — When [situation], I want [motivation], so I can [outcome]
✓
Ulwick’s ODI quantifies opportunities — Importance vs. Satisfaction maps where to innovate using data, not intuition
✓
JTBD only has value if it changes decisions — Discovery without roadmap changes is ritual, not a method

Next Module:

2.6 - OKRs for Innovation: aligning ambition with measurable execution

← Back to Track 2.6 - OKRs for Innovation →