What is your end to end process for prioritizing features on your roadmap?

Generally the process I follow to prioritize features is: Aggregating feedback: from customers, users, and stakeholders through various avenues Review User metrics to help identify pain points, feature requests etc. Align feature prioritization with long term Vision/Strategy (This needs to be defined ahead of the prioritization exercise) Assess the potential impact and value of each feature using factors such as customer metrics, market trends, competitive analysis, and alignment with company go ...Read More

The simple answer is to prioritize the features that will bring your customers the most value and consequently drive the most revenue for your business/organization. Unfortunately, it's rarely that straightforward, particularly if you aren't working on customer facing features. Here are the four steps for prioritization: Solicit input from your partners: It's important to identify what your design, engineering, data science, product marketing, and other cross-functional partners find important. ...Read More

I could give a really detailed answer about my process, but I don't really have one. I've found that my "prioritization process" is actually pretty simple and is about attempting to answer the questions I listed out below (will repeat them here): What, fundamentally is the problem this idea is meant to solve? How worth it is solving that problem vs. others I know about? Does solving this problem create opportunities or risks in any form that I should think about? Is this a problem I need to solv ...Read More

Prioritization is the most important role of the product management function, and there seems to be a general sense that there is one major moment of prioritization that culminates in a completed roadmap. The reality is that the exercise in prioritization starts much earlier. Like many organizations, we are resource-constrained and have many more ideas than we can realistically action. Therefore, prioritization is one of the most important things we can do to help the company succeed. This means ...Read More

Here's a rough e2e prioritization process: Set context with the team and your stakeholders on the overall business, product stage and strategy, key problems, behavioral data, and user research. Establish roadmap themes based on these key problems, needs, and opportunities. Engage everyone in brainstorming solutions for these important problems and opportunities. De-duplicate ideas and group brainstormed ideas/solutions together. Arrange projects ideas into an ordered list. Sort the list by both ...Read More

Here are the steps I take for end to end feature prioritization - Talk to various stakeholders (sync and async) and collect a list of features from them with the following details - Impact, expected ETA of the request, mapping with business goals Talk to the engineering team and get a list of the foundational/tech debt features which they want to implement to improve efficiency of the team and create a modern tech stack Align the business with the capacity split between business features and fou ...Read More

At Carta, our end-to-end process for prioritizing features is rooted in strategic alignment, user-centricity, collaboration, and data-driven decision-making. For simplicity, you can think of the process in the following way: Align: Our process begins by aligning the team's product strategy with the overarching business objectives, ensuring that every feature we prioritize contributes directly to the company's strategic goals. During this process, we gather valuable insights from various sources, ...Read More