# JTBD (Jobs To Be Done): What It Is and How to Apply It

- URL: https://vladimirnovozhilov.com/en/blog/jtbd-jobs-to-be-done-metodologiya/
- Author: Владимир Новожилов
- Published: 2026-08-31
- Category: Product marketing

> JTBD (Jobs To Be Done) is a methodology explaining that people 'hire' products to get a specific job done and achieve a desired outcome. This article covers the theory, its history from Clayton Christensen to Outcome-Driven Innovation, a JTBD interview template, job statement writing, differences from personas and CJM, real-world examples, and a step-by-step implementation plan.

If you've ever wondered why a product with great features doesn't sell while a competitor with a simpler solution keeps growing — chances are you were describing the customer instead of the customer's job. **JTBD (Jobs To Be Done)** flips this lens: instead of asking "who is our user," you start asking "what job does this person want done, and why do they hire our product specifically to do it." In this article, we'll break down what JTBD is, how the JTBD theory works, how to run a JTBD interview, what a job statement looks like, and how to apply the methodology in product and marketing to lift conversion and reduce churn.

## What is JTBD (Jobs To Be Done): the essence of the methodology

**Jobs To Be Done** (literally "work to be done" or "jobs that need doing") is a methodology that explains customer behavior through the task at hand rather than through customer traits. The core idea: people don't buy products for their own sake — they "hire" them to make progress toward a desired outcome in a specific life situation.

When someone runs into a situation where the current state of affairs doesn't satisfy them, they get a **customer job** — a job they want done. For them, the product is just a tool, an "employee" they hire to do the work. If the tool delivers, it gets "rehired"; if not, it gets "fired" and replaced with something else. Hence the methodology's central metaphor — **hiring a product**.

A simple example: a person doesn't buy a drill — they buy "a clean hole in the wall to hang a shelf and make the room feel cozier." The drill is just one candidate for that job; the shelf could also be hung with adhesive strips or by calling a handyman. Once you understand the real job, you're competing not with other drills but with every possible way to get that job done.

### How JTBD differs from the conventional approach

Classic marketing starts with segmentation by demographics and behavior. The problem is that a "35-year-old male manager" might hire the exact same product for completely different jobs, while two very different people might hire it for the same job. The JTBD methodology makes the unit of analysis not the person but the **job**, which is far more stable over time: the job of "grabbing a quick bite on the road" hasn't changed in decades, even as the ways to solve it have evolved.

This delivers three practical benefits:

- **Stability.** Jobs outlive technologies and segments, so a strategy built on jobs is more durable.
- **Precision.** You understand the real reason behind a purchase or switching behavior, rather than attributed motives.
- **Innovation.** You can see where current solutions fall short — and that's where product growth opportunities live.

## History of JTBD: from Clayton Christensen to Outcome-Driven Innovation

The methodology has two parents and two complementary branches.

**Clayton Christensen**, a Harvard Business School professor and author of the theory of disruptive innovation, popularized the idea in the 2000s. His famous line goes: "People don't want a quarter-inch drill — they want a quarter-inch hole." Christensen provided the philosophical framework: a product is hired for a job, and the job has functional, emotional, and social dimensions. He's also behind the famous **milkshake marketing case**, discussed below.

**Tony Ulwick**, founder of Strategyn, took it further and turned JTBD theory into a measurable engineering process — **Outcome-Driven Innovation (ODI)**. Ulwick argues that every job has a set of **desired outcomes** — results that can be framed as metrics: "minimize the time it takes to…", "reduce the likelihood that…". Each outcome is rated by importance and satisfaction, and the intersection of "important but underserved" reveals opportunities for the product.

This is how two schools of the **Jobs to Be Done framework** emerged, and it's useful to distinguish them:

