Revised Product Prioritization Framework

Given the recent post from @puniaviision highlighting constraints. (Engineering & Products constraints). I believe it would make sense to reconsider the product prioritization weightings, specifically around operational & technical commitments.

If we assume a max score across the entire proposed rubric, technical and operational commitments only contribute to 24% of the entire scoring methodology. To me, this seems too low.

While I am confident we will be able to expand technical resources, I fear technically complex products will get pushed through decision gates potentially constraining future growth (due to engineering/product bandwidth consumption) and potentially damaging relationships with prospective methodologies. (My language is too harsh, but just making a point).

I don’t have a good answer to the appropriate weighting, however, think it makes the most sense to source community feedback on this first. I view the product prioritization framework as the first line of defense/offense for the Coop and really a regulator to future growth. @Metfanmike knows I have done a little work around analyzing the current framework and would like to layer in this line of thought before sharing it with the group.

@catjam, @Metfanmike & @jdcook – what are your thoughts here?

5 Likes