How do you build a business case for technical debt work?

This question tests your ability to translate abstract technical issues into concrete business impact, demonstrating strategic thinking. A great answer frames debt as a business liability, quantifies its impact on velocity and cost of delay, proposes a clear capacity-based plan (e.g., 20% of sprint), and connects the fix to enabling future roadmap items. The red flag is complaining about poor code without presenting a data-driven business case tied to future outcomes.