Skip to main content
Paul McAvinchey
Co-founder of Product Collective
Asked a question last year

What are some common methodologies for prioritizing feature development?

Where am I?

In Product Collective Answers you can ask and answer questions and share your experience with others!

Kent J McDonald
Product Manager & Writer

The approach I find most helpful is to consider whether the feature will help make progress toward our target outcome.  If so keep considering it. If not, dump it.

Then from there, consider whether the feature helps to address risks or validate assumptions. If so, you may want to work on it sooner rather than later. It’s also helpful to consider if technical implementation considerations drive doing one feature sooner than others.

This approach works best when you’re considering several features that are all associated with the same general effort.