← Glossary · Methodology

WSJF (Weighted Shortest Job First)

WSJF (Weighted Shortest Job First) is a SAFe prioritization formula that ranks work items by dividing their Cost of Delay — the sum of business value, time criticality, and risk reduction or opportunity enablement — by job duration (size or effort). Items with the highest WSJF score deliver the most value in the least time and should be sequenced first.

How WSJF Works

The WSJF formula is: WSJF = Cost of Delay ÷ Job Duration. Cost of Delay is itself a composite of three factors scored on a relative scale (often Fibonacci): user-business value, time criticality (how urgency changes the economic value), and risk reduction or opportunity enablement (RR/OE). Dividing that sum by the estimated job size yields a prioritization score — not a measure of absolute value, but of value-per-unit-of-time.

Because WSJF is ratio-based, a small, urgent item that reduces a significant risk can outrank a high-value feature that takes months to build. This makes it especially effective in SAFe, where WSJF is applied at both the portfolio level (sequencing epics) and the program level (sequencing features during PI planning) — wherever teams need to rank a shared backlog across multiple sprints rather than single user stories.

Scoring WSJF in Practice

Teams estimate each dimension relatively — not in dollars or hours, but by comparing items against a reference item. A common workshop technique is to pick a mid-sized item, assign it a score of 8 on each dimension, then vote on whether other items are higher or lower. The team divides the summed Cost of Delay by the job-size estimate (story points or T-shirt size mapped to numbers) and ranks the resulting scores.

The most common mistake is treating WSJF scores as precise calculations rather than structured conversation aids. The real value is forcing a team to explicitly discuss time criticality and risk alongside business value — dimensions that informal gut-feel prioritization routinely underweights. A product operating system that surfaces connected data — revenue attached to accounts, open risks linked to features, feedback volume by request — gives those WSJF conversations a factual grounding instead of relying on gut feel alone.

WSJF vs Other Prioritization Models

WSJF differs from RICE (Reach, Impact, Confidence, Effort) in two key ways: it explicitly models time criticality and opportunity cost, and it originates from Lean-Agile / SAFe rather than growth-product culture. RICE suits feature-level decisions where reach data is available; WSJF suits program-level sequencing where Cost of Delay — including the cost of not doing something now — is the dominant variable.

ICE scoring (Impact, Confidence, Ease) is the lightest-weight alternative, best for early-stage teams moving fast without rich data. WSJF sits between ICE and a full economic framework: more rigorous than ICE, more opinionated than a custom weighted model, and tightly integrated into SAFe's PI planning cadence.

FAQ

WSJF (Weighted Shortest Job First) — questions

What is the WSJF formula?

WSJF = Cost of Delay ÷ Job Duration. Cost of Delay = User-Business Value + Time Criticality + Risk Reduction or Opportunity Enablement (RR/OE). All three Cost of Delay components are scored on a relative scale and summed before dividing by job size.

What scale should I use for WSJF scoring?

Most SAFe practitioners use a modified Fibonacci sequence (1, 2, 3, 5, 8, 13, 20) for relative estimation. The exact scale matters less than consistency — pick a reference item, assign it a middle value on each dimension, and score everything else relative to it.

When should I use WSJF instead of RICE?

Use WSJF when time urgency and risk reduction are significant drivers — common at the program or portfolio level in SAFe. Use RICE when you have reliable reach and conversion data and are prioritizing at the feature or experiment level.

What makes a good Cost of Delay estimate?

A good Cost of Delay estimate is grounded in real signals: customer revenue at risk, contract commitments with dates, competitive threats with known timelines, and quantified risk exposure. The more connected your product data — revenue, feedback volume, open risks — the more defensible your Cost of Delay numbers become.

Related terms

See wsjf (weighted shortest job first) on one spine.

AIOProductOS puts your customers, revenue, feedback and product work on a single shared record — so concepts like this stop being theory and start being a query against your own data. Connectors included, no per-connector fee; flat plans from $199/mo, every module included. Every plan starts with a 14-day onboarding runway on your own data.