As a Product Manager or Product Owner, you are often facing difficult choices when prioritizing features for your product. Should you target a specific demographic, or the ones that make the most sense to you, or the regulatory requirements? What priority should technical improvements have, such as refactoring, changing the architecture, or improving automation in development?
Balancing these different types of requirements is particularly difficult if you’re just starting in the role, if you’re working with multiple teams, or if the technical constraints weigh heavy on your development time. While there is no perfect way to prioritize, it’s useful to know a number of techniques that help you analyze, make decisions, and communicate them in a way that is clear and accepted by stakeholders and the teams.