I really recommend to check GIST [1] as a replacement for pure roadmaps. It focuses on goals and some kind of experiments to define what should be implemented s

I really recommend to check GIST [1] as a replacement for pure roadmaps. It focuses on goals and some kind of experiments to define what should be implemented sooner. GIST is as close to scientific approach as we have right now. RICE model might help as well [2] However, being 100% honest, I tried all the models above and they did not stick to me. I'm playing Product Manager role for 16 years already and rely on customers feedback + intuition. When you have deep experience in the domain, you internalize many models and your neural network in the brain quite often just makes the right decisions. Don't decide quickly though, rely on your "slow" subsystem, decide as late as possible (and collect evidence). Another trivial observation is that customers almost always ask you about some kind of solution. They rarely provide real problems. PM job is to dig into problems as deep as possible and then find a solution. In many cases solution is completely different from what customers asked. In some cases problem can be solved without new features. [1] https://medium.com/@itamargilad/why-i-stopped-using-product-roadmaps-and-switched-to-gist-planning-3b7f54e271d1 https://medium.com/@itamargilad/why-i-stopped-using-product-... [2] https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/ https://www.intercom.com/blog/rice-simple-prioritization-for...