Cost of delay is the economic cost of delivering something later rather than sooner: the value you lose for every unit of time a project is not finished. It answers a question most portfolios never quantify, which is what a month of waiting actually costs. Put a number on it and prioritization stops being an argument about opinions and becomes arithmetic.
The idea comes from product development economics, popularized by Donald Reinertsen. Its power is that it converts "this is urgent" into a figure you can compare across projects. Two initiatives can have identical returns and completely different costs of delay, and the one that bleeds value faster while it waits is the one you sequence first.
Key takeaways
- Cost of delay is the value lost per unit of time a project is late or unstarted, usually expressed in dollars per week or per month.
- It is what makes urgency comparable. Two projects with the same total value can have very different costs of delay, and that gap should decide their order.
- Delay is not always linear. Reinertsen names four profiles: linear, fixed-date, expedite, and standard (intangible). Each behaves differently over time.
- CD3, cost of delay divided by duration, ranks work by the value it unblocks per unit of time. Highest CD3 goes first.
- An approximate cost of delay you actually use beats a precise one you never calculate. The relative order between projects is more robust than the absolute figures.
- Cost of delay is the numerator inside WSJF. Understand it first, then the scoring model built on it makes sense.
What is cost of delay?
Cost of delay is the amount of value an organization forgoes for each period a benefit is delayed. If a project will earn 120,000 dollars a year once live, then every month it slips costs roughly 10,000 dollars in benefit never recovered, plus any competitive or compliance cost on top. That monthly figure is the cost of delay, and it is money already gone the moment the delay happens, not a future risk.
The reason it matters for a portfolio is that value and urgency are different things. A large project that delivers value slowly can have a lower cost of delay than a small project that unlocks revenue immediately. Sequencing by size or by total return alone gets this backwards. Cost of delay is the correction.
What is the cost of delay formula?
At its simplest, cost of delay is the value delivered divided by the time over which it is delayed:
Cost of delay = value lost per unit of time (for example, dollars per week)
For a benefit that accrues steadily, estimate the annual value and divide down to the period you sequence in. A project worth 240,000 dollars a year has a cost of delay of 20,000 dollars per month, or about 4,600 dollars per week. Where delay also carries a one-off penalty, a missed regulatory deadline, a lost contract, a fixed fine, add that to the running figure for the periods after the deadline. The output you want is a rate: value at risk per week or per month, per project, on a comparable basis.
How do you calculate cost of delay?
Calculate cost of delay in four steps, and accept estimates rather than chasing precision you do not have:
- Estimate the value. Annual revenue, cost saving, risk reduction, or benefit the project delivers once live. Use the same value basis you use in the project business case so the numbers reconcile.
- Choose a time unit. Weeks or months, matching the cadence you actually sequence and fund in.
- Convert value to a rate. Divide annual value by 52 or 12 to get value per week or per month. That rate is the linear part of the cost of delay.
- Add non-linear penalties. If there is a deadline, contractual date, or step change in value, layer that on for the periods it applies. A project whose value collapses after a regulatory date has a cost of delay that jumps sharply at that point.
Do this for every project competing for the same capacity, and you have a common currency for urgency. The relative ordering is the durable output. Even if every absolute figure is off by 20 percent, the ranking between projects usually holds, and the ranking is what you need.
What are the four cost of delay profiles?
Reinertsen observed that delay does not cost the same shape over time. Four profiles cover most real projects, and knowing which one applies changes how hard you should push to start.
| Profile | How the cost behaves | Typical example |
|---|---|---|
| Linear | Steady loss for every period of delay | A feature that earns a fixed amount per month once live |
| Fixed date | Little cost until a deadline, then a cliff | A compliance change due on a regulatory date |
| Expedite | Very high, urgent cost from day one | A production outage or a time-critical market window |
| Standard (intangible) | Low now, rising later, hard to quantify | Technical debt or a usability gap that compounds |
The trap is the standard, intangible profile. Because its cost is low and fuzzy today, it loses every prioritization fight to the linear and fixed-date work, and the delay quietly compounds until it becomes an expedite. Naming the profile forces that conversation before the cliff, not after.
What is CD3 (cost of delay divided by duration)?
CD3, cost of delay divided by duration, ranks work by how much value each item unblocks per unit of time it occupies your capacity. You divide each project's cost of delay by how long it takes to deliver, and you do the highest result first. It formalizes an intuition good schedulers already have: a quick job that stops a large bleed should jump ahead of a slow job that stops a small one.
An illustrative comparison. Project A has a cost of delay of 20,000 dollars a month and takes 4 months, giving a CD3 of 5,000. Project B has a cost of delay of 12,000 dollars a month and takes 1 month, giving a CD3 of 12,000. Project B is smaller and less valuable in total, yet it should go first, because it clears far more value per month of the capacity it consumes. Sequencing by total value alone would have picked A and left money on the table.
What is the difference between cost of delay and WSJF?
Cost of delay is the value lost per unit of time; WSJF (weighted shortest job first) is a scoring model that divides cost of delay by job size to produce a prioritization score. In other words, cost of delay is the numerator and WSJF is the full fraction. CD3 and WSJF are the same idea; WSJF is the name SAFe gives it and it approximates cost of delay from three components (business value, time criticality, and risk reduction or opportunity enablement) rather than a single dollar figure.
Use raw cost of delay when you can estimate value in money and want the honest economic figure. Use WSJF when money estimates are unreliable and a relative scoring proxy is good enough, which on a fast-moving backlog it often is. The full mechanics of WSJF, including how the three components are scored, live in the weighted shortest job first guide, alongside RICE and weighted scoring.
Why is cost of delay important in a portfolio?
Cost of delay matters because portfolio sequencing decisions are usually made on the wrong variable. Teams fund the biggest project, the loudest sponsor's project, or the one that is easiest to estimate, and they treat the order of delivery as a scheduling afterthought. But the order is where most of the value is won or lost. Two portfolios with the same projects and different sequences produce different amounts of value, and the difference is the sum of avoidable delay costs.
The common mistake is treating cost of delay as too hard to estimate and therefore not estimating it at all, which defaults you to a worse method. A rough figure that changes the sequence beats a perfect figure that arrives after the decision. Fold the estimates into how to prioritize a project portfolio, and make sure the value you assume is the value you later measure in benefits realization management, or the numbers become fiction the second time you use them.