Library
When Coffee and Kale Compete · 9 of 11
When Coffee and Kale Compete
Entrepreneurship HIGH

JTBD Research and Interview Methods

interviews research struggling-moments compensatory-behaviors customer-discovery

Key Principle

JTBD research discovers what customers actually do, not what they say they do. The gap between stated and revealed preferences is systematic: customers give socially desirable answers, claim to love products they never use, and overestimate their own future behavior. The corrective is to study energy (observable emotional intensity around a struggle), compensatory behaviors (workarounds customers have already built), and churned customers (who reveal satisfaction-driven or struggle-driven departures). Every reliable demand signal comes from evidence of past action, not stated intention.

"I feel like customers have this really bad habit of lying sometimes. They'll say, 'Yeah. I love your product. I use it all the time.' Then, you look at the logs, and you realize they haven't logged in once since signing up -- so you know it's not true." -- Alan Klement, Chapter 4

Why This Matters

Most product failures trace back to skipping discovery or conducting discovery that confirms assumptions rather than revealing struggle. The chotuKool mini-refrigerator was backed by Christensen and Innosight yet failed because the team "jumped to a solution too quickly" without verifying that customers were actively struggling with existing alternatives (Ch. 9). By contrast, Justin Jackson sold out Product People Club in thirty minutes with a 400-person waitlist -- because his research had already identified the specific emotional struggle (solopreneur isolation and motivation paralysis) through years of observing audience behavior (Ch. 9).

The method matters because analytics alone cannot surface motivation. Behavioral data shows what customers do but never why. JTBD insights live in the causal story behind switching, which only direct conversation reveals.

"I think the biggest thing that Jobs [JTBD] encourages people to do, which I'm a big fan of, is to stop spying on customers and start talking with customers." -- Alan Klement, Chapter 4

Good Examples

Compensatory behavior as product blueprint (Ch. 8). Omer Yariv studied med/surg nurses who had independently evolved workarounds for tracking patient interventions: hand-written notes became a notepad system, then a self-made grid worksheet, then photocopies shared with peers. Each iteration encoded a trade-off decision the nurses had already made. Organic peer adoption (other nurses photocopying the grid) proved demand without any marketing. The evolution of workarounds revealed both the shape of the unmet need and the value hierarchy the customer held.

Life-context interview question (Ch. 10). Justin Jackson found that asking "What was going on in your life when you signed up?" surfaced the real trigger behind purchases -- quitting a job, working alone all day, feeling scared. Questions about awareness and consideration mapped the funnel; the life-context question revealed the struggling moment that made someone actually buy.

"That last question -- 'What was going on in your life when you signed up?' -- is gold." -- Alan Klement, Chapter 10

Energy detection across segments (Ch. 8). Omer surveyed broadly (doctors, nurses, administrators) then narrowed by filtering for emotional intensity. Med/surg nurses -- high patient volume, rapid turnover -- showed the strongest energy. ICU nurses had too few patients; oncology nurses knew their long-term patients too well. The structural conditions of the work, not individual attitudes, predicted who would adopt.

Counterpoints

Stated preferences systematically overestimate demand (Ch. 4). Dan's team at Clarity considered building a "save search results" feature. When they asked customers whether they had ever tried to save results or used browser bookmarklets for it, the answer was no. No prior struggle meant no real demand; the feature was killed before development. The test: if no customer has attempted a workaround, there is no Job pulling them toward that feature.

Building for "everyone affected" means building for no one (Ch. 8). Hospitals, patients, and nurses all want to prevent adverse events -- yet adverse events persist. The universal desire masked the fact that only med/surg nurses experienced the structural conditions (volume, turnover, information gaps) that made the problem acute and solvable. Segmenting by demographic rather than by struggle intensity produces unfocused products.

Skipping struggle verification wastes elite resources (Ch. 9). "Godrej, Christensen, and Innosight jumped to a solution too quickly. Instead, they should have spent some time investigating if customers were really struggling and how intensely." The chotuKool case proves that no amount of business-model sophistication compensates for missing the energy check.

Key Quotes

"When I interview potential customers, I look for evidence of a struggle. I'm looking for an energy to tap into. That's how I know a struggling moment exists and that there's an opportunity to create something. If a group of people is not struggling -- if I can't feel that energy -- then there's probably no opportunity there." -- Alan Klement, Chapter 8

"I decided to take a closer look at the patterns I had been noticing within my audience... Could I find any reoccurring struggling moments that people were experiencing?" -- Alan Klement, Chapter 9

"Customers weren't leaving because we were doing a bad job. They were actually leaving because they felt like they had been satisfied." -- Alan Klement, Chapter 11

Rules of Thumb

  • Revealed over stated: Ask what customers have already tried, not what they would hypothetically use. "Have you ever tried to solve this?" is the gateway question.
  • Energy is the demand signal: If interviewees show no emotional intensity -- frustration, anxiety, urgency -- the opportunity is probably inert.
  • Compensatory behaviors are free product specs: When customers build their own workarounds and peers copy them, you have both validated demand and a design prototype.
  • Interview the churned: Satisfied leavers don't complain; they just go. Incentivized interviews with canceled subscribers reveal whether churn is from failure or from Job completion (Ch. 11).
  • "What was going on in your life?": This single question surfaces the situational trigger that separates browsers from buyers.
  • Segment by struggle intensity, not demographics: Filter for the intersection of high struggle frequency and ability to act.
  • Feature validation protocol: (1) Have you tried to solve this? (2) What workarounds did you use? (3) Are you struggling to make progress? (4) Do you want to hire something for this? No evidence at step 1 means deprioritize.
  • Functional vs. emotional: If your research only surfaces functional gaps (missing tools, missing skills), you are probably asking the wrong questions. The deepest Jobs are emotional -- isolation, fear, motivation, identity.
  • Atypical customers are free insights: When someone far outside your expected profile hires your product, interview them immediately. The gap between their context and your assumptions is where hidden markets live (Ch. 10).
  • One product, one Job: When research reveals a downstream Job (e.g., customers who overcame isolation now need marketing help), build a separate product rather than bolting features onto the original. Feature bloat dilutes the core Job (Ch. 10).

Related References