Lenny's PodcastThe ultimate guide to JTBD | Bob Moesta (co-creator of the framework)
CHAPTERS
- 0:00 – 0:36
JTBD misconception: context makes “irrational” choices rational
Bob opens by reframing JTBD away from simplistic “pain and gain” thinking. He argues that what looks like an anomaly is usually a missing piece of context, and the real goal is to understand when people will change behavior.
- •JTBD is about context + outcome, not pain + gain
- •Stories that seem irrational usually lack full context
- •Innovation comes from understanding what drives behavior change
- •The job is to find conditions where people will switch
- 0:36 – 1:38
Bob’s background and why this episode goes deep on JTBD
Lenny introduces Bob Moesta as a co-creator of the JTBD framework and highlights the audience excitement around this topic. The setup previews a tactical, end-to-end guide: what JTBD is, how to apply it, and how to interview customers.
- •Bob’s role as JTBD co-creator and longtime product builder
- •Why JTBD resonates with founders and product leaders
- •What the conversation will cover: application, interviews, examples
- •Audience questions and anticipation drive the agenda
- 1:38 – 4:58
Sponsors and quick pre-roll (Sidebar, Merge)
Lenny shares sponsor messages before the interview begins in earnest. These segments focus on career peer groups (Sidebar) and speeding up integrations via a unified API (Merge).
- •Sidebar: curated peer groups as a “personal board of directors”
- •Merge: unified API for shipping integrations faster
- •Reducing engineering overhead and accelerating roadmaps
- •Transition into the main conversation
- 4:58 – 7:44
What JTBD is: “People hire products to make progress” (Snickers vs. Milky Way)
Bob explains JTBD as demand-side thinking: people don’t buy products for their features, they hire them to make progress in a specific situation. The Snickers vs. Milky Way example reveals how the true competitive set changes with context.
- •Core idea: products are hired for progress, not purchased for attributes
- •Demand-side vs. supply-side competition framing
- •Snickers job: quick energy/meal replacement; competitors include coffee/protein drinks
- •Milky Way job: emotional recovery/comfort; competitors include wine/brownies/a run
- 7:44 – 11:42
Struggling moments create demand (and why roadmaps should follow them)
Bob argues demand isn’t created by products; it’s triggered by struggling moments that may exist long before anyone builds a solution. He shares how studying anomalies helped SNHU unlock massive growth by serving a different “back-to-school” job.
- •Causality: struggling moments → demand (not product → demand)
- •SNHU example: “anomalies” revealed a distinct job for older/returning students
- •Customer-centricity means mapping struggles, not just planning features
- •Roadmaps should anchor to struggling moments (especially beyond 90–120 days)
- 11:42 – 14:07
Forces of Progress model: push/pull vs. anxiety/habit (and friction reduction)
Bob lays out the behavioral system behind switching: push from the current situation, pull toward a new outcome, plus anxiety about the new and habit of the present. He shows how reducing friction can outperform adding features, using a real estate moving/storage example.
- •Four forces: Push (F1), Pull (F2), Anxiety (F3), Habit (F4)
- •Switch happens only when (F1+F2) > (F3+F4)
- •More features can increase anxiety rather than conversion
- •Reducing friction can boost sales (moving + storage bundle increased sales ~30%)
- 14:07 – 14:51
Demand-side sales: design the sales process around how people buy
Bob explains why sales processes often fail: they’re built around how companies want to sell, not how customers want to buy. He previews his approach as enabling progress rather than persuading, setting up the Autobooks case study.
- •Shift from “sell” to “help them buy”
- •Buying journey differs from the seller’s funnel assumptions
- •Friction in buying is often the real blocker
- •Demand Side Sales as an operating lens
- 14:51 – 16:59
Autobooks case study: rethinking demos to match buying phases (4x conversion)
At Autobooks, the team defaulted to pushing prospects into demos and closing motions, regardless of where customers were in their journey. By diagnosing buying-stage and tailoring demos accordingly, they shortened the sales cycle and dramatically improved conversion.
- •Two-sided selling complexity (banks + small businesses)
- •Problem: one demo/one close motion misaligned to customer timeline
- •Solution: ask where buyers are, then tailor demo type to their stage
- •Result: ~half the sales cycle time and ~4x conversion improvement
- 16:59 – 18:30
The six phases of buying—and why ‘what people say’ diverges from trade-offs
Bob expands the buying journey into six phases from first thought through ongoing use. He explains why surveys mislead (people claim they want one thing, but choose another) and why story-based analysis reveals real trade-offs.
- •Six phases: first thought, passive looking, active looking, deciding, first use, ongoing use
- •Passive vs. active looking: problem-aware/solution-unaware vs. solution-aware framing
- •Trade-offs reveal truth better than stated preferences
- •ENERGY STAR vs. finished basement example: survey desires vs. actual choices
- 18:30 – 18:39
JTBD interviewing method: extract the story, cluster pathways, find hire/fire criteria
Bob explains how JTBD research works: start with a precise framing question, interview recent buyers (or equivalent), and pull out pushes, pulls, anxieties, habits, and decision trade-offs. Instead of segmenting by traits, you cluster by pathways—sets of reasons that co-occur.
- •Start with “What happened that made today the day?” framing
- •Interview recent purchase/switch attempts to capture real causality
- •Capture pushes/pulls/anxieties/habits + hire/fire criteria
- •Cluster pathways (sets of reasons), don’t just segment by demographics
- 18:39 – 24:52
Bob’s TBI, reading/writing challenges, and why it shaped his approach
Bob shares the impact of early brain injuries on his ability to read and write, and how that pushed him toward concrete, story-driven learning. He explains how he “writes” books through recorded conversations and structured chapter systems.
- •Closed-head injuries led to major reading/writing limitations
- •Discomfort with vague marketing research terms (fast/easy/cheap)
- •Pattern recognition strengths and repeated-pass comprehension strategy
- •Scribe Media process: outline + recorded sessions → book in ~3–4 months
- 24:52 – 27:18
Why people switch jobs: progress over money (and the myth of ‘luck’)
Bob applies JTBD to employment, arguing employees “hire” companies to make progress. He explains that job changes often appear like luck, but follow the same forces: pushes, pulls, anxieties, and habits—while money is often a proxy for deeper needs like respect or growth.
- •Employees hire companies; switching is driven by progress goals
- •“Luck” narratives dissolve when you map the real switching story
- •Many switches don’t increase pay; people trade money for learning/trajectory
- •Money often represents respect, responsibility, or identity
- 27:18 – 33:53
Interviewing tactics: fewer interviews, no rigid script, and getting past ‘layers of language’
Bob gives practical advice for conducting JTBD interviews: learn interrogation-style conversation techniques, talk only to people who truly tried to make progress, and avoid rigid discussion guides. He details how to push past shallow answers using bracketing, mirroring, and investigating timelines.
- •Learn tactical interviewing (e.g., Chris Voss techniques)
- •Sample size: patterns repeat ~7–8; typically do 10–12 interviews per round
- •Avoid strict discussion guides; follow meaning-rich threads
- •Layers of language: pablum → fantasy/nightmare → what actually happened
- 33:53 – 36:25
Applying JTBD quickly: start with recent buyers or churn, then map functional/emotional/social energy
Bob outlines a lightweight entry point for teams: interview 10 recent buyers about the story (not product feedback), and talk to churned users to see the new struggle that triggered leaving. He introduces a practical lens for motivation: functional, emotional, and social “energy” in the system.
- •Start by interviewing recent buyers about the buying story
- •Churn interviews reveal new struggles and context shifts
- •Look for functional (time/effort/knowledge), emotional, and social drivers
- •Stats without context mislead; context determines value and behavior
- 36:25 – 40:16
Readiness signals: ‘bitchin’ ain’t switchin’ and how to detect real push forces
Bob explains why stated intent is unreliable and why complaints rarely predict switching. Real readiness shows up in concrete triggers, constraints, and events that create true push—often uncovered only by reconstructing the timeline and trade-offs behind the decision.
- •Never trust what people say they’ll do; look for actions taken
- •Complaints ≠ switching (Basecamp Gantt chart example)
- •Early explanations are often post-rationalizations; probe for real triggers
- •Value depends on starting point + desired outcome; avoid overshooting solutions
- 40:16 – 51:05
Misconceptions, ‘flavors’ of JTBD, and the Clay Christensen connection
Bob addresses criticism by distinguishing qualitative, demand-side JTBD (his method) from more prescriptive, supply-side variants (e.g., outcome-centric approaches). He explains his long mentorship with Clay Christensen, and why conference-room hypothesizing without field interviews goes wrong.
- •Different JTBD ‘flavors’: qualitative demand-side vs. prescriptive supply-side systems
- •JTBD research is hypothesis-building, not hypothesis-testing
- •Danger: inventing jobs in a room—guaranteed to be wrong
- •Clay relationship: turning practical hacks into theory + method (e.g., Competing Against Luck)
- 51:05 – 58:06
When not to use JTBD: no real choice, deep habits, and ‘use’ vs. ‘buy’ questions
Bob explains JTBD isn’t always the right tool, especially when customers lack meaningful choice (e.g., employer-selected health insurance) or when behavior is too habitual to recall (e.g., buying gum). In these cases, observing usage and friction via ethnography/prototyping can be more useful.
- •JTBD breaks down when there’s no meaningful choice or agency
- •Some categories are too habitual—people invent reasons after the fact
- •Ask about usage moments when purchase moments aren’t recallable
- •Alternative tools: ethnography, friction mapping, prototyping
- 58:06 – 1:07:05
Core takeaways, lightning round, and the dining room table story (emotion beats stated preference)
Bob summarizes the pillars of JTBD—struggling moments, progress definition, and choosing trade-offs customers accept—then moves into rapid-fire questions. He closes with memorable stories: downsizers who said they didn’t want a dining table (but needed it emotionally), and the mentors who shaped his craft.
- •Three takeaways: study struggling moments, define progress by customer standards, align trade-offs
- •Lightning round: recommended books, favorite media, interview question, favorite product
- •Dining room table insight: symbolic/emotional needs drive decisions; design for contradictions
- •Mentors and origins: Deming, Taguchi, Willie Moore, Clay Christensen
- 1:07:05 – 1:09:54
Where to find Bob and how listeners can help
Bob shares where he’s most reachable and the different platforms/companies he runs. He asks the community to keep asking questions and help create formats that let him answer conversationally rather than in writing.
- •Best contact: LinkedIn
- •The Rewired Group, Laser Ventures, and The Circuit Breaker podcast
- •Community-driven Q&A and continued discussion
- •Preference for spoken/conversational responses over written replies
