The Causal Interview Protocol
by Bob Moesta • Co-founder and CEO at The Rewired Group
Co-creator of the Jobs to Be Done Framework, entrepreneur who started eight companies, and adjunct lecturer at the Kellogg School of Management.
🎙️ Episode Context
Bob Moesta, co-creator of the Jobs to Be Done framework, joins Lenny to demystify the theory and application of JTBD. Moesta explains that products are hired to solve struggling moments rather than just based on demographics. He details the 'Four Forces of Progress' that drive or inhibit behavior change, outlines a specific 'Causal Interview Protocol' for uncovering deep insights, and breaks down the 'Demand-Side Buying Timeline' to align sales processes with customer psychology. The conversation covers practical examples from Snickers to software like Intercom and Autobooks, emphasizing that understanding the context and outcome is more critical than pain and gain.
Problem It Solves
Unreliable customer data where people rationalize their decisions with logic after the fact, missing the emotional and contextual drivers.
Framework Overview
A specific interviewing technique designed to reconstruct the customer's timeline and uncover the causal mechanisms behind a purchase, resembling a criminal investigation or therapy session rather than a standard survey.
⚡ Step-by-Step Framework
Interview only people who have already made the progress (purchased/switched).
Do not use a discussion guide; follow the story and the energy.
Penetrate the 'Pablum' and 'Fantasy/Nightmare' layers to get to the 'Reality' layer.
Cluster interviews by causal pathways, not demographic segments.
Listen for the 'struggling moment' that triggered the search.
Interview only people who have already made the progress (purchased/switched).
Do not use a discussion guide; follow the story and the energy.
Penetrate the 'Pablum' and 'Fantasy/Nightmare' layers to get to the 'Reality' layer.
Cluster interviews by causal pathways, not demographic segments.
Listen for the 'struggling moment' that triggered the search.
When to Use
During customer discovery, when validating zero-to-one product concepts, or when trying to understand why a product is being hired.
Common Mistakes
Asking 'Why?' repeatedly (which invites rationalization) instead of 'What happened?' or 'Tell me the story'; believing customers' hypothetical claims ('I would buy this').
Real World Example
Discovering why people buy Snickers (meal replacement/mastication for energy) vs. Milky Way (emotional reward/melting texture), leading to completely different competitive sets.
It's criminal and intelligence interrogation that feels like therapy because most people don't actually know why they bought.
— Bob Moesta