Weighted Shortest Job First (WSJF): Formula, Examples, and Best Practices

What is Weighted Shortest Job First?

Weighted Shortest Job First is a prioritisation method often used in product and engineering planning. It favors work that creates high economic impact quickly.

WSJF formula

WSJF = Cost of Delay / Job Size

Higher WSJF scores should generally be prioritised first, because they represent more value per unit of effort.

WSJF components explained

• Cost of Delay: economic impact of not doing the work now.
• Business value: expected customer or commercial upside.
• Time criticality: how quickly value decays with delay.
• Risk reduction or opportunity enablement: value of reducing uncertainty or unlocking future work.
• Job size: relative effort or duration to deliver.

WSJF example

Initiative A has Cost of Delay 24 and Job Size 6, so WSJF is 4. Initiative B has Cost of Delay 18 and Job Size 3, so WSJF is 6. Even though A has a higher raw delay cost, B should usually be done first because value arrives faster.

Common WSJF mistakes

• Using inconsistent effort sizing across teams.
• Confusing urgency with business value.
• Not refreshing scores as context changes.
• Treating WSJF as a final answer without stakeholder review.

How DecisionGrid improves WSJF at scale

DecisionGrid complements WSJF by turning economic sequencing logic into an always-updated portfolio view. Teams can bring WSJF-informed initiatives into the platform and use live project scoring to keep execution order current as data changes.

• Capture inputs that matter for sequencing, including budget, expected revenue, complexity, and timeline.
• Use built-in risk prediction and model confidence for each active project.
• Automatically re-rank active projects using the app score model (50% normalized ROI, 50% risk weight).