- **Jobs-as-progress (the switching / forces school)** — focuses on the purchase story, emotions, and the forces pushing a person to switch solutions. Closer to marketing and positioning.
- **Jobs-as-activities (Ulwick's Outcome-Driven Innovation)** — focuses on breaking the job into steps and measurable outcomes. Closer to product development and prioritization.

In practice, combining both works best: the switching approach explains why the customer came to you in the first place, and ODI shows exactly what to improve in the product.

## How JTBD theory works: "hiring" a product to get a job done

To apply JTBD theory, you need to understand the mechanics of decision-making. At the moment a person considers "hiring" a new solution, four **forces of progress** act on them:

1. **Push.** The pain and discomfort of the current situation: the old solution is frustrating, the job isn't getting done.
2. **Pull.** The appeal of the new solution: the promise of a better outcome.
3. **Anxiety.** Fear of the new: "what if it doesn't work," "migrating data sounds hard."
4. **Habit.** Inertia toward the current solution: "it's good enough," too much effort to switch.

A purchase happens when **Push + Pull outweigh Anxiety + Habit**. This is critical for marketing: most teams only pump up Pull (listing features) while ignoring anxiety and inertia. Yet anxiety is often exactly what kills a deal in B2B and IT, where switching vendors or systems feels risky.

![Forces of progress determine whether a customer buys or sticks with the old solution](./images/jtbd-jobs-to-be-done-metodologiya-forces.png)

This framework is a working tool. When analyzing any purchase decision, write out all four forces in the customer's own words. Then, in your communication, amplify Push and Pull while systematically neutralizing Anxiety (case studies, guarantees, free migration, pilots) and Habit (an easy first step, turnkey onboarding).

### Types of jobs: functional, emotional, and social

Every job has multiple layers. The same purchase typically addresses several types of tasks at once, and a strong methodology accounts for all three.

| Job type | What it solves | Customer's question | Example in B2B/IT |
|---|---|---|---|
| **Functional job** | A practical task, an objective result | "What do I need to accomplish?" | Pull together a report in 10 minutes instead of two hours |
| **Emotional job** | An internal state, self-perception | "How do I want to feel?" | Not worrying that data will be lost or a deadline missed |
| **Social job** | How others perceive them | "How do I want to appear?" | Looking like a competent manager in front of the team and leadership |

A common beginner mistake is seeing only the functional job. But in services and B2B, decisions are often driven by the emotional and social components: a manager picks the "safe" vendor to avoid personal risk. If you only address the function, you lose to a competitor who also relieves fear and reinforces the buyer's status.

## JTBD vs. personas, CJM, and empathy maps: what's the difference

JTBD doesn't replace other tools — it answers a different question. Personas answer "who," the customer journey map answers "how the journey unfolds," the empathy map answers "what they feel," and JTBD answers "why and for what purpose." Below is a comparison table that most Russian-language write-ups skip.

| Criterion | JTBD | User personas | Customer Journey Map | Empathy map |
|---|---|---|---|---|
| **Main question** | What job is the customer doing, and why do they hire the product | Who is our typical user | How does the customer move toward their goal | What does the customer think, feel, see, hear |
| **Unit of analysis** | The job and its outcome | A person's profile (demographics, behavior) | Stages and touchpoints | Emotional state |
| **Stability over time** | High — jobs change slowly | Low — segments become outdated quickly | Medium | Medium |
| **What it gives the product** | Purchase drivers, growth opportunities, priorities | Communication tone, audience empathy | Bottlenecks and gaps in experience | Understanding of barriers and motives |
| **Risk when used in isolation** | Abstraction without interview data | Stereotypes instead of real motives | A pretty diagram with no explanation of behavior | Guesswork without facts |
| **Pairs best with** | ODI, switching interviews | JTBD and CJM | JTBD and metrics | JTBD and interviews |

Practical takeaway: **start with JTBD** — it lays the foundation of real motives. Then overlay the jobs you found onto a customer journey map to see the stages, and use personas as a "packaging" tool to keep the team empathetic to the audience. That way each tool does its own job instead of duplicating another.

## How to write a Job Statement: structure and examples

A **Job Statement** is a short formulation of the customer's job that doesn't mention your product. A proper JTBD statement describes the situation, the motivation, and the desired outcome in a way that fits any possible solution to the task, including non-obvious competitors.

The classic structure (switching school):

> **When** [situation/trigger], **I want to** [motivation/action], **so that** [desired outcome].

Examples of strong statements:

- "When I'm driving alone to work, I want to keep myself occupied and not get hungry, so the long commute feels shorter" (the famous milkshake).
- "When I need to report on a project to leadership, I want to quickly put together a clear summary, so I look in control and don't have to spend my evening on it."
- "When a new employee joins the team, I want to quickly give them access to the knowledge base, so they reach full productivity in a week instead of a month."

In the Outcome-Driven Innovation school, the statement is closer to a verb-plus-object phrasing: "listen to music on the go," "track order status." The desired outcomes attached to it are written as metrics: "minimize the time spent finding the right track," "reduce the likelihood of missing an important notification."

### Job statement checklist

Before treating a job statement as final, run it through these criteria:

- **No mention of the product.** No brand names, no features, no technologies — only the job.
- **A situation (trigger) is present.** It's clear when and in what context the job arises.
- **A desired outcome is present.** It's clear what the customer wants to achieve, not just what to do.
- **Stability.** The statement won't become outdated if the underlying technology changes.
- **Measurability.** The outcome can be tied to a metric (time, money, risk, effort).
- **Customer's language.** The statement sounds like the customer's own words, not your marketing jargon.
- **One job per statement.** Don't lump several tasks into one phrase.

If a statement passes all seven points, it's a workable job statement you can rely on in product and communication decisions.

## JTBD interviews: how to run them and what to ask

A **JTBD interview** is an in-depth interview that reconstructs the real purchase story — from the moment a person first started thinking about a solution to the deal itself and first use. The goal isn't to find out "what do you like," but to reconstruct the timeline and the forces of progress that led to hiring the product.

The main rule: **work with real, recent purchases, not hypotheticals**. People are poor predictors of future behavior, but they recall specific events reasonably well when guided along a timeline.

### How to structure a JTBD interview

1. **Find the "first thought" moment.** When did you first realize you needed a solution like this? What was happening in your life/work at the time?
2. **Reconstruct the triggers.** What pushed you to start looking? Was there a specific event, or did it build up gradually?
3. **Explore the alternatives considered.** What options did you look at? What did you compare it to (including "doing nothing" or manual workarounds)?
4. **Capture the decision moment.** What tipped the scale? What almost stopped you?
5. **Uncover anxieties and habits.** What were you afraid of when switching? What kept you from changing?
6. **Follow through to first use.** Did it live up to expectations? What was the "moment of value"?

### JTBD interview question template

Here's a JTBD template you can copy and adapt to your product. This is a ready-made set of questions for a JTBD interview — save it as a base for your guide.

| Stage | Question |
|---|---|
| Trigger | "Think back to the moment you first realized you needed a solution like this. What was happening then?" |
| Trigger | "What exactly stopped satisfying you about how you were handling this before?" |
| Search | "What options did you consider? What else came to mind besides buying something?" |
| Search | "Where did you look for information, who did you talk to?" |
| Anxieties | "What worried you before making the decision? What were you afraid of?" |
| Inertia | "What made it tempting to just leave things as they were?" |
| Decision | "What was the last straw that made you commit?" |
| Expectations | "What did the ideal outcome look like to you?" |
| Usage | "When did you first feel that the solution actually worked?" |
| Wrap-up | "If this product disappeared tomorrow, what would you do?" |

Ideally, run 8–12 such interviews per job type — after about the tenth conversation, patterns usually start repeating and new insights become rare.

### Common mistakes when running JTBD interviews

Most articles skip this, yet these mistakes recur project after project:

- **Asking about the future and hypotheticals** ("Would you buy if…") instead of the real story. Hypothetical answers are almost always misleading.
- **Asking leading questions** ("Speed matters to you, right?") and getting an echo of your own assumptions back.
- **Focusing on the product** rather than the job — missing the real competitors.
- **Ignoring emotions and the social layer**, staying limited to function.
- **Only interviewing happy customers**, losing the insights of those who churned or never bought (which is exactly where the real churn drivers hide).
- **Not digging into the trigger** — the most valuable piece, because the trigger tells you exactly when to switch on marketing.

## A step-by-step plan for implementing JTBD in product and marketing

Theory is useless without implementation. Here's a working, step-by-step plan for applying JTBD in product and marketing — seven steps a team goes through.

1. **Define the market through the job.** Formulate the customer's core job (not a segment), e.g., "keep team tasks organized" instead of "CRM for small business."
2. **Collect interview data.** Run 8–12 JTBD interviews with recent buyers and, crucially, with people who churned or declined to buy.
3. **Break the job into stages and outcomes.** Describe the steps of doing the job and list desired outcomes as metrics (time, effort, risk, cost).
4. **Write job statements.** Draft a set of statements using the checklist above — this becomes the core of your product and positioning.
5. **Find opportunity gaps.** Rate each desired outcome by importance and satisfaction. "Important but underserved" equals a product priority.
6. **Repackage marketing around the job.** Rewrite key messages from "we do X" to "you achieve outcome Y in situation Z," amplify Push/Pull, and neutralize Anxiety/Habit.
7. **Measure and repeat.** Track conversion, activation, and churn. Return to interviews whenever metrics or the market shift.

Step 6 matters especially in B2B and services: the product is often already good, but the messaging speaks the language of features rather than jobs. Simply repackaging messages around the real job can lift landing page conversion and lead quality without a single product change.

## JTBD in action: real-world examples

The best way to understand the methodology is to walk through real JTBD examples from practice.

### The milkshake marketing case (McDonald's)

A classic. A chain wanted to boost milkshake sales and spent a long time tweaking flavor and add-ins based on demographics. Christensen's team asked a different question: **what job are people hiring the milkshake for?** It turned out a large share of sales happened early in the morning: commuters bought a shake to keep themselves occupied on a long, boring drive and to avoid getting hungry before lunch. The real competitors weren't other milkshakes but bananas (gone too fast, messy), bagels (too dry), and coffee (spills).

The insight flipped the strategy: the shake needed to be **thicker** (so it lasts longer through the straw) and sold faster in the morning. Classic segmentation would never have revealed this. It's the textbook example of how the "hiring" lens explains real behavior.

### A B2B/IT case: fighting churn

A common scenario in subscription-based IT products and services: the team tries to cut churn with discounts and new features, but customers keep leaving. A series of switching interviews with churned customers reveals the true job: people didn't hire the service for its feature set — they hired it to **close out monthly reporting calmly, without stress**. Once the product stopped saving them that stress (the interface got more complex, onboarding got harder for new employees), the job stopped getting done — and customers "fired" the product.

The fix wasn't new features but returning to the original job: simplified onboarding, ready-made report templates, and removing anxiety at the start. This kind of focus on the customer's real job typically delivers a meaningful churn reduction — around a third — because you're fixing the cause, not the symptom.

![Typical impact after implementing JTBD in product and marketing](./images/jtbd-jobs-to-be-done-metodologiya-impact.png)

### A marketing case: repositioning

A team collaboration tool positioned itself as a "task management tool" and competed in an overcrowded category. JTBD interviews revealed that managers were hiring it for a social job — "see the big picture on the project and look in control in front of leadership." By shifting the key message from features to this outcome ("always know what's happening on the project and be ready for any question from leadership"), the team increased landing page conversion and got higher-quality leads. The product didn't change — the job it was being "hired" for in the messaging did. That's the essence of JTBD in marketing.

## How JTBD helps reduce churn and increase conversion

Let's connect the methodology to revenue. JTBD affects the funnel at three points:

- **Acquisition and conversion.** When the message matches the customer's real job and situation, relevance goes up: people recognize themselves. This is especially visible on landing pages and the first screen — conversion to a lead is higher, and leads are warmer.
- **Activation.** By understanding the "moment of value" (when the job is first accomplished), you can redesign onboarding so customers reach it faster. This is a key retention lever early in the lifecycle.
- **Retention and churn.** Churn is a signal that "the product stopped doing the job" or "a better performer was found." Switching interviews with churned customers reveal the exact cause, so you can fix it precisely instead of throwing discounts at the problem.

A practical rule: check every growth initiative against the question "what job does this help get done better?" If there's no answer, you're probably improving something the customer doesn't care about.

## Templates and tools for working with JTBD

To keep the methodology from staying purely theoretical, build a minimal working kit. Below is a JTBD template outline of artifacts your team should maintain.

| Artifact | What it contains | Where it's used |
|---|---|---|
| JTBD interview guide | List of questions by stage (see table above) | Research, customer development |
| Job statement map | Set of "When… I want… so that…" statements | Product, positioning |
| Forces of progress map | Push / Pull / Anxiety / Habit for a key decision | Marketing, sales |
| Desired outcomes table | Outcomes + importance + satisfaction | Backlog prioritization (ODI) |
| Job type map | Functional / emotional / social | Messaging, value proposition |

What matters: the tools themselves are secondary. You can track all of this in a plain spreadsheet — the value comes from quality interviews and honest prioritization, not a nicely designed template. Don't let filling out diagrams replace actually talking to customers.

## Pros and cons of the JTBD methodology

An honest look, without the evangelism.

**Strengths:**

- Focuses on the real reasons behind purchases and switching, not demographics.
- Stability: jobs outlive technologies and segments.
- A shared language for product, marketing, and sales.
- A direct path to prioritization (via desired outcomes) and positioning.
- Explains churn well and reveals growth opportunities.

**Limitations:**

- Requires quality interviews — the methodology is useless on weak data.
- Prone to abstraction: without discipline, job statements turn into vague phrases.
- Two schools (switching and ODI) confuse newcomers; you need to deliberately pick the right tool for the task.
- Doesn't replace quantitative research and metrics — it's a complement, not an alternative.
- Easy to slip into "cargo cult" behavior: drawing diagrams instead of actually changing the product and messaging.

Bottom line: JTBD is a powerful lens, but not a silver bullet. It delivers the most value when paired with analytics, CJM, and constant contact with customers.

## In short: how to start applying JTBD this week

To condense everything above into a short plan:

1. Pick one product and formulate a hypothesis about the customer's core job.
2. Run 5–8 JTBD interviews with recent buyers and one or two people who churned.
3. Reconstruct the timeline and the forces of progress, and identify the triggers.
4. Draft 3–5 job statements using the checklist above.
5. Rewrite your landing page's first screen around the job and outcome you found.
6. Measure conversion and churn, then repeat the cycle.

That's enough to see an initial effect and feel how JTBD theory turns into concrete decisions. Later, add a desired outcomes map and Outcome-Driven Innovation prioritization once you want to manage the product more systematically.

## FAQ on Jobs To Be Done

**What does the acronym JTBD stand for?** JTBD stands for Jobs To Be Done — "jobs that need to be done." It's a methodology that explains purchasing behavior through the customer's task and the metaphor of hiring a product.

**Where should you start implementing it?** With interviews. No template can replace 8–12 quality conversations with real buyers. Everything else is built on that data.

**Are JTBD and customer development the same thing?** No. Customer development is a broad process for testing hypotheses about customers. JTBD is a specific lens within it, focused on the job and the motives rather than on the people themselves.

JTBD doesn't require relearning everything — it requires changing the question you ask. Stop describing who your customer is and start figuring out what job they want done and why they hire your product specifically to do it. That single question is where higher conversion, lower churn, and clear positioning all begin.

## FAQ

### What is JTBD in simple terms?

JTBD (Jobs To Be Done) is an approach where you look not at customer characteristics but at the task the customer wants to solve. People 'hire' a product to make progress toward a desired outcome in a specific life situation. Understanding this job lets you build a more precise product, positioning, and marketing.

### How does JTBD differ from user personas?

Personas describe who the customer is: age, gender, job title, habits. JTBD describes what the customer is trying to accomplish and why. Very different people 'hire' the same product for the same job, so JTBD is more stable than demographics and explains real purchase and switching decisions more accurately.

### How do you write a proper job statement?

Use the structure 'When [situation], I want to [motivation/action], so that [desired outcome].' The statement should avoid mentioning your product or specific features, remain stable over time, and be measurable by outcome. Example: 'When I'm driving alone to work, I want to keep myself occupied and not get hungry, so the commute feels shorter.'

### What questions should you ask in a JTBD interview?

Ask about the purchase history: when they first started thinking about a solution, what was happening in their life, what alternatives they considered, what triggered the decision, and what doubts they had. The goal is to reconstruct the timeline and forces of progress, not to ask 'what do you like.' Work with real, recent purchases rather than hypotheticals.

### Does JTBD work in B2B and IT?

Yes. In B2B and IT, a job often has functional, emotional, and social components: getting the task done, reducing personal risk, and looking good to leadership. JTBD helps you articulate value more precisely, reduce churn, and increase conversion because it focuses the product and communication on the customer's outcome.

### Who created the Jobs To Be Done methodology?

The idea was popularized by Clayton Christensen of Harvard Business School, while the practical, measurable Outcome-Driven Innovation framework was developed by Tony Ulwick. Christensen provided the 'hiring a product' philosophy, and Ulwick provided the metrics and the desired-outcomes method that underpin modern product and marketing practices.