Jobs to Be Done

A framework for understanding customer motivation by focusing on the specific outcome a customer seeks to achieve rather than their demographics or explicit requests. JTBD assumes customers 'hire' products to get a job done in a particular circumstance.

What is Jobs to Be Done?

Jobs to be done is a lens for understanding customer decision-making that reframes the question from “who is our customer?” to “what outcome are they trying to achieve?” It assumes that customers don’t want products; they want to make progress on meaningful goals.

A customer doesn’t want a calendar app; they want to manage their time and commitments. A customer doesn’t want project management software; they want to track progress and coordinate work. The app or software is the vessel; the job is the outcome.

The Core Insight

JTBD separates functional outcomes (what does the product do?) from emotional and social outcomes (how does it make the customer feel?). A timer app’s functional job is “track elapsed time.” Its emotional job might be “take ownership of my day” or “feel productive.” A product that solves the functional job but not the emotional job will underperform.

This reframing matters because it prevents companies from being blindsided by unconventional competitors. Incumbent calendar tools were disrupted not by better calendar tools but by messaging apps that became de facto coordination mechanisms. The job (coordinate with collaborators) remained constant; the solution shifted.

Jobs Framework Elements

A complete job statement includes: the customer context (circumstance in which the job arises), the functional outcome (what needs to be accomplished), the emotional outcome (how the customer wants to feel), and the social outcome (how the customer wants to be perceived). All three dimensions matter.

For example: A young professional preparing for a high-stakes presentation (context) wants to gather compelling evidence quickly (functional), feel confident and authoritative (emotional), and be seen as thorough and credible (social). A solution addressing only functional outcome (finding data) but not confidence or credibility will miss the mark.

Jobs in Discovery and Design

Understanding the job guides discovery. Instead of asking “would you use this product?” ask “how is this job currently being done?” Customers often solve jobs with workarounds—spreadsheets, manual processes, even combinations of products. These workarounds reveal job importance.

Jobs thinking also prevents feature creep. A feature that does not advance customer progress on their core job is distraction. This discipline forces prioritization: every feature must serve the job.

Jobs and Segments

JTBD naturally creates segments based on jobs rather than demographics. Two customers in the same role might have different jobs. A junior analyst needs to execute against defined metrics; a director needs to discover new metrics worth tracking. Same tool category, different jobs.

Segmenting by job rather than role or company size improves targeting and reduces feature sprawl because each segment’s job is more specific and actionable.

Why It Matters for Product People

JTBD reframes product strategy from “maximize features” to “optimize job completion.” This mindset shift prevents the false confidence that more features mean more value. It also reveals where competitors are winning: they are better solving the emotional or social dimension of the job, not the functional dimension.

JTBD also provides defensibility. When you deeply understand and optimize a specific job, competitors struggle to displace you because they are not just beating you on features—they have to fundamentally reshape how customers accomplish that job.

JTBD connects to product discovery (how to understand customer needs), value proposition (what outcome you deliver), and product positioning (which job you claim to solve). Together, they form the foundation of product strategy.