Cost of Delay
Cost of delay is the value a business loses for each unit of time that a piece of work is not delivered, often expressed as money per week. It combines how valuable an initiative is with how urgent it is. Popularized in product development by Don Reinertsen, it reframes prioritization from "what is cheapest to build" to "what is most expensive to postpone."
How Cost of Delay Works
To estimate cost of delay, a team asks: once this is delivered, how much value will it create each week, and what happens to that value if it arrives later? Value can come from new revenue, protected revenue, cost savings or avoided risk.
Urgency shapes the answer. For some work, a delay simply pushes the same stream of value later. For other work, value decays over time as competitors move, or drops sharply after a deadline such as a regulatory date, a trade show or the end of a contract. Black Swan Farming, the consultancy most associated with practical cost of delay, describes these patterns as urgency profiles.
Cost of delay is most powerful when combined with duration. Dividing cost of delay by the time needed to complete the work gives CD3 (cost of delay divided by duration), a scheduling rule that puts the highest value per unit of time first. Reinertsen's book The Principles of Product Development Flow (2009) made the economic case for this approach, summed up in his advice: "If you only quantify one thing, quantify the Cost of Delay." The Scaled Agile Framework adapts the same idea as Weighted Shortest Job First (WSJF), using relative scores instead of money.
Why Cost of Delay Matters
Most prioritization looks at value and effort but ignores time. Cost of delay makes time visible. It shows that a queue of waiting work is not free, that large batches hold value back, and that a small, urgent item can deserve to jump ahead of a larger, more valuable one.
It also improves conversations. "This feature is worth roughly $10,000 a week" is easier to compare and challenge than "this is high priority." Even a rough estimate tends to expose very different assumptions between stakeholders. For product leaders, it connects sequencing decisions on the product roadmap directly to business economics.
Cost of Delay Example
A team must choose the order of two features, assuming value starts the week each ships:
- Feature A: cost of delay $10,000 per week, takes 4 weeks. CD3 = 2,500.
- Feature B: cost of delay $6,000 per week, takes 1 week. CD3 = 6,000.
If the team builds A first, B waits 4 extra weeks: 4 × $6,000 = $24,000 of delay cost. If it builds B first, A waits 1 extra week: 1 × $10,000 = $10,000. Building B first saves an estimated $14,000, even though A is the more valuable feature.
Cost of Delay vs. Opportunity Cost
Cost of delay measures the value lost while a specific item waits, so it guides sequencing. Opportunity cost is the value of the best alternative you give up entirely when you choose one option, so it guides selection. Both push teams to treat capacity and time as scarce resources.