Oct 26, 2023 · 1h 23m · lennys-podcast
What AI means for your product strategy | Paul Adams (CPO of Intercom)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Intercom Chief Product Officer Paul Adams joins Lenny Rachitsky to discuss why generative AI represents an existential paradigm shift for software, how product teams must adapt their roadmaps and organizational structures, and the timeless product frameworks that drive enduring tech companies.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 20.2% of the talking time here. How this is scored →
Lenny as informed peer 3.6 Guest teaching 5.0 Guest disagreement 0.9 Lenny pushing back 0.4
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 1:08:50 Dismissing academic JTBD debates
Paul shows his most contrarian and dismissive stance, bluntly arguing that customers do not care about nuanced theoretical debates over JTBD variants and that over-intellectualizing frameworks has no place in practical work.
Hardest push from Lenny ▶ 1:03:00 Pushing back on extreme pendulum swingsLenny questions the premise of swinging the pendulum dramatically in organizational strategy, challenging Paul on whether leaders should actively strive to prevent overcorrection rather than resignedly accepting it.
Biggest teaching moment ▶ 21:25 Strategic audit for products in AI's pathPaul delivers an in-depth framework for analyzing SaaS products against specific LLM capabilities, educating product managers on how to diagnose whether their entire UI/workflow is vulnerable to disruption.
Lenny holds their own ▶ 34:10 Lenny demonstrates AI translation pipelineLenny displays his hands-on technical familiarity with modern AI media pipelines by explaining how his team runs real-time voice translation, accent cloning, and lip-sync adjustments for international podcast releases.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| Overcoming Failure: The Cannes Keynote Panic Attack | 3 | 2 | 1 | 0 | Lenny invites Paul to share his career failure stories, empathizing with the fear of public speaking. Paul open-heartedly recounts his panic attack on stage at Cannes and how he recovered. The dynamic is collaborative and supportive. | |
| Lessons from Google+: Fear-Driven Products and Joining Facebook | 4 | 5 | 1 | 1 | Paul details his time at Google working on fear-driven projects like Google+ and his research into small-group communications before leaving for Facebook. Lenny demonstrates contextual knowledge about the scrutiny Paul faced during that departure. | |
| Designing the Company: Principles of Shipping and Failure | 3 | 5 | 1 | 0 | Paul explains the Intercom engineering culture of 'shipping to learn' and taking large bets rather than purely incremental ones. Lenny listens attentively, validating the psychological difficulty of managing failure in real time. | |
| The AI Wave: A Paradigm Shift Beyond Mobile | 4 | 6 | 2 | 1 | Paul details why he views generative AI as a seismic shift larger than mobile and the internet. Lenny contributes examples of mobile-first leadership mandates at Airbnb and Facebook, prompting Paul on practical ways leaders can enforce AI adoption. | |
| Evaluating Product Relevance in the Path of AI | 4 | 7 | 1 | 0 | Paul delivers a masterclass on auditing product workflows against AI capabilities (summary, text gen, reasoning, action taking) to determine if a product is in the meteor's path. Lenny prompts for concrete case studies, following Paul's analytical breakdown. | |
| Building Fin: Intercom's AI Customer Service Bot | 4 | 6 | 0 | 0 | Paul describes the creation and operational impact of Fin, Intercom's customer service bot, noting that organizational adoption is often harder than the tech itself. Lenny helps structure the breakdown by asking about measurable impact and strategic shifts. | |
| Mind-Blowing AI Frontiers: Code, Vision, and Voice | 5 | 6 | 1 | 1 | Paul lists frontier AI capabilities that blew his mind, including vision, code generation, and voice replication. Lenny actively builds on the conversation, sharing how his podcast is currently testing real-time voice translation and video dubbing. | |
| Structuring AI Teams: Integration vs. Bolting On | 4 | 6 | 1 | 1 | Paul explains why companies should not create isolated 'bolted-on' AI teams, drawing a cautionary parallel to Google's siloed mobile team in London. Lenny asks clarifying questions regarding organizational design and reading sources. | |
| Sponsor Message: Help Bar by Chameleon | 0 | 0 | 0 | 0 | Lenny reads a dedicated sponsor segment for Help Bar by Chameleon. As a standard solo promotional read, there is no guest interaction or debate. | |
| Counterbalancing Hype and Debunking Doomsday Fears | 3 | 5 | 1 | 0 | Paul discusses balancing extreme optimism with deliberate consumption of skeptical viewpoints and clarifies why AI won't instantly cause mass unemployment. Lenny validates the importance of balancing viewpoints and transitions to frameworks. | |
| Product Frameworks: Before/After and Pricing Discipline | 3 | 6 | 1 | 0 | Paul outlines his 'before/after' framework and reflects on Intercom's past pricing mistakes caused by compounding tiers and add-ons. Lenny draws out a concrete takeaway for founders tackling pricing. | |
| Framework: Differentiation vs. Table Stakes | 4 | 6 | 1 | 1 | Paul breaks down his simplified Kano model of differentiation versus table stakes, warning against innovative differentiation that users don't care about. Lenny synthesizes the tactical implications for early-stage startup roadmap sequencing. | |
| Framework: Swinging the Pendulum in Product and Hiring | 4 | 6 | 1 | 1 | Paul discusses swinging the pendulum too far when hiring experienced big-company specialists instead of generalists, and notes that you often have to cross boundaries to find limits. Lenny questions whether swinging the pendulum excessively should be avoided or embraced. | |
| Framework: Product-Market-Story Fit | 5 | 5 | 1 | 0 | Paul explains Product-Market-Story fit, citing Rdio vs Spotify to show that superior products fail without clear storytelling. Lenny connects this concept directly to positioning frameworks and recent insights from guest April Dunford. | |
| Jobs to Be Done and the Four Forces Framework | 5 | 6 | 2 | 0 | Paul defends a simplified, practical application of Jobs to Be Done and the Four Forces framework, bluntly dismissing academic nuance wars. Lenny affirms the value of cutting fluff and focusing strictly on utility. | |
| Lightning Round: Books, Culture, Sticky Notes, and Kindness | 4 | 4 | 1 | 1 | In the lightning round, Paul shares book recommendations, his perspective on The Bear, reference check questions, and sticky note mottos on his screen. Lenny enthusiastically engages, relating his own experiences with leadership advice and candor. | |
| Irish Culture, Fresh Guinness, and Dublin Seafood | 2 | 4 | 0 | 0 | Paul explains why fresh Guinness in Ireland tastes superior due to transit degradation, and recommends Dublin seafood. Lenny closes out the conversation warmly. |
Statements from this episode (32)
Adams: Google Buzz and Google+ were driven by fear, not user needs
“A lot of the motivation for those projects came from a place of fear. You know, it didn't come from a place of let's make a great product for people. Let's like really understand the things people struggle with when communicating with family and friends. Like …”
Adams: Google isolated the Google+ team in a separate restricted building
“Google had done a lot of things at the time that, that, that were the first for them. I don't know if they've done them since, but things like everyone worked in Google plus was sent to a different building, that building a different key card. If you didn't wo…”
Adams: Google quarantined me and forensically analyzed my laptop when I left
“When I left Google kind of assumed that I was one of the spies, you know, I was quarantined when I told them I was leaving. They you know, forensically analyzed my laptop, like all sorts of stuff like that.”
Adams: High quality standards create constant tension with shipping fast
“So there's a real tension there, a real trade-off where people have these high standards, which we encourage, and we encourage them to ship fast and learn and make mistakes. It's a constant kind of tension that we're navigating.”
Adams: AI is bigger than mobile and potentially bigger than the internet
“This is a like meteor coming towards you. Like this is, you know, bigger than mobile as a kind of technology shift, as big as the internet. Maybe it's bigger than the internet itself as a kind of social, you know, technology shifts, the way it'll shape, shape …”
Adams: Working over 50 hours weekly causes fatigue and bad decisions
“I don't believe in working crazy hours. You know, I don't know what hours I work. I don't know, 50 hours a week, maybe. I think beyond that, you start to make bad decisions and things like that. You get tired.”
Adams: Almost all B2B SaaS and workflow products face AI disruption
“Any product that has any kind of workflow in it, Which is, is almost all B to B SaaS products. Any product that has multimedia in it, they're in the fire, they're in the meteor line or whatever. I don't know if this metaphor is working, but like, you know, the…”
Intercom took a bet-the-farm approach to AI by rebuilding its strategy
“So we literally ripped up our strategy almost entirely and started again, like from first principles and said, okay, why do people use Intercom? You know, Intercom is a customer support product. And then very soon after that, Sam Altman, who's the, you know, f…”
Adams: Google will be fine despite a slow start with Bard
“I think other companies like Google with Bard Have to do it, you know, and maybe they were a little bit slow, but it's so early in this tech cycle that I think they're fine.”
Adams: Some customers resolve 50% to 70% of support queries with Fin
“We have some customers who are hugely successful with it. They can answer up to 50, 60, 70% of their inbound questions with Fin.”
Adams: Intercom's AI pivot has not yet transformed its financials
“Has it transformed our business? Like financially? Not yet.”
Intercom maintains a 1:5 ratio of product managers to engineers
“Here at Intercom, we have a kind of a one to five ratio. So like a PM has about five engineers on a team.”
Adams: Radiologists will stop analyzing X-rays and only review AI findings
“Radiologists will not take x-ray. Well, I guess it might take them, but they won't analyze them for sure. They'll look at what AI says, check that it's right. And then it's like kind of bedside manner time. Like, you know, tell the patient, maybe tell them wha…”
Adams: AI will soon replicate deceased individuals using their lifetime data
“AI will be able to ingest all the things people say and do, And when people die, it'll be able to replicate that person, you know? And so like, there's an afterlife.”
Adams: Great AI products require ML engineers building atop foundation models
“Ultimately, you need, like, really great machine learning engineers. Like, that's where it starts. And if you don't have that, then you know, you gotta find it hard to build truly, really, truly great things. You know, so, like, what OpenAI provide what Entrop…”
Adams: Companies must integrate AI across teams rather than siloing it
“What we're trying not to do is have like the kind of like AI inbox team who, oh, and they're the only people who work on AI features in the inbox. I think it's much better to have everyone learn about it. I, by the way, I'm a big believer in generalists, like …”
Adams: Future reporting and project management software may just be input boxes
“I think, again, this is, like, hand wavy. Who knows? Maybe that's all done. Dead now. And the reporting product of the future is just a box, and the box just goes to the database, and the box is just what was our best salesman last year? January. Okay. Who was…”
Adams: AI doomsday job-loss scenarios will not play out as feared
“People don't end up losing jobs. The jobs get moved around and also, you know, for customer support, for example, it's a high attrition job. So people saying like, Hey, everyone's going to lose their job. A bot's going to take over. It's like, maybe some of th…”
Adams: Aligning SaaS Pricing to Value Is Deceptively Difficult
“Pricing is, like, deceptively difficult. We had a principle around, like, aligning price to value. You know, people should pay based on the amount of value they get in the product. Easy to say and incredibly hard to do. Value is subjective.”
Adams: Intercom Compounded Pricing Mistakes Out of Risk Aversion
“The biggest mistake was we could, a lot of mistakes compounded. And this is an area where I do, I think we were risk averse. We ended up, we've ended up with too many pricing models. We've built on top of old, you know, compounded mistakes.”
Adams: SaaS Companies Must Resist Adding Pricing Tiers and Add-Ons
“The number one thing I would say is keep it simple. It's simple. It's so tempting to like with us, for example, like a lot of SaaS products, you know, have add-ons... With products, tiers, add ons, tiering in the add on. You know, people can't understand their…”
Adams: Google Wave failed because customers didn't care about its differentiation
“Google wave was an amazingly innovative product. That no one really cared about.”
Adams: Intercom splits resources 50/50 between table stakes and differentiation
“These days, the pace of income today is like we're kind of 50, 50 probably in terms of resources, but it has swung 70, 30 in both directions at times.”
Adams: Startups must invest heavily in differentiation before building table stakes
“If you're a startup, you need to invest a lot more in differentiation. And then over the years, I think you start to balance the books a bit.”
Adams: Highly specialized employees struggle in fluid startup cultures
“People who are highly specialized can thrive in big companies, really thrive. They're invaluable employees, but in a fluid, Startupy culture with a lot of ambiguity that can really drown, really struggle.”
Adams: Google privacy debates blocked shipping on a year-long project
“I remember when I went, I remember at Google, privacy was like really top of mind to the point that it would like block decisions, like block product progress, just privacy, circular conversations. So many circular conversations and nothing ever got built or s…”
Adams: Teams must cross boundaries and feel pain to find real limits
“There was kind of an idea that to know where the boundary is, you gotta cross it. And crossing, it's painful, but if you don't cross it, you'll never know. So if you go, if you think you're going up to the boundary and you stop before it, turns out it's actual…”
Adams: A good market requires people to care deeply about the problem
“To have a good market, you need a lot of people with the same problem, and they need to care a lot about it. Again, back to the Google social stuff, we found a lot of people With the same problem. They didn't really care. They didn't really care. Like, you kno…”
Adams: Product teams must learn to explain products as much as build them
“I think all product people, whether you're a designer, product manager, people in research, data science, need to think about the story all the time. Work with marketing, work with product marketing, and like, learn about how to explain the product as much as …”
Adams: Debating Jobs to Be Done variations is irrelevant to product development
“There's like so many people who spend so much of their energy debating the nuances and peculiarities of one version. Who cares? Who can, like, no one cares. Oh, well, I don't care. They care, obviously. I, I'm like, your customers don't care. Like people you'r…”
Adams: Best reference check asks what first performance review feedback will be
“So this question is, What feedback will I be giving this person in their first performance review? That's an amazing question because the person can't dodge it. You know, there's an answer and it's incredibly enlightening.”
Adams: Firing someone is kinder because it always benefits both sides
“And then, and since then I've done it quite a few times in a bunch of different circumstances and realized it always works out for both sides. And the nicest thing to do is to do the harder thing. You know, it's actually the nicer thing to do.”