The framework(s) call out some interesting considerations like the importance of constraints and building dependable systems for prioritization within a project. Brandon separates the approach between prioritization of projects vs. This post by Brandon Chu is definitely worth a read. Mariano Capezzani has developed a 4-step framework that starts with the critical first step of “Know the context.” Check out this article from Product School with the rundown. Soni shares their approach for both cases and a helpful decision flow. In other cases, it is accidental or is realized later after the work was done. In one case, the tech debt arises from an intentional decision. Soni points out that there are two types of tech debt. Vishal Soni wrote up their approach to tech debt in this practical tech debt prioritization guide. Check out these 6 steps from the Chief Product Officer at Crowd Cow and former Director at Amazon. This old Quora response by Ian McAllister has been shared a lot in the product management community. Vision, Impact, Confidence, Time, Onboard, Risk, You. Suyash Bharadwaj shared the VICTORY framework in April 2022 to help product people ensure they are working on the right things. GRIDS stands for Gather and group like ideas, Review and Respond, Investigate, Decide, Share. Read the full walkthrough at Product First.

Kate Horowitz offers up this 5-step framework for building product roadmaps and work prioritization. Throughout his writeup, Russell suggests various measurements in these categories with visuals of how he might lay out the spreadsheet calculations. The acronym refers to Affordability, Effectiveness, Impact, Optionality, Uncertainty. This isn’t a scoring framework, but something like this could probably be a good foundation for building a custom score for your own needs. Russell McGuire writes about this loose framework of different types of criteria. These are examples where PMs have shared their workflows and mindset going into prioritization.

Checkit certainty software