What Is Cost of Delay? How to Use It for Better Product Prioritization

Cost of Delay (CoD) is a prioritization concept that measures the economic impact of delaying a piece of work — the value that is foregone for every unit of time that a feature, improvement, or initiative isn’t delivered. Developed by Don Reinertsen and popularized by Joshua Arnold, Cost of Delay reframes the question from “what is most important?” to “what is the cost of waiting to do this?”

This reframing is powerful because it connects the timing of delivery decisions to their economic consequences — making the trade-offs between different work items visible in a shared, quantitative language.

Why Cost of Delay Matters

Most product prioritization frameworks evaluate items by their expected value — RICE scoring, opportunity scoring, MoSCoW, or weighted criteria matrices all assess how much value an item will create. What they often miss is the urgency dimension: two items of equal value are not equal in priority if one becomes less valuable over time while the other retains its value indefinitely.

Cost of Delay captures this urgency by asking: if we delay this item by one week, how much value do we lose? The answer differs dramatically based on the item’s nature:

High urgency, low decay: A security vulnerability fix that becomes critical — every day it’s unpatched, risk accumulates.

Time-sensitive opportunity: A feature that would capitalize on a market trend — delay past a certain point and the window closes.

Steady, durable value: A feature with constant demand that generates consistent value whenever it’s delivered.

Early plateau: A feature that’s most valuable immediately post-launch but levels off quickly — delaying delivery significantly reduces lifetime value.

Calculating Cost of Delay

True Cost of Delay requires estimating the value generated per unit of time (typically weekly or monthly), which then becomes the cost of each unit of delay. This can include:

• Revenue impact: Direct new revenue or revenue protected by delivering the feature
• Risk reduction: The cost of not addressing a vulnerability, compliance gap, or technical risk
• Market opportunity: Revenue or market position that can only be captured within a time window
• User or customer value: Churn avoided, satisfaction improved, or adoption accelerated

For teams that find it difficult to monetize all value precisely, relative CoD estimation — ranking items by their relative cost of delay rather than assigning dollar amounts — still captures the urgency dimension that absolute scoring misses.

CD3: Cost of Delay Divided by Duration

The most influential application of Cost of Delay is the CD3 formula:

CD3 = Cost of Delay ÷ Duration (size of the work)

CD3 provides a more complete prioritization signal than CoD alone, because it accounts for how long each item takes to deliver. A high-CoD item that takes six months to build might yield lower CD3 than a moderate-CoD item that can be delivered in two weeks — because the smaller item can be delivered now, capturing its value sooner.

CD3 is essentially a return-on-investment calculation that values both the economic urgency of the item and the efficiency of the delivery.

Applying Cost of Delay in Practice

Start with relative estimates: Exact monetization of CoD is difficult. Starting with relative comparisons — “this item has 3x the cost of delay as that one” — is more practical and still produces significantly better prioritization than ignoring urgency entirely.

Identify the urgency profile: For each item, understand which of the four urgency profiles (steady, time-sensitive, plateau, or increasing) describes it best. This shapes how urgency should factor into prioritization.

Use CoD to challenge intuition: When the team’s intuitive priority order conflicts with the CoD-informed order, investigate. Often CoD analysis reveals that items the team assumed were lower priority are actually creating significant value by sitting in the queue.

Key Takeaways

Cost of Delay is one of the most intellectually important concepts in product prioritization — because it makes the economic consequences of sequencing decisions visible. Teams that incorporate it into their prioritization thinking make better sequencing decisions, ship value sooner, and can defend their prioritization choices in economic terms that executives and stakeholders understand. It doesn’t replace other prioritization inputs, but it adds the urgency dimension that most frameworks underweight.