Technical debt ratio

What it means

Technical debt ratio expresses debt as a normalized estimate, often remediation effort divided by an estimated development cost. The ratio can help compare areas, but it is only as credible as the estimates, scope, and assumptions behind it. It should be used for conversation and prioritization rather than precise accounting.

Example

A module is estimated to need ten engineer-days of cleanup against 100 engineer-days of replacement scope. The resulting ratio is 10 percent, but the team also considers change frequency and production exposure.

Limitations

Estimates are uncertain and can be gamed by changing the denominator. A low ratio can hide severe operational risk, while a high ratio may describe a stable legacy component. Report uncertainty and evidence.

How to use the signal

Report estimate uncertainty and raw evidence so a normalized percentage does not create false accounting precision.

Weave can add observed change and rework context to debt-ratio discussions. Store estimation methodology with the metric and avoid presenting Weave workflow data as a remediation-cost calculation.