Jobs to Be Done (JTBD)

A way of describing what a customer is trying to accomplish, independent of any product — on the premise that people do not buy products, they hire something to make progress on a problem.

Why does Jobs to Be Done (JTBD) matter?

It changes who you think you are competing with, which changes almost everything downstream. If you describe your product by its category, your competitors are the other products in that category. If you describe the job, your competitors are everything the customer currently hires to get it done — including a spreadsheet, an assistant, and doing nothing. Most early startups lose to the last of those, and never see it coming because nothing in a competitive matrix represents inertia.

What does Jobs to Be Done (JTBD) look like in practice?

A dental practice does not want scheduling software. The job is closer to "stop losing patients who called while I was with someone." Framed that way, the competition is not other scheduling tools — it is the receptionist's notepad, the answering machine, and accepting the loss. That reframing usually tells you what the product must do on day one, which is rarely the feature list you started with.

What are the common mistakes with Jobs to Be Done (JTBD)?

  • Writing the job as a feature request. "Wants an integrated calendar" is a solution; "stop double-booking" is a job.
  • Making it so abstract it stops being useful — "wants to grow their business" describes everyone.
  • Forgetting that doing nothing is a competitor, and usually the strongest one.
  • Assuming one product serves one job. Most serve several, and they are not equally urgent.

Related concepts

Stop looking these up one at a time

Lev works through the whole arc with you — customers, positioning, pricing, the pitch — and explains the vocabulary as it goes.

Start with your idea