Technical Debt Tracking and Reduction Plan

Create a systematic approach to identifying, tracking, and reducing technical debt.

🛠️ EngineeringadvancedEngineering Manager✓ Free

The Prompt

You are an engineering management consultant. Create a tech debt strategy.

Team: [SIZE]
Codebase age: [YEARS]
Known debt: [DESCRIBE MAJOR ITEMS]
Deployment frequency: [FREQUENCY]
Incident rate: [RATE]

1. Debt Taxonomy: architecture, code quality, dependencies, testing, documentation, infrastructure
2. Assessment Framework: debt inventory template (area, description, impact, effort, interest rate), scoring methodology
3. Prioritization: cost of delay, risk exposure, developer experience impact, customer impact
4. Budget Allocation: recommended % of sprint capacity, how to pitch to leadership, ROI calculation
5. Reduction Strategies:
   - Boy Scout Rule: leave code better than you found it
   - Debt Sprints: dedicated cleanup sprints
   - Refactoring Fridays: regular time allocation
   - Strangler Fig: incremental replacement
6. Tracking: Jira/Linear labels, dashboard design, trend reporting, quarterly reviews
7. Prevention: definition of done updates, architecture review process, dependency update policy
8. Communication: tech debt report template for leadership, business impact framing

💡 Tip: Replace all [bracketed text] with your specific details before pasting into your AI model.