Jobs to Be Done Framework for Product Marketers

What Is Jobs to Be Done Theory?

Jobs to Be Done (JTBD) is a framework for understanding why people buy things. Not what they buy. Not who buys it. Why. The theory was developed and popularized by Clayton Christensen, the Harvard Business School professor best known for "The Innovator's Dilemma." His core insight was deceptively simple: people don't buy products. They hire products to do a job.

The classic example is the milkshake. Christensen's research team was hired by a fast-food chain to increase milkshake sales. Traditional market research would have asked customers about milkshake preferences: thicker, thinner, more chocolate, different flavors. Instead, the team asked a different question: what job are you hiring this milkshake to do?

They discovered that nearly half of milkshakes were purchased before 8:30 AM by commuters. These buyers didn't want a milkshake because they loved milkshakes. They needed something to make a long, boring commute more interesting. The milkshake had to fit in a cup holder, last the length of the drive, and be filling enough to tide them over until lunch. The job wasn't "enjoy a milkshake." The job was "make my commute bearable and keep me full until noon."

This reframing changes everything. When you understand the job, your competitors aren't other milkshakes. Your competitors are bananas, bagels, donuts, boredom, and Snickers bars. The competitive set expands dramatically because you're competing against everything else the buyer could hire to do that same job.

For product marketers, this is transformative. Traditional competitive analysis looks at feature-to-feature comparisons within a product category. JTBD competitive analysis looks at everything the buyer considers when trying to accomplish a goal. That's a fundamentally different and much more useful lens for positioning your product.

The theory rests on several core principles that matter for practical application:

• Jobs are stable over time. The way people accomplish jobs changes (horse to car to Uber), but the underlying jobs themselves rarely change. People have always needed to get from point A to point B. The job is durable. The solution is not.
• Jobs are solution-agnostic. A job doesn't care about your product. It exists independently. "Help me manage my team's projects" is a job. Asana, Trello, spreadsheets, whiteboards, and sticky notes are all solutions that can be hired for that job.
• Jobs have functional, emotional, and social dimensions. The functional job is the practical task ("organize my projects"). The emotional job is how the person wants to feel ("in control, not overwhelmed"). The social job is how they want to be perceived ("competent manager who has their act together").
• People switch solutions when they find something that does the job better. Not better in some abstract sense, but better at the specific job they're hiring for, with less friction in switching.

"People don't want a quarter-inch drill. They want a quarter-inch hole." This quote, attributed to Theodore Levitt, captures the JTBD mindset. But JTBD goes further: they don't want the hole either. They want the shelf on the wall. They want the organized living room. They want to feel proud when friends visit.

Why JTBD Matters for Product Marketers

Most product marketing starts with personas. You build an Ideal Customer Profile, define buyer personas, map their journey, and craft messaging around who they are. That's useful work. But it's incomplete, and it often leads to messaging that's descriptive rather than motivating.

JTBD fills the gap that personas leave open. A persona tells you that your buyer is a VP of Engineering at a mid-market SaaS company. That's helpful for targeting. But it doesn't tell you why that VP of Engineering would buy your product right now, today, instead of living with the status quo. JTBD answers that question by identifying the specific progress the buyer is trying to make.

Here's a concrete example. Say you're marketing a developer experience platform. Your persona might be "Sarah, VP of Engineering, 50-person team, Series B startup." That helps you know where to run ads and what tone to use. But the job tells you what to say. Sarah's job might be "reduce the time my team spends on environment setup so they can ship features faster and I can show the board we're hitting delivery milestones." Now you know the emotional stakes, the functional need, and the social pressure. That's messaging fuel.

JTBD also reveals why buyers reject your product, which is just as valuable as understanding why they buy it. In Christensen's framework, there are four forces that influence every purchase decision:

1. Push of the current situation: What's frustrating enough about the status quo to make someone consider switching?
2. Pull of the new solution: What's attractive about the new product? What progress does it promise?
3. Anxiety of the new solution: What worries people about switching? Will it actually work? Is it hard to implement?
4. Habit of the present: What inertia keeps people where they are? Familiarity, sunk costs, "good enough" status quo?

For a purchase to happen, the push and pull forces must be stronger than the anxiety and habit forces. Most product marketing focuses exclusively on the pull (look how great our product is!) and ignores the other three forces entirely. JTBD gives you a framework for addressing all four, which makes your messaging dramatically more persuasive.

