All related (5)
Navin Ganeshan
Head of Driver Products, Amazon Relay, AmazonMay 31

This is definitely a popular topic of discussion amongst PMs, and probably a heated one at times. This is a good post that covers the most common including RICE, KANO and story-maps.

Personally, I'm less dogmatic about the specific methodology than the discipline in using some framework, even it's as basic as attaching value-to-effort. Most seasoned PMs will concede that they always have to make tweaks or compromises to a standard framework to suit their team or company. So, I would not suggest looking for the best one, but one that works best for your team. Attaching Value-to-Effort, or using story-points are always a great place to start. The Kano model or MosCow model are similar and allow for a more nuanced approach that lets you distinguish between must-haves and nice-to-haves, and help you calibrate how much to invest in back-end scaling which may not be as noticable.   

But always take into account what stage of evolution your product is in, and the extent of data that have to make prioritiation decisions. Your approach is necessarily diffrerent when launching a new product vs evolving one that is several generations old.  

Lisa Dziuba
Head of Product Marketing, LottieFiles | Formerly WeLoveNoCode (made $3.6M ARR), Abstract, Flawless App (sold)August 11

Product prioritization is the art of choosing the right features to develop, in the correct order at the opportune time. It balances the importance of features alongside their complexity and the end value they will deliver. The main idea of prioritization in Product Management is to maximize business results with the available resources. 

Despite all difficulties with feature prioritization, you can get it right using one of the popular frameworks. Consider them a way to structure your thinking process, keep focus and stay on course. The job of the Product Owner leading this process is to pick the proper framework for the company’s needs. I used and worked with those prioritization methodologies:

1. RICE Method

2. Impact–Effort Matrix
3. Feasibility, Desirability, and Viability Scorecard
4. Weighted Scoring Prioritization
5. MoSCoW Analysis
6. Cost of Delay

I shared my practical learning of using those prioritization models with a detailed guide to every framework + many practical examples of how it looks in practice. I hope, it will help your prioritization tasks!

Vasanth Arunachalam
Director, Technical Program Management, Meta | Formerly Microsoft
It could be a combination of any of these things - * Look at data (dashboards, customer feedback channels, internal partner team feedback) to check progress (on product success, platform performance) -Take any actions necessary (filing bugs, resolving a SEV) * Supporting your cross functional team to deliver on roadmap projects -Brainstorm product and technical solutions. -Sprints, design reviews, code reviews -Removing blockers * Look at data to proactively surface opportunities, hot spots, technical bottlenecks etc * 360 communications often tailored meticulously fo...
Navin Ganeshan
Head of Driver Products, Amazon Relay, Amazon
(Reposting this from a related question)  A technical product manager at Amazon is generally referred to as a Product-Manager-Technical (PM-T). A PMT can have ownership over a product, a functional area or even a program, but their primary focus is on formulating the vision, the strategy and roadmap for that area. They are also ultimately responsible for the end metrics of adoption, quality and effectiveness of the features they deliver. They are also the primary customer champions synthesizing their current pain-points, as well as anticipating future needs. They develop concept document...
Devika Nair
Director of Product, Oracle Cloud Infrastructure, Oracle
In my opinion, you can be successful in any role by not having the expertise if you recognize it and are willing to learn. The product manager is generally not the most technically advanced person on the team, but they bring in other expertise and experience to the team (e.g., customer data, market insights, etc). What has helped me is identifying key experts in the organization and leaning into them. I've usually not found a single technically "advanced" person on any of my teams. Different members of the team might have expertise in different areas. PMs with the expertise to identify the...