The Jobs-to-Be-Done Framework for Startup Founders

People don't buy products. They hire them to do a job. That one reframe — from "who is my customer?" to "what job is my customer trying to accomplish?" — changes how you build, market, and sell everything.

What Jobs-to-Be-Done Actually Means

The JTBD framework, developed by Clayton Christensen and expanded by researchers like Bob Moesta, starts with a deceptively simple question: what progress is this person trying to make in their life or work?

A "job" isn't a task. It's a goal with context and emotion attached. The famous example: people don't want a drill. They want a hole in their wall. But zoom out further — they want to hang a picture. Zoom out again — they want their house to feel like a home.

Each layer of zoom reveals different competition, different messaging, and different product decisions.

Jobs have three dimensions:

• Functional: the practical outcome (process invoices faster)
• Emotional: how they want to feel while doing it (confident, in control)
• Social: how they want to be perceived (look competent to my team)

A product that serves all three dimensions creates significantly stronger attachment than one that only solves the functional need.

How JTBD Differs from Personas

Personas describe who your customer is. JTBD describes what they're trying to accomplish. The difference matters because people who look completely different can share the same job.

A 45-year-old CFO and a 28-year-old startup founder might both be "hiring" a financial forecasting tool to get clarity before a board meeting. Same job. Very different personas. If you built your product strategy around persona differences, you'd end up with unnecessary complexity and probably worse marketing.

Conversely, two people with identical demographic profiles can have radically different jobs. The persona tells you nothing useful about which one will buy.

JTBD is not a replacement for personas — it's a different layer of understanding that often matters more for product decisions.

Finding the Real Job

The job customers articulate isn't always the job that drives their purchase. To find the real job, you need to understand the moment the decision was made — what Moesta calls the "switch."

Ask customers who recently bought (or considered buying) your product:

• What was happening in your life when you first started looking for a solution?
• What made you finally decide to act?
• What were you worried about when you switched?
• What would happen if this solution disappeared tomorrow?

The answers reveal the real job. Often it's triggered by a specific event — a new manager, a failed quarter, a team expansion, a deal lost. That trigger is the context that makes the job urgent.

Applying JTBD to Product Decisions

Once you understand the job, it clarifies decisions that would otherwise be debates:

What features to build. If the job is "get board-ready numbers in under two hours," then UI speed and one-click export matter more than advanced customization. Cut what doesn't serve the job.

What to cut. Features that serve adjacent or imagined jobs — however technically impressive — drag you down. JTBD gives you permission to cut with confidence.

How to sequence your roadmap. Map every proposed feature back to the core job. Prioritize the ones that reduce friction in completing that job.

Practical Examples

Slack. The job isn't "send messages at work." It's "feel connected to my team without drowning in email." That's why Slack built threads, emoji reactions, and status indicators — they serve the emotional and social dimensions of the job.

Notion. The job for many users isn't "take notes." It's "stop using five different tools and feel like I have my work organized." The all-in-one positioning is a direct response to that job.

Calendly. The job is "schedule a meeting without three back-and-forth emails making me look disorganized." The product solves the functional and social job in one move.

How to Run a JTBD Research Session

Structure your interviews around the moment of purchase or adoption:

1. Ask them to tell you the story of when they first started looking for a solution
2. Ask what they were using before and what frustrated them about it
3. Ask what alternatives they considered and why they didn't work
4. Ask what was the thing that made them finally move forward
5. Ask what their life looks like now vs. before

Listen for the words they use naturally. The language customers use to describe their job is often the exact copy that should appear in your marketing.

JTBD isn't a one-time exercise. The most useful founders make it a continuous discipline — constantly checking whether the job they built for is still the job customers are trying to do.