AI is a tool, not a silver bullet - product discovery with Peppe Silletti

This section explores the distinction between product engineers and product managers. Peppe Silletti emphasizes that product engineers typically work on smaller, specific aspects of a product—owning outcomes from end to end—such as prototyping, implementing, and measuring the impact of features. In contrast, product managers are portrayed as the 'big picture' custodians, focusing on overall strategy, stakeholder management, and holistic product perspective. The conversation highlights a shift in thinking, with product engineers taking on more responsibility and ownership traditionally held by product managers, especially in high-trust environments like PostHog, where engineers make many product decisions themselves.

Peppe discusses how AI has changed the landscape of product development, particularly in reducing the cost and time of writing code. While AI can generate MVPs rapidly, the importance of customer discovery and data-driven decision-making remains unchanged. The key challenge is avoiding the trap of overbuilding or including too many features, which can add noise and obscure real user needs. He emphasizes that AI tools should augment—not replace—the fundamental activities of problem framing, customer interviews, and feedback loops. The narrative stresses that AI is a tool that, if misused, can lead to faster but misguided product directions.

This section emphasizes durable skills that will remain valuable even as AI takes on more coding tasks. Peppe emphasizes the importance of framing problems correctly, conducting non-solution-biased customer interviews, and understanding user experience broadly, including API design and internal tools. These skills foster better collaboration, more accurate problem identification, and more effective solutions. He advocates for engineers to develop empathy, understand the bigger system, and engage early in discovery processes, making them more impactful and aligned with real user needs.

Peppe discusses how to prioritize tasks after achieving product-market fit, stressing the importance of identifying patterns across customer feedback and usage analytics. He notes that challenges include distinguishing between real pain points and latent needs that customers can’t articulate. Prioritization should balance customer pain points, technical feasibility, and potential ROI. He also highlights the risks of feature bloat and the necessity of maintaining discipline to avoid overcomplication, which can harm user experience and system maintainability. Ultimately, he advocates for a measured approach, emphasizing simplicity, user focus, and early discovery.

The podcast explores how the role of product engineers is evolving, with examples like PostHog illustrating that many teams have historically operated with engineers owning end-to-end product decisions. Peppe notes that in some innovative companies, engineers are deeply involved in discovery and decision-making, often replacing traditional product managers. The conversation points toward a future where engineers are more autonomous, owning outcomes, engaging directly with customers, and making strategic decisions—shifting the traditional boundaries of roles. This evolution emphasizes the importance of skills like problem framing, UX understanding, and system awareness.