Software Growth

JTBD (Jobs to be done)

Jobs to be done is a framework that explains why people buy by focusing on the progress they want to make, instead of on who they are or what features exist.

Jobs to be done (JTBD) is a way to understand customers by the job they hire a product to do. It was developed by Clayton Christensen and colleagues. Instead of asking "who is our customer?" you ask "what is this person trying to get done, in what situation, and what are they using now?" For a founder it replaces guessing at features with a clearer view of why anyone switches.

The core idea

The Harvard Business Review article "Know Your Customers' Jobs to Be Done" by Christensen, Taddy Hall, Karen Dillon and David Duncan argues that companies have more customer data than ever yet their innovation still mostly fails. The authors say that is because teams focus on product attributes and customer profiles, not on the reasons customers buy. They report that 94 percent of executives surveyed were dissatisfied with their organization's innovation performance. When you understand the job, they argue, innovation becomes much more predictable.

Demographics versus jobs

Two customers with identical profiles may want opposite things, while two very different people may hire the same product for the same reason. A 25-year-old freelancer and a 55-year-old agency owner might both use your time-tracking tool because "when a client questions my invoice, I need proof of the hours". That shared situation is more useful for positioning than age or job title.

How Intercom applies it in software

Des Traynor describes how Intercom uses JTBD: rather than segmenting by customer type, the team identifies specific instances of work customers need done, writes down the core jobs it serves, and checks product decisions against them. He also advises focusing on verbs, not nouns, because calling yourself a "help desk" brings along every assumption of that category, and measuring real consumption, since "sign up is not consumption" (Jobs-to-be-Done Radio). Intercom also limits its messaging to jobs it does well.

How to find the job

  1. Interview recent buyers, and recent cancelers.
  2. Ask about the moment they started looking: what happened, what were they doing, what had they tried?
  3. Capture the situation, the desired outcome and the alternatives.
  4. Write jobs in the form "When [situation], I want to [action], so I can [outcome]."
  5. Group similar stories. Three to five jobs usually cover most customers.

Where JTBD helps

  • Positioning: your real competitors are whatever else gets the job done, including a spreadsheet. See positioning.
  • Prioritization: features that do not serve a core job are candidates to skip, which helps against feature creep.
  • Onboarding: guide new users toward the job that brought them.

Limits

JTBD is a research lens, not a formula. It gives you no number to track. Teams also overcomplicate it with long job maps when a handful of interviews would do. For a bootstrapped team, five customer interviews and a one-page list of jobs is plenty, and it pairs well with an ideal customer profile.

When the framework doesn't fit

You run jobs-to-be-done, everything checks out, but the company fails anyway.

Jason Cohen / “You didn’t do it right” (October 11, 2026)

In his October 2026 essay, Jason Cohen lists JTBD alongside OKRs, Scrum and content marketing as frameworks whose fans answer every failure with "you didn't do it right." He calls this the Precision Fallacy: the belief that a more precise implementation would have worked, when the precision in question is undefined or impossible to follow. His alternative is to treat a framework like a shirt off the rack. Sometimes it fits as is. More often you tailor it, and sometimes you swap it for another.

For JTBD, that means using it to answer a specific question, such as why people switch to you or what to put on your homepage. If the interviews keep producing vague jobs that don't change any decision, try a different method. Bob Moesta, who co-created the framework, covers when not to use it in his conversation with Lenny Rachitsky (51:05).

A related tool for early-stage founders is Rob Snyder's PULL framework, which he walked through on Lenny's Podcast in October 2026: a Project the buyer is working on, which is Unavoidable, a List of options they are considering, and the Limitations of those options. Like JTBD, it starts from what the buyer is trying to get done. It also tests whether that work is unavoidable.

  • Listen: The ultimate guide to JTBD, Bob Moesta on Lenny's Podcast (August 2023). See "Struggling moments and demand" (07:29), "The JTBD interview process" (18:30) and "When not to use JTBD" (51:05).
  • Read: “You didn’t do it right”, Jason Cohen (October 11, 2026). A short essay on how to tell whether a framework fits your team.
  • Read: Your target market isn’t demographic, Jason Cohen (September 2025). It argues that use cases and situations define a market better than demographics, and lists the traits to look for instead.
  • Watch: An 86-minute guide to finding PMF, Rob Snyder on Lenny's Podcast (October 25, 2026). The PULL framework, applied from idea to first sales calls.

Sources

Back to the SaaS glossary