Technical Debt Prioritization Matrix
Create a systematic framework to assess and prioritize technical debt in [product area]. Include: 1) Categorization system for different types of technical debt (architectural, code quality, testing gaps, etc.), 2) Assessment criteria including business impact, customer experience impact, development velocity impact, and risk factors, 3) Effort estimation approach, 4) ROI calculation methodology for debt repayment, 5) Visualization matrix plotting impact vs. effort, 6) Recommended allocation percentage of development resources for ongoing debt reduction, 7) Communication templates for explaining technical debt to non-technical stakeholders, and 8) Success metrics for measuring debt reduction progress.
How to Use This Prompt
- Copy the prompt using the button above
- Replace placeholders in [brackets] with your specific details
- Paste into your AI assistant (ChatGPT, Claude, Gemini, etc.)
- Iterate as needed - ask follow-up questions to refine the output
Why This Prompt Works
This prompt produces a comprehensive technical debt management framework by combining categorization, quantitative assessment, and communication tools in one output. The ROI calculation methodology and impact-vs-effort visualization make it possible to justify debt repayment investments to non-technical stakeholders, while the recommended resource allocation percentage provides a sustainable, ongoing approach to debt reduction.
When to Use This Prompt
- Engineering velocity has slowed and you suspect accumulated technical debt is the root cause
- Making a case to leadership for dedicating sprint capacity to infrastructure and code quality improvements
- Planning a major platform migration or refactoring initiative and need to scope and prioritize the work
Tips for Better Results
- Describe specific areas of known technical debt (legacy APIs, outdated dependencies, missing tests) so the AI categorizes and scores them
- Include metrics like deployment frequency, incident rates, or build times to help the AI quantify the business impact of debt
- Mention your engineering team size and current sprint allocation so resource recommendations are proportional and actionable