Cost of delay
Cost of delay is the economic impact of not having a feature available — revenue forgone, cost incurred, risk that compounds — expressed as a per-unit-time number (per week, per month). It's the economic input to WSJF and the strongest argument against multi-quarter backlogs where high-CoD items wait behind low-CoD ones.
CoD makes prioritisation explicit and economic. A feature with $200K/month of foregone revenue is worth doing this month even if it's a 4-week project; a feature with $10K/month is worth waiting on if the team is busy. The hard part is measuring CoD honestly: it's a multi-component estimate (revenue impact, urgency window, risk-reduction value) and most organisations have weak instincts for any of them. Common approximations: revenue is the customer-pipeline value; urgency is the date-based decay (compliance deadline, contract clause, market window); risk reduction is the option value of learning early. Even rough CoD numbers radically improve prioritisation because most backlogs are sorted by gut, not economics.
Related terms
- Weighted shortest job first (WSJF)
Weighted Shortest Job First is SAFe's prioritisation formula: WSJF = Cost of Delay ÷ Job Size, where Cost of Delay is a relative score combining user-business value, time criticality, and risk reduction.
- Lean portfolio management
Lean Portfolio Management is SAFe's approach to aligning strategy and execution at the portfolio level — funding value streams (not projects), managing portfolio flow through a Portfolio Kanban, and governing investment through Lean Budgets and Guardrails rather than detailed up-front project plans.
- Jobs-to-be-done
Jobs-to-be-done (JTBD) is a product-discovery framework, popularised by Clayton Christensen, that frames features in terms of the 'job' a customer is hiring the product to do — the underlying outcome they want — rather than demographic personas or feature lists.