Jobs to be Done

First PublishedMay 24, 2026Last UpdatedMay 25, 2026ByAtif Alam

The decision this page enables: what job the customer is hiring your product to do — and what they’ll fire to make room for it.

What it is

Jobs to be Done (JTBD) is a framing from Clayton Christensen: people don’t buy products, they hire products to make progress on a job. The classic example: someone doesn’t buy a quarter-inch drill; they buy a quarter-inch hole. They don’t buy the hole; they buy a place to hang the family photo. They don’t buy a place to hang the family photo; they buy “I belong here.”

JTBD pairs well with buyer personas. Personas describe who you serve; JTBD describes what they’re trying to accomplish. The same person hires different products for different jobs in different contexts.

Why it matters

• It surfaces non-obvious competition. The competition for a unified-workspace tool isn’t only other workspace tools — it’s a custom-built internal script, a brittle Zapier, or “we just live with it.” All of those are hired for the same job.
• It clarifies positioning: lead with the job (outcome), not the feature (mechanism).
• It directly feeds the positioning statement template and the Workbook → Audience & message → Core message.

The shape of a job

A job has three layers of outcome that all matter:

flowchart LR
    Job["Job<br/>(situation + motivation)"] --> Func["Functional outcome<br/>what gets done"]
    Job --> Emo["Emotional outcome<br/>how it feels"]
    Job --> Social["Social outcome<br/>how it looks to others"]
    Func --> Hire["Hire / fire criteria"]
    Emo --> Hire
    Social --> Hire

The job is the situation + motivation. The three outcomes (functional, emotional, social) are how the customer evaluates a candidate solution. The hire/fire criteria are the specific things that make them switch from one solution to another.

Most teams over-index on functional outcomes and underweight emotional/social outcomes — especially in B2B, where the social outcome (looking competent to peers) is often the strongest driver.

How to find the job

A simple 4-step process:

1. Listen for situations and progress, not features. In discovery interviews, follow up on “the last time I had to…” and “I really need to…” — these are job-flagging phrases.
2. Identify the switch. When did the customer last switch tools or processes for this job? What forced the switch?
3. Triangulate three outcomes. For the same job, name the functional, emotional, and social outcome. If one of the three is empty, push harder in interviews.
4. Write the job statement (template below) and pressure-test it against 3-5 real customers.

The four forces of progress (when a customer switches)

Bob Moesta’s extension of JTBD: when a customer switches from one solution to another, four forces are at work — two pushing them toward the new solution, two holding them back:

Force	What it is
1. Push of the current situation	The pain or dissatisfaction with what they do today (this is the demand side)
2. Pull of the new solution	The promise / appeal of your product (this is the supply side)
3. Anxiety about the new solution	Fears about switching costs, learning curve, risk, “will I look stupid?“
4. Habit of the present	The comfort of the current workaround, even if it’s painful (inertia)

Switching only happens when (1) + (2) > (3) + (4). Most products focus only on (2) — the pull — and ignore that (3) and (4) are usually the bigger blockers. Naming the anxieties and habits explicitly is what unlocks the switch.

Templates

The job statement (the core JTBD template)

When [situation],
I want to [motivation],
so I can [expected outcome].

Example for the SaaS-workspace product:

When my team is shipping a release and the dependent tools keep breaking,
I want to manage the whole workflow from one place,
so I can stop being the person who's always firefighting integrations.

Note that the outcome (“stop being the person who’s always firefighting”) includes the emotional/social layer, not just the functional one.

Three-outcome map

Job: [one-line job summary]

Functional outcome:  [what gets done — measurable]
                     e.g. ship the release without integration breakage

Emotional outcome:   [how it feels — internal]
                     e.g. less anxiety, more confidence at standup

Social outcome:      [how it looks — external perception]
                     e.g. seen as the operator who runs a tight ship,
                          not the one who's always behind

Four forces of progress checklist

Push of current:
  - "..."  (customer quote about pain today)
Pull of new:
  - "..."  (customer quote about why your solution attracted them)
