Understanding and Managing Technical Debt: Annual, Monthly, Weekly, and Daily Perspectives

Catching Smoke

Discussing technical debt is like trying to catch smoke; solutions often dissolve when new concerns arise, leading to endless cycles of debate over small improvements versus large rewrites.

Annual Debt (Rewrite)

Annual debt emerges after extensive discussion, often concluding that a complete rewrite is the only solution, though sometimes the issue stems from growth or market changes rather than true debt.

Labeling such challenges as debt can mislead, implying past mistakes when the situation may simply reflect successful evolution or external shifts.

Monthly Debt (New Project)

Monthly debt requires several months to resolve; it may start as a prototype or concept that later needs code cleanup and stabilization, demanding dedicated resources and planning.

Teams must weigh the cost‑benefit of addressing this debt, allocate focused effort, or accept the trade‑offs.

Weekly Debt (New Card)

Weekly debt can be tackled by adding cards or issues to a sprint; it often appears as a better implementation discovered during development, but integrating it into the current PR can distract reviewers.

Such debt should be assigned to someone, not necessarily the discoverer, and added to the sprint backlog to avoid maintaining duplicate code paths.

Daily Debt (Tidying)

Daily debt is not true debt but missed opportunities to improve existing code, such as refactoring unclear sections or extracting well‑named methods to reduce ergonomic pain.

Addressing daily debt improves code ergonomics and prevents recurring confusion.

Why We Don’t Fix Debt

Two main reasons: fear of wasting time under delivery pressure, and the boredom of refactoring which receives little recognition compared to new feature launches.

When engineers feel their time isn’t valued or improvements aren’t praised, they are less motivated to tackle daily or weekly debt.

25% Rule

Allocate 10% of time (≈4 hours per week) to daily debt, another 10% to weekly debt, and the remaining 5% to monthly and annual debt, using the time for planning and prioritization rather than direct fixes.

Daily Debt 10%

Spend up to four hours each week improving the code you work with, integrating refactoring into the team’s culture.

Weekly Debt 10%

Dedicate another ten percent of time to weekly debt, allowing the team to place manageable items on the project board and allocate effort accordingly.

Monthly & Annual Debt 5%

Use the remaining five percent for meetings and strategic planning to understand and prioritize larger debt items.

Resolving Debt Through Culture

Fixing technical debt is less about large‑scale rewrites and more about setting a strong example in daily work, celebrating refactoring, recognizing when good is sufficient, and knowing when to improve without striving for perfection.