#Problem management priority matrix how to

This could be for legal reasons, safety concerns, or business reasons. ‘Must have’ represents the features that you should absolutely not launch without. Let’s take a closer look at what these categories really mean: Must have The name is an acronym of four prioritization categories: Must have, Should have, Could have, and Won’t have. It’s a particularly useful tool for communicating to stakeholders what you’re working on and why. Known as the MoSCoW Prioritization Technique or MoSCoW Analysis, MoSCoW is a method used to easily categorize what’s important and what’s not. Join Product School's private Slack community and network with over 100,000 PMs. We’ll then show you some A+ advice on the prioritization process of seasoned Product Managers.ĭiscover the World's Largest Product Management Community Here, we’ll show you the top three prioritization techniques that all Product Managers should know MoSCow, RICE, and Kano. They’ve built great things, and built even greater prioritization frameworks! Luckily, a whole community of Product experts have come before you. It can feel daunting, but for a successful launch, it has to be done.

Prioritization is absolutely essential for Product Teams and product development. Finally, your Data Analyst is convinced that Feature B is completely unnecessary and that users are crying out for Feature C. But a key stakeholder is gently suggesting that Feature B be included in V1. In Product, prioritization is on a whole other level! The engineers are telling you that Feature A will be really cool and will take you to the next level. You choose which task to work on first, which deadline needs to be met above all others, and what order to answer your emails in.

#Problem management priority matrix how to

If you’ve transitioned to product from another discipline, or have spent years working in any office-based role, you might already think you know how to do it. One of the most challenging aspects of Product Management is prioritization.