Anxiety:
  - "..."  (what they're afraid of about switching)
Habit:
  - "..."  (what they're comfortable with about today, even if painful)

For our solution to win, we have to:
  - Amplify Push by:    ...
  - Sharpen Pull by:    ...
  - Reduce Anxiety by:  ...  (free trial, migration help, money-back guarantee)
  - Break Habit by:     ...  (forced trigger, peer pressure, deadline)

Metrics to track

• Number of distinct jobs identified per segment — most products serve 1-2 jobs well; a third is usually scope creep. Floor: ≥1 job clearly named per segment.
• Job-statement quote density — direct customer quotes that map to each clause of the job statement. Floor: 3 quotes per clause from 3 different customers.
• Switch-event capture rate — fraction of new customers for whom you know what they fired to hire you. Aim: 60%+ — ask the question explicitly during onboarding.
• Anxiety-driven drop-off — % of trials/signups that abandon at known anxiety points (security check, data import, sharing with team). Track this; small UX changes here often move conversion more than features.

Examples

SaaS workspace (B2B through-line)

Job statement:

When my small product/engineering team is mid-release and the connections
between our tools keep breaking,
I want to run the whole workflow from one place,
so I can stop being the person who's always patching things together
in front of my team.

Three outcomes:

• Functional: the release ships without an integration breaking it
• Emotional: the team lead feels in control, not reactive
• Social: they’re seen as the operator who runs a tight ship, not the one who lives in firefighting mode

Four forces analysis (from win/loss interviews):

• Push: “every CI failure is two hours I won’t get back” — strong.
• Pull: “one tool instead of three” — moderate; needs reinforcement with a free trial.
• Anxiety: “what if it doesn’t fit our Linear workflow?” — biggest single blocker, mitigated by a hands-on import workflow.
• Habit: “we already pay for the three things; this is more spend” — addressed by positioning the product as a replacement not an addition.

The product’s marketing copy is built directly on the social outcome — “stop being the person who patches things together” — because that line was the most-quoted phrase across interviews. Functional outcomes alone (faster, fewer breakages) didn’t sell; the social framing did.

Consumer fitness app (B2C contrast)

Job statement:

When I notice I've broken my workout streak again,
I want a way to come back without feeling judged,
so I can stay in the habit long-term instead of giving up.

Three outcomes:

• Functional: complete a workout this week
• Emotional: feel good about restarting; no guilt
• Social: be the kind of person who “keeps showing up” — even if just to themselves

Four forces:

• Push: “I feel guilty about the last two missed weeks” — strong, but a fragile push that disappears the moment the guilt does.
• Pull: “this app doesn’t punish me when I miss” — moderate.
• Anxiety: “another app I’ll abandon in a month” — biggest blocker; addressed by a 7-day refund and a one-tap “rest week” toggle.
• Habit: doing nothing — surprisingly strong; addressed by a 10-second restart flow.

The B2C lesson: in consumer products the emotional outcome usually dominates the functional one, and the four-forces frame helps you spot why every “feature push” in B2C marketing tends to underperform.

Common pitfalls

• Confusing the job with the feature. “I want to use the AI assistant” is not a job; “I want to draft the spec faster than I can on a blank page” is.
• Skipping emotional and social outcomes. Especially in B2B. The job has all three layers; functional alone is incomplete.
• Inventing jobs. A job not grounded in real customer language from discovery interviews is just a thesis. Treat it as one and validate.
• Ignoring forces 3 and 4 (anxiety, habit). Most marketing focuses on push and pull. Anxiety and habit are usually the bigger blockers; addressing them moves conversion more than amplifying pull.
• Conflating personas and jobs. Personas describe who; jobs describe what they want done. One persona can have multiple jobs. One job can be shared across personas. Use both lenses, not one.

See also

• Buyer Personas — the who that pairs with this what.
• Needs & Pain Points — needs are the input; jobs are one way to organize them.
• Strategy: Positioning — the category you sit in is the category of products that get hired for the same job.
• Customer Discovery Interviews — how to surface jobs in interview language.
• Workbook → Audience & message — where the job statement becomes the core message.