Jobs to Be Done (JTBD): What It Is, Examples and How to Apply It

Table of Contents

• Summary: JTBD vs. traditional segmentation
• What is Jobs to Be Done: customers "hire" solutions

  • The milkshake case
  • The three dimensions of a "job"
• The 4 forces of progress

  • How to apply them to your web copy and onboarding
• How to run a JTBD timeline interview

  • The timeline milestones
  • Questions for your interview
• From interviews to the roadmap: the 8 stages of the customer's job
• Validate fast with no-code tools
• Action plan: apply JTBD this week

Jobs to Be Done (JTBD) is a framework for understanding why people buy: not because of what your product is, but because of the progress they want to make when they "hire" it. It helps you decide what to build, how to explain it and what to change in onboarding, before you spend months on features nobody asked for.

This guide explains the core idea, the three dimensions of a "job", the 4 forces of progress, how to run a timeline interview (with questions ready to use) and a five-step plan you can apply this week.

Summary: JTBD vs. traditional segmentation

Criterion	Traditional segmentation (buyer persona)	Jobs to Be Done
Core question	Who is my customer?	What progress are they trying to make, and in what circumstance?
Variables	Age, location, role, habits	Context, trigger, alternatives, anxieties
How it's used	Decide who to talk to	Decide what to build and what to say
Risk if used alone	Features based on assumptions about the profile	You lose sight of which segment to reach

It's not a fight between methods. A buyer persona gives you the "who"; JTBD gives you the "why now". The best teams use both.

What is Jobs to Be Done: customers "hire" solutions

The core idea of JTBD is that customers don't buy products: they hire them to make progress in a given circumstance. Clayton Christensen popularized it in the innovation world, and Bob Moesta and Anthony Ulwick developed it through different methods: Moesta with timeline interviews and the forces of progress, Ulwick with outcome-driven mapping.

Instead of "who is the customer and what features do they want?", the question becomes: what is this person trying to get done, and what solution would they hire to do it? Technology is interchangeable; what stays stable is the job the person wants to get done.

The milkshake case

The classic example: a fast-food chain wanted to sell more milkshakes. Surveys about flavor and texture moved nothing. By observing who bought in the morning, a different job appeared: people with a long commute who wanted something to keep them entertained, that could be drunk with one hand and that kept them full until lunch. The competitors weren't other shakes, but bananas, donuts and bagels.

The lesson for a digital product is the same: your real competition is not the one in a feature table, but everything the customer uses today to get the job done, including an Excel sheet or a notebook.

The three dimensions of a "job"

A job is not just a task. It has three layers, and a buying decision is almost always explained by all three at once:

• Functional: the practical task. For example, charging subscriptions every month or consolidating a team's sales reports.
• Emotional: how they want to feel. For example, peace of mind that there will be no calculation errors or forgotten charges.
• Social: how they want to be perceived. For example, as an organized, analytical person in front of their boss or board.

If you only solve the functional layer, your product competes on features. If you also speak to the emotional and social ones, you compete on something customers do remember.

The 4 forces of progress

For someone to leave what they use today and adopt something new, the forces driving them must outweigh the forces holding them back. There are four:

1. Push of the current situation: today's frustrations and pains. It's what starts the search.
2. Pull of the new solution: what the new product promises and the result the person imagines.
3. Anxiety about change: fear of migrating data, of the learning curve, of it failing or of losing money.
4. Habit and inertia: the comfort of "how it's always been done", even if it's inefficient.

Push and pull move people to buy; anxiety and habit hold them back. Most sales pages work only on the pull (more features, more promises) and forget that many sales are lost to anxiety and habit.

How to apply them to your web copy and onboarding

Communicate push and pull in the headline, and reduce anxiety and habit in the supporting text and buttons.

Before (feature-centered):

"We are the leading AI-powered SaaS management software for small businesses. It includes invoicing, inventory and advanced reporting modules."

After (progress-centered):

• Headline (push + pull): "Losing sales and making mistakes charging your subscriptions by hand in Excel? Automate recurring billing and take back control of your cash flow."
• Microcopy and buttons (anxiety + habit): "No credit card. We help you import your data. Cancel anytime."

The same logic applies after sign-up. If the user stalls because of uncertainty or inertia, a generic newsletter won't help. Event-based messaging tools like Loops or Customer.io let you trigger a useful message when a milestone happens, or doesn't: signed_up, created_first_project, payment_failed. If someone signed up but didn't create their first project within 48 hours, they get the exact help to take that step.

How to run a JTBD timeline interview

