More All Things Product episodes
Published 24 Feb 2026
Duration: 783
Product teams and engineering teams need clear boundaries and distinct roles to avoid burnout, quality issues, and misalignment in responsibilities.
Where exactly is the boundary between product and engineeringand what happens when it gets blurry? In this episode, Teresa Torres and Petra Wille dig...
The podcast highlights challenges in product-engineering collaboration, emphasizing misaligned responsibilities and blurred boundaries. Product teams often overstep into technical decisions, such as prioritizing bugs or managing tech debt, while engineers are burdened with non-technical tasks like defining component order. Historically, product managers have been treated as "order takers," dictating engineering priorities without considering technical complexity, leading to burnout, quality issues, and overwork for both teams. Clear role boundaries are essential: product teams should focus on defining goals, user needs, and product vision ("the what"), while engineers own technical implementation, architecture, and quality ("the how"). The legacy of viewing engineering as a cost center has perpetuated a culture where engineers execute tasks without strategic input, further complicating collaboration.
Skilled engineering teams require autonomy and expertise to manage technical debt, bugs, and system design, pushing back against product teams that micromanage implementation details. Effective collaboration hinges on clear communication, with product managers addressing non-technical aspects like stakeholder communication around major bugs, rather than technical decisions. Both product and engineering leaders must adapt: product teams need to shift from project-based thinking to continuous product management, while engineering leaders must prioritize proactive tech debt management. Solutions include establishing clear role boundaries, empowering engineers to own technical complexity, and fostering leadership accountability to drive cultural shifts toward mutual respect and collaboration. Product managers are not responsible for engineering quality or code accountability, but must escalate systemic issues to engineering leadership and advocate for organizational changes, such as adopting a product-centric mindset and establishing engineering leadership to address skill gaps and ensure maintainable, scalable products.
12 May 2026 Product Builder Myth
Product teams must balance AI integration with diverse talent, address risks of diminished creativity and expertise gaps, and prioritize collaboration, design, and governance to achieve sustainable innovation in product development.
5 May 2026 Taste
The podcast challenges the notion that taste in product development is innate or unteachable, argues it often overrides data and user needs, questions its cultivability through experience, explores AI's potential to engage with human aesthetic judgment, and critiques using taste to bypass design expertise in favor of collaborative, user-centered innovation.
28 Apr 2026 Command And Control
Critiques command-and-control leadership's rigidity in complex environments, advocating for decentralized, trust-based collaboration that balances autonomy, situational awareness, and domain expertise to adapt to modern organizational challenges.
21 Apr 2026 Predicting The Future
Recommended: Useful notes on avoiding overconfidence in predictions.
Critiques overconfidence in AI's future impact, emphasizing polarized forecasts, evolving job roles amid automation, the value of scenario planning and historical parallels, the need to account for varied adoption rates and non-AI workflows, avoid logical fallacies, and adopt flexible strategies that balance technological optimism with systemic problem-solving.
14 Apr 2026 Product Work Is Relationship Work
Product managers in the AI era must balance task-driven efficiency with relational skills like collaboration, curiosity, and intentional stakeholder alignment to navigate automations challenges and foster cohesive teams.