Differentiation vs. Table Stakes
by Paul Adams • Chief Product Officer at Intercom
Paul Adams is the Chief Product Officer at Intercom, with over a decade of leadership there. Previously, he held key roles at Facebook (Global Head of Brand Design), Google (User Researcher), and Dyson.
🎙️ Episode Context
Paul Adams discusses Intercom's radical pivot to an AI-first strategy, treating AI as a 'meteor' level event necessitating a complete roadmap overhaul. He shares candid lessons on failure, organizational design, and introduces practical frameworks for balancing product differentiation against table stakes. The conversation covers the nuances of 'Product-Market-Story Fit' and how to operationalize AI without falling into the trap of over-intellectualizing strategy.
Problem It Solves
Solves the dilemma of prioritizing exciting new features versus boring but necessary infrastructure, preventing churn or failure to close deals.
Framework Overview
A simplified Kano model that balances two forces: 'Attraction' (Differentiation) which gets people interested, and 'Entry Requirements' (Table Stakes) which allows them to actually use or switch to your product.
🧠 Framework Structure
Differentiation Drives Attraction: Un...
Table Stakes Drive Adoption: Standard...
The Maturity Swing: Startups must ove...
Contextual Audit: Regularly ask 'Are ...
When to Use
During quarterly roadmap planning or when sales win-rates drop despite having 'cool' features.
Common Mistakes
Over-focusing on differentiation to the point where the product is unusable for enterprise clients (missing 'boring' features).
Real World Example
Intercom initially lost deals to Zendesk despite better UX because they lacked basic reporting/permissions. They had to shift resources 50/50 to build 'boring' table stakes.
Be different and better in ways people care about.
— Paul Adams