Your team is split on prioritizing feature requests. How do you decide which ones to tackle first?

You need to look at Impact, Effort and vision I have a four question framework to help me in this scenario - 1. What is the business value which can be created via this change and how fast can we see it? 2. What is the user value which can be created via this change and how fast can we see it? 3. Why should we build right now? 4. Is there any detrimal effect if we defer/deprioritise this over the other?

Conducting thorough stakeholder interviews and using tools like user personas and journey maps can provide deeper insights into the true needs behind feature requests. Regularly involving cross-functional teams in discussions ensures that all perspectives are considered, leading to more balanced and effective prioritization. Additionally, documenting these needs and the rationale behind prioritization decisions can help maintain transparency and alignment throughout the project lifecycle.

Begin by thoroughly understanding the needs behind each feature request. Engage with all stakeholders, including customers, sales teams, and developers, to gather comprehensive insights. Understanding the underlying problems or opportunities that each feature aims to address will help in making informed decisions that align with user needs and product strategy.

First, gather a clear understanding of the needs driving each feature request. This involves identifying who the stakeholders are and what their specific requirements entail. Conducting stakeholder interviews and surveys can provide valuable insights into the importance and urgency of each request.

1. Long-term: Does it align with company’s larger mid-long term strategy? If no, the effort to build will be waste later. 2. Effort v/s Impact (business): One month of work generating USD 1m monthly incremental topline is better than six months to drive USD 5m annually (assuming similar customer impact) 3. Effort v/s Impact (customer): Which of the missing features is driving customers away and from which segment? Solve for the high-risk ones first. 4. Short-term: Is there a feature hindering larger organisation’s goals (modernisation/migrations)? You should solve for that dying legacy platform first (since it is likely going to bring down a larger flow and hence impact customers in their journey)

Focus on understanding user needs and the potential impact of each feature. Consider factors like user satisfaction, market demand, and business goals. Use data to identify features that improve user experience and offer a competitive edge.

From my experiences at IRCTC and Puma, I've learned to assess the potential impact of feature requests by evaluating user engagement, product performance, and business objectives. Prioritizing features with significant benefits ensures our decisions support both immediate needs and future growth.

Next, evaluate the potential impact of each feature on your product and users. Consider factors such as user satisfaction, market demand, and alignment with business goals. Features that significantly enhance user experience or offer a competitive advantage should be given higher priority. Utilize data analytics to support your assessments with quantitative evidence.

When working at Freshworks, I came to understand what a particular feature would mean to a customer and to the product as a whole. To assess impact, there were a lot of trackers, attaching support tickets, call recordings, emails and any other document related to a request of a feature. The product team will assess the impact of every such tracker incessantly and will also analyze factors such as engagement, revenue and so on. Based on the impact analysis, the feature would released in subsequent release cycles.

It's not just about building cool features, it's about making sure they actually move the needle for our users and the business.

Another factor we consider is how a feature fits into our overall roadmap. Sometimes, a smaller feature that seems less important now can actually pave the way for a bigger, more impactful feature later on. It's about thinking ahead and making sure our priorities align with our long-term vision.

Assessing the effort required to implement each feature is crucial. For example, at Google, the team balances the development of high-impact features with quick wins. Some features, like significant algorithm updates, require extensive resources but have a huge impact. Conversely, minor UI improvements might be implemented quickly but offer limited value. By evaluating both impact and effort, Google ensures efficient use of resources and maintains a balanced roadmap. This approach can help your team make informed prioritization decisions.

Assessing the effort required to implement each feature is crucial in prioritization. Consider available resources, including time, budget, and personnel. Some features may offer great value but require substantial effort, potentially delaying other important work. Conversely, quick wins that require minimal effort might be attractive but offer less value. Striking a balance by considering both impact and effort helps determine a feature's feasibility, ensuring effective and strategic decision-making. #ProductManagement #Prioritization #ResourceManagement

Estimate the time and effort needed for development and testing. Consider the availability of team members and other resources.

To decide which feature requests to tackle first, you would evaluate them against the customer needs that were mutually decided upon at the start of the project. This ensures that every effort contributes meaningfully to solving real user problems and advancing the product's objectives. For example, if your strategic goal is to improve user engagement, you would prioritize features that directly enhance interaction or retention rates, aligning with the core needs identified through customer feedback. By focusing on aligning feature requests with both strategic objectives and customer needs, you ensure that each development effort moves towards delivering a better product experience.

