Jobs to be done (JTBD)

Overview

Jobs to be Done (JTBD) is a product development framework that reframes how we think about customer needs by focusing on the functional, emotional, and social "jobs" customers are trying to accomplish rather than on demographic segments or product categories. Developed by Clayton Christensen and popularized by researchers like Bob Moesta and Rodney Olson, JTBD shifts perspective from "Who is our customer?" to "What is the customer trying to achieve?" and "What obstacles stand in their way?" When a customer "hires" a product, they're hiring it to do a specific job—a drill isn't really a product people want; they want to create holes to hang pictures and feel proud of their home. Understanding this deeper job helps product teams build products that actually solve customer problems rather than incrementally improving existing features.

Why is Jobs to be Done Valuable?

JTBD provides a powerful lens for identifying genuine customer needs and market opportunities that traditional market research often misses. Companies that understand the job their customers need done can innovate more effectively—they focus on solving the core job rather than chasing feature requests that don't address fundamental needs. JTBD also reveals non-obvious competitors; if the job is "stay updated on news during my commute," competitors include news apps, podcasts, radio, and conversation with colleagues. This broader competitive understanding prevents myopic focus on direct competitors and reveals genuine market threats. From a product strategy perspective, JTBD helps teams prioritize features and make trade-offs—does this feature help customers accomplish their core job better, or is it distraction? JTBD also improves marketing messaging by explaining the actual value of products in terms customers care about rather than feature specifications.

When Should You Apply Jobs to be Done?

Apply JTBD framework in these situations:

• Entering new markets or customer segments: When you don't fully understand why customers choose your product, JTBD research reveals the actual jobs driving adoption and guides your strategy.

• Struggling with market fit: If your product isn't gaining traction despite addressing an apparent market need, JTBD analysis may reveal that you're not solving the job customers actually care about.

• Building competing products or entering crowded categories: Understanding the job helps you differentiate by solving it better than competitors or addressing dimensions competitors ignore.

• Making product strategy decisions: When choosing between feature options or considering major pivots, JTBD provides a framework for evaluating which direction better serves the core job.

What Are the Challenges of Jobs to be Done?

JTBD research is qualitative and demanding; you must conduct extensive interviews with customers, which requires time and skill to do well. Interview analysis is subjective—different researchers may identify different jobs from the same data. People often struggle to articulate their jobs explicitly, so JTBD research requires deep listening and inference, not just asking "What job are you trying to do?" There's also risk of over-simplification; complex products often address multiple jobs, and focusing too narrowly on one job may prevent you from serving the broader customer need. Some industry experts debate JTBD methodology and effectiveness, and the framework can feel abstract without rigorous execution. Additionally, JTBD insights are sometimes too abstract to guide tactical product decisions—you still need to break down the job into specific features and use cases.

How to Apply Jobs to be Done Framework

Start by selecting a job worth understanding—focus on a customer segment or market that matters to your strategy. Conduct qualitative research interviews with 20-30 customers or prospects, asking them to tell stories about when they tried to accomplish the job, what obstacles they faced, and what solution they eventually chose. Listen for the job to be done (functional, emotional, social dimensions), the circumstances triggering the job, and the obstacles and anxieties preventing completion. Analyze patterns across interviews to identify common job dimensions and circumstances. Create job scenarios—specific situations where the job arises—that guide product decisions. Use these insights to evaluate existing features, identify gaps, and prioritize new development. Share your JTBD findings with product and engineering teams so everyone understands the customer's real objective, not just requested features. Periodically revisit JTBD research as markets and customer needs evolve.