
Technical debt is not every inelegant piece of code. It is a decision or condition that increases the cost and risk of future change, operation, or recovery. Discuss it through commercial consequences: lost orders, incorrect money states, exposed data, slow releases, or dependence on one specialist.
Do not attempt to “pay all debt.” Maintain a register tied to critical journeys and reserve capacity for work whose cost of delay and risk exposure exceed the cost of treatment.
Title:
Component and owner:
Observable condition:
Original context or decision:
Affected business journey:
Credible failure scenario:
Impact:
How quickly would we detect it?
How would we recover?
Change frequency:
Options: accept / mitigate / repair / replace:
Estimate and dependencies:
Next decision date:
Without a consequence scenario, “rewrite the module” cannot compete fairly for investment.
Use a consistent one-to-five scale:
| Factor | Question |
|---|---|
| Impact | What happens to money, customers, or data? |
| Likelihood | Do incidents and weak signals support the scenario? |
| Exposure | How often is the path used or changed? |
| Detectability | Will the team know before the customer? |
| Recoverability | Is rollback, workaround, and skill available? |
| Cost of delay | What worsens if the business waits a quarter? |
| Effort | What does safe treatment require? |
A formula can aid ordering but must not hide critical classes. A serious vulnerability needs a security response rather than waiting for its composite backlog score.
One strong control can sometimes reduce more risk than an immediate full rewrite.
Walk through product and price, search and PDP, basket and promotion, delivery, payment, order/ERP, return, account, analytics, and product feeds.
For each, ask which component fails repeatedly, resists testing, lacks ownership, relies on unsupported versions, or requires manual recovery. Link relevant incidents and change lead time to the record.
Use a persistent capacity allocation or explicit risk budget. The exact percentage depends on context; the essential control is that risk work is not cancelled every sprint for an unexamined feature.
Monthly review:
“Code rewritten” is insufficient. Completion may require data migration, regression coverage, removal of the old path, documentation, monitoring, load evidence, and a verified rollback.
Use scenario, likelihood, impact, cost of delay, and treatment options. “Old code” is weak; “each price update can disable checkout for two hours” is decision-ready.
Sometimes for a critical risk. More often, maintain capacity, pair treatment with roadmap work, and use explicit thresholds rather than an occasional unbounded refactoring month.
Use a range and confidence level, supported by incidents and expert scenarios. False numerical precision does not improve prioritisation.
Reviewed: 3 September 2026.
Continue with the replatforming checklist, platform selection, and dependency mapping.
Pingvera can make part of the debt observable by showing failure frequency, detection time, and critical-journey stability.
Pingvera watches whether an online business actually works — uptime, checkout, orders, domain, SSL and server — and alerts you in Telegram, email or a webhook before a customer has to tell you.
Start freeRead next: Ecommerce Replatforming Checklist · Ecommerce Returns Economics · How to Monitor Ecommerce Integrations · CAC Payback Period for Ecommerce · Run a free site check.
Read next: Ecommerce Replatforming Checklist · Ecommerce Returns Economics · How to Monitor Ecommerce Integrations · CAC Payback Period for Ecommerce · Run a free site check.