How do you quantify and prioritize technical debt?

Quantification methods: effort estimation (hours to fix), cost of delay (impact if not fixed), code metrics (complexity, coverage, duplication), interest (ongoing cost of not fixing). Frameworks: Technical Debt Ratio (remediation cost / development cost), SQALE. Track: in issue tracker with labels, technical debt register. Prioritize: high interest (constant pain), blocking business features, security debt (immediate). Process: regular review meetings, allocate sprint capacity (20%), address during related feature work. Tools: SonarQube, CodeScene for visualization. Balance with feature delivery.