The timeline interview reconstructs, step by step, how a person came to buy (or cancel). You talk about concrete past events, not future intentions, because people are bad at predicting what they will do and very good at telling what they already did.

The timeline milestones

This is an adaptation of the outline Moesta uses; your interview should cover these moments:

1. First thought: the moment the person notices something isn't working or could be better.
2. Passive search: they pay attention to recommendations and content, without investing time or money.
3. Active search: they compare tools, request demos, evaluate alternatives.
4. Trigger event: the concrete event that turns annoyance into urgency: a failure, an expensive mistake, a change in the team.
5. Decision: they commit: pay, sign or register.
6. First use: they find out whether the product delivers on its promise or creates friction.

The trigger event is the most valuable data point: it tells you when your product becomes relevant and, therefore, where and when to show up.

Questions for your interview

Run the conversation like an investigator reconstructing a scene. Ask for physical, concrete details (where they were, what screen they had open) because detail activates memory and reduces the bias of saying what they think you want to hear.

To isolate the trigger event

• "Tell me about the day you decided to look for another solution. What happened that week that hadn't happened before?"
• "Where were you, what did you have open on screen and what were you trying to do when you thought: I can't go on like this?"

To explore the search and alternatives

• "Before signing up, what other tools, spreadsheets or processes did you try?"
• "Who did you ask for recommendations? What did you type into Google or ChatGPT when you started comparing?"

To uncover anxieties and habits

• "Right before paying or signing, was there any doubt that almost stopped you?"
• "How hard was it to leave your previous system or convince your team? What was most confusing in your first 15 minutes of use?"

Avoid questions like "would you pay for this?" or "would you like it to have X?". They produce polite, unreliable answers. For more practice with this kind of conversation, the guide to the Steve Blank method explains how to go talk to customers before building.

From interviews to the roadmap: the 8 stages of the customer's job

Ulwick proposes splitting any job into eight stages, useful for locating exactly where your customer suffers:

1. Define: plan and set goals.
2. Locate: gather the data or materials needed.
3. Prepare: set up the environment, tools and data.
4. Confirm: check everything is ready before acting.
5. Execute: perform the core task.
6. Monitor: check progress and quality.
7. Modify: adjust and correct.
8. Conclude: close, save or export the results.

When interviews reveal strong friction in one stage, that friction becomes a priority in your backlog, instead of adding features by gut feeling. An illustrative example:

Friction in "Prepare": users lose hours cleaning and formatting data before they can analyze it.

• Product priority: one-click import and automatic connectors.
• B2B message (team efficiency): "Eliminate the manual work of preparing data. Connect your CRM and centralize reports for leadership."
• B2C message (speed and simplicity): "Forget the Excel mess. Upload your file with one click and see your results instantly."

It's the same friction, but it translates differently depending on whether a company is buying (it cares about team time and control) or an individual (they care about speed and simplicity). If you need to organize the whole value proposition, the interactive Business Model Canvas helps connect the job to segments, channels and revenue.

Validate fast with no-code tools

Once you know which job to solve, you don't need months of development to test it. AI builders like Lovable or Emergent let you stand up an MVP with authentication and payments in a matter of days, and Lovable connects to Supabase and lets you export the code to GitHub so you aren't locked into the platform. Before choosing one, check current pricing and limits: they change often.

The tool matters least; what matters is measuring with real data whether anyone pays to solve that job. If you want to go deeper down that path, see the guide to building a Micro-SaaS with AI and the one on validating a business idea in a week. And before setting a price, calculate your margin with the profit margin calculator.

Action plan: apply JTBD this week

1. Interview 5 recent customers. Choose people who bought or cancelled in the last 30 days. Rebuild their timeline and note the trigger event and the alternatives they tried. If you don't have customers yet, interview people who solve the problem today with another tool or by hand.
2. Map the 4 forces. Move your findings into a matrix of push, pull, anxiety and habit, with verbatim quotes. Patterns that repeat in three or more people are your priorities.
3. Rewrite your message and onboarding. Change the headline to talk about progress, add guarantees that lower anxiety and set up event-based messages (with Loops, Customer.io or similar) for the points where people stall.
4. Prioritize the roadmap by friction. Place each friction in one of the 8 stages and solve the heaviest one first.
5. Validate with an MVP and real payment. Measure conversion and willingness to pay before scaling the architecture.

JTBD doesn't replace judgment or market analysis; what it does is shift the conversation from "what features do I add" to "what progress does my customer need". With five well-run interviews you'll have more clarity than with months of assumptions.