Technical Debt Language

Option C is the professional ROI case for technical investment. The structure is:

1. Quantify the current cost of NOT fixing it — "$96,000/quarter in incidents" — this is the "cost of doing nothing"
2. Quantify the engineering cost — "2 engineers × 12 weeks ≈ $60,000" — makes it concrete
3. Project the ROI — "70% reduction in P1s = $67,200 savings → pays back in one quarter"
4. Mention compound benefits — "faster feature velocity" — secondary payoff

Leadership approves technical work when it can be expressed as a financial decision: cost of problem vs. cost of fix vs. expected benefit.

Technical debt language that works with leadership:
• "We're currently spending X hours/week on workarounds for this — that's N engineer-weeks/year"
• "Every new feature in this module takes 2× longer than it should because of X"
• "The current architecture limits us to Y transactions/second — to hit our Q4 target of 2Y, we need to rearchitect sooner or face re-doing this work under pressure"

Option B is the professional infrastructure investment argument. It frames the decision around risk and compliance timelines, not technical preference:

• Hard deadline — "EOL in December, compliance audit in February" — creates urgency with external forcing functions
• Risk quantification — "known CVEs on unpatched software" — security risk is a real business cost
• Comparison of doing it now vs. deferring — "3 days now" vs "high-pressure, high-risk upgrade in January"
• ROI framed as risk avoidance — "cost of breach or compliance failure dwarfs 3 days" — doesn't require exact numbers because the asymmetry is obvious

Infrastructure investment arguments work best when they appeal to:
1. Compliance obligations — non-negotiable, regulatory
2. Risk avoidance — security breach, SLA penalty
3. Compound cost of deferral — "costs $10K now or $100K under pressure in 6 months"
4. Enabling future revenue — "this is a prerequisite for the Series B data room"