In this episode, you’ll hear:
Why product managers shouldn’t own bug tracking, tech debt, or architecture decisionsHow blurred boundaries between product and engineering lead to burnout and quality issuesThe difference between being responsible for a product and owning another team’s workHow legacy IT and project-based mindsets still shape modern product orgsWhy treating engineers as “order takers” breaks down in evergreen product environmentsWhat strong engineering leadership should own (and why that matters)When it does make sense for product to step in—especially around communication and coordinationKey ideas worth calling out:
The product trio owns the “what”; engineering owns the “how”Product managers are not people managers for engineers—and shouldn’t be accountable for engineering qualityIf quality is a problem, the solution is escalating and fixing the system, not managing individual bugsSkilled engineering teams naturally push back when boundaries are crossed—and that’s a good thingRemoving the PM as a middleman creates better flow and clearer ownershipCreate direct paths for stakeholders to get bug status without routing everything through productUse dashboards, shared tools, or Slack channels instead of one-off updatesEscalate systemic quality issues to engineering leadership, not individual contributorsAdvocate for real engineering leadership if your org expects product teams—not IT teamsFollow Teresa Torres: https://ProductTalk.org Follow Petra Wille: https://Petra-Wille.com