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.
16 Jun 2026 Organizational Change Is Exhausting
Organizational change struggles often stem from overwhelming rapid shifts, requiring individual-driven strategies focused on personal habits, collaboration, and customer insights, alongside systemic factors like pain, urgency, and resource visibility, rather than top-down mandates.
9 Jun 2026 Learning Together
Organizational learning strategies emphasize collaborative methods for accountability, alignment, and communities of practice, advocating hybrid approaches balancing individual autonomy with group engagement to address scalability and tailored development needs.
2 Jun 2026 Procurement
Corporate procurement faces systemic inefficiencies like outdated workflows, bureaucratic hurdles, and excessive compliance demands, frustrating vendors and speakers who seek streamlined processes, fair compensation, and agile alternatives to rigid corporate practices.
26 May 2026 Is Technology Good?
Technology's dual impact on societyfrom AI's promise to social media's role in inequalitycalls for ethical innovation, community-driven solutions, and balanced narratives to address isolation, climate challenges, and systemic disparities while prioritizing human well-being and equity.
19 May 2026 AI Engineering
Transitioning from non-engineering to engineering involves building AI-driven training tools like an interview coach, navigating technical challenges in scalability and CI/CD, and leveraging iterative development and data analysis to democratize complex skills through dynamic, AI-powered coaching systems.