Intercom on Jobs-to-be-Done
Source: https://www.intercom.com/resources/books/intercom-jobs-to-be-done ↗
A short Intercom ebook that collects the company's internal writing on Jobs-To-Be-Done — how they use it to frame customer research, how they structure interviews, how they translate findings into product decisions.
The Intercom team were early and public adopters of JTBD, and the book's value is the specificity: actual interview scripts, actual frameworks, actual before-and-after product changes.
For product direction it is the most accessible practical introduction to the method, particularly for teams who have read Christensen and Ulwick and don't know where to start.
Free, short, illustrated; hand it to a PM the first time JTBD comes up in conversation.
Central argument
Intercom argues that Jobs-to-be-Done is not merely a research taxonomy but an operational system that should directly govern product decisions — from how interviews are structured to how findings are translated into feature prioritisation. The book's central thesis is that understanding the causal mechanism behind why customers switch to or away from a product (the 'hiring' moment) is more predictive of product success than demographic segmentation or usage analytics. By publishing their actual interview scripts and internal frameworks, Intercom makes an implicit argument that JTBD only delivers value when it is institutionalised as a repeatable practice, not applied as a one-off research exercise.
Critique
Because the book is essentially a collection of Intercom's internal writing, its frameworks are optimised for a B2B SaaS context with relatively high-consideration purchase decisions — the 'switching moment' construct is most legible when customers consciously evaluate alternatives, which does not hold equally for low-friction consumer products or embedded platform decisions. The specificity that makes the book useful (actual scripts, actual cases) is also its constraint: readers may over-index on Intercom's particular interview cadence and mistake a worked example for a universal method. There is also little engagement with the harder epistemological problem that customers frequently cannot accurately reconstruct the causal story of why they hired a product, which risks treating interview narratives as more reliable than they are.
Why it matters for product
For a CPO, the book's most actionable contribution is the argument that discovery interviews should be structured around the timeline of a specific past decision rather than hypothetical future preferences — a discipline that directly counters the tendency of product teams to run validation research that confirms existing roadmaps. The operational framing also has implications for team structure: if JTBD interviews require a specific facilitation skill and a defined translation layer between insight and backlog, that is an argument for embedding research capability in product trios rather than treating it as a centralised function that delivers reports.