How to prioritize a feature backlog using WSJF — Weighted Shortest Job First — gives product teams a quantitative framework that balances business value, time sensitivity, risk reduction, and job size to rank features more defensibly than gut instinct alone.
WSJF originates from SAFe (Scaled Agile Framework) but can be applied by any product team regardless of whether they use SAFe.
What Is WSJF?
WSJF scores each backlog item by dividing its Cost of Delay by its Job Duration (relative size). Items with high value and short duration score highest and get prioritized first.
WSJF Score = Cost of Delay / Job Duration
Cost of Delay has three components:
- Business Value — revenue impact, retention impact, strategic importance (1–10)
- Time Criticality — does value decay if delivered late? Is there a regulatory deadline? (1–10)
- Risk Reduction / Opportunity Enablement — does this unblock other work or reduce technical or market risk? (1–10)
Cost of Delay = Business Value + Time Criticality + Risk Reduction
WSJF = Cost of Delay / Job Duration
Worked Example
| Feature | Biz Value | Time Crit | Risk Red | CoD | Duration | WSJF | |---|---|---|---|---|---|---| | Fix checkout bug on mobile | 8 | 9 | 3 | 20 | 1 | 20.0 | | Add SAML SSO for enterprise | 7 | 5 | 5 | 17 | 8 | 2.1 | | Redesign onboarding flow | 9 | 4 | 4 | 17 | 5 | 3.4 | | Export to CSV | 5 | 3 | 2 | 10 | 2 | 5.0 | | Build notification center | 6 | 3 | 3 | 12 | 6 | 2.0 |
Priority order by WSJF: Fix checkout bug → Export to CSV → Redesign onboarding → Add SAML SSO → Build notification center
The checkout bug scores first not because it has the highest business value but because the combination of high time criticality and short duration makes delaying it extremely costly relative to effort.
H3: How to Score Duration
Use Fibonacci relative sizing, not absolute hours:
- 1 = very small (1–2 days)
- 2 = small (3–5 days)
- 3 = medium (1–2 weeks)
- 5 = large (2–4 weeks)
- 8 = very large (1–2 months)
- 13 = extra large (2+ months)
According to Lenny Rachitsky on his newsletter, the most productive prioritization frameworks are the ones that force explicit scoring of time sensitivity — teams that only score business value systematically under-prioritize time-critical work until it becomes a crisis.
Practical Adjustments
When WSJF scores are too close to call: Add a tiebreaker dimension — confidence in the estimate (1–5). Multiply WSJF by confidence before ranking. This surfaces the difference between a 15-point item you understand well and a 15-point item built on assumptions.
When scores feel wrong: Trust your intuition as a signal, not an override. If the scoring produces a result that seems wrong, diagnose why. Usually it means a dimension was scored inconsistently — revisit the inputs, don't just swap the order.
When stakeholders dispute the scores: Run the scoring exercise collaboratively. Stakeholders arguing about WSJF scores are actually arguing about strategy — surface that conversation explicitly.
According to Shreyas Doshi on Lenny's Podcast, the value of a scoring framework like WSJF is not primarily in the output — it is in the conversation it forces. Teams that score together align faster than teams that argue about priority in the abstract.
H3: WSJF vs. RICE vs. ICE
| Framework | Best for | Key difference | |---|---|---| | WSJF | Agile teams with dependency-heavy backlogs | Explicitly accounts for time sensitivity | | RICE | Growth teams optimizing for user impact | Separates reach and confidence | | ICE | Early-stage teams with simple backlogs | Fastest to apply, least nuance |
According to Gibson Biddle on Lenny's Podcast, the best prioritization frameworks are the ones your team will actually use consistently — a simpler framework applied every sprint beats a sophisticated one that requires a spreadsheet meeting to run.
FAQ
Q: What does WSJF stand for? A: Weighted Shortest Job First. It prioritizes items by dividing Cost of Delay (business value + time criticality + risk reduction) by job size, surfacing high-value short-duration work first.
Q: How is WSJF different from RICE prioritization? A: WSJF explicitly accounts for time criticality and risk reduction, making it better for backlogs with regulatory deadlines, customer commitments, or dependency chains. RICE is better for growth-focused teams optimizing for user impact reach.
Q: How do you score job duration in WSJF? A: Use Fibonacci relative sizing (1, 2, 3, 5, 8, 13) rather than absolute hours. Relative sizing is more accurate for longer-horizon estimates and forces team alignment on scope.
Q: When should you use WSJF instead of other frameworks? A: When your backlog has significant time-sensitive items — regulatory deadlines, customer commitments, or dependencies that block other teams. If time sensitivity is low across your backlog, RICE may be simpler.
Q: How often should you re-run WSJF scoring? A: At each sprint or planning cycle. WSJF scores are not static — time criticality in particular changes as deadlines approach or recede.
HowTo: Prioritize a Feature Backlog Using WSJF
- List all backlog items and score each on Business Value, Time Criticality, and Risk Reduction using a 1 to 10 scale for each dimension
- Sum the three scores to calculate Cost of Delay for each item
- Estimate job duration for each item using Fibonacci relative sizing: 1 for very small through 13 for extra large
- Divide Cost of Delay by Job Duration to calculate the WSJF score for each item
- Sort the backlog by WSJF score descending to produce the prioritized order
- Review the output for intuitive mismatches — if a result seems wrong, diagnose the scoring inputs rather than overriding the output