Prioritization & decisions · Economic sequencing model
WSJF
Sequence work by relative cost of delay divided by relative job size.
Job size
Start here · 5-minute visual lesson
Do first the work that is most expensive to delay relative to how long it occupies scarce capacity.
Think of it like this: At a hospital, urgency and treatment time both matter: a quick, time-critical case may go before a larger valuable one.
- 1Estimate value
- 2Add time criticality
- 3Add risk reduction
- 4Divide by job size
Important work sits in a static ranked backlog while the cost of waiting changes.
The team sees which value decays fastest and where splitting a large job improves flow.
Learn by deciding
SSO, audit export, or migration?
SSO is valuable, but audit export has a nearer deadline and is smaller. Which factor captures this?
Time criticality captures decay; job size rewards the shorter valuable item.
A migration scores poorly because it is huge. Is it unimportant?
Not necessarily. The score is telling you to look for smaller independently valuable slices.
Can two teams compare their WSJF numbers directly?
Only if they used the same reference scale and scoring conversation. Relative numbers are local.
01 · Understand
In plain English
Weighted Shortest Job First favors economically urgent, valuable, risk-reducing work that can be completed relatively quickly.
Origin and context
WSJF adapts Don Reinertsen’s cost-of-delay thinking. SAFe operationalizes it with relative user/business value, time criticality, risk reduction or opportunity enablement, and job size.
The problem it solves
A static priority list ignores how value decays with time and how long work occupies scarce capacity. WSJF focuses on sequence and economic delay.
The concepts, explained
Learn the vocabulary first. Each concept changes a decision you will make when using the framework.
Cost of delay
The economic value lost while work waits. It combines value, urgency, and the opportunity or risk unlocked by acting.
User or business value
The relative benefit created for customers or the organization when the job is completed.
Time criticality
How quickly the value decays. A deadline, market window, or compounding loss makes delay more expensive.
Risk reduction or opportunity enablement
The uncertainty removed or future work made possible by completing the job now.
Relative job size
A shared estimate of the work needed to reach done. Smaller independently valuable slices usually flow sooner.
WSJF score
Cost of delay ÷ job size. A high score identifies work that is expensive to postpone and relatively quick to complete.
02 · Deep dive
Go beyond the definition
Follow the reasoning inside WSJF, then challenge it before you use it.
1 of 4mental model
The mental model
What changes in the way you see the problem
Cost of delay
Use this concept to examine the problem from a distinct WSJF perspective.
User/business value
Use this concept to examine the problem from a distinct WSJF perspective.
Time criticality
Use this concept to examine the problem from a distinct WSJF perspective.
Risk reduction / opportunity enablement
Use this concept to examine the problem from a distinct WSJF perspective.
Relative job size
Use this concept to examine the problem from a distinct WSJF perspective.
WSJF = cost of delay ÷ job size
Use this concept to examine the problem from a distinct WSJF perspective.
Reasoning trace
Watch each step earn the next one
A platform compares SSO (8 value + 8 urgency + 5 enablement = 21; size 5; WSJF 4.2), audit export (5+5+3=13; size 3; 4.33), and design-system migration (3+2+8=13; size 8; 1.63). Audit export sequences first by score, although a hard SSO contract date may change the decision.
- 01Frame
Choose a comparable set of jobs.
Decision question: How does value decay if this waits one month? - 02Interrogate
Agree on a relative scale and reference item.
Decision question: Can the job be sliced without losing the outcome? - 03Interrogate
Score user/business value with shared evidence.
Decision question: How does value decay if this waits one month? - 04Interrogate
Score how sharply value changes with time.
Decision question: Can the job be sliced without losing the outcome? - 05Interrogate
Score risk reduction or opportunity enablement.
Decision question: How does value decay if this waits one month? - 06Interrogate
Sum these three as relative cost of delay.
Decision question: Can the job be sliced without losing the outcome? - 07Interrogate
Estimate relative job size; divide and sort.
Decision question: How does value decay if this waits one month? - 08Decide
Review dependencies, split oversized jobs, and recalculate regularly.
Decision question: Can the job be sliced without losing the outcome?
Failure-mode lab
Which mistake is most likely on your team?
Choose one to turn it into a control for your next workshop.
Context adaptation
The canonical version is only a starting point
Scale-ups can use WSJF for quarterly sequencing without adopting SAFe. Enterprises can score at portfolio and team levels but should not compare numbers produced by unrelated scoring rooms.
Signals it fits
- Several jobs compete for the same constrained capacity
- Delay has material economic consequences
- Teams can score comparatively
Signals to switch tools
- Work cannot be meaningfully split or compared
- A non-negotiable duty must be completed
- Scores are dictated rather than discussed
Now use the framework. The workbench below turns your own context into a first decision draft.
Work my problem03 · Apply
How to use WSJF
- 01
Choose a comparable set of jobs.
- 02
Agree on a relative scale and reference item.
- 03
Score user/business value with shared evidence.
- 04
Score how sharply value changes with time.
- 05
Score risk reduction or opportunity enablement.
- 06
Sum these three as relative cost of delay.
- 07
Estimate relative job size; divide and sort.
- 08
Review dependencies, split oversized jobs, and recalculate regularly.
04 · See it work
A worked example
A platform compares SSO (8 value + 8 urgency + 5 enablement = 21; size 5; WSJF 4.2), audit export (5+5+3=13; size 3; 4.33), and design-system migration (3+2+8=13; size 8; 1.63). Audit export sequences first by score, although a hard SSO contract date may change the decision.
Business case study
Illustrative fictional scenario
An enterprise SaaS train uses invented relative scores in a cross-functional workshop. It splits a 13-point migration into smaller independently valuable slices and recalculates. This teaches flow economics rather than documenting a named company.
Across company types
Scale-ups can use WSJF for quarterly sequencing without adopting SAFe. Enterprises can score at portfolio and team levels but should not compare numbers produced by unrelated scoring rooms.
05 · Work your problem
Turn the framework into a result
Explore the mechanics
Copy the working template
Job,Business value,Time criticality,Risk reduction / opportunity enablement,Job size,WSJF,Dependency note
06 · Use judgment
Where it helps—and where it breaks
Use when
- Several jobs compete for the same constrained capacity
- Delay has material economic consequences
- Teams can score comparatively
Do not use when
- Work cannot be meaningfully split or compared
- A non-negotiable duty must be completed
- Scores are dictated rather than discussed
Advantages
- Makes time criticality visible
- Rewards smaller valuable slices
- Useful for ongoing resequencing
Limitations & criticisms
- Relative scores are not currency
- Large groups may anchor on loud opinions
- The standard factorization can double-count
Common failure modes
- Treating job size as duration with false accuracy
- Using different reference scales
- Leaving the sequence unchanged for months
Often confused with
RICE estimates reach-adjusted impact per effort; WSJF emphasizes delay economics and relative sequencing.
Practical checklist
Reflection questions
- How does value decay if this waits one month?
- Can the job be sliced without losing the outcome?
07 · Check
Five-question knowledge check
Key takeaways
- Sequence work by relative cost of delay divided by relative job size.
- Makes time criticality visible
- Relative scores are not currency
08 · Go deeper
Sources and further reading
- Weighted Shortest Job FirstScaled Agile · Scaled Agile Framework
Relative cost of delay divided by job duration and SAFe factorization.
- The Principles of Product Development Flow — Chapter 1Donald G. Reinertsen · Celeritas Publishing · 2009
Foundational economic reasoning about queues, cost of delay, and product-development flow.