Product Managers: Prioritize Features Like a Pro

Mastering Product Management: A Guide for Technology Professionals

Are you a product manager struggling to balance user needs, technical feasibility, and business goals? Many product managers in technology face this challenge daily. Is there a better way to prioritize features and deliver successful products?

The life of a product manager is a constant juggling act. We’re expected to be visionaries, strategists, communicators, and, at times, even therapists (dealing with conflicting stakeholder opinions). One of the biggest hurdles? Deciding what to build next. Too often, I see product teams relying on gut feelings or loudest-voice-in-the-room prioritization, which inevitably leads to wasted resources and unmet user needs.

The Problem: Feature Prioritization Paralysis

Imagine this: You’re leading the product development for a new mobile banking app at a fintech startup in Atlanta. Your team has a backlog overflowing with feature requests: biometric login, mobile check deposit, personalized financial advice, budgeting tools, and even a dark mode option. Everyone has an opinion on what’s most important. The CEO wants the “shiny” personalized advice feature to attract investors. The marketing team is pushing for dark mode because “everyone is doing it.” Meanwhile, your developers are concerned about the complexity of biometric login. How do you cut through the noise and determine what to build first?

Without a structured approach, you risk building features that nobody wants, delaying critical functionality, and ultimately, launching a product that fails to gain traction in the competitive Atlanta market. According to a report by the Standish Group ([https://www.standishgroup.com/](https://www.standishgroup.com/)), 31.1% of projects are canceled before completion, and 52.7% of projects will cost 189% of their original estimates. That’s a lot of wasted time and money.

What Went Wrong First: The “Squeaky Wheel” Approach

Early in my career, I fell into the trap of prioritizing features based on whoever complained the loudest. If the sales team kept hounding me about a specific integration, I’d bump it up the list. If a major client threatened to leave unless we implemented a particular feature, I’d cave. This “squeaky wheel” approach felt responsive in the short term, but it was a disaster for long-term product strategy. We ended up with a Frankenstein product – a collection of disparate features that didn’t work together cohesively and didn’t address the core needs of our target users. We were constantly reacting instead of proactively shaping the product.

We even tried a simple voting system where everyone on the team got to rank features. This quickly devolved into a popularity contest, with the most vocal (not necessarily the most insightful) team members swaying the vote. The result? Features that made the loudest people happy, but didn’t move the needle on key metrics like user engagement or conversion rates. We should have focused on mobile app success metrics from the beginning.

The Solution: A Data-Driven Prioritization Framework

The key to effective prioritization is to move away from subjective opinions and towards a data-driven approach. One of the most effective frameworks I’ve found is the RICE scoring model:

• Reach: How many users will this feature impact in a given timeframe (e.g., per quarter)? Estimate the number of users who will interact with the feature.
• Impact: How much will this feature impact users? Use a scale (e.g., 1-5) to represent the level of impact (1 = minimal, 5 = massive).
• Confidence: How confident are you in your reach and impact estimates? Express this as a percentage (e.g., 50% = low confidence, 100% = high confidence).
• Effort: How much effort will it take to build this feature? Estimate the number of person-months required.

To calculate the RICE score, use this formula: (Reach x Impact x Confidence) / Effort. The higher the score, the higher the priority.

Here’s how we applied the RICE framework to the mobile banking app example:

1. Biometric Login:

• Reach: 5,000 users (estimated number of active users per quarter)
• Impact: 4 (high impact on security and convenience)
• Confidence: 90% (based on market research and competitor analysis)
• Effort: 3 person-months
• RICE Score: (5000 x 4 x 0.9) / 3 = 6000

1. Mobile Check Deposit:

• Reach: 3,000 users
• Impact: 5 (critical for many users)
• Confidence: 95%
• Effort: 2 person-months
• RICE Score: (3000 x 5 x 0.95) / 2 = 7125

1. Personalized Financial Advice:

• Reach: 1,000 users (initially, as it requires user data and onboarding)
• Impact: 5 (potentially high, but uncertain)
• Confidence: 60% (due to unproven market demand)
• Effort: 4 person-months
• RICE Score: (1000 x 5 x 0.6) / 4 = 750

1. Budgeting Tools:

• Reach: 4,000 users
• Impact: 3 (helpful for financial management)
• Confidence: 80%
• Effort: 2.5 person-months
• RICE Score: (4000 x 3 x 0.8) / 2.5 = 3840

1. Dark Mode:

• Reach: 6,000 users
• Impact: 2 (mostly aesthetic)
• Confidence: 90%
• Effort: 1 person-month
• RICE Score: (6000 x 2 x 0.9) / 1 = 10800

Based on the RICE scores, Dark Mode clearly emerged as the top priority, followed by Mobile Check Deposit. While the CEO favored Personalized Financial Advice, the data showed it had lower reach, confidence, and a higher effort, making it a lower priority at this stage.

This is where a tool like Jira or Asana comes in handy. Create a project for each feature and track the RICE score, tasks, and timelines.

Building a Product Roadmap

Once you’ve prioritized your features, the next step is to create a product roadmap. This is a visual representation of your product strategy, outlining the features you plan to build and when. Your roadmap should be a living document, updated regularly to reflect changing market conditions and user feedback.

I recommend using a tool like Productboard or Aha! to create and manage your roadmap. These tools allow you to visualize your product strategy, track progress, and communicate your plans to stakeholders.

Your roadmap should include:

• Themes: High-level strategic goals (e.g., “Improve User Engagement,” “Increase Customer Acquisition”).
• Epics: Large bodies of work that support the themes (e.g., “Implement Personalized Onboarding,” “Develop Referral Program”).
• Features: Specific functionalities that support the epics (e.g., “Create Interactive Tutorial,” “Offer Discount for Referrals”).
• Timeline: Estimated start and end dates for each feature.

Remember, the roadmap isn’t set in stone. Be prepared to adjust it based on user feedback, market trends, and technical constraints. A good rule of thumb is to review and update your roadmap quarterly. To make the right calls, build what users want, not what you think.

The Result: A Focused and Successful Product

After implementing the RICE framework and building a clear product roadmap, we saw a significant improvement in our product development process. We were able to make more informed decisions, prioritize the features that would have the biggest impact, and deliver a product that met the needs of our users.

Let’s revisit the mobile banking app example. By focusing on Dark Mode and Mobile Check Deposit first, we were able to quickly deliver features that resonated with our target audience. Dark Mode improved user experience, particularly for users in low-light environments, leading to a 15% increase in daily active users within the first month. Mobile Check Deposit streamlined the banking process for many users, resulting in a 20% increase in customer satisfaction scores.

A few months later, after gathering more user data and validating the market demand, we revisited the Personalized Financial Advice feature. We refined the concept, simplified the implementation, and launched a pilot program with a small group of users. The results were promising, so we gradually rolled out the feature to the broader user base.

This iterative approach, guided by data and user feedback, allowed us to build a successful mobile banking app that met the needs of our users and achieved our business goals.

Here’s what nobody tells you: even with the best frameworks and tools, prioritization is still hard. You’ll still have to make tough calls, balance competing priorities, and deal with conflicting opinions. But by using a data-driven approach, you can increase your chances of building a product that people love. And to create a product people love, user research is essential.

Product management in the tech world is about making smart choices. By adopting a data-driven prioritization framework like RICE, you can move beyond guesswork and build products that truly resonate. Start using RICE scoring this week to prioritize your top three features, and watch how your product strategy becomes more focused and effective. Also, consider how data, automation and vigilance can improve your tech strategy.