Technical Debt is a Key Performance Indicator (KPI) that represents the estimated development effort (in hours) required to fix the issues or violations detected in your platform.
These issues typically arise from:

• Not following best practices
• Customizing or modifying out-of-the-box (OOTB) functionality
  

Why Technical Debt Matters

#

Tracking how this KPI evolves over time and across instances helps you identify clear trends in your ecosystem’s health:

• Is the instance improving?
• Is it declining?
• Are issues accumulating faster than they are being resolved?
  
  

This makes Technical Debt a reliable health indicator for long-term quality and governance.

Important Considerations

#

Technical Debt represents high-level guidance, not a precise estimate.
It only measures coding effort and does not include additional activities that vary across products and projects, such as:

•  Technical & architectural analysis
•  Code reviews & testing
•  Release management
  
  
  
  

Global Technical Debt

#

Global Technical Debt extends beyond coding work. It includes all non-coding activities required to fully remediate issues, such as:

• Requirements & analysis
• Project management
• Testing
• Release planning and coordination
  
  

This provides a more holistic view of the true effort needed to restore your platform to best-practice standards.