Make invisible costs visible
Technical debt that lives only in engineers’ heads never gets paid down — it just slows everything until a rewrite feels like the only option. A registry turns vague unease into a concrete, prioritized list that product and engineering can plan against. By scoring each item’s impact and effort, you can finally sequence debt work alongside features instead of pretending it does not exist.
How it works
Each row captures a debt item: a short name, the affected area, an impact description, an impact rating, an effort-to-fix rating, and an owner. Impact and effort are rated low, medium, or high. The tool derives a priority from the pair using an impact-versus-effort heuristic: high impact with low effort is a quick win and ranks top; high impact with high effort is important but needs planning; low impact ranks bottom regardless of effort.
The registry exports as a Markdown table sorted by derived priority, so the most valuable, cheapest fixes float to the top of your backlog review. The priority labels give product and engineering a shared language for deciding what to tackle and what to defer.
Tips and example
Keep impact descriptions concrete and tied to consequences: “Auth tokens never expire, so a leaked token is valid forever” reads as high impact; “Variable names in one helper are unclear” reads as low. A high-impact, low-effort item like “Add the missing index causing the slow dashboard query” should jump the queue. Re-rate items as reality shifts — debt that was low impact can become high the moment that area gets hot.