Why Traditional Customer Segmentation Falls Short
Most product teams segment their users by demographics — age, location, income, job title. These categories feel intuitive, but they often predict behaviour poorly. Knowing that your user is a 35-year-old urban professional tells you very little about why they chose your product over an alternative, or what would make them leave.
The Jobs to Be Done (JTBD) framework, popularised by the late Harvard Business School professor Clayton Christensen, offers a more powerful lens: focus not on who your customer is, but on what they're trying to get done.
The Core Idea: People "Hire" Products to Do Jobs
The central metaphor of JTBD is that customers don't buy products — they hire them to make progress in a specific circumstance. When someone buys a project management tool, they're not buying software — they're hiring it to reduce the chaos of coordinating a team. When someone buys a language learning app, they're hiring it to feel capable and confident in a new country.
This reframe is powerful because it immediately expands your view of competition. Your project management tool isn't just competing with other project management tools — it's competing with spreadsheets, email threads, and whiteboards. Whatever the user might hire to do the same job is your competitor.
The Three Dimensions of Every Job
Functional Jobs
The practical, utilitarian task: "I need to get from A to B," "I need to file my taxes," "I need to track my team's work." These are the obvious, surface-level needs most products are built around.
Emotional Jobs
How users want to feel as a result of getting the job done: confident, organised, respected, relieved, in control. Often, the emotional job is more important than the functional one — and the product that wins is the one that nails both.
Social Jobs
How users want to be perceived by others: "I want to look like someone who has their finances together." Social jobs are often unspoken but powerful drivers of product choice, particularly in consumer markets.
How to Conduct a JTBD Interview
The best way to uncover jobs is through structured interviews focused on the moment of purchase or adoption — not on product satisfaction. You're trying to reconstruct the story of how they came to hire your product (or a competitor).
- Start at the beginning: "Walk me through the first time you realised you needed something like this." This surfaces the triggering event.
- Explore the struggle: "What were you doing before? What was frustrating about it?" Understand the inadequacy of current solutions.
- Understand the search: "How did you go about looking for a solution? What did you consider?" This reveals your competitive landscape.
- Probe the decision: "What made you choose this one? Was there anything you were nervous about?" This uncovers the functional, emotional, and social jobs in play.
Applying JTBD to Product Development
Once you've identified the core job, use it as a filter for every product decision:
- Does this feature help users make progress on the job faster or more reliably?
- Are there "hiring criteria" our product fails to meet that are causing churn?
- Are we solving the job in a way that also addresses the emotional and social dimensions?
- Is there a segment of job-havers whose needs we're currently ignoring?
A Simple Template to Get Started
Write out your core job statement in this format:
"When [situation], I want to [motivation/goal], so I can [expected outcome]."
For example: "When our sprint planning meeting runs over time, I want a faster way to visualise task dependencies, so I can keep the team aligned without wasting the afternoon."
This statement becomes the north star for feature prioritisation, messaging, and positioning. Every great product is, at its core, a better solution to a job that people genuinely need done.