The Jobs-To-Be-Done (JTBD) Framework: A Practical Guide

People do not buy products. They "hire" them to make progress in a situation they are stuck in. That is the core idea behind Jobs-To-Be-Done (JTBD): the unit of analysis is not the customer's demographics or the product's features, but the job the customer is trying to get done. Understand the job well enough and your product decisions, messaging, and sales conversations all get sharper. This guide covers what a job is, how to write a job statement, how to interview for one, and how to actually use it.

What "job" actually means

A job has three dimensions, and skipping any of them leads to shallow conclusions:

• Functional — the practical task. "Keep track of which deals need a follow-up."
• Emotional — how the person wants to feel. "Not look disorganized in front of my boss."
• Social — how they want to be perceived. "Be seen as the rep who never drops a lead."

A spreadsheet does the functional job. It fails the emotional and social ones the moment a deal slips through the cracks. That gap — functional job met, emotional and social jobs unmet — is where better products win.

Jobs are also stable while solutions churn. The job "get a meal I do not have to cook" has been hired out to diners, frozen dinners, and delivery apps across decades. Anchoring on the job instead of the current solution is what keeps you from being disrupted by the next one.

The forces that drive a switch

JTBD models a purchase as a struggle between four forces:

• Push of the current situation — the problem that makes the status quo painful.
• Pull of the new solution — the attraction of a better outcome.
• Anxiety about the new solution — fear it will not work or will be hard.
• Habit of the present — inertia and comfort with what exists.

A switch happens only when push plus pull beats anxiety plus habit. This is a genuinely useful lens for sales and marketing, because it tells you the two levers you often ignore: you can win not only by increasing pull (more features, better pitch) but by reducing anxiety (proof, guarantees, easy onboarding) and weakening habit (making migration trivial).

Writing a job statement

A clean job statement follows the form: verb + object + context, phrased in the customer's terms and free of any solution.

• Weak: "Customers want a CRM." (That is a solution, not a job.)
• Better: "When a lead comes in from three different channels, I want to see all of them in one place, so I do not respond twice or miss one entirely."

Notice the structure: a triggering situation ("when…"), a motivation ("I want to…"), and an intended outcome ("so I…"). If you can only describe the job by naming your product, you have not found the job yet.

How to interview for a job

You do not discover jobs from surveys or feature requests. You discover them by reconstructing the timeline of a real, recent purchase. The most useful interview walks a customer backward from the moment they started using something new:

1. When did you first realize you needed a different solution? (Finds the first push.)
2. What were you using before, and what specifically frustrated you? (Maps the old job and its gaps.)
3. What made you finally look? (The triggering event — often a specific incident, not a slow drift.)
4. What almost stopped you from switching? (Surfaces anxiety and habit.)
5. What did "it's working" look like once you switched? (Defines the outcome, i.e., the real success criteria.)

The specifics matter more than the generalities. "I lost a deal because two of us emailed the same lead" is a job. "I wanted to be more efficient" is noise.

A worked example

A five-person startup sells a tool and captures leads from a website form, WhatsApp, and Facebook Lead Ads. Interviews with three churned trial users reveal the same story: leads landed in three inboxes, two reps sometimes contacted the same person, and follow-ups slipped.

Turn that into a job statement: "When leads arrive from several channels at once, I want them unified and assigned automatically, so no lead is contacted twice or forgotten."

Now apply the forces:

• Push: losing deals to duplicate and dropped follow-ups.
• Pull: one inbox, automatic assignment, nothing slips.
• Anxiety: "will it capture every channel we use?"
• Habit: "we already have a shared Gmail label system."

This reframes the roadmap. The winning move is not another dashboard (more pull) — it is proving complete multi-channel capture (kill the anxiety) and making setup take minutes (beat the habit). The same statement rewrites the sales pitch: lead with the duplicate-contact pain, not a feature list. One well-built job statement drove product, positioning, and sales at once.

Common mistakes with JTBD

A few traps catch teams the first time they try this:

• Confusing solutions with jobs. "Customers want a mobile app" is a solution. The job might be "check on my pipeline while I'm away from my desk." Name the job, then decide whether an app is even the right answer.
• Writing jobs at the wrong altitude. "Grow my business" is too broad to act on; "assign incoming leads before a rep double-contacts them" is actionable. Aim for the level where a design or messaging decision changes.
• Interviewing for opinions instead of history. Asking "what features would you like?" invites made-up answers. Reconstructing a real past purchase surfaces what people actually did.
• Treating the job as static within a segment. The same person hires different solutions in different contexts. The triggering situation is part of the job, not a footnote.

Jobs across the buying committee

In B2B, one purchase usually serves several jobs at once. The end user's job might be "stop losing leads," while the manager's job is "get visibility into the team's pipeline," and the approver's job is "not overspend on tools that go unused." These jobs can conflict — the feature that delights the user may be the one the approver sees as risk. Mapping the distinct job for each person in the buying committee, and the forces acting on each, tells you which objection to address for whom. A pitch that nails the user's job but ignores the approver's anxiety stalls at exactly the moment budget gets approved.

Turning jobs into decisions

A job is only useful if it changes what you do:

• Product: prioritize the features that complete the job's unmet emotional and social dimensions, not just the functional one.
• Messaging: open with the triggering situation and the push, so the reader thinks "that's me."
• Sales: diagnose which of the four forces is blocking each deal, then address that specific force.

How Inleads helps

JTBD works best when you can see the real situations that trigger a switch, and most teams cannot, because the evidence is scattered across channels and disconnected from what people do next. Inleads pulls the raw material for job discovery into one place. Multi-channel capture (web forms, WhatsApp, Facebook Lead Ads, LinkedIn, NPS, API/SDK) collects the touchpoints where a job first shows up, and the customer data platform unifies them into a single profile, so you can see the actual sequence a customer took rather than a fragmented guess. NPS capture is a direct line to the emotional and social sides of a job — why someone would or would not recommend you. Because product analytics and the CRM live together, you can tie what a person said about their job to what they then did in the product, using the AAARRR funnel to spot exactly where an unmet job causes people to stall. The AI copilot built into the CRM can help synthesize notes and NPS responses into recurring themes. See how capture works on the lead capture page and the analytics on the product analytics page.