Product Thinking Podcast

Episode 266: Building for Builders

Host: Melissa Perri
Released: April 8, 2026

Episode Overview

This episode explores how successful product management goes beyond training product managers and delves into building effective organizational systems, leadership, and culture that enable impactful product work. Melissa Perri curates conversations with three product leaders—Nan Yu (Linear), Andrew Davidson (MongoDB), and Jody Bailey (Stack Overflow)—offering practical lessons for keeping teams focused, understanding real customer problems, and resisting the distractions of process overhead and shiny new technologies.

Key Discussions & Insights

1. Cutting Through Process: Creating Value (Nan Yu, Head of Product, Linear)

Timestamp: 01:33–06:34

• Speed and Directness Over Process

  • Nan Yu emphasizes that product teams need to move quickly and directly toward meaningful outcomes, rather than get bogged down by cumbersome tools or unnecessary process:
    • “Speed is everything—from I engage with a CTA, I click on a button or something like that and it should just respond immediately... We really focus on directness so that even things like, look, projects are called projects. They're self explanatory.” (01:33)
  • Administrative overhead, like mindless data entry, is highlighted as a drain on valuable PM and team efforts.
  • “You're not here for data entry, you’re not here to do administrative work… We're trying to get that off of your plate.” (01:59)

• Reducing PM Pain: Better Tools, Fewer Handoffs

  • Poorly designed tools push engineers away, leaving PMs stuck with non-valuable admin work:
    • “If you talk to an engineer... they say, I spent all my time in cursor or VS Code... I just didn’t touch Jira. But then I shipped a bunch of code, they're going to get a great performance review.” (02:39)
  • The cycle: engineers focus on shipping, PMs stuck with issue trackers, leading to the misconception that PM work is just data-wrangling.

• Dig Deeper Than Feature Requests

  • Nan Yu advocates for uncovering the real customer problems, not just responding to superficial feature asks:
    • “We have to solve real problems for real people. And a real problem is not a problem that someone has in the abstract, right? It’s an actual specific instance of a problem.” (04:10)
    • Example: Feature requests around date notifications often mask deeper issues about certainty and communication, leading Linear to offer flexible granularity for date fields rather than spammy notifications.

• Notable Quote:

  • “No one dreams of that, right? We want to be talking to customers, understanding their needs, empathizing with them... that’s why we’re doing this job. All that administrative stuff just comes to us by default.” (02:39)

2. Building For Developers: Power & Simplicity (Andrew Davidson, SVP Product, MongoDB)

Timestamp: 07:10–09:38

• Developers: The Ultimate Power Users

  • Davidson paints developers as uniquely sophisticated—and unforgiving—users:
    • “Developers... are extremely sophisticated… they love overcoming issues. So on the one hand, that sounds amazing… but on the flip side, they’re some of the most sort of love-hate, fickle... If they feel like you’re wasting their time... they could be completely the opposite and be like, get out of here. I don’t want to use this at all.” (07:26)
  • Developers demand tools that are powerful yet simple, allowing deep customizability but also quick onboarding, frictionless experience, and minimal time-wasting.

• Building Experiences that Respect Users’ Time

  • The best developer tools must integrate seamlessly (local environment, CI/CD, infra as code) and respect developers’ workflows.

• Notable Moment:

  • Host Melissa Perry draws a parallel between developer tools and other business-critical platforms:
    • “They’re in them 24/7... If you think about what other people use, Salespeople are in Salesforce all the time... To developers, it’s like their Salesforce.” (09:08)

3. AI Hype vs. Real Problems: Lessons from Rushing In (Jody Bailey, CPO/CTO, Stack Overflow)

Timestamp: 10:42–14:57

• The ‘AI Solution’ Trap

  • Jody Bailey describes the “oh crap” moment when generative AI emerged, and organizations rushed to respond:
    • “I think many people in many different industries had that oh crap moment... we've got to release something, we've got to have an AI solution… One of the mistakes I think almost everybody made… is we focused on delivering AI solutions, not solving user problems or customer problems.” (10:56)

• Refocusing on the User

  • Bailey highlights the classic “solution looking for a problem” pitfall, reminding teams to ground work in customer needs, not tech trends.
  • “We were solving for we have to have AI. And I think a lot of different companies did that… we also spent a lot of time doing things that really didn’t bear fruit.” (11:17)

• Stack Overflow’s Evolving Strategy

  • Strategic focus returns to core strengths: trusted knowledge, community, and expanding what it means to be a "technologist."
  • The approach now combines protecting canonical Q&A content with new spaces for broader, more conversational or derivative questions:
    • “We want to make sure that we create a space where people feel comfortable, where they can interact in different ways… protect what we’ve always done while creating safe spaces for some of those other conversations that are important...” (13:33)

• Notable Quote:

  • “It's just one of those reminders to always focus on solving problems for your users or customers and not to just focus on the shiny object.” (11:44)

Memorable Quotes

• “You're not here for data entry... We want to be talking to customers, understanding their needs, empathizing with them.”
  — Nan Yu (02:39)

• “Developers... will jump through hoops... but if they feel like you're wasting their time... get out of here. I don't want to use this at all.”
  — Andrew Davidson (07:26)

• “We focused on delivering AI solutions, not solving user problems or customer problems... always focus on solving problems for your users.”
  — Jody Bailey (11:17, 11:44)

Timestamps for Key Segments

• 01:33 — Nan Yu on speed, directness, and minimizing admin overhead
• 02:39 — Nan Yu on why PMs get saddled with clunky tools and admin work
• 04:10 — Nan Yu on solving real problems vs. surface feature requests
• 07:26 — Andrew Davidson on the demands of building for developers
• 10:56 — Jody Bailey on the industry’s AI “panic” and common mistakes
• 13:33 — Jody Bailey on evolving Stack Overflow’s strategy and expanding its user base

Takeaways

• Minimize overhead: Build processes and tools that keep teams working on work that matters, not on mindless data entry.
• Go deeper than requests: Push past what users say they want—anchor in specific, real moments to uncover true needs.
• Respect your users’ expertise: Especially with technical audiences, combine deep power and simplicity. Never waste their time.
• Fall in love with the problem, not just technology: Avoid chasing trends for their own sake; always ground innovation in actual customer needs.
• Evolve but stay true to your core: Keep your organization’s strengths and user value top of mind as you adapt to new technologies and markets.

Noteworthy Moments

• [01:33] Nan Yu: Speed and directness must be built into product workflows to maximize value.
• [07:26] Andrew Davidson: Developer customers have zero patience for friction—they expect both power and ease of use.
• [10:56] Jody Bailey: Chasing AI for the sake of AI led many teams astray; real progress aligns with genuine user needs.

This episode is a practical guide for product leaders to refocus on what matters: keeping teams on meaningful work, deeply understanding customers, and steering clear of distractions—be they bureaucracy, tools, or technology fads.