Jobs to Be Done: The Founder Guide to the JTBD Framework

Jobs to be done (JTBD) is a customer-research framework that asks "what is the customer trying to accomplish?" instead of "who is the buyer?" -- revealing the functional, emotional, and social progress a person seeks when they hire a product or service. For startups, JTBD gives you a sharper lens for positioning and messaging than persona research ever can.

Most founders build products first and search for customers second. JTBD flips that sequence: start with the progress a customer is already trying to make, then build positioning around that insight. The core idea -- developed by Clayton Christensen and Bob Moesta -- is simple. People do not buy products. They hire products to get a job done. This guide covers the framework, why it matters for startups from pre-seed to Series A, and how to apply it across positioning, messaging, and GTM.

TL;DR: Jobs to Be Done in 60 Seconds

• JTBD reframes demand around the progress a customer wants to make -- not around their demographics.
• Customers "hire" products to get a job done. Understanding the job reveals competitors and demand you did not know existed.
• Jobs have three dimensions: functional, emotional, and social. Winning products address all three.
• JTBD isolates why someone switches, making it sharper than persona research for positioning and creative.
• Start by interviewing recent switchers to reconstruct the struggling moment that triggered the purchase.

What Is the Jobs to Be Done Framework?

The JTBD framework is a theory of demand. Customers do not buy because of who they are. They buy because they hit a moment of struggle and "hire" a product to close the gap between where they are and where they want to be. The job is the unit of analysis: the progress a person tries to make in a specific circumstance.

Christensen and Moesta developed this while studying milkshakes. People bought them in the morning not for taste but because a milkshake kept a commuting driver occupied and full until lunch. Once you see the job, the competitive set, feature priorities, and messaging all change.

Every job has three dimensions:

Products that win big nail all three dimensions. Products that stagnate usually only solve the functional job and compete on price alone.

Why Does Jobs to Be Done Matter for Startups?

For an early-stage startup, acting on wrong insights burns runway. JTBD changes the questions you ask -- and the answers you get.

When you ask "what do you want," you get feature requests -- guesses about solutions, not demand. When you ask "what were you doing the day you decided to search for a solution," you get the struggling moment that made someone stop tolerating their workaround. That moment is what your brand positioning needs to name.

JTBD also reveals competitors invisible to traditional analysis. If the job is "show up prepared for every client meeting," the competition includes Slack threads, shared Google Docs, and the project manager who manually wrangles everyone. None appear on a G2 category page. This is non-consumption: most of the market patches together workarounds because no product exists for their specific job.

For startups building brand messaging, JTBD provides the raw material. Your value prop becomes "the fastest way to get [job] done" with the exact context the customer already wants.

How to Do Jobs to Be Done Research (Step by Step)

JTBD research reconstructs the timeline around a purchase or switching event. The founder-friendly process:

1. Identify recent switchers. Interview people who recently hired your product or a competitor's, plus people who recently fired it. Target 10 to 15 interviews per job.
2. Reconstruct the timeline. Walk them through the day they decided to search. What triggered it? What had they been tolerating? Find the first thought that made the status quo unacceptable.
3. Map the forces of progress. Identify the push of the old solution, the pull of the new, the anxiety of switching, and the habits holding them in place.
4. Map the job dimensions. Document functional, emotional, and social jobs. In B2B, the emotional job often dominates: buyers want to feel confident they will not get fired.
5. Write the job statement. Synthesize interviews into one solution-agnostic statement.
6. Prioritize. Score jobs on importance and frequency. The ones that are both critical and frequent are your priorities.

Pair JTBD interviews with customer discovery interviews for a fuller picture.

How to Write a Jobs to Be Done Statement

A job statement captures what the customer is trying to accomplish without describing your product. The format:

When [situation], I want to [verb + object], so I can [outcome].

Use concrete verbs. "Manage my team" is vague. "Make sure every engineer knows what to build this week" is specific. Name the outcome -- not just the task, but why it matters.

The test: if someone who has never seen your product reads the statement and nods because they felt that frustration, you captured a real job. If they need your product explained first, you wrote a feature description.

Jobs to Be Done vs Personas: What Is the Difference?

Personas describe who the customer is. JTBD describes what they are trying to accomplish. Different questions, different uses.

The strongest GTM strategies use both. Personas tell you who to reach and where. JTBD tells you what to say and what to build.

How to Use Jobs to Be Done in Your Go-To-Market

JTBD earns its keep when it changes what you say and where you invest:

• Positioning. Lead with the job, not the feature. If the job is "show up prepared for every client meeting," your brand positioning should say that -- not "AI-powered collaborative knowledge base."
• Ad creative. "Still sending five emails to find one meeting time?" converts better than "Introducing SmartCalendar v2." JTBD gives you the struggling moment for every headline. At Stackmatix, JTBD-driven ad creative consistently outperforms persona-driven creative.
• Landing pages and SEO. Name the job in your hero headline and target job language in keywords. "How to reconcile bank transactions faster" gets more search volume than "best accounting automation platform."
• Onboarding. Deliver progress toward the core job in the first five minutes. If the job is "close the books by Friday," onboarding should reach a reconciled balance, not tour your dashboard. Time-to-job-completion is the metric.
• GTM planning. JTBD reveals demand gaps -- underserved jobs, high-frequency jobs, segments competitors ignore -- that shape your go-to-market strategy.

