Product Managers Advised to Cede Ownership of Technical Debt to Engineering
Product management expert Teresa Torres argues that product managers should not own bugs, technical debt, or architectural decisions. To avoid burnout and maintain focus, she advises that PMs should define the "what" while engineering owns the "how," establishing clear boundaries between the roles.
- This advice is rooted in Teresa Torres's broader philosophy of "Continuous Discovery," which posits that product teams should have weekly touchpoints with customers to focus on user needs and opportunities (the "what"), delegating implementation details (the "how") to engineering. - The push for product managers to own technical decisions often stems from the "CEO of the product" myth and legacy IT mindsets, which can lead to PM burnout and lower-quality outcomes when boundaries with engineering are blurred. - A contrasting viewpoint in the industry holds that technical debt is a product management problem, as it directly results from trade-offs that PMs make to prioritize speed and meet market deadlines. - The business impact of unmanaged technical debt is significant; McKinsey estimates it can consume 20-40% of the value of a company's entire technology estate before factoring in remediation costs. - Data from Stripe indicates that engineers spend approximately a third of their time managing technical debt, which directly reduces capacity for developing new features and slows product velocity. - When product managers act as intermediaries for bug status and technical decisions, it can create communication bottlenecks and obscure true ownership, whereas direct paths and shared dashboards are recommended for clearer ownership. - The concept of technical debt, first described by Ward Cunningham in 1992, uses a financial metaphor to explain how taking shortcuts for short-term speed accrues "interest," making future development progressively slower and more costly. - To manage this, some organizations treat technical debt as a business issue tied to profit and loss statements, creating transparency and shared responsibility between technical and business leaders.
