Reducing subjectivity and bias in prioritization is about discussion
This original post is really great. Not only is it well written and has awesome imagery but it takes a great stance on how to solve a lot of these problems.
First, the numbering introduced will definitely provide more detail into why someone ranked something as such. I wonder if you can get that without learning the system with them just giving the reason.
Then you can rank the knowledge around those assumptions in something like Assumption Mapping. This is an exercise I really like.
Second, I've found that feasibility isn't as helpful as it might first seem. It tends to show high complexity or high amounts of unknowns.
You can always break these things down though. It would be valuable to take things with low feasibility and break them up until you can make them feasible and then rank them based on value.
Third, modification I've made to prioritization on a grid is to initially place things based on one value set (or stakeholder) and then draw arrows where it would go when taking into account another value set (or stakeholder). You get an annotated graph that shows both.
In the end, I think all of this is helpful facilitation to have a conversation but someone needs to make a decision based on the information at some point. Setting that as an expectation is valuable for these conversations as well.
