The Product Frameworks Compendium. 1. Prioritization Frameworks

 Those 9 frameworks will allow you to prioritize your tasks, initiatives, and opportunities better. Ultimately leading to better outcomes.

a. Eisenhower Matrix

The template is handy for prioritizing your tasks.

Free template (Miro): https://miro.com/templates/eisenhower-matrix/

b. Impact vs. Effort (2x2)

You can use this template for prioritizing tasks and initiatives.

Free template (Miro): https://miro.com/templates/impact-effort-matrix/

c. Risk vs. Reward

This template is handy for prioritizing initiatives you want to take.

Free template (PPTX): open Google Slides

d. Opportunity Score by Dan Olsen

Use this framework to prioritize opportunities (customer problems, needs, desires). I find it much more straightforward and intuitive than the one from Jobs-to-be-Done. And I verified that where it matters the most, it gives similar results:

My introduction (PDF): 

The official Dan Olsen's template (PPTX): 

e. Kano Model

Kano Model was initially developed to prioritize features. You might find it helpful. But remember, you want to prioritize problems, not solutions.

Free template (Miro): https://miro.com/templates/kano-model/

f. Weighted Decision

This framework is helpful when prioritizing any decision with many factors to consider. Each factor has an assigned weight. It’s self-explanatory:

Free template with formulas (XLSX): open Google Sheets

g. (R)ICE Framework

ICE Framework is useful for prioritizing initiatives and ideas. I like it because it considers not only the value but also risk and economic factors.

ICE stands for:

• Impact

• Confidence

• Ease

Another version, RICE, splits Impact into two separate factors: Reach and Impact.

ICE template (XLSX):

RICE template

h. MoSCoW Method

MoSCoW involves dividing requirements into 4 separate buckets:

• Must-have

• Should-have

• Could-have

• Won't-have

You don’t need a template, as this is just an additional property you can add to your backlog (e.g., in Jira).

I don’t really like it because the MoSCoW is commonly used in project management when those priorities are set by the customer. As you know, empowered product teams get goals and are held accountable for the outcomes, not the features.

i. Weighted Shortest Job First (WSJF)

WSJF is part of SAFe, a methodology that claims to be Agile and uses many “modern terms,” but deep inside, can’t stop obsessing over controlling people and implementing heavy processes.

Being part of SAFe is not the only issue with WSJF. Look at this formula:

WSJF = (user/business value + time criticality + (risk reduction (RR) + opportunity enablement (OE) value) ) / job size

You will do much better using Dan Olsen’s Opportunity Score formula and then accounting for the estimated cost of implementing the Idea.

Use logic if needed (e.g., a black swan event) instead of sticking to that complex formula and speculating about the other parameters.

PAWEŁ HURYN