This connects directly to how you build buyer personas. Instead of personas based on demographics and job titles, you build personas based on the jobs they're trying to accomplish. A "job-based persona" is more actionable than a demographic one because it tells you what to say, not just who to say it to.

Jobs vs Needs vs Wants: Clarifying the Terminology

One of the biggest sources of confusion around JTBD is the terminology. Jobs, needs, wants, outcomes, pains, and gains all get used interchangeably in marketing and product conversations, but they mean different things in the JTBD framework. Getting this straight matters because it changes how you conduct research and how you structure your messaging.

A job is the progress that a person is trying to make in a particular circumstance. It's the fundamental thing they're trying to accomplish. "Help me onboard new hires quickly so they're productive in their first week" is a job. Jobs are defined from the buyer's perspective, in their language, and they're context-dependent. The circumstance matters as much as the desired progress.

A need is a specific requirement within the job. If the job is "onboard new hires quickly," the needs might include "automated provisioning of tools and accounts," "a structured checklist that managers can follow," and "a way to track completion across the organization." Needs are more granular than jobs and are often where feature-level thinking lives.

A want is a stated preference that may or may not align with the actual job. "I want a beautiful dashboard" is a want. It might relate to a real job ("help me look competent when presenting to leadership") or it might be a surface-level preference that doesn't actually drive purchase behavior. The danger of wants is that they're easy to collect (just ask people what they want) but unreliable as a foundation for positioning. People don't always know what they want, and what they say they want often doesn't match what they actually do.

An outcome is the measurable result that defines success for the job. "New hires are fully productive within 5 days instead of 15" is an outcome. Outcomes are incredibly useful for messaging because they're specific, measurable, and directly connected to the buyer's definition of success. Our voice of customer framework helps you capture these from real buyer conversations.

Here's why this matters for product marketers: if you build positioning around wants, you'll create messaging that sounds nice but doesn't motivate action. If you build positioning around jobs and outcomes, you'll create messaging that connects to what buyers actually care about and what they'll actually pay to solve.

Key Insights from Competing Against Luck

Clayton Christensen's "Competing Against Luck" is the fullest expression of JTBD theory. It's not a product marketing book, but it contains insights that every PMM should internalize. Here are the ones that matter most for our work.

Innovation is not about technology. It's about the customer's job. Christensen argues that most innovation fails because companies focus on making their products better (faster, cheaper, more features) rather than understanding the job better. For PMMs, this is a direct challenge to feature-based positioning. Listing features is talking about your product. Talking about the job is talking about the customer's world.

The "struggle moment" is the trigger for every purchase. People don't wake up and decide to buy software. They reach a moment of struggle where the status quo becomes intolerable. Maybe a critical customer churned because nobody saw the warning signs. Maybe the board asked a question the team couldn't answer. Maybe a new hire took three weeks to get productive when competitors onboard in three days. These struggle moments are the most powerful messaging triggers you have, and they're the first thing you should uncover in customer research.

"Non-consumption" is your biggest competitor. The most common alternative to your product isn't a competitor's product. It's nothing. People doing the job manually, using spreadsheets, or simply not doing it at all. Christensen calls this "non-consumption," and it represents a massive market opportunity that most PMMs ignore because they're too focused on competitive comparisons. If 80% of your potential market is using spreadsheets to do the job your product automates, your positioning should address the spreadsheet-to-product transition, not the product-to-product comparison.

Social and emotional jobs often outweigh functional ones. This is counterintuitive for B2B marketers who think buyers are rational. They're not. A VP of Sales might buy a forecasting tool partly because the functional job is "improve forecast accuracy." But the emotional job is "stop feeling anxious every Sunday night about the Monday pipeline meeting." And the social job is "be the revenue leader who always has the numbers." If your messaging only addresses the functional job, you're ignoring two-thirds of the motivation.

Customers fire solutions as much as they hire them. Understanding why people leave a product is just as valuable as understanding why they adopt one. The firing criteria reveal what the current solution is failing to do, which directly informs your positioning validation. If customers are firing your competitor because onboarding is too complicated, that's a positioning opportunity you can claim.

"Customers don't buy products. They pull them into their lives to make progress. Understanding that progress is the key to unlocking growth."

How to Identify Jobs in Your Market

Theory is useful. Application is what matters. Here's how to actually identify the jobs that exist in your market through practical research methods that any PMM can execute.

Method 1: JTBD Customer Interviews

The JTBD interview is different from a standard customer interview. You're not asking about features, satisfaction, or preferences. You're reconstructing the story of how someone came to buy your product (or a competitor's product, or nothing at all). The technique is sometimes called a "switch interview" because you're mapping the forces that led someone to switch from one solution to another.

The interview follows the customer's timeline backward from the purchase moment. You're trying to uncover:

1. The first thought: When did you first realize you needed something different? What happened?
2. Passive looking: What did you start paying attention to? Were you browsing, reading, or asking around?
3. Active looking: When did you start actively evaluating solutions? What triggered the shift from passive to active?
4. Decision and purchase: How did you make the final choice? What tipped you over the edge?
5. The consuming moment: What happened after you started using the product? Did it deliver on the job?

At each stage, you're probing for the four forces: push of the current situation, pull of the new solution, anxiety of switching, and habit of the present. Use our voice of customer research template to structure these conversations and capture insights consistently.

You need 8-12 interviews to start seeing patterns. Don't just interview happy customers. Interview people who evaluated your product and chose a competitor. Interview people who considered buying but did nothing. These "non-buyers" often reveal the most important jobs because they show you the anxiety and habit forces that your marketing hasn't addressed.

Method 2: Win/Loss Analysis Through a JTBD Lens

If your company does win/loss analysis (and it should), you can reframe it through a JTBD lens. Instead of coding wins and losses by feature gaps or pricing issues, code them by the job the buyer was trying to accomplish. You'll often find that you win deals where the buyer has a specific job (say, "consolidate three tools into one platform to reduce vendor management overhead") and lose deals where the buyer has a different job ("get the most powerful point solution for this one specific function").

This job-based segmentation of wins and losses is far more actionable than feature-based analysis. It tells you which jobs your product is best at, which directly informs your positioning and your ICP definition.

Method 3: Sales Call Mining

Listen to recorded sales calls with a JTBD ear. You're listening for the buyer's language when they describe their situation: the frustration with the status quo, the progress they're trying to make, the risks they're worried about. Buyers almost never articulate a clean "job statement" on a call. But they describe the ingredients. Your work is to synthesize those ingredients into a structured job.

Look for phrases like: "We've been trying to..." "The problem is that..." "What we really need is..." "If we could just..." "The thing that keeps happening is..." These are job signals. Capture them verbatim. The buyer's exact language is gold for messaging.

Method 4: Support and Community Mining

Customer support tickets, community forums, Reddit threads, and review sites (G2, Capterra, TrustRadius) are full of job signals. People describe what they were trying to accomplish and how the product helped or failed. This is unprompted, unfiltered feedback that reveals jobs in the customer's own words. Run a structured analysis of your last 100 support tickets or 50 G2 reviews, tagging each one with the underlying job. Patterns will emerge fast.

Building a Jobs Map

Once you've identified the jobs in your market through research, you need to organize them into a usable framework. A jobs map is the tool for this. It takes the raw insights from your research and structures them into something you and your team can actually use for positioning, messaging, and product decisions.

The Job Map Structure

A job map breaks a core job into its sequential steps. Think of it as the process the buyer goes through to accomplish the job, independent of any specific solution. For each step, you identify what the buyer is trying to achieve and where current solutions fall short.

The standard job map has eight stages, based on Tony Ulwick's Outcome-Driven Innovation framework:

1. Define: What needs to be accomplished? (Determine the scope and plan the approach)
2. Locate: What inputs are needed? (Find the information, materials, or people required)
3. Prepare: How do I set up the environment? (Get everything ready for execution)
4. Confirm: Is everything in order before executing? (Verify readiness and validate the approach)
5. Execute: Carry out the job. (The core action that accomplishes the goal)
6. Monitor: Is it working as expected? (Track progress and identify issues)
7. Modify: What adjustments are needed? (Make changes based on monitoring)
8. Conclude: Finish up and move on. (Complete the job and transition to the next activity)

Let's make this concrete. Say the core job is "Help me launch new products successfully." A simplified job map might look like this:

For each step in the map, ask: where is this step hardest or most time-consuming with existing solutions? The steps where current solutions fail the most are your biggest positioning opportunities. If every competitor helps with execution (step 5) but nobody helps with defining launch tiers and success metrics (step 1), that's a differentiation angle you can own.

Mapping Multiple Jobs

Most products serve multiple jobs. A customer success platform might serve "reduce churn," "expand existing accounts," and "prove ROI to leadership." Each of these is a distinct job with its own map. Your task is to identify which jobs are most important to your target audience and which jobs your product serves best. The intersection of those two answers is your positioning sweet spot.

Organize your jobs into a hierarchy: one or two "core jobs" that define your primary positioning, three to five "related jobs" that support secondary messaging, and any number of "peripheral jobs" that you can reference but don't lead with. This hierarchy prevents the common trap of trying to position your product as everything to everyone.

Using JTBD in Positioning

This is where JTBD delivers its biggest payoff for product marketers. Most positioning starts with the product: what it does, what category it belongs in, how it's different from competitors. JTBD positioning starts with the buyer: what progress they're trying to make and why current alternatives aren't getting the job done.

The shift is subtle but profound. Instead of "We're a customer success platform with predictive health scores," you get "When your retention team is reactive because they can't see churn coming, you need a way to identify at-risk accounts before it's too late." The first statement describes the product. The second statement describes the buyer's world and positions the product as the solution to a real struggle.

Here's how to translate your JTBD research into positioning using a positioning framework:

Step 1: Lead with the Job, Not the Category

Traditional positioning opens with the category: "We're a [type of product] for [audience]." JTBD positioning opens with the job: "When you're trying to [achieve this progress] but [current alternatives fall short because], [product name] helps you [accomplish the job] by [how it works differently]."

This structure forces you to articulate the buyer's struggle before you talk about your product. That's powerful because it shows the buyer you understand their world before you pitch your solution. Empathy before features. Context before claims.

Step 2: Define Competitive Alternatives Through the Job Lens

When you position through JTBD, your competitive set changes. You're not just competing against products in your category. You're competing against everything the buyer currently uses to accomplish the job. That might include manual processes, spreadsheets, other SaaS tools, consultants, or doing nothing at all.

This expanded competitive set is actually an advantage. It lets you position against the status quo, which is often a more compelling argument than positioning against a specific competitor. "Stop managing customer health in spreadsheets" is a stronger message for many buyers than "Switch from [Competitor X] to us."

Step 3: Anchor Differentiation in Underserved Job Steps

Your job map reveals where current solutions fail. Those failure points are your differentiation opportunities. If you know that buyers struggle most with the "confirm" step (validating their approach before execution), and your product uniquely helps with that step, that's your positioning anchor. You're not just different. You're different in a way that matters to the buyer's job.

This is a much stronger foundation for differentiation than feature comparison. Features can be copied. But being the product that's purpose-built for an underserved job step creates a positioning moat that's hard to replicate because it requires deep understanding of the buyer's workflow, not just engineering capability.

Using JTBD in Messaging

If positioning is the strategic decision about how your product shows up in the market, messaging is how you communicate that decision across every touchpoint. JTBD research gives you the raw material for messaging that resonates because it's built from the buyer's own language and concerns. Our messaging framework template provides the structure. JTBD provides the content.

The Four Forces Messaging Model

Remember the four forces from Christensen's framework? Each one maps to a specific type of messaging:

Push messaging (activating dissatisfaction): This messaging amplifies the buyer's frustration with the status quo. "Your team is spending 40% of their time on manual data entry instead of actually analyzing results." "Every month, three at-risk accounts slip through the cracks because nobody has visibility." Push messaging works best at the top of the funnel, where your goal is to interrupt the status quo and create urgency.

Pull messaging (painting the future state): This messaging describes the progress the buyer will make with your product. "Imagine knowing exactly which accounts are at risk 30 days before they churn." "What if every new hire was fully productive by day three?" Pull messaging is aspirational but specific. It paints a picture of life after the switch that's concrete enough to be believable.

Anxiety-reducing messaging (removing risk): This messaging addresses the fears that prevent action. "Deploy in under 30 minutes with no engineering resources." "Our team migrates your data for you, free of charge." "See results in the first week, or cancel anytime." Anxiety messaging is critically important in the mid-to-late funnel, where buyers are interested but haven't committed. Most companies under-invest here.

Habit-breaking messaging (disrupting inertia): This messaging challenges the "good enough" status quo. "Spreadsheets worked when you had 50 customers. You have 500 now." "Manual processes don't scale. You've probably already noticed." Habit-breaking messaging is about making the cost of inaction visible. It's the gentle (or not so gentle) push that says "the thing you're tolerating is actually costing you."

Mapping Messages to the Buyer's Timeline

The buyer doesn't experience all four forces simultaneously. They move through a timeline: first they feel the push (something is frustrating), then they start exploring (pull messaging catches their attention), then they evaluate (anxiety messaging builds confidence), and finally they commit (habit-breaking messaging overcomes inertia). Your messaging should follow this sequence across your funnel touchpoints.

Top of funnel (ads, blog posts, social): Lead with push messaging. Activate the dissatisfaction. Mid-funnel (website, demos, case studies): Balance pull and anxiety messaging. Show the future state and remove risk. Bottom of funnel (proposals, sales calls, ROI calculators): Focus on habit-breaking and anxiety reduction. Make it easy to say yes.

This is how you connect JTBD to your broader go-to-market strategy and ensure that your positioning and messaging work together across every channel.

JTBD Case Studies: Theory in Practice

Theory and frameworks are useful, but seeing JTBD applied to real products makes it concrete. Here are three examples of companies that used job-based thinking to transform their positioning and messaging.

Case Study 1: Intercom's "Business Messenger" Pivot

Intercom started as a customer communication platform, essentially a modern intercom system (hence the name). But as the market evolved, they found themselves being compared feature-by-feature to live chat tools like Drift and Zendesk. That's a race to the bottom.

By applying JTBD thinking, Intercom realized their best customers weren't hiring them for "live chat." They were hiring them for a bigger job: "engage website visitors at the exact right moment to convert them into customers or help them succeed." The job wasn't communication. The job was conversion and success through communication.

This led to their repositioning as a "Business Messenger" and later as a "customer messaging platform." The competitive set shifted from chat tools to the entire customer engagement stack. Their messaging moved from "talk to website visitors" to "connect with the right customer, at the right time, with the right message." The job reframing changed everything: product roadmap, pricing, sales narrative, and market category.

Case Study 2: Basecamp and the "Calm Company" Job

Basecamp (formerly 37signals) competes in the crowded project management space against tools like Asana, Monday.com, Jira, and dozens of others. Feature-by-feature, Basecamp loses many comparisons. It's intentionally simpler. In a head-to-head feature evaluation, project managers would often choose a competitor.

But Basecamp doesn't compete on features because they understood the job differently. Their buyers aren't hiring a project management tool. They're hiring a way to reduce the chaos and noise that comes with managing projects across a team. The job is "bring calm to our work" or more specifically "stop the constant pinging, the notification overload, and the anxiety of always being behind."

This job-based positioning lets Basecamp charge a flat rate regardless of team size, avoid feature bloat, and attract customers who are exhausted by the complexity of competing tools. They positioned against the anxiety and noise of other solutions, not against the solutions themselves. Their homepage doesn't say "better project management." It says "the project management tool that doesn't make you feel like you're drowning." The simplicity that would be a weakness in a feature comparison becomes the key selling point when the job is "make work calmer."

Case Study 3: Notion as "One Tool for Everything"

Notion's growth story is a masterclass in JTBD positioning. On paper, Notion is a note-taking and documentation tool. It competes with Google Docs, Confluence, Evernote, and dozens of others. If you position it feature-by-feature in any single category, it's rarely the best option.

But Notion understood that their power users were hiring them for a different job: "consolidate my team's scattered tools into one workspace so we can actually find things and stay aligned." The job wasn't "take notes." The job was "end the chaos of having information in 12 different tools."

This job crosses category boundaries. Notion isn't just competing against Confluence for documentation. It's competing against the combination of Confluence + Trello + Google Docs + Airtable + the shared drive nobody can navigate. The "one tool" positioning works because it addresses a real job that no single category competitor addresses. Their messaging consistently focuses on consolidation: fewer tabs, fewer tools, one source of truth. That's a job-based message, not a feature-based one.

Each of these case studies illustrates the same principle: when you understand the buyer's job, you can find positioning angles that transcend feature competition. This connects directly to how you approach product-market fit. You don't achieve fit by building more features. You achieve it by being the best solution for a specific job.

"The companies that win don't have the best products. They have the deepest understanding of the job their customers are hiring them to do."

JTBD isn't just an academic framework. It's a practical tool that changes how you research, how you position, how you message, and how you compete. Start with five customer interviews using the switch interview method. Build your first job map. Translate one job into a positioning statement. Then test it. The shift from product-centric to job-centric thinking is one of the highest-leverage moves a product marketer can make.