Prioritization, or more specifically deciding what you will and will not build, is a key decision teams make on a regular basis.
Yet many teams use ineffective approaches to prioritization that add more confusion than clarity, and leave teams focusing on who screams loudest.
In this lightning talk, Kent McDonald shares some key prioritization tips that help your team ensure you’re working on the right thing.
To find out more about prioritization in different contexts, subscribe to InsideProduct.
An Overview on Priority
Some things to consider the next time you need to do a prioritization exercise on your product.
Epic Portfolio Prioritization
My answer to a question about prioritization frameworks, and prioritizing a set of epics.
Prioritizing when rebuilding a product
When you prioritize a product replacement, you decide what features your product will and will not have. Then for each feature that you include, you dive into details how you’ll deliver.
Priority Decisions for a New Product
Prioritization for a new product is tricky because you don’t have any history to tell you if people are interested in your product and what makes them interested.
Prioritizing your product optimizations
Once you hit product market fit, your product moves into the growth stage of the product life cycle and you switch into product optimization. At this point, you experiment to prioritize.
Prioritizing during feature refinement
Feature refinement provides a way to do that in a way that allows you consider options and focus on the essential aspects of the feature and discard the aspects that aren’t completely necessary.
Prioritizing a bunch of stakeholder requests
The key to prioritizing stakeholder requests is to balance value, viability, feasibility, and usability. You need to consider any potential impact to customers and the overall business.