Boundaries Between Product & Engineering - All Things Product Podcast with Teresa Torres & Petra Wille

Teresa Torres and Petra Wille examine the blurred line between product and engineering, where product managers drift into owning bugs, tech debt and architecture. They argue this starts as helpfulness but leads to PM burnout and weaker outcomes. The conversation traces the pattern to legacy IT mindsets and the 'CEO of the product' myth. Their core position is that product owns the 'what' and engineering owns the 'how', and that quality problems should be fixed at the system level through strong engineering leadership rather than by PMs managing individual defects. The episode matters because many PMs feel like bug-status middlemen or are held accountable for technical decisions outside their expertise.

01Key takeaways

• Keep the PM out of the middle of bug status; give stakeholders direct access through dashboards or shared channels.
• Treat tech debt and architecture as engineering-owned decisions, with product contributing business context.
• Escalate systemic quality issues to engineering leadership rather than individual contributors.
• Expect and welcome engineers pushing back when product crosses into their domain; it signals healthy boundaries.
• If your organization expects product teams to act like IT project teams, advocate for proper engineering leadership.
• Distinguish being responsible for a product outcome from owning every piece of work that produces it.

02Key sections

The problem of blurred boundaries

PMs often take on bug tracking, tech debt and architecture decisions out of good intentions. Over time this erodes their focus and produces burnout.

Where the myths come from

Legacy IT project mindsets and the idea that a PM is the CEO of the product both push PMs toward owning engineering work they do not control.

Responsibility versus ownership

Being responsible for a product outcome is different from owning another team's work. The product trio splits the 'what' from the 'how'.

Fixing quality at the system level

When quality is poor, the remedy is escalating to engineering leadership and changing the system, not having PMs manage individual bugs.

When product should step in

Product can appropriately help with communication and coordination, such as sharing status through dashboards or shared channels, while engineering retains technical decisions.

03From the post

“Listen to this episode on: Spotify | Apple Podcasts Where exactly is the boundary between product and engineering—and what happens when it gets blurry? In this episode, Teresa Torres and Petra Wille dig into a tension many product teams quietly struggle with: product managers taking on responsibility for bugs, tech”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.