Track 1 — Engineering Economics

Module 1.3: Cost of Delay & Prioritization

Turn backlog prioritization from opinion-based to economics-based. Master Cost of Delay, WSJF, and debt interest rate calculations.

4 Lessons~55 minIntermediate

🎯 What You'll Learn

  • How to calculate Cost of Delay for four categories (revenue, risk, compliance, efficiency)
  • How to apply WSJF to rank engineering investments by economic return
  • How to calculate technical debt "interest rates" for prioritization
  • How to present engineering priorities to executives in financial language
1

Lesson 1: What Is Cost of Delay?

Cost of Delay (CoD) is the economic impact of not delivering a feature, fix, or initiative on time. It transforms prioritization from subjective opinion ("my feature is more important") to objective economics ("this feature costs us $50K/week in lost revenue").

Revenue CoD

A feature that would generate $200K/quarter in new revenue has a CoD of ~$15K/week. Every week of delay is $15K in unrealized revenue.

Calculate: (Annual revenue opportunity / 52 weeks) = Weekly CoD
Risk CoD

A security vulnerability with 20% chance of a $500K breach has an expected CoD of $100K (20% × $500K). The longer it stays unpatched, the higher the cumulative risk.

Expected CoD = Probability × Impact × Time exposed
Compliance CoD

Missing a compliance deadline (SOC 2, GDPR) can mean losing enterprise deals, contract penalties, or regulatory fines.

Example: SOC 2 non-compliance = can't close enterprise deal worth $500K ARR
Efficiency CoD

A developer productivity improvement saving each engineer 2 hours/week across 50 engineers = 100 hours/week. At $75/hr burdened rate, that's $7,500/week in CoD.

Calculate: (Hours saved × team size × burdened cost rate) = Weekly CoD
📝 Exercise

Pick your top 5 backlog items. Calculate the Cost of Delay for each using the categories above. Which one has the highest weekly CoD?

2

Lesson 2: WSJF — Weighted Shortest Job First

WSJF is an economic prioritization framework: divide Cost of Delay by job duration to find the items that deliver the most economic value per unit of time invested.

WSJF Formula

WSJF = Cost of Delay / Job Duration. Higher WSJF = do first. A $10K/week CoD item taking 1 week (WSJF: 10) beats a $50K/week CoD item taking 10 weeks (WSJF: 5).

Always compare WSJF scores, not raw CoD values
Job Duration Estimation

Use T-shirt sizes (S=1wk, M=2wk, L=4wk, XL=8wk) for quick estimates. Precision doesn't matter — relative ordering does.

If two items have similar WSJF ±20%, other factors can break the tie
The Urgency Profile

Not all CoD is constant. Some items have linear CoD (steady loss over time). Others have step-function CoD (zero until a deadline, then catastrophic).

Step-function CoD items (compliance, contract deadlines) need special treatment
📝 Exercise

Apply WSJF to your top 10 backlog items. Estimate job duration for each. Calculate WSJF and re-rank your backlog. How does the order change from your current prioritization?

3

Lesson 3: Technical Debt Prioritization

Not all technical debt should be paid off. Some debt is cheap to carry. The PDI framework helps you identify which debt to remediate first based on economic impact, not technical severity.

Economic Severity vs. Technical Severity

A "critical" code smell with no user impact has low economic severity. A "minor" API design issue blocking 3 teams has enormous economic severity. Always prioritize by economics.

Map: debt item → affected teams × frequency of impact × cost per occurrence
The Debt Interest Rate

Like financial debt, technical debt accrues interest. An API with no documentation costs 15 minutes per developer per interaction. At 20 interactions/week across 5 developers: 25 hours/week.

High-interest debt (affecting many people frequently) = remediate first
Quick-Win Identification

Items with high WSJF and low effort — "pay off the credit card, not the mortgage." A 4-hour fix that saves 2 hours/week across 10 engineers has massive ROI.

Target: items with ROI (annualized savings / cost to fix) > 5x
📝 Exercise

List your top 10 technical debt items. For each, calculate the "interest rate" (ongoing cost per week). Sort by interest rate. The top 3 are your priority remediation targets.

4

Lesson 4: Presenting Prioritization to Leadership

Executives don't want to hear about story points or WSJF scores. They want to know: "How much money are we leaving on the table, and what does it cost to pick it up?"

The Revenue Opportunity Frame

"We have 5 features with combined CoD of $75K/week. With current velocity we'll deliver them over 12 weeks. If we reduce tech debt first (2 weeks), velocity increases 30%, and we deliver all 5 in 8 weeks total — saving $225K."

Always show the alternative timeline and its economic impact
The Risk Reduction Frame

"Our current security debt exposes us to $2M in aggregate risk. A 4-week remediation sprint reduces this to $300K. The $150K investment in remediation buys a $1.7M risk reduction."

Use expected value calculations for risk items
The Competitive Frame

"Our deployment frequency is 15x slower than the industry median. This means competitors iterate 15x faster. In a market moving at AI speed, this is an existential risk."

Link engineering metrics to market positioning and competitive advantage
📝 Exercise

Create a one-page "Engineering Investment Proposal" using CoD and WSJF for your next quarter's priorities. Frame every item in dollar terms with clear ROI.