Jobs to Be Done
People do not buy products. They hire them to do a job. This is the central insight of the Jobs to Be Done (JTBD) framework, developed by Clayton Christensen and refined by practitioners like Bob Moesta and Alan Klement. It sounds simple. It changes how you think about product development, competition, and market opportunity once you internalize it.
The Core Idea
"People don't want a quarter-inch drill. They want a quarter-inch hole." Theodore Levitt said this decades ago. JTBD takes it further: people do not even want a quarter-inch hole. They want to hang a shelf. And they want to hang a shelf because they need to organize their living room. And they need to organize their living room because they just had a baby and the place is chaotic.
The "job" is not the task. It is the progress someone is trying to make in a specific circumstance.
Surface level: "I need a project management tool."
Task level: "I need to track who is working on what."
Job level: "I need my team to ship reliably without me
micromanaging every task."
When you understand the job at this level, your competitive landscape changes. Jira is not just competing with Asana and Linear. It is competing with spreadsheets, Slack check-ins, daily standups, and a team lead with a good memory. Anything that helps a manager ensure reliable delivery without micromanaging is a competitor.
The Framework
A job has three components: the functional dimension, the emotional dimension, and the social dimension.
Functional Dimension
This is the practical outcome. What does the user need to accomplish?
Examples:
- "Help me get from point A to point B" (Uber, Lyft, public transit,
walking, bike share, own car)
- "Help me learn a new skill" (Coursera, YouTube, books, bootcamps,
mentorship, on-the-job training)
- "Help me communicate with my team" (Slack, email, in-person
meetings, phone calls, carrier pigeons)
Emotional Dimension
How does the user want to feel during and after getting the job done? This is where most products differentiate.
Examples:
- Uber vs public transit: same functional job, different emotional
job. Uber makes you feel in control and comfortable. Public transit
makes you feel anxious about timing and uncomfortable in crowds.
- Robinhood vs Vanguard: same functional job (invest money),
different emotional job. Robinhood makes you feel empowered and
excited. Vanguard makes you feel responsible and secure.
The emotional dimension explains why people pay premium prices for functionally equivalent products. A 1 coffee from a gas station achieve the same functional job. The emotional jobs are completely different.
Social Dimension
How does the user want to be perceived by others?
Examples:
- Tesla vs Toyota Camry: the social job of driving a Tesla includes
"be seen as someone who cares about the environment and technology."
- Notion vs Google Docs: some of Notion's appeal is the social
dimension. Teams that use Notion signal that they are organized,
modern, and thoughtful about their tools.
- LinkedIn Premium: the functional job is marginal. The social job
("this person is serious about their career") does real work.
How to Identify the Job
The Switch Interview
Bob Moesta developed the "switch interview" technique for uncovering jobs. Instead of asking users what they want, you interview people who recently switched to or from your product. The moment of switching reveals the job better than anything else.
Switch interview structure:
1. First thought:
"When did you first realize your old solution wasn't working?"
(The seed of switching. Often weeks or months before the actual switch.)
2. Passive looking:
"Did you start looking at alternatives? What triggered that?"
(The job becomes conscious. Something made the status quo intolerable.)
3. Active looking:
"What did you compare? What were your criteria?"
(Reveals what dimensions of the job matter most.)
4. The decision:
"What made you choose [product]? What almost stopped you?"
(The push, the pull, the anxiety, and the inertia.)
5. After the switch:
"Is it doing what you expected? What surprised you?"
(Reveals whether the job is being served or not.)
The Four Forces
Every switch decision is governed by four forces. Two push toward change, two resist it.
Forces pushing toward a new solution:
1. Push: Dissatisfaction with the current solution
"Our project management spreadsheet keeps breaking."
2. Pull: Attraction of the new solution
"Linear looks fast and clean and the team would actually use it."
Forces resisting change:
3. Anxiety: Fear about the new solution
"What if it doesn't integrate with our other tools?"
4. Inertia: Comfort with the current solution
"We've used this spreadsheet for two years and everyone knows it."
For a switch to happen, push plus pull must exceed anxiety plus inertia. This is why products fail even when they are objectively better: the anxiety and inertia are too high. It also explains why making your product easier to try (reducing anxiety) and easier to migrate to (reducing inertia) can be more valuable than adding features (increasing pull).
Slack's early growth was driven by understanding this. The functional pull was strong (better team communication), but the inertia (everyone already uses email) and anxiety (another tool to check) were enormous. Slack reduced inertia by importing message history and integrating with email. They reduced anxiety with a free tier that let teams try without commitment. The product was good, but the switching strategy is what made it win.
JTBD & Competition
JTBD redefines your competitive landscape. Your real competitors are not products in the same category. They are anything the user currently hires to do the job.
Product: Spotify Discover Weekly
Category competitors: Apple Music, YouTube Music, Pandora
JTBD competitors: Asking friends for recommendations, reading music
blogs, hearing songs in coffee shops, Shazam,
browsing record stores, radio DJs
Product: Zoom
Category competitors: Google Meet, Microsoft Teams, WebEx
JTBD competitors: Phone calls, flying to meet in person, email
threads, Slack huddles, not having the meeting at all
Product: Notion
Category competitors: Confluence, Google Docs, Coda
JTBD competitors: Spreadsheets, Slack messages, someone's memory,
tribal knowledge, not documenting anything
This matters because your biggest competitor is often "do nothing" or "use a workaround." The job of convincing someone to switch from a dedicated competitor is different from convincing them to switch from a cobbled-together workaround. Against a workaround, you compete on coherence and time savings. Against a direct competitor, you compete on specific dimensions of the job.
Applying JTBD to Product Decisions
Prioritization
When you understand the job, prioritization becomes clearer. Features that serve the core job are high priority. Features that serve adjacent jobs are lower priority. Features that serve no job are waste.
Product: A video conferencing tool
Core job: "Help me have a productive conversation with remote
participants."
High priority (serves core job):
- Reliable audio and video
- Screen sharing
- Low latency
Medium priority (adjacent job):
- Recording and transcription
- Calendar integration
- Virtual backgrounds
Low priority (different job):
- Built-in project management
- Social features
- Gamification
Zoom won by being fanatically focused on the core job. "It just works" was the value proposition. They did not try to be a project management tool or a social network. They made video calls reliable. Everything else came later.
Messaging & Positioning
JTBD gives you the language for marketing. Instead of describing what your product does, describe the progress it enables.
Feature-focused messaging:
"Calendly provides automated scheduling with time zone detection,
buffer times, and calendar integration."
Job-focused messaging:
"Stop wasting time going back and forth on meeting times.
Share your link and let people book when it works for both of you."
The second version speaks to the job. The first version speaks to the implementation.
Innovation Opportunities
JTBD reveals opportunities that traditional market analysis misses. If you only look at product categories, you see saturated markets. If you look at jobs, you see underserved needs.
Category analysis: "The personal finance app market is crowded."
Job analysis: "People hired Mint to feel in control of their money.
Mint stopped making them feel in control (stale data, overwhelming
interface, ads). The job is underserved. There is an opportunity for
a product that makes people feel financially confident with minimal
effort."
This is roughly how YNAB and Copilot found their markets.
When JTBD Does Not Help
JTBD is not a universal tool. It works best for understanding why people switch and what progress they seek. It is less useful for:
- Incremental feature decisions. JTBD tells you the job but not whether the search filter should be on the left or the top.
- Technically-driven innovation. Sometimes a new technology creates a job that did not exist before. Nobody was "hiring" a smartphone before the iPhone. JTBD works better for evolutionary products than revolutionary ones.
- B2B with complex buying committees. When the buyer, the user, and the administrator are different people, each has a different job. JTBD still applies, but you need to map multiple jobs simultaneously.
Common Pitfalls
- Defining the job too broadly. "Help me be more productive" is not a job. It is a platitude. Jobs are specific to a context. "Help me prepare for my weekly team meeting in under 10 minutes" is a job.
- Defining the job too narrowly. "Help me add a row to a spreadsheet" is a task, not a job. Jobs include the desired progress and the context.
- Ignoring the emotional and social dimensions. Focusing only on functional jobs produces utilitarian products that lose to competitors who understand feelings.
- Treating JTBD as a one-time exercise. Jobs evolve as circumstances change. The job that Slack was hired for in 2014 (replace clunky internal email) is different from the job it serves now (be the operating system for work). Revisit the job regularly.
- Confusing the job with the solution. "I need a CRM" is not a job. "I need to remember every interaction with a prospect so I can follow up at the right time" is a job. The CRM is one possible solution.
Key Takeaways
JTBD reframes product development around the progress users seek, not the features they request. Every job has functional, emotional, and social dimensions. Your real competitors are not products in the same category but anything the user currently hires to do the job. Use switch interviews to uncover jobs by studying the moment when users change solutions. The four forces model (push, pull, anxiety, inertia) explains why people switch or do not switch. Define jobs at the right altitude: specific enough to be actionable, broad enough to reveal the full competitive landscape.