User generic
Folding Burritos

How to Prioritize (By Ex-Flipkart PM)

A majority of product managers find prioritization their biggest challenge at work. Knowing that it can set your product up for success or failure; how do you build, rank and prioritize a product roadmap with multiple stakeholders, limited resources and missing data to back decisions. 

Key Takeaways: – 1. Asking the right questions; should you build a new feature or improve an existing one?

2. Asking the right questions; should you build a new feature or improve an existing one?

3. Managing multiple feature requests from customers, investors and internal teams

4. Visualizing and evangelizing roadmaps better for stakeholder management

5. Aligning and motivating teams to collaborate on the roadmap

User generic
Product School of Francisco

How to prioritize features

A quick brief video teaching you a better method of feature prioritization than the most used  by many Product Managers. But is it really serving your purpose well? We think not, so go ahead and see if this one works out you and your Company. The new approach shown focuses on giving weightage to different feature requests based on following factors: 

  • % Users Affected
  • Easy to Implement
  • Retention Value
  • Conversion Value
User generic

Setting Priority in 5 minutes

Knowing which steps will get you the most bang for your buck, effort-wise, will help you organize your teams so they never reach Ikea-levels of frustration and so that you end up with the best possible product. It will allow you to structure your workflow so that you can estimate how long it’s going to take, set a schedule, and plan accordingly.

A quick graphical approach using Impact and Effort metrics to figure out prioritization order of tasks based on their position on graph. While tasks with maximum impact & minimum efforts lies on top pf priority, ones involving high impact & effort  need to be planned before time.

User generic
One Month

Kano Model for Prioritization

The video covers, explanation of Requirement Categorization as a prioritization exercise: • Threshold/ Must Have Requirements: The absence of these features affects customers’ satisfaction. If these featured are not present, customers are dissatisfied and they can walk out from your services. But their presence does not increase customer satisfaction after a mid-point as these are the basic requirements that a user expects to be there.

• Linear Requirements: These are the features: more we provide, the more satisfied our customers become. There is a proportional relationship between the presence of these requirements and the customer satisfaction.

• Exciter Requirements: These are those features which customers don’t even know they want. If we provide them, they feel delighted

User generic
iZenBridge Consulting Pvt Ltd

MoSCoW Model of Prioritization

The video covers, explanation of four Requirement Categorization: o Must Have Features: Must Have features forms the minimum scope for the product to be useful and must be added before the product is launched. o Should Have Features: The Should have features are not essential for the product launching but gives high value to the user and considered to be important. A good mix of Must Have and Should Have featured is a good idea where all the Must Have features are available. The priority of ‘Should Have’ features is determined from the Must Have Features. For example, some Must Have features need Should Have features to work well.

o Could Have Features: These are nice to have features, and these will be the first features to be removed from the scope if there is time or money constraints. o Won’t Have Features: These features requested initially but excluded from the current scope and may be included in a future phase of development

User generic
iZenBridge Consulting Pvt Ltd

Leave a Reply

Your email address will not be published. Required fields are marked *