The JTBD Blueprint: Why Customers "Hire" Your Solution
Type: media
Stage: Stage 1: Problem Proof
Difficulty: intermediate
A guide to the Jobs-to-be-Done framework to uncover the deeper functional and emotional progress users are trying to make.
Overview
Most founders validate the wrong thing. They confirm that people have a problem, but miss the deeper question: what progress is the person actually trying to make? The Jobs-to-be-Done framework reframes your research around the 'job' a customer is trying to accomplish — and it predicts whether they'll pay to accomplish it.
The hiring concept
Customers don't buy products. They hire them to move from a painful current state to a desired future state.
When someone buys project management software, they're not buying features — they're hiring a solution to feel in control of their work. When someone buys accounting software, they're hiring it to feel less anxious about money.
This framing changes what you validate. You're not asking 'do they have this problem?' — you're asking 'what are they currently hiring to solve it, and why is that hire failing them?'
The three dimensions of a job
Every job has three layers you need to validate:
• Functional — the practical task the person needs to complete (e.g., 'track my invoices')
• Emotional — how they want to feel while doing it or after it's done (e.g., 'confident I won't miss anything')
• Social — how they want to be perceived by others (e.g., 'look professional to clients')
A solution that only addresses the functional dimension is easy to copy. Solutions that address all three dimensions create loyalty. Your problem interviews should surface language from all three layers — not just the task.
Why this predicts innovation success
Research shows that innovation success rates jump from 17% to 86% when founders focus on underserved jobs — problems where importance is high but current satisfaction is low.
The formula: find a job that matters a lot to people and that existing solutions handle poorly. That gap is your market.
To score this: ask interviewees to rate how important the job is (1–10) and how satisfied they are with current solutions (1–10). A gap of 4+ points between importance and satisfaction is a strong signal of an underserved market.
The Switch Interview
Standard problem interviews ask general questions. The Switch Interview asks about the specific moment someone changed behavior.
Ask: 'Tell me about the last time you switched from one solution to a different one for this problem. What happened right before you decided to make the switch?'
The moment of switching — when someone 'fires' one solution and 'hires' another — reveals more about what really matters than any other question. You'll hear the actual trigger, the real frustration, and the specific outcome they were hoping for.
Do this with five people who recently switched, and you'll know more about what your market wants than most founders learn from fifty generic interviews.
Putting it into practice
After your Switch Interviews, sort your findings into the three dimensions. Look for patterns:
• What functional jobs appear in every story?
• What emotional states keep coming up?
• What social signals matter to this audience?
If you can't articulate all three for your target user, you don't yet understand the job well enough to build for it.