How Do You Balance Technical Debt with Delivering Features?

Technical debt is inevitable in any long-term project, but how do you decide when to address it? Prioritizing new features often comes at the cost of accumulated debt, leading to slower development in the long run. On the other hand, dedicating too much time to refactoring can delay feature releases. What’s your approach to maintaining the balance between innovation and sustainable code quality?