💡

InsightHunt

Hunt the Insights

P

Paul Adams

Episode #235

Chief Product Officer

Intercom

🎯Product Strategy📈Growth & Metrics👥Team & Culture

📝Full Transcript

15,442 words
Paul Adams (00:00:00): This is a meteor coming towards you. This is going to radically transform society. And I think if people don't explore AI properly, it will leave them behind. I'd start with the thing your product does. "What's the core premise behind it? Why do people use it? What problem does it solve for them?" That kind of thing. So, go back to basics. And then ask, "Can AI do that?" And for a lot, the answer is going to be, "Yes, it can." For some it might be, "It can partially do it." And then, maybe for others, "It can't do that, at least not yet." And then, for some of it'll be replacement, AI would replace, it'll just do it. And, in other places, it'll be augmentation. It'll augment. It'll help people. But yeah, I think that you've got to match your product, and what AI can do, and what it will be able to do, and then ask yourself, "Okay, what are we going to do?" Lenny (00:00:52): Today my guest is Paul Adams. Paul is chief product officer at Intercom, a role that he's held for over 10 years. Prior to this role, he was global head of brand design at Facebook, a user researcher at Google, a product designer at Dyson, and his first job was an automotive interior designer. In our conversation, Paul shares some amazing stories of failure, including the story of him giving a huge presentation where he froze on stage and had to walk off. And what he learned from these experiences of failure. We then get deep into how to think about AI as a part of your product strategy, including a ton of great examples from Intercom's experience going all in on AI. Paul also shares some of his favorite frameworks, and product lessons, and so much more. (00:01:34): This is the first recording I've ever done not from my home studio, instead from a hotel room. So, this is a fun experiment for us all. With that, I bring you Paul Adams after a short word from our sponsors. This episode is brought to you by Eppo. Eppo is a next generation A/B testing and feature management pl...

💡 Key Takeaways

  • 1Treat AI as a fundamental shift (a 'meteor'), not a feature; rebuild strategies from first principles.
  • 2Map product workflows against AI capabilities to determine if the goal is 'Replacement' (automation) or 'Augmentation' (copilot).
  • 3Product-Market Fit is insufficient without 'Story Fit'; great products fail if the narrative doesn't resonate.
  • 4When correcting organizational issues, accept that 'swinging the pendulum' too far (over-correcting) is often necessary to find the right boundary.
  • 5In hiring, ask references: 'What feedback will I be giving this person in their first performance review?' to get honest insights.
  • 6Balance your roadmap between Differentiation (attraction) and Table Stakes (entry requirements) based on your company's maturity.
  • 7Don't bolt AI onto the side with a specialized team; integrate it into every product team's core competency.

📚Methodologies (4)

🎯 Product Strategy

A first-principles approach to AI adoption that treats the technology as an inevitable force (meteor). It involves stripping the product back to its core purpose and rigorously testing if AI can perform the core tasks better than the status quo.

Core Principles

  • 1.Return to Basics: Ignore the tech initially; define exactly what problem the product solves for the user.
  • 2.Capability Mapping: Ask 'Can AI do this?' for every core interaction (read, write, summarize, see, act).
  • 3.Categorize Impact: Determine if AI acts as a 'Replacement' (doing the work fully) or 'Augmentation' (helping the human).
  • +1 more...

"This is a meteor coming towards you... I think if people don't explore AI properly, it will leave them behind."

#'meteor'#assessment#strategy
View Deep Dive →
🎯 Product Strategy

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.

Core Principles

  • 1.Differentiation Drives Attraction: Unique features explain why a customer wants your product (the hook).
  • 2.Table Stakes Drive Adoption: Standard features (permissions, reporting) are required to play the game; without them, customers can't switch.
  • 3.The Maturity Swing: Startups must over-index on differentiation; scaling companies must swing back to fill table stakes gaps.
  • +1 more...

"Be different and better in ways people care about."

#differentiation#table#stakes
View Deep Dive →
📈 Growth & Metrics

PMF (Product-Market Fit) is insufficient. You need a compelling 'Story' that connects the product to the market's specific anxieties and energy. If the story is convoluted, the product effectively doesn't exist to the user.

Core Principles

  • 1.Market Definition: Market is not just people; it is People + Problems + Energy (how much they care).
  • 2.Narrative Clarity: The story must explain the value simply. Complexity kills conversion.
  • 3.Emotional Connection: The story must tap into the user's existing energy or anxiety (using frameworks like 'Four Forces').

"A lot of the motivation for those projects came from a place of fear... It didn't come from a place of 'Let's make a great product'."

#product-market-story#growth#metrics
View Deep Dive →
The Pendulum Swing

by Paul Adams

👥 Team & Culture

When correcting an undesirable state (e.g., lack of experience), organizations inevitably over-correct (swing the pendulum too far). Leaders should recognize this as a necessary part of finding the equilibrium rather than a failure.

Core Principles

  • 1.Identify Undesirable State: Acknowledge what is broken (e.g., 'We are too amateur').
  • 2.Cross the Boundary: To know where the limit is, you often have to cross it (over-correct).
  • 3.Stabilize: After feeling the pain of the over-correction, swing back to the middle ground.
  • +1 more...

"To know where the boundary is, you got to cross it."

#pendulum#swing#team
View Deep Dive →