Planet RoadmapMost prioritization frameworks compare value to effort and stop there. Cost of delay adds the missing dimension: time. By treating every month of waiting as a cost rather than a free option, cost of delay reframes the question from "is this feature good?" to "what does it cost us to keep it on the shelf?" The framing alone changes which features rise to the top.
What Is Cost of Delay?
Cost of delay is the value you forgo by not having a feature in production. If a feature would generate $20,000 a month in revenue and you delay shipping it for three months, the cost of delay is $60,000 — money you simply do not collect. The number forces a conversation that does not otherwise happen: whether the things blocking that feature are worth more than the value being deferred.
The concept comes from Don Reinertsen's queueing-theory work on Lean product development, and it shows up in SAFe as the numerator in WSJF. But you do not need a SAFe rollout to use it. Any team that prioritizes work can estimate cost of delay and use it to defend hard tradeoffs.
The Four Cost of Delay Archetypes
Reinertsen identified four shapes that cost-of-delay curves usually take. Knowing which archetype a feature fits helps you estimate the value more accurately.
- Urgency — value decays steadily over time. Most features are this shape.
- Fixed-date — value is high before a date and drops to zero after. Tax season, holiday launches, and regulatory deadlines all create fixed-date curves.
- Expedite — paying a premium to ship faster is sometimes worth it because the cost of delay is so steep. This is the case for production incidents and competitor responses.
- Intangible — strategic features that build optionality. Hard to quantify but real, and easy to under-prioritize because the dollar value is fuzzy.
Estimating Value
The most common objection to cost of delay is that "we cannot put a number on it." That is rarely true. A rough estimate with stated confidence is more useful than no estimate. Common signals: monthly revenue impact, churn reduction multiplied by average revenue per user, support hours saved, user time recovered, or the dollar value of the optionality unlocked.
For features without obvious revenue, convert time savings to dollars at a fully-loaded hourly rate. For strategic features, estimate the expected value of the future opportunity — even a low probability times a large number can be substantial. Then apply a confidence multiplier to discount everything proportionally to your certainty.
Cost of Delay vs CD3 vs WSJF
These three terms get used interchangeably but they are not the same. Cost of Delay is the raw dollar amount of value lost per unit time. CD3 — Cost of Delay Divided by Duration — divides that monthly cost of delay by job size, producing a rate-adjusted ranking score in dollars per month per month. WSJF is a Fibonacci-scaled abstraction of CD3 used in SAFe; the inputs are relative scores instead of dollars.
- Cost of Delay alone tells you the absolute economic stakes of a single feature.
- CD3 ranks features against each other in dollar terms — useful when stakeholders want money on the table.
- WSJF ranks features in relative units — faster to score, but harder to defend to non-product audiences.
Common Pitfalls
The biggest mistake is over-precision. Reporting cost of delay to the dollar implies false confidence. Round to the nearest thousand or ten thousand and explicitly attach a confidence percentage so the audience can see the uncertainty.
Another pitfall is double-counting. If a feature retains a customer worth $10,000 a year, do not also count their support cost savings — the value is already in the retention number. Pick the cleanest signal and stick with it.
Finally, do not let cost of delay override strategy. A high cost-of-delay number for a feature on the wrong roadmap means you are losing money quickly on the wrong work. Cost of delay is a sequencing tool, not a strategy tool.
Putting It Into Practice
Start small. Pick five candidate features for the next quarter and estimate cost of delay for each: monthly value, probability of realizing it, and months of expected delay. Sort by total cost of delay and the order will often be different from your gut ranking. To make the math fast, use a free cost of delay calculator — fill in the inputs, compare features side by side, and export the result for your planning notes.