It's so easy to get caught up in the day-to-day and lose sight of the big picture. One other way we stay aligned is by having regular "strategy check-ins" with our team. This helps us ensure we're all on the same page and that our individual work is contributing to our overall objectives.

Your product strategy should guide prioritization decisions. For example, Basecamp, a successful but less famous project management tool, consistently evaluates features against their long-term goals. If a feature doesn’t align with their focus on simplicity and user-friendliness, it isn’t pursued. This strategic alignment ensures that every new feature supports Basecamp's vision and enhances the product cohesively. This approach can help your team prioritize features that contribute to your overarching goals.

Aligning with the product strategy is essential for prioritization decisions. Each feature request should be evaluated against the product's roadmap and long-term goals. If a feature doesn't align with the direction you're heading, it might not be worth pursuing, regardless of its individual merits. I prioritize features that support strategic objectives and contribute to the product's overall vision, ensuring we stay on course and achieve our goals. #ProductManagement #StrategicAlignment #VisionDriven

One way to build consensus is to share the available bandwidth in terms of points, say you have 100 points of development bandwidth and each feature has its assigned points against it may be 10 points for feature one, 15 points for feature 2. Let everyone split 100 points against each feature, pick the common features by default and have a discussion for rest of the features, this usually brings a consensus. Every participant also feels valued.

Atlassian, the company behind Jira, ensures all voices are heard by facilitating discussions where team members present their viewpoints and data. By using insights from understanding needs, assessing impact, estimating effort, and aligning with strategy, they reach a mutual agreement on feature priorities. This collaborative approach helps align the team on what’s best for the product, even if compromises are necessary. This method can effectively guide your team through prioritization challenges.

When my team is split on prioritizing feature requests, building consensus is essential. I facilitate discussions where each member can voice their opinions and present their arguments. Using data and insights from understanding needs, assessing impact, estimating effort, and aligning with strategy guides these conversations. The goal is to reach mutual understanding and agreement on what’s best for the product, even if it means making compromises. This approach ensures collaborative and well-informed decisions. #Teamwork #ConsensusBuilding #ProductManagement

In order to foster consensus, team members must be encouraged to participate in open discussions about product priorities. Based on common objectives and the overall benefit of the product, it seeks to come to a consensus. Frameworks such as MoSCoW (Must have, Should have, Could have, Won't have), RICE (Reach, Impact, Confidence, Effort), and the Kano model offer systematic methods for objectively evaluating and ranking feature requests. These frameworks help teams reach consensus by coordinating priorities with strategic objectives.

It's not just about getting everyone to agree, but about making sure everyone feels heard and understands the rationale behind the decisions. We've found that using a simple "weighted scoring" system can be helpful for prioritizing features. Each team member can score features based on their impact, effort, and alignment with strategy. This allows for a more objective way to compare features and reach a consensus, even when opinions differ.

If you have clearly defined OKRs and a feature prioritization framework (RICE, MosCow, etc.), it will minimize prioritization conflicts within the team. Reviewing multi-quarter roadmaps with the larger cross-functional team at a regular cadence should also help build the "buy-in" from all stakeholders, which will reduce prioritization discussions as the team is aware of the long-term plan and how the features align with the objectives. Lastly, be open to feedback during these prioritization discussions, as changing market conditions may necessitate a reassessment of the OKRs and a shift in priorities.

Consider using a Proof of Concept (PoC) for features that were not initially selected, or create an MVP (Minimum Viable Product) version of the feature. This approach allows you to: 1.Avoid keeping stakeholders waiting. 2.Release a small, functional part of the feature in the current sprint. 3.Assess the outcome of this release. 4.Based on the results, decide on the new priority for the feature.

While defining the product strategy, specifically for the regulated markets, it becomes super important to keep the regulatory aspects into focus from the initial stages of product development to ensure product compliance. missed regulation could lead to massive pitfalls and setbacks for product and the overall company

2nd order effects. Some of the decisions are irreversible and can cause tons of headache in terms of tech debt down the line. Make sure you understand how your current decisions can impact your product's future growth.

Assess each feature's potential impact on key metrics such as user satisfaction, revenue, and market competitiveness. Gather data and feedback from users to understand their needs and pain points. Align the features with your product's strategic goals and long-term vision. Consider the development effort required for each feature and the resources available. Facilitate a discussion with your team to weigh the pros and cons of each request, encouraging a consensus-driven decision. This approach ensures that you prioritize features that offer the most significant value and align with your overall strategy.