Back to blog

Jobs-to-be-done

Jobs To Be Done Framework: 5 Practical Steps

12/28/2024 · 11 min read

Last reviewed: 3/6/2026

Ninety-five percent of new products fail in their first year. The reason is not bad engineering or weak marketing. It is a fundamental misunderstanding of what customers actually want. Teams build features nobody asked for, launch products that solve the wrong problems, and watch competitors win with seemingly similar ideas.

The jobs to be done framework fixes this by changing the question. Instead of asking "What features should we build?" it asks "What job is the customer hiring this product to do?" That shift in perspective, from product-out to customer-in, is the difference between guessing and knowing.

This guide breaks the JTBD framework into five practical steps you can start using today. No deep pockets required. No PhD in innovation theory. Just a structured way to uncover what your customers actually need and build products they will choose.

What Is the Jobs to Be Done Framework?

The jobs to be done methodology is built on one powerful idea. People do not buy products. They "hire" products to make progress in a specific situation. A person does not buy a drill because they want a drill. They buy a drill because they want a hole in the wall. And they want a hole in the wall because they want to hang a picture that makes their home feel complete.

Tony Ulwick developed the theory, and Clayton Christensen popularized it. The JTBD framework moves attention from the product to the customer's underlying motivation for change. According to Harvard Business Review's innovation research, companies that understand customer jobs outperform competitors in both product development success rates and market adoption speed.

Three dimensions of every customer job

Every job a customer needs done has three dimensions that drive their decision.

Functional: the practical task they need to complete. "Help me file my taxes accurately." Emotional: how they want to feel during and after the process. "Help me feel confident I am not making mistakes." Social: how they want to be perceived by others. "Help me look financially responsible to my partner."

Most product teams focus only on the functional dimension. The jobs to be done framework insists you capture all three. This is what separates products people tolerate from products people love.

Why jobs stay stable over time

Products and technologies change constantly. Customer jobs do not. People have needed to "manage personal finances" for centuries. The tools evolved from ledger books to spreadsheets to apps, but the job stayed the same.

This stability makes the JTBD framework ideal for long-term product strategy. When you anchor your roadmap to customer jobs instead of competitor features, you build something durable. You also build a foundation for strong positioning, which connects directly to how you define your ideal customer profile.

The JTBD Formula: When / I Want / So That

The jobs to be done methodology uses a simple formula to capture customer jobs precisely. The structure is: "When [situation], I want to [motivation], so I can [expected outcome]."

Example: "When I am onboarding a new enterprise client, I want to show them value within the first week, so I can reduce the risk of early churn and secure the expansion conversation."

This formula works because it captures three essential elements. The situation provides context. The motivation describes what the customer is trying to accomplish. The expected outcome explains why it matters to them.

What makes a good job statement

A well-crafted job statement must be solution-agnostic. It focuses on what customers want to accomplish, not how they currently do it. "Maintain oral health" is a job. "Brush teeth" is a solution. The distinction matters because it opens up the innovation space.

Job statements must also be measurable. Each statement should include criteria customers use to gauge success. Companies that define needs as measurable outcomes make innovation far more predictable. When you write job statements for your value proposition canvas, this precision pays off immediately.

Step 1: Conduct JTBD Interviews

JTBD interviews are different from standard user research. You are not asking about product features. You are reconstructing the story of a decision.

Start by identifying recent customers who switched to your product (or away from it). The switching moment is where the richest insight lives, because it reveals what pushed someone to seek change and what pulled them toward a specific solution.

How to run the interview

Begin by setting context. Ask about the customer's daily routine and the situation that triggered their search. Then dig into specific pain points and challenges they faced with their previous solution.

Uncover what drove and motivated the change. Define success criteria from the customer's perspective. Capture emotional and social dimensions, not just functional needs. A single one-hour JTBD interview can yield between 20 and 30 desired outcomes from one customer.

