Jobs to Be Done Framework Explained (With Examples)

The Jobs to Be Done framework says customers don't buy products; they hire them to get a job done. Once you understand the job, you can design, position, and price around real motivation rather than assumed demographics.

What "jobs to be done" actually means

The idea, popularized by Clayton Christensen, is deceptively simple: people make purchases to make progress in their lives. That progress is the "job." The product is just the thing they hire to do it.

A milkshake isn't bought because someone is a "milkshake person." It's hired in the morning to keep a commuter full and give them something to do during a long, boring drive. That same milkshake is hired in the afternoon by a parent to treat a child. Those are two completely different jobs with different competitors, different buying criteria, and different improvements that matter.

This reframe matters because most segmentation slices customers by who they are (age, role, company size) rather than why they act. Demographic and firmographic data predicts what people look like, not what they're trying to accomplish. JTBD gets you to motivation.

If you want to see how segmentation can mislead strategy, Customer Segmentation Methods for Small Business goes deeper on where the standard approaches break down.

The three parts of a job

Every job has three layers:

• Functional job: The practical task. "Get my weekly expense reports submitted on time."
• Emotional job: How the person wants to feel, or not feel, while doing it. "Not feel like an idiot in front of finance."
• Social job: How the person wants to be perceived by others. "Look organized and on top of things."

Most product teams optimize hard for the functional job and ignore the other two. That's why products that check every feature box still lose to ones that feel better or make people look better.

The "hire and fire" metaphor

Customers fire one solution when they hire another. Understanding what people currently use to get the job done tells you everything about your real competition. If your project management tool is being hired to replace sticky notes and a shared Google Doc, your competition isn't Asana. It's inertia and free tools. That's a very different positioning challenge.

A worked example: B2B expense management software

A 12-person SaaS company was building expense management software. They had solid functionality: receipt scanning, approval workflows, and sync with QuickBooks. After 18 months they had 41 paying accounts and were stuck at roughly $18,000 MRR with almost no word-of-mouth growth.

They ran JTBD interviews with 12 customers. What they found:

• Finance managers hired the tool to avoid month-end panic, not to "manage expenses." The trigger wasn't the existence of receipts; it was the dread they felt the week before close.
• Operations leads hired it to stop being the person employees complained to about slow reimbursements. The job was reducing conflict, not improving efficiency.
• Founders hired it mostly to feel like a real company, not to save time.

Those are three different jobs. The company had been messaging on feature parity with competitors, which spoke to no job particularly well.

After reorienting their onboarding and homepage copy around the "month-end panic" job (the most common one, representing roughly 60% of their base), they saw trial-to-paid conversion go from 14% to 22% in eight weeks. They didn't change a single feature. They changed how they described the problem they solved.

How to run a JTBD customer interview

JTBD interviews are different from standard user interviews. You're not asking people what they want in a product. You're reconstructing a purchase decision like a detective reconstructs a crime scene. The goal is to understand the timeline from first awareness of a problem to the moment they bought or switched. Every detail in that timeline is a data point.

Step-by-step interview guide

Before the interview

• Recruit people who recently made a purchase decision. Within 60 to 90 days works best; memory is clearest.
• Target switchers, not just happy users. People who switched from a competitor or from doing nothing give you the richest signal.
• Keep sessions to 45 to 60 minutes. You're going deep on one decision, not surveying broad behavior.

Opening: find the moment of purchase

Start here, not with the product:

"Walk me through the day you decided to buy. What was happening that week?"

You want the narrative, not the answer. Let them talk. The emotional texture of the story is the data.

Middle: work backwards to find the trigger

Key questions:

• "What was going on in your life or work that made this a priority right now, and not six months ago?"
• "What were you using before? Why wasn't that working anymore?"
• "Who else was involved in the decision? What were they worried about?"
• "What almost made you not buy it?"

Probe for the "first thought." When did they first realize something needed to change? That moment is often the real job, not the search for a solution.

End: map the emotional and social layers

• "How did you feel after you bought it? What did you hope would be different?"
• "Did you tell anyone you'd made the switch? What did you say?"
• "If this stopped working tomorrow, what would you do?"

That last question reveals your real competition.

After the interview

Transcribe or take notes on three things: the trigger, the struggling moment, and the exact words they used to describe the job. That language is your copywriting.

JTBD interview quick-reference

Run eight to twelve interviews before drawing conclusions. Patterns emerge quickly; you'll hear the same trigger language by the fifth or sixth conversation.

The most common JTBD mistake

Defining the job at the product level instead of the customer's level.

Teams new to JTBD often write job statements like: "Help me track my expenses faster." That's a feature description wearing a job costume. It describes what the product does, not what progress the customer wants to make.

A real job statement sounds like this: "When I'm approaching month-end close and receipts are scattered everywhere, I want to feel confident I won't miss anything so I don't have an awkward conversation with my CFO."

That statement captures the functional trigger (month-end close, scattered receipts), the desired outcome (confidence, completeness), and the emotional job (avoid an awkward conversation). You can design a product, write copy, and build an onboarding flow directly from it.

The test: if your job statement could appear on your product's settings page, it's too narrow. If it could describe what a person wants from five different products or approaches, you're at the right level.

Where JTBD fits in your broader strategy work

JTBD is primarily a discovery tool. It tells you what to build and how to talk about it. It doesn't tell you whether a market is worth entering or how to beat a well-funded competitor.

For the competitive layer, pair JTBD findings with a competitive analysis to understand who else is being hired for the same job and how customers compare options. Knowing the job also tells you who your real competitors are, which often isn't who you assumed.

For go-to-market, JTBD interview findings map directly into messaging and channel decisions. When you know the exact moment someone starts looking (the trigger), you know where to reach them and what to say. That feeds directly into building your go-to-market strategy.

JTBD also improves prioritization. When five features are competing for one sprint and data is scarce, knowing which job is most common and most urgent makes the call easier. That kind of constrained decision-making is covered in more depth in how to make better decisions under uncertainty.

When JTBD is not the right tool

JTBD works best when:

• Customers make a deliberate purchase decision, not a habit-driven one.
• You're in early-stage product discovery or repositioning.
• You suspect your current customers aren't your ideal customers.

It adds less value when:

• You're optimizing an existing funnel with plenty of behavioral data already.
• The purchase is commoditized and mainly price-driven.
• You're in a regulated market where customer choice is heavily constrained.

In those cases, lean harder on behavioral analytics and quantitative testing than on qualitative interviews.

Key takeaways

• JTBD reframes the question from "who is our customer?" to "what progress is our customer trying to make?" That shift surfaces the real competition and the real opportunity.
• Every job has three layers: functional (what needs doing), emotional (how they want to feel), and social (how they want to be seen). Most teams only optimize for the first.
• JTBD interviews focus on reconstructing a past purchase decision, not asking customers what they want. Recruit recent switchers and probe for the trigger moment.
• Define jobs at the customer's level, not the product's level. If your job statement reads like a feature description, rewrite it.
• JTBD is a discovery tool, not a strategy tool. Pair it with competitive analysis and positioning work to translate insights into market decisions.
• Eight to twelve interviews is usually enough to identify the two or three core jobs driving most of your market. More interviews refine; they rarely overturn.