Prioritization tools

Prioritization is essential in product management because resources are always limited, and you want to ensure you are delivering constant value for customers in a way that is viable for the business. Without clear prioritization, effort gets scattered, roadmaps lose direction, and opportunities slip through the cracks. It’s the discipline that turns endless possibilities into meaningful progress.

Weighted Shortest Job First

The Weighted Shortest Job First (WSJF) framework is a prioritization model that helps teams determine which features or initiatives to work on first by calculating a relative value based on several key metrics.

To use WSJF, first identify four key components: Business Value, Customer Value, Opportunity Enablement Value, Urgency, or any other value you deem relevant for your business. The sum of these values equals the Cost of Delay. Then the Job Size indicates how much effort/complexity a given feature has. Calculate the WSJF score by dividing the Cost of Delay components by the Job Size. The items with the highest WSJF scores should be prioritized first, as they deliver the most value relative to the effort required. This approach ensures teams focus on delivering maximum economic benefit in the shortest possible time.

How to use WSJF

1. Start by defining the value/parameters that are relevant for your business (Customer Value, Urgency, etc.).

2. Add estimations for each value, so you can calculate the cost of delay (impact) of a given feature.

   Recommendation: Using Fibonacci numbers (1, 2, 3, 5, 8, 13, …) in WSJF scoring is a hack borrowed from agile estimation. The idea is that as things get bigger and fuzzier, your certainty drops—so the gap between options should widen. Fibonacci doesn’t make WSJF mathematically more accurate; it makes the conversation sharper and the decisions faster. The truth is, estimation has never been about the exact number. It’s about sparking the right conversations.

   That’s why Fibonacci helps:

   • The gaps match how uncertainty grows as work gets bigger.
   • It keeps teams from endless debates like “Is this a 3 or a 4?”
   • And it shifts focus back to understanding the work, not chasing precision.

3. Calculate the effort (size) of a given feature. You may want to have the software engineer team in the conversation to try to be fair with these effort estimations.

4. Then divide the Cost of Delay by the Size to get the WSJF value. The higher the WSJF value, the more value it indicates relative to effort.

<aside> 🐦

Pro Tip: When running a WSJF session with stakeholders, kick off with a feature everyone understands. Use it as a baseline so the team has a clear reference point—this makes scoring the rest faster, fairer, and far less subjective.

</aside>

WSJF framework

Combining 2 frameworks - WSJF & Impact-Effort Matrix

The WSJF’s "Cost of Delay" can inform the "Impact/Value" axis, while "Size" can inform the "Effort" axis on the Impact-Effort matrix. Therefore, you could use WSJF-calculated values to populate a more nuanced or data-driven Impact-Effort matrix—for example, plotting each initiative where the y-axis is "Cost of Delay" and the x-axis is "Job Size." This would make your Impact-Effort matrix more rigorous, leveraging WSJF’s analysis.

Impact-Effort Matrix

The Impact-Effort Matrix is a prioritization tool that helps teams decide which tasks to focus on by categorizing them based on the level of impact they deliver versus the effort required to implement them.

The matrix is divided into four quadrants:

• High Impact, Low Effort (Quick Wins): These items should be your top priority as they provide significant value with minimal investment.
• High Impact, High Effort (Big Projects): These initiatives require careful planning but can deliver substantial value.
• Low Impact, Low Effort (Fill-In Jobs): These tasks are easy to complete but don't add much value. Do them if you have spare capacity.
• Low Impact, High Effort (Time Wasters): These items should generally be avoided or eliminated as they consume resources without delivering proportional value.

How to use the Impact-Effort Matrix

1. This template automatically plots features on the matrix using Impact (cost of delay) and effort (size) from the WSJF table.
2. Seeing the features on a matrix is a view that can help people make better decisions by visualizing the work to be done in each quadrant.
3. Important to highlight that prioritization frameworks should not decide on behalf of the team/stakeholders involved, but should serve as support for better, more informed decisions

Impact-Effort Matrix

<aside> 🆙

Quick Wins (high impact & low effort)

Untitled

</aside>

<aside> 🏗️

Big Projects (high impact & high effort)

Untitled

</aside>

<aside> ⛳

Fill-in Jobs (low impact & low effort)

Untitled

</aside>

<aside> 🗑️

Time Wasters (low impact & high effort)

Untitled

</aside>

Untitled