How to actually pull off Jobs To Be Done (without losing your mind or building features nobody wants)
A practical field guide to JTBD: how to run switching interviews, map the four forces, avoid the classic traps, measure real progress, and turn it all into product, marketing and sales decisions.
6 October 2026 · 9 min read
Most product strategy, customer research, and marketing roadmaps are built on a foundation of pure, unadulterated guesswork that can sometimes be confused as professional rigor. We sit in air-conditioned rooms, drink lukewarm coffee, look at a bunch of pie charts about demographic age brackets and geographic regions, and then praise our deep psychic ability to know what human beings want to buy.
Truth is, we don't.
Demographics tell you who is buying your stuff, which is about as useful for predicting actual behavior as knowing someone’s favorite color or whether they prefer chunky peanut butter over smooth. People don't buy products because they fit neatly into a spreadsheet cell labeled "Millennial Professional, Income Bracket $100k." They buy things because they are trying to make progress in a specific, highly inconvenient circumstance. They are trying to get a job done.
The Jobs-to-Be-Done (JTBD) framework addresses exactly this. But like every good thing, it’s only as good as the execution. This guide here will show you precisely how to pull this off.
Part 1: The Research Process
JTBD research is retrospective, narrative-driven detective work. You aren't asking people what they want, because customers are notoriously, hilariously bad at predicting future behavior or dreaming up innovative solutions. Instead, you are investigating a historical crime scene: how they solved a recent, burning problem.
1. Target the Recent Switchers
Find people who recently purchased your product, or a competitor’s alternative, within the last two to four weeks. If you interview someone who bought your software eighteen months ago, their memory of the purchase process will have morphed into a comforting fictional narrative where they look much smarter and more rational than they actually were. Strike while the memory iron is hot.
2. Run the Switching Interview (The Timeline Method)
When you sit down with these folks, treat it like an investigative documentary. You want to trace their journey backward from the moment they handed over their credit card all the way back to the initial "first thought" that crossed their mind. Walk through the timeline step-by-step:
- When did they first realize the old way wasn't cutting it?
- What was the exact straw that broke the camel's back?
- How long did they suffer before doing something about it?
- What alternative solutions did they Google, try, reject, or ignore?
Say you’re interviewing someone who just ditched their project management tool for a new platform. Instead of asking how they like the buttons, you map the true timeline:
- Three months ago (first thought), they spent a miserable Sunday night manually color-coding spreadsheets because their old software wiped out four team updates.
- They suffered in silence for six weeks (duration of pain) while their team mutinied.
- The straw that broke the camel's back (the trigger) happened when a client emailed asking why a major deliverable was missing, and the old tool crashed trying to load the file.
Before landing on your site, they spent two frustrating nights Googling free templates, tried a bloated enterprise alternative that was too expensive, and completely ignored three other options because their onboarding pages looked like a tax form.
3. Map the Four Forces of Progress
Every single purchase decision is a tug-of-war influenced by four psychological forces.
- The Push of the Situation: What annoying, frustrating, or downright painful problem triggered their search for a new escape hatch?
- The Pull of the New Solution: What shiny, alluring promise did your product (or the competitor's) make that made them think, "Ah, yes, this will finally save me"?
- The Habit of the Present: What comfortable, lazy routines tied them to the old, broken way of doing things just because it was familiar?
- The Anxiety of the New: What secret fears, doubts, and cynical suspicions did they harbor about making the switch? "Will this break my existing workflow? Will I look like an idiot if it fails?"
Part 2: What to Look Out For
If you wander into JTBD interviews unprepared, you will fall headfirst into several classic psychological and methodological traps.
Beware of Stated Preferences
When a user says, "I really need an automated multi-channel reporting dashboard with AI-driven widget syncing," do not run back to your engineering team shouting eureka. They are giving you a solution, not a job. Your job as the researcher is to peel back the layers of that feature request until you find the raw human motivation underneath. Why do they want that report? Is it because they spend four hours every Friday poring over CSV files before presenting to an executive team that has no idea what they are talking about? Dig past the requested tool to find the actual struggle.
Separate Solutions from Core Jobs
Remember Theodore Levitt’s classic wisdom: people don't want a quarter-inch drill; they want a quarter-inch hole. In a modern software or service context, customers don't want your fancy enterprise platform. They want the business outcome that platform enables. The solution can change, evolve, or get disrupted by artificial intelligence tomorrow, but the underlying job remains stubbornly, beautifully stable.
Do Not Ignore the Emotional and Social Layers
A functional job is only the tip of the iceberg. Every single human endeavor is propped up by complex psychological scaffolding. Make sure your research captures all three dimensions:
- The Functional Job: The practical, nuts-and-bolts physical or digital task that needs executing (e.g., compiling data, publishing content, migrating a database).
- The Emotional Job: How the user actually wants to feel while executing the work. Do they want to feel calm, in control, intelligent, or relieved of crushing operational anxiety?
- The Social Job: How the user wants to be perceived by their peers, their boss, or their clients. Do they want to look like an innovative thought leader, a dependable executor, or a rockstar who saves the quarter?
Take a marketing manager buying a high-end backlink or SEO visibility platform.
- The Functional Job: They need to secure authoritative placements to increase organic search visibility and rankings without triggering manual penalties from search engines.
- The Emotional Job: They want to stop waking up at 3:00 AM sweating over algorithm updates and instead feel a deep, grounding sense of calm and total control over their traffic metrics.
- The Social Job: They want to walk into the quarterly review meeting looking like an absolute rockstar who single-handedly turned SEO into a predictable profit center, rather than the person who burns marketing budget on vanity metrics that nobody can explain.
Part 3: What to Measure
JTBD forces you to measure things that reflect genuine customer progress and friction.
- Job Completion Rate: When a user sets out to accomplish a core job using your product, do they actually cross the finish line successfully, or do they drop halfway through in a fit of rage?
- Time-to-Hire and Time-to-Fire: How quickly do customers adopt ("hire") your solution when a triggering event disrupts their routine, and how fast do they abandon ("fire") competing tools that let them down?
- Circumstance Frequency: How often does the specific triggering circumstance arise in the customer's daily workflow? A job that happens once a year requires a completely different strategic approach than a job that happens ten times a day.
- Anxiety and Friction Indices: Track where users hesitate, stall, or flood your support inbox with questions during onboarding. That is where your product is failing to calm their pre-existing fears.
Think about how circumstance frequency changes everything: If you sell corporate tax compliance software, your customer experiences that triggering circumstance precisely once a year, meaning your onboarding has to be foolproof because they will have forgotten how your interface works by next April.
Contrast that with an internal team collaboration tool where the circumstance happens twenty times a day. If your anxiety and friction indices spike because users stall out on permission settings or flood your support inbox every time they try to invite a colleague, your product is actively teaching them to look for your competitor.
Part 4: How to Use the Data
You need to weaponize these insights across your entire organization:
1. Product Development & Roadmap Prioritization
Stop letting the loudest customer or the highest-paid person in the room dictate your product roadmap based on whatever random idea popped into their head during a morning shower. Prioritize features based on underserved job steps, specifically targeting the moments where customers experience the highest friction, anxiety, or failure rates.
2. Marketing & Copywriting That Resonance Built
Throw away generic, buzzword-laden marketing copy that talks about "synergistic enterprise solutions." Instead, take the exact phrases, emotional pain points, and triggering situations your interviewees used during the switching interviews and mirror them right back in your landing page copy. When a prospective customer lands on your site and reads a sentence that describes their exact internal monologue word-for-word, conversion stops feeling like a sales funnel and starts feeling like an inevitability.
3. Sales & Onboarding Friction Reduction
If your research reveals that customers harbor a deep-seated anxiety about migrating data or breaking existing workflows, don't hide that anxiety behind upbeat marketing spin. Address it head-on in your onboarding flows. Show them step-by-step safety nets, offer human reassurance, and accelerate their path to the first tangible "win" so they can stop worrying and start succeeding.
The Golden Formula
Whenever you feel like your team is losing the plot, bring everyone back to a single, elegant sentence structure that anchors every strategic decision:
"When [Situation/Trigger], I want to [Motivation/Job], so I can [Expected Outcome]."
Get that right, and you’ll never have to guess what your market wants ever again.
Where this shows up in the work
Keep reading
- The marketing funnel is nice, but it misses a very crucial aspect: the whyThe funnel is a model of the business, not of the customer's mind. Bob Moesta's demand-side thinking shows what is happening underneath each stage, and why that changes demos, content, search and sales.
- Personas describe people. Jobs explain decisions.JTBD is a lens, not an identity. Used well it explains why someone switched; used badly it becomes another artefact nobody opens.
- Positioning is not copywritingIf the words outrun the product, you have bought yourself an expensive disappointment. Positioning should be the shortest accurate description of real value.