![]() We’ve compiled dozens of proven product management frameworks to help you do just that. ![]() That’s why you have to learn to prioritize your work, optimize your cross-functional team’s workflows, and know-how to quickly assess whether or not an initiative is worth your company’s time and budget. Tune into our webinar below to learn more about supercharging your product roadmap with customer feedback.Īs a product manager (PM), how do you decide what to work on next? How do you determine if an initiative is worth pursuing in the first place? In most cases, nobody is going to hand you a written plan guiding you step-by-step to complete your initiative. It prevents you from advancing the product toward the agreed-upon vision. If you’re always reacting to everything that comes across your desk, it leads to a scattershot approach of putting out fires. Prioritization should be rooted in taking proactive action to execute the product strategy. It’s not that feedback offers no value, but it should be informative rather than prescriptive. That’s why a reactive approach to prioritization is the wrong way to pick things. Since products ideally have lots of customers, products need to create solutions that serve the needs of lots of people. But they’re only seeing things from a limited perspective and bring their baggage, preferences, and small sample size of experiences to the table. Similarly, customers don’t always know how to express exactly what they want.Ĭustomers have problems, and they’re quick to tell you the solution to their problem. Is that the same thing as what they need? Of course not. But all of it needs to be taken with a grain of salt. It offers product managers insight into what people value, what they dislike, and what they want. Input from customers, partners, stakeholders, and advisors is a gift. How to balance feedback with real product needs If you try to do too much all at once, you’re doing a disservice to your customers, your team, and your stakeholders. Only try to solve the essential problem with the minimum amount of effort. If you find yourself with too many priorities, you need to pare things back. It’s a huge bonus if it also delights the customer, but without solving any problems, it’s pretty hard to delight them for long. This process requires research and understanding of the potential users as much as possible to be sure it’s solving that problem. Therefore, you must find the subset of possible features that will accomplish that goal. Without that, there’s no point in even bothering. ![]() Minimum Viable Products (MVPs) must solve a real problem for the user. Since there’s no track record to look back at or current users to talk to, there’s plenty of room for opinions to dominate whatever data you have.ĭo you try to wow people with something snazzy? Do you pack it with features so it can appeal to a broader audience? Or do you make sure it does one thing well? Narrowing down what’s required for the initial version of a product can be tricky. What’s prioritized for version 1.0 of the product?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |