We scan new podcasts and send you the top 5 insights daily.
The core of a Jobs-to-be-Done (JTBD) interview is to uncover the full story of what causes a customer to switch from one product to another. This line of inquiry reveals their true motivations and the underlying 'struggle' that triggers their search for a new solution.
Prospects often describe wants (e.g., "a more efficient system"), which are not true problems. Asking about the motivation behind their desire forces them to articulate the underlying pain that actually drives a purchase decision.
Asking users for solutions yields incremental ideas like "faster horses." Instead, ask them to tell detailed stories about their workflow. This narrative approach uncovers the true context, pain points, and decision journeys that direct questions miss, leading to breakthrough insights about the actual problem to be solved.
Instead of asking direct questions like 'what's important?', prompt customers to recount specific, recent experiences. This storytelling method bypasses generic answers, reveals the 'why' behind their actions, and provides powerful narratives for persuading internal stakeholders.
When interviewing customers, operate exclusively in 'demand mode,' focusing only on their struggle. Avoid 'supply mode,' where you discuss solutions. According to Chris Spiek, mixing the two invalidates the interview because it shifts from pure discovery to biased validation, and the interview should be considered a failure.
Standard discovery questions about 'pain points' are too broad. Instead, focus on concrete 'projects on their to-do list.' This reveals their immediate priorities, existing attempts, and the specific 'pull' that will drive a purchase, allowing you to align your solution perfectly.
To master JTBD interviews, first practice on purchases unrelated to your work (e.g., a colleague's new car). This builds the crucial skill of focusing on the customer's story without the natural, and detrimental, tendency to start discussing your own product's features and solutions.
Instead of guessing your competitive advantage, ask potential customers which other solutions they've evaluated and why those products didn't work for them. They will explicitly tell you the market gaps and what you need to build to win.
Directly asking customers for solutions yields generic answers your competitors also hear. The goal is to uncover their underlying problems, which is your job to solve, not theirs to articulate. This approach leads to unique insights and avoids creating 'me-too' products.
Standard questions like 'What's your biggest pain point?' often yield poor results. Reframing the question to what work a customer would offload to a new hire bypasses their pride or inability to articulate problems, revealing the tedious, high-value tasks ripe for automation.
The only reliable way to understand a customer is to "forward deploy"—work alongside them in their actual environment. This direct experience of their job closes the context gap that interviews can't bridge, revealing unspoken needs and frustrations.