One of the hardest calls you’ll make is deciding which features or fixes can’t wait. Every stakeholder insists their request is urgent, but in reality, some delays hurt the business far more than others.
That’s where Cost of Delay (CoD) and Weighted Shortest Job First (WSJF) come in. They help you compare backlog items by looking not just at effort, but also at the cost of waiting.
What Is Cost of Delay?
Cost of Delay = The economic impact of not delivering a feature sooner.
It might show up as:
- Lost revenue (e.g. missing a seasonal campaign).
- Lost customers (e.g. churn because of a poor experience).
- Lost opportunity (e.g. late to market against competitors).
The higher the cost of delaying something, the higher it should rise in priority.
WSJF: Weighted Shortest Job First
In the SAFe framework, Cost of Delay is paired with WSJF, which adds effort into the equation.
The formula is:
WSJF = Cost of Delay ÷ Job Duration
This means you’re not just prioritising the most painful delays, but also the ones you can solve quickly.
How to Apply Cost of Delay / WSJF
1. Estimate Cost of Delay.
Break it into three elements (often scored on a scale of 1–10):
- User-business value
- Time criticality (urgency)
- Risk reduction or opportunity enablement
2. Estimate Job Duration.
Get a rough idea of how long it will take the team (person-days/weeks).
3. Calculate WSJF.
Divide CoD by job duration. Higher score = higher priority.
Example: Voucher Feature vs UI Tweak
- Voucher Feature
- User-business value = 8
- Time criticality = 9 (seasonal campaign)
- Risk reduction = 5
- Cost of Delay = 22
- Duration = 2 weeks
- WSJF = 22 ÷ 2 = 11
- UI Tweak (cosmetic)
- User-business value = 3
- Time criticality = 2
- Risk reduction = 1
- Cost of Delay = 6
- Duration = 2 weeks
- WSJF = 6 ÷ 2 = 3
👉 Even if both tasks take the same time, the voucher feature clearly ranks higher.
Visual: Cost of Delay Framework
Option 1: A formula diagram:
- Three boxes: Value, Time Criticality, Risk Reduction → arrow → Cost of Delay.
- Cost of Delay ÷ Duration = WSJF.
Option 2: Example comparison table (like above) for clarity.
Pros and Cons
✅ Pros
- Focuses on business impact, not just effort.
- Encourages tough but transparent trade-offs.
- Works well when multiple “urgent” requests compete.
⚠️ Cons
- Estimations can be subjective.
- Harder to explain to non-technical stakeholders.
- Best suited for medium/large teams with multiple streams of work.
When to Use WSJF
- When your backlog has too many “critical” items.
- When you need to justify priorities in business terms.
- When timing matters (e.g. seasonal features, compliance deadlines).
It’s less useful for small backlogs or when the “cost of delay” is unclear.
WSJF helps you move past the shouting matches of “my feature is urgent” by putting a number on what delay actually costs. It’s not about being perfect — it’s about making trade-offs more transparent.
👉 Reflection: Next time you’re juggling competing “urgent” requests, try running a quick WSJF session. You might be surprised which items really can’t wait.
