Cost of Delay (CoD)
What is the Cost of Delay (CoD)?
Cost of delay (CoD) is the value lost for each week or month a piece of work goes undelivered, from lost revenue, lost savings or added risk. Popularized by Donald Reinertsen, it underpins prioritization methods such as CD3 and WSJF.
Updated November 2026 · 3 min read
Cost of delay (CoD) is the value a business loses for each unit of time that a piece of work is not delivered, usually expressed as money per week or per month. It turns urgency into a number, so teams can compare features, projects and fixes on the same basis and sequence work to lose the least value. A feature with a cost of delay of $40,000 a week that ships a month late loses roughly $160,000, even if no one ever sees that money on a report.
The idea was popularized in product development by Donald Reinertsen, particularly in The Principles of Product Development Flow (2009), where he argued that teams should quantify the economic cost of waiting rather than relying on intuition about urgency. It underpins prioritization methods such as CD3 and weighted shortest job first (WSJF).
Where cost of delay comes from
- Lost revenue. Sales that cannot close until a capability exists, or new revenue that starts later than it could.
- Lost savings. Efficiency gains, such as automation that reduces manual work, that do not begin until delivery.
- Risk and penalties. Regulatory deadlines, contractual commitments and security exposure, where the cost may jump sharply after a date.
- Market timing. Opportunities with a short window, such as a seasonal peak or a competitor's weakness, where late delivery captures less of the total value.
Not every item loses value at the same rate. Kanban practitioners describe classes of service such as expedite, fixed date, standard and intangible, which reflect different urgency profiles. A fixed-date item may have little cost of delay until shortly before the deadline, then a very large one.
How to estimate and use cost of delay
- Pick a time unit. Weeks work well for most product teams.
- Estimate the value per week once delivered. Use revenue, savings or avoided cost. Rough ranges are fine; the goal is relative accuracy.
- Adjust for urgency. Ask whether waiting reduces the total value, not just postpones it.
- Estimate duration. How many weeks the work will occupy the team.
- Divide cost of delay by duration. This is CD3 (cost of delay divided by duration). Do the highest score first.
- Revisit. Update estimates as you learn, especially for large items.
How to calculate cost of delay: Example
Consider a hypothetical B2B software team with three items, each of which can only be worked on one at a time:
| Item | Cost of Delay per Week | Duration (Weeks) | CD3 Score |
|---|---|---|---|
| A: Compliance feature unblocking $2.08M a year in deals | $40,000 | 4 | 10,000 |
| B: Billing fix reducing failed payments | $20,000 | 1 | 20,000 |
| C: Reporting improvement | $10,000 | 2 | 5,000 |
Item A's figure comes from $2,080,000 divided by 52 weeks. CD3 says do B, then A, then C. B finishes at week 1, A at week 5 and C at week 7, so the total cost of delay is $20,000 × 1 + $40,000 × 5 + $10,000 × 7 = $290,000.
Doing the highest-value item first (A, then B, then C) finishes them at weeks 4, 5 and 7, for $160,000 + $100,000 + $70,000 = $330,000. Doing the shortest first (B, C, A) also costs $330,000. Sequencing by CD3 saves $40,000 compared with either approach, with no extra work.
Cost of delay vs. WSJF
WSJF, used in the Scaled Agile Framework (SAFe), follows the same logic but replaces money with relative scores. Cost of delay is estimated as the sum of user-business value, time criticality and risk reduction or opportunity enablement, and divided by job size. It is easier to apply where teams cannot estimate value in money, but it loses the ability to compare items against real business figures.
Common pitfalls
- Chasing false precision. Spending weeks on a perfect estimate delays the work it is meant to prioritize. Ranges are enough.
- Ignoring duration. High value alone does not set the order. A large item can block several smaller, urgent ones.
- Treating every deadline as urgent. Many dates are arbitrary. Ask what actually happens if the date slips.
- Overloading the team. Starting everything at once delays everything. Limiting work in progress is often the cheapest way to cut total cost of delay.
Cost of delay connects naturally to feature prioritization, WIP limits and portfolio prioritization, where the same reasoning applies to whole projects.
Frequently asked questions
How do you calculate cost of delay?
Estimate the value per week a piece of work would produce once delivered, from revenue, savings or avoided cost, and adjust for whether waiting reduces total value rather than just postponing it. A compliance feature unblocking $2.08 million a year in deals has a cost of delay of $40,000 a week. Rough ranges are fine, since relative accuracy is what matters.
What is CD3 in cost of delay prioritization?
CD3 stands for cost of delay divided by duration. Divide each item's cost of delay per week by the number of weeks it will occupy the team, then do the highest score first. This favors short, valuable work over large items that would block it, and usually loses less total value than ordering by value alone or shortest job first.
What is the difference between cost of delay and WSJF?
WSJF, used in SAFe, follows the same logic but replaces money with relative scores: cost of delay is the sum of user-business value, time criticality and risk reduction or opportunity enablement, divided by job size. It is easier where value cannot be estimated in money, but its scores cannot be compared with real business figures.
Related terms
Portfolio Prioritization
Ranking initiatives against agreed criteria so money goes where it counts.
Cut Line
The point in a ranked list where funding or capacity runs out.
Capital Allocation
Deciding where money goes, from projects to acquisitions, for long-term value.
Demand Management
Capturing and shaping new work requests so only the best ones are committed.