At Stackmatix, we use JTBD as a core input for venture-backed startups. When a founder brings us a product and audience, we first map the jobs that audience is already trying to complete. Every recommendation flows from that map.

Common Jobs to Be Done Mistakes Founders Make

• Defining the job as a feature. "Users need a dashboard" is a feature request, not a job. Strip your product from the statement and see if a real human struggle remains.
• Ignoring emotional and social jobs. Most founders stop at functional. In B2B, the need for confidence often drives purchases more than any feature matrix.
• Treating JTBD as a survey. Jobs emerge through timeline reconstruction, not self-reporting. Customers tell stories about events, not labels.
• Skipping the struggling moment. Without it, you have a wish. Pinpoint the event that made someone stop tolerating the old way and start searching.
• Confusing buyer with user. In B2B, the user and signer have different jobs. Onboarding solves the user's job; sales solves the buyer's.

Key Takeaways

• JTBD reframes demand around the progress a customer is trying to make, revealing the struggling moment behind every switch.
• Use personas to find your audience; use JTBD to craft what you say. JTBD is the sharper tool for messaging and positioning.
• Conduct 10 to 15 interviews, reconstruct purchase timelines, find the struggling moment, and write solution-agnostic job statements.
• Apply JTBD across your GTM: positioning, ad creative, landing pages, SEO, onboarding, and GTM strategy.

Frequently Asked Questions

What Is Jobs to Be Done?

Jobs to be done is a customer-research framework developed by Clayton Christensen and Bob Moesta that reframes markets around the progress a customer is trying to make rather than around the customer's demographic or psychographic profile. Instead of asking "who is the buyer," JTBD asks "what job is the customer hiring this product to do." A job includes functional dimensions (the practical task), emotional dimensions (how the customer wants to feel), and social dimensions (how the customer wants to be perceived by others). For startups, JTBD reveals demand drivers that traditional persona research often misses -- such as non-consumption, workarounds, and competitors you did not know you had.

What Is the Difference Between Jobs to Be Done and Personas?

Personas describe who the buyer is -- demographics, role, goals, pain points, and behavioral traits. Jobs to be done describes what the buyer is trying to accomplish -- the progress they seek in a specific context. A persona might describe a "VP of Engineering at a Series A startup," while a job describes "when I am onboarding a new engineer, I want to minimize the time to first commit so the new hire feels productive and confident on day one." The two frameworks are complementary: personas help you identify and empathize with your audience, while JTBD helps you understand the causal reason they buy. Most startups benefit from using both, but JTBD is often the sharper tool for messaging, positioning, and ad creative because it cuts directly to the switching trigger.

How Do You Write a Jobs to Be Done Statement?

A jobs to be done statement follows a simple format: "When [situation], I want to [verb + object of progress], so I can [outcome]." For example: "When I am planning my quarterly roadmap, I want to surface the features customers have actually requested, so I can prioritize based on demand instead of gut feel." The key rules are: use a concrete verb (not "improve" or "optimize" -- those are too vague), name the specific context or situation that triggers the job, describe the outcome in emotional or functional terms, and avoid embedding a solution in the statement. A good JTBD statement describes the progress the customer seeks independent of your product. If you can swap your product name into the statement and it still makes sense, the statement is solution-agnostic -- and that is the goal.

Why Do Companies Use the Jobs to Be Done Framework?

Companies use JTBD because it reveals demand drivers that other research methods miss. Traditional methods -- surveys, focus groups, win-loss analysis -- often capture what customers say they want rather than why they switched. JTBD identifies the struggling moment, the push of the old solution, the pull of the new, and the anxieties and habits that keep people stuck. This makes it especially valuable for product strategy, competitive positioning, and marketing. Companies from Intercom to Basecamp to IKEA have used JTBD thinking to discover new growth categories, redesign onboarding flows, and sharpen ad creative -- not by asking customers what they want, but by understanding the job they are already trying to do.

How Do Startups Use Jobs to Be Done in Marketing?

Startups use JTBD in marketing by translating job statements directly into messaging, ad creative, landing page copy, and SEO content. Instead of writing headlines about features or benefits in the abstract, you write headlines that name the job the customer is trying to get done. A landing page for a scheduling tool might lead with "Stop trading emails to find a meeting time" rather than "Smart calendar with AI-powered scheduling." The job language speaks to the struggling moment the customer already experiences, which converts at a higher rate than feature language. Startups also use JTBD to segment audiences by job rather than by persona -- grouping customers who share the same job to be done, even if they have different titles, industries, or demographics. In ad creative, JTBD-driven copy often outperforms persona-driven copy because it connects with the emotional context of the switching moment.