Linear teams move fast. The tool is built for speed, with keyboard shortcuts, auto-assignments, and cycles that keep work flowing. But moving fast in the wrong direction is worse than moving slowly in the right one. WSJF (Weighted Shortest Job First) helps you pick the right work before you start executing.
This guide shows how to use WSJF scoring alongside Linear without adding process overhead.
What WSJF Measures
WSJF calculates the cost of delay divided by job duration. The formula: (Business Value + Time Criticality + Risk Reduction) / Job Size. Higher scores mean you should do the work sooner.
The key insight is "cost of delay." Not all features decay at the same rate. A competitive response loses value every week you wait. A performance fix is urgent now but irrelevant after the migration. WSJF captures that time sensitivity.
Why Linear Teams Need WSJF
Linear's priority field (Urgent, High, Medium, Low, No priority) is better than most tools. But it still forces subjective labels. Two PMs will set different priorities for the same issue.
WSJF adds math to the conversation. Instead of arguing "Is this High or Medium?", you discuss "What is the cost of delay? How long will it take?" Those are concrete questions with concrete answers.
Linear teams often run in cycles (their version of sprints). WSJF is perfect for cycle planning because it accounts for job size. A high-value, small item beats a high-value, large item.
Setting Up WSJF with Linear
Linear does not have custom number fields like Jira. Your workflow needs to account for that.
Step 1: Score externally. Open the WSJF Calculator and enter your cycle candidates. Score business value, time criticality, and risk reduction on a 1-10 scale. Enter job size as estimated effort.
Step 2: Add scores to Linear. Use Linear labels to create score buckets: "WSJF-High" (score > 5), "WSJF-Medium" (2-5), "WSJF-Low" (< 2). Apply these labels to scored issues.
Step 3: Filter and plan. Create a Linear view filtered by WSJF labels, sorted by priority. Use this view for cycle planning.
Step 4: Review after each cycle. Time criticality changes. An item scored low last cycle might be urgent now. Re-score the top candidates before each cycle.
WSJF vs RICE for Linear Teams
RICE focuses on reach and impact. It answers "How many users benefit and by how much?" WSJF focuses on time sensitivity. It answers "What do we lose by waiting?"
Use RICE when you are optimizing for growth and need to maximize user impact. Use WSJF when you are balancing competing deadlines, competitive pressures, or technical risks.
Many teams use both. RICE for quarterly roadmap planning, WSJF for cycle-level prioritization. See the comparison guide for more on choosing the right framework.
Tips for Linear-Specific Workflows
Use Linear's project grouping to separate scored items by product area. Score within each project, then compare top items across projects for the final cycle plan.
Linear's triage queue is a natural entry point for WSJF. Before moving an issue out of triage, ask: "Does this have a cost of delay?" If yes, score it. If no, it can wait.
For teams using Linear's roadmap feature, WSJF scores help sequence initiatives. The roadmap shows what you plan to build. WSJF determines the order.
Read the feature prioritization guide for a broader look at fitting scoring into your product process. The value-effort matrix is a faster alternative when you need a quick sort without full WSJF scoring.