JTBD reframes 'features vs benefits' into the underlying job the customer is hiring your product.
Jobs-to-be-Done (JTBD) is a framework — most famously articulated by Clayton Christensen and Bob Moesta — that reframes buyer motivation. Customers don't buy products; they "hire" products to make progress on a job. Understanding the job (not the persona, not the features) explains why customers switch, what they compare you to, and what would make them fire you. Startups that operationalize JTBD tend to produce sharper positioning, better product decisions, and higher win rates in evaluations.
JTBD is a lens on motivation: what job is the customer trying to get done, in what context, and what's making it hard? It is not a persona (personas describe who; JTBD describes why). It is not a feature list. It is not a use case (use cases describe how the product is used; JTBD describes why it was purchased). The classic example: people don't buy quarter-inch drills; they buy quarter-inch holes; and even more precisely, they buy the ability to hang a picture on the wall.
The core JTBD research method is the switch interview: talking to customers who recently switched from an old solution (including "nothing") to yours. Structure: (1) walk me through the first moment you started looking for a new solution, (2) what were you doing before, (3) what triggered the search, (4) what did you consider, (5) what almost stopped you from buying, (6) what happened after purchase. Run 15-25 switch interviews to see patterns. Fewer than 10 produces false patterns; more than 30 rarely adds new insight.
Bob Moesta's model identifies four forces acting on every purchase decision: (1) Push of the current situation (pain with status quo), (2) Pull of the new solution (attraction of new capability), (3) Anxiety about the new solution (fear of switching), (4) Habits of the present (comfort with current tools). A purchase happens when Push + Pull > Anxiety + Habits. Most product marketing over-invests in Pull (feature benefits) and under-invests in Anxiety reduction (switching risk, implementation ease) — which is why deals stall in evaluations that seemed to be going well.
Once you have 15-25 switch interviews, patterns emerge: what job is the majority of your customer base hiring you for, what are the actual alternatives they compared, what triggered the search. Positioning derived from this looks like: "For [context/trigger], instead of [real alternative], hire us to [job to be done], so you can [outcome]." This is specific, differentiated, and provably tied to real customer language — which produces higher-converting website copy, sales pitches, and product decisions.
Every feature request should be evaluated against "which job does this help the customer make progress on?" Features that don't map to a real job produce feature bloat. Features that make an underserved job significantly easier produce category-defining wins. Product roadmaps organized around jobs (not around features or personas) tend to age better because jobs change slowly while features and technology change fast.
Confusing JTBD with personas (they're complements, not substitutes). Running "JTBD interviews" that are just discovery calls with a new label. Extracting jobs from what customers say they want (they don't know) instead of what they actually did. Applying JTBD to prospects who never bought (survivorship bias — talk to switchers, not prospects). Using JTBD as a one-time exercise instead of a repeated practice.
Investor directory · Fundraising library · Articles A–Z · Company funding database