The world does not need another prioritization framework. However, one thing that always bugs me about (many) prioritization conversations is that teams often leave out the expected value curve of the work. “Level of effort” (or complexity, even) has never cut it for me because it assumes one fixed effort point. I am more concerned about the effort/time to impact curve because that (to me) more accurately represents product development.
Awesome post and analysis. Thank you 🙇
You nailed it.