Create advanced Works with: Any AI

Technical Debt Prioritization Brief

Table output Has example

Argue for debt work in business terms.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Prepare a case for technical debt work. The debt items and their effects: [DEBT_ITEMS]. Engineering time lost, incidents, or delays attributed to them: [IMPACT_DATA]. Upcoming roadmap items affected: [ROADMAP_ITEMS].

Produce: a table: Debt item | Symptoms | Cost (hours per month, incidents, delays, with source) | Risk if ignored | Fix effort | Payback period = effort / monthly savings, showing arithmetic | Priority. Identify items that block planned roadmap work. Propose a policy: reserve a fixed share of capacity (for example 15 to 20 percent), tackle debt tied to roadmap items first, and track results.

Write a persuasive brief for non-technical stakeholders (200 words) using business language (speed, reliability, customer impact), with no jargon. Include metrics to track (cycle time, defects, incident count) and a 90-day plan. Use only my data and mark estimates; do not exaggerate.

Rank items by payback period with the arithmetic, identify the one item to fix first, and write the two-sentence request for capacity in business terms, including what will be delayed if the request is granted.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Item 1: Manual deploy script. Cost: 6 hours per week lost (24 hours a month); 2 failed deploys last quarter. Fix effort 40 hours. Payback = 40 / 24 = 1.7 months.
Item 2: Untested billing module. Cost: 1 incident (8 hours) per quarter, about 2.7 hours a month; fix effort 80 hours; payback 30 months, but high risk.
Item 3: Old library. Cost: blocks the planned reporting feature (3 weeks delay); fix effort 60 hours.
Ranking by payback: 1, 3 (blocks roadmap), 2 (risk).
Request (about 70 words): "We ask for 15 percent of capacity this quarter. It removes 24 hours a month of lost time and unblocks reporting. Without it, reporting slips three weeks."
Metrics: deploy time, incidents, cycle time.

• tech-debt