Jobs to Be Done Framework: A Practical Guide for Startup Founders

A customer doesn't want a drill. They want a hole.

More specifically, they want to hang a picture on the wall so their living room looks nice.

Even more specifically: They want their spouse to think their living room looks nice so they feel proud when friends come over.

The 'job' isn't drilling. It's "Create a space I'm proud to show people."

Understanding the job changes everything about how you build and position your product.

This is the Jobs to Be Done (JTBD) framework. It's one of the most powerful customer research tools available to founders, and it's often misunderstood.

This guide explains the framework, shows real examples, and walks you through applying it to your own idea.

What Is Jobs To Be Done?

Jobs to Be Done, pioneered by Clayton Christensen, says:

Customers don't buy products. They hire products to do jobs.

A job is the progress a customer wants to make in a particular context.

When someone "hires" your product, they're bringing it in to make progress on something that matters to them.

Understanding that job — the progress, the context, the stakes — is more powerful than understanding demographics, features, or even stated needs.

The Three Types of Jobs

Every job has three dimensions:

1. The Functional Job

What: What task do they want to accomplish?

Example: "I want to track my business expenses accurately."

This is the surface-level job. It's important but often not enough to drive purchasing.

2. The Emotional Job

What: How do they want to feel?

Example: "I want to feel in control of my finances" or "I want to feel smart and organized."

This is where positioning happens. People buy products that make them feel a certain way about themselves.

3. The Social Job

What: How do they want to be perceived by others?

Example: "I want to be seen as a disciplined, organized founder" or "I want my accountant to think I have my finances together."

This is often the most powerful but least understood.

Real Example: The Milkshake That Changed Everything

Clayton Christensen famously studied a fast-food chain's milkshake sales.

The chain wanted to increase milkshake sales, so they surveyed customers: "What do you want in a milkshake?" Answer: Vanilla, chocolate, and strawberry, with fruit.

They added fruit. Sales didn't change.

Then they observed behavior. They noticed that milkshakes were purchased almost exclusively in the morning by lone commuters who bought nothing else.

They asked those commuters: "What job did you hire this milkshake to do?"

Interesting pattern emerged: "I have a long commute. I need something that's not messy that I can eat in the car that keeps me full until lunch but I can finish quickly."

The functional job: "Provide convenient breakfast" The emotional job: "Feel like I'm treating myself" The social job: Didn't apply here

That insight was gold. The milkshake's real competition wasn't other milkshakes or breakfast foods. It was not eating, or grabbing a donut from the coffee shop.

The chain made milkshakes thicker (easier to eat one-handed), changed the position (checkout counter for convenience), and shifted messaging. Sales increased significantly.

This happened because they understood the job, not just the product.

How to Discover the Jobs Your Customers Are Hiring For

The JTBD discovery process is an interview structure. Here's how to run it:

Step 1: Understand the Trigger

Ask: "Tell me about the first time you realized you had a problem that needed solving."

Listen for: What prompted the search? What were they doing before? What changed?

Example: "I was fumbling with multiple spreadsheets trying to reconcile expenses. I realized I was spending way too much time on this and thought 'There has to be a better way.'"

Step 2: Explore the Current Solution

Ask: "What do you currently use to solve this?"

Listen for: Not just the tool, but how they use it and what's unsatisfying about it.

Example: "I use Google Sheets. I manually enter expenses from my email and credit card statements. It works but it's tedious and error-prone."

Step 3: Identify the Functional Job

Ask: "What exactly are you trying to accomplish?"

Listen for: The practical outcome they want.

Example: "I want to track expenses accurately so I know what I've spent by category."

Step 4: Identify the Emotional Job

Ask: "How would it feel if this problem disappeared? How would you feel differently about your finances?"

Listen for: The emotional state they're seeking.

Example: "I'd feel relieved. I'd feel like I have my finances under control instead of chaotic."

Step 5: Identify the Social Job

Ask: "If you solved this problem perfectly, how would others perceive you differently?"

Sometimes they'll say "I don't care what others think." That's valid. Not all jobs have a social component.

Example: "My accountant would think I had my books together. My business partner would trust that I know where money is going."

Step 6: Identify the Constraints

Ask: "What would make you decide NOT to use a tool like this?"

Listen for: Deal-breakers, trade-offs, competing priorities.

Example: "If it required me to change how I work, I'd stick with spreadsheets. If it costs more than $100/month, I can't justify it."

From Jobs to Product Features

Once you understand the jobs, you can map them to features:

When JTBD Fails

JTBD is powerful but not universal. It fails when:

• The job is purely functional and emotionless (mining equipment)
• Customers can't articulate their jobs clearly
• The social component is irrelevant (B2B infrastructure tools)
• You over-interpret emotional language

Don't force JTBD if it doesn't apply. Use it when customer motivation is complex.

JTBD for Product Positioning

Where JTBD really shines is positioning. Once you understand the jobs, you can position directly to them:

Bad positioning: "Expense tracking software with AI categorization" Good positioning (JTBD-based): "Feel in control of your finances. Spend 2 hours less/month on expense tracking. Your accountant will think you're organized."

The second positioning maps directly to the functional, emotional, and social jobs.

JTBD for Pricing

Understanding jobs also informs pricing:

If the emotional job is "feel in control," and you enable that, you can charge a premium. If the job is purely functional, commodities pricing applies. If the social job is strong (status, credibility), you can create tiers that signal status.

Connection to Customer Research

JTBD is one technique within comprehensive customer research →. It's not a replacement for interviews; it's one framework you apply during them.

Best practice: Do 10 general customer interviews, then 5 JTBD-specific interviews once you've identified patterns.

JTBD Interview Template

Here's a script you can use:

1. "Tell me about the last time you faced [problem area]."
2. "What were you doing before you realized this was a problem?"
3. "What did you try to solve it?"
4. "Why didn't that work perfectly?"
5. "What would improve if this problem disappeared?"
6. "How would you feel differently?"
7. "Would anyone else think differently of you?"
8. "What would make you decide this isn't worth solving?"

The Power of JTBD

JTBD shifts you from building "what people ask for" to building "what people actually need."

People ask for features. People need progress.

Build for the progress, and the features follow naturally.

Use Edmired to structure JTBD interviews and map jobs to product opportunities. Join the beta.