Cost of delay

Cost of Delay quantifies the economic impact of not delivering something sooner. It answers the question: "What value are we losing by waiting?" If a feature would generate $10,000 per week once launched, each week of delay costs $10,000. This framing transforms prioritization from subjective debate into economic analysis, revealing that timing matters as much as what you build.

Why it matters

Traditional prioritization focuses on value: which feature is worth more? But this ignores timing. A highly valuable feature delivered a year from now may be worth less than a moderately valuable feature delivered next month, if that delay costs more than the value difference.

Cost of Delay matters because it makes timing costs visible:

Reveals hidden costs. Delays feel free but aren't. Cost of Delay quantifies what you're losing.

Changes prioritization. When you factor in delay costs, optimal sequencing often differs from simple value ranking.

Creates urgency. Features with high Cost of Delay should be built sooner, even if their total value is lower than alternatives.

Enables trade-off discussion. Debates become about economics rather than preferences.

Components of cost of delay

Cost of Delay can arise from several sources:

User/Business Value. The ongoing value a feature provides once delivered. A feature generating $10K/month has a delay cost of $10K per month of delay.

Time Criticality. Value that's tied to timing. A feature for holiday shopping has high time criticality before December and near-zero after.

Risk Reduction. Value from avoiding bad outcomes. Delaying a security fix risks a breach; that risk has a cost.

Opportunity Enablement. Value from enabling future opportunities. A platform feature that unlocks a new market creates delay cost through missed opportunity.

These components interact. A feature might have moderate user value but extreme time criticality, creating high total Cost of Delay.

Calculating cost of delay

The simplest Cost of Delay calculation:

Cost of Delay = Value per Time Unit × Units of Delay

If a feature generates $50K per month and is delayed 3 months, the Cost of Delay is $150K.

More sophisticated calculations consider:

Value decay. Some opportunities diminish over time. Missing a market window might reduce ultimate value, not just delay it.

Probability-weighted outcomes. Risk reduction has expected value based on probability and impact.

Relative estimation. When precise numbers are unavailable, relative scoring (this feature's Cost of Delay is 3× that one's) still improves decisions.

Cost of delay profiles

Different items have different delay profiles:

Standard. Value is constant over time. Delay costs accumulate linearly. Most features follow this pattern.

Urgent. Value is immediate and high. Delay costs are severe and immediate. Bug fixes and urgent customer requests.

Time-critical. Value is tied to a specific window. Delay past the window means total loss. Seasonal features, event tie-ins.

Intangible. Value is hard to quantify but real. Technical debt reduction, morale improvements.

Understanding the profile helps prioritize appropriately.

Cost of delay in wsjf

Weighted Shortest Job First (WSJF) uses Cost of Delay as the core prioritization factor:

WSJF = Cost of Delay ÷ Job Size

This formula favors items with high delay costs that can be completed quickly. It addresses the common mistake of prioritizing large, valuable items over smaller items that could deliver value sooner.

The key insight: delivering something valuable quickly is often better than delivering something more valuable slowly, because you start capturing value sooner.

Practical applications

Feature prioritization. Sequence features by WSJF rather than simple value ranking.

Technical debt. Quantify the ongoing cost of not addressing technical problems - slower development, increased bugs, team morale.

Capacity decisions. When deciding whether to hire or invest, consider the Cost of Delay of work not getting done.

Vendor selection. A more expensive vendor who delivers faster might have lower total cost when delay is factored in.

Scope decisions. Cutting scope to deliver sooner may be better when Cost of Delay is high.

Challenges with cost of delay

Estimation difficulty. Future value is inherently uncertain. Cost of Delay estimates are educated guesses.

Comparability. Different items may have different value types that are hard to compare on one scale.

Gaming. If teams know Cost of Delay drives prioritization, they may inflate estimates.

Complexity. Sophisticated Cost of Delay analysis can become complex. Sometimes simpler methods suffice.

Not all delay is equal. A week's delay in January differs from a week's delay in November for seasonal products.

Beyond cost of delay

Cost of Delay is one factor in good prioritization, not the only factor:

Dependencies. Some work must precede other work regardless of Cost of Delay.

Learning value. Some work generates learning that informs future decisions.

Strategic fit. Some work supports strategy even without immediate Cost of Delay.

Team considerations. Skill development, morale, and sustainable pace matter.

Use Cost of Delay to inform decisions, not to mechanically determine them.

Tools like Klero help understand Cost of Delay by revealing which customer needs are most urgent. When feedback shows customers are struggling with something today, the Cost of Delay for addressing it is more apparent.