The key technique is the "timeline interview." Walk the customer backward from the purchase decision. When did they first realize the old way was not working? What did they try before your product? What almost stopped them from switching? These questions reveal the forces of progress that the jobs to be done framework is designed to uncover.

Start with 8 to 12 interviews. That is enough to identify clear patterns. You can expand later to validate and prioritize.

Step 2: Build a Job Map

A job map visualizes the complete job a customer is trying to accomplish. It breaks the job into sequential steps, from initial trigger to final evaluation.

Most jobs break down into 10 to 20 distinct steps. The map shows the ideal process flow, not how customers currently use existing solutions. This distinction is important. You are mapping the job, not the product.

The universal job map structure

Jobs typically follow this sequence: define what the job requires, locate necessary inputs, prepare the environment, confirm readiness, execute the core task, monitor progress, modify as needed, and conclude the job. Each step represents a potential opportunity for your product.

Job mapping helps you spot gaps that competitors miss. When you break a job into specific steps, you see where customers struggle, where they piece together multiple tools, and where current solutions fall short. These gaps are your innovation opportunities.

The job map also becomes a powerful input for your SaaS marketing strategy. When you understand every step of the job your customer is hiring you to do, your go-to-market messaging becomes dramatically more specific and compelling.

Step 3: Document Customer Desired Outcomes

Desired outcomes are how customers measure success when completing a job. Each market you study typically reveals between 75 and 150 different outcome statements. That depth of insight is what makes the jobs to be done methodology so powerful.

Writing effective outcome statements

Every outcome statement must be measurable, controllable, solution-agnostic, stable over time, and tied directly to the job. Good outcome: "Minimize the time it takes to identify which accounts need immediate attention." Bad outcome: "Have a better dashboard."

The first version is precise, measurable, and independent of any specific solution. The second is vague and tied to a feature. When you accumulate 75 to 150 outcomes like the first version, you have a complete map of what customers value. That map drives every product and marketing decision.

Categorizing outcomes by job dimension

Organize outcomes across functional, emotional, and social dimensions. Research shows that customers express 20 to 30 emotional and social jobs for any given functional job. Capturing this full picture is what separates surface-level research from genuine customer understanding.

This depth of customer insight also transforms your positioning work. When you know exactly which outcomes are underserved, you can build messaging that speaks to real pain, not assumed pain. That is the connection between JTBD research and the customer journey map.

Step 4: Prioritize Underserved Outcomes

Not all outcomes deserve equal attention. The JTBD framework uses opportunity scores to identify which customer needs are most important and least satisfied.

Calculating opportunity scores

For each outcome, measure two things: how important it is to the customer and how satisfied they are with current solutions. The formula is: Opportunity Score = Importance + (Importance minus Satisfaction).

High importance plus low satisfaction equals a major opportunity. High importance plus high satisfaction means the need is already well served. Low importance outcomes, regardless of satisfaction, are distractions.

This evidence-based approach focuses innovation efforts where they will have the most impact. Instead of brainstorming hundreds of ideas and hoping one sticks, you target confirmed gaps in the market.

Moving from scores to strategy

Prioritized outcomes become the foundation of your product roadmap and your go-to-market strategy. Every feature you build should address a specific underserved outcome. Every message you write should speak to the job the customer is trying to accomplish.

This is where the jobs to be done framework connects directly to product marketing. The outcomes you identify in JTBD research become the value claims in your positioning, the pain points in your sales enablement, and the proof points in your case studies.

Step 5: Validate Solutions Against Customer Jobs

Before investing heavily in development, validate that your solution actually helps customers complete their job better. The JTBD framework measures progress across three dimensions: time, predictability, and efficiency.

Three validation questions

Time: How much faster can customers complete their job with your solution? Predictability: How reliably can they achieve their desired outcome? Efficiency: How much waste, effort, or loss does your solution eliminate?

These customer-centric metrics replace subjective feature discussions with objective outcome-based decisions. Every feature you build should demonstrably improve at least one of these three dimensions.

Rapid validation methods

Use job-centric testing, where you assess solutions based on how well they help customers complete their core job. Measure each feature against specific desired outcomes. Track customer progress in speed, predictability, and efficiency.

Teams can validate solutions in a single day of focused testing. This rapid validation approach saves months of building the wrong thing, and gives you concrete evidence to bring into go-to-market planning.

JTBD Framework Examples in Practice

The jobs to be done methodology works across industries and company sizes. Here are three patterns that illustrate how it changes product and marketing decisions.

Example 1: SaaS onboarding

The job: "When I sign up for a new tool, I want to see value within the first session, so I can justify the time investment to my manager." The functional need is activation speed. The emotional need is confidence. The social need is looking competent to stakeholders.

A team using the JTBD framework would optimize onboarding not just for feature exposure but for the moment the customer feels "this was worth it." That moment is the job done well.

Example 2: Competitive displacement

The job: "When my current vendor keeps raising prices without adding value, I want to find an alternative that delivers the same outcomes at lower cost, so I can protect my budget for higher-priority initiatives." The switching trigger is not a feature gap. It is a progress gap. JTBD interviews reveal these triggers with precision.

Example 3: Enterprise expansion

The job: "When I have proven the tool works for my team, I want to demonstrate ROI to other departments, so I can expand the deployment and strengthen my internal reputation." Understanding this expansion job transforms how you build customer success programs and internal champion enablement.

Common Pitfalls When Implementing JTBD

The jobs to be done framework is powerful, but teams make predictable mistakes when adopting it.

Confusing the buyer's journey with the user's job

The buyer's journey describes how someone purchases a product. The user's job describes what they need to accomplish. These are different things. Mixing them up leads to solutions that are easy to buy but fail to deliver progress.

Focusing only on functional jobs

Teams that ignore emotional and social dimensions build products that work but do not inspire loyalty. Customers switch from functional-only products the moment a competitor offers the same capability with a better experience.

Surface-level interviews

Asking "What do you want?" is not a JTBD interview. The jobs to be done methodology requires reconstructing the timeline of a decision, uncovering the forces that drove change, and identifying the specific outcomes the customer was seeking. Shallow interviews produce shallow insights.

Trying to solve too many jobs at once

Scope creep kills JTBD implementations. Start with one core job. Map it thoroughly. Prioritize outcomes. Validate solutions. Then expand to adjacent jobs. This focused approach builds organizational confidence in the methodology and produces faster results.

Connecting JTBD to Product Marketing

The jobs to be done framework is not just a product development tool. It is the foundation of effective product marketing.

When you know the job your customer is hiring your product to do, positioning becomes precise. You stop guessing at pain points and start speaking to documented needs. Your messaging shifts from "here is what our product does" to "here is the progress you will make."

JTBD research feeds directly into your ideal customer profile. The customers who share the same underserved job are your best-fit segment. The outcomes they prioritize become your value propositions. The language they use in interviews becomes your messaging.

This connection between JTBD and go-to-market strategy is where the framework delivers its highest ROI. Teams that use JTBD insights for both product development and marketing alignment build products that sell themselves, because the positioning matches the job perfectly.

What to Do Next

Start small. Conduct 8 to 12 JTBD interviews with recent customers. Map the core job. Document desired outcomes. Prioritize the underserved ones. Then validate your solution against those outcomes before building anything new.

The jobs to be done framework does not require a massive organizational overhaul. It requires curiosity about your customers and discipline in how you capture and act on what they tell you. The teams that adopt this methodology consistently outperform those that rely on intuition alone.

If you need help implementing JTBD research or connecting it to your go-to-market strategy, explore consulting services designed for product and marketing teams. For more frameworks on customer research, positioning, and product marketing strategy, browse the full blog.

Related Reading

• How to build an ideal customer profile from JTBD insights
• Value proposition canvas: connect features to buyer outcomes
• Customer journey map: design the path from awareness to advocacy
• SaaS marketing strategy: the complete guide
• Work with a product marketing consultant
• Explore all product marketing articles