> I don't know that this is true for all technical debt. Even if there might be some exceptions for some technical debt, it's always true from the product owne

> I don't know that this is true for all technical debt. Even if there might be some exceptions for some technical debt, it's always true from the product owner's and business perspective. Keep in mind that it takes resources, and sometimes even downtime, to address technical debt. In the POV of a product manager, addressing technical debt is an investment with the promise of little short-term returns with the tradeoff of significant risk in the form of downtime and regressions and bugs. And more importantly, technical debt is not a "one and done" deal. There are always more rewrites and refactoring to be done, and the one you're doing today might be the topic of technical debt discussions in the future.