Product Managers: Stop Building Useless Features

Navigating the Product Maze: A Product Manager’s Guide to Success

Are you a product manager in technology feeling overwhelmed by competing priorities and unclear metrics? Many product managers struggle to translate vision into tangible results, leading to wasted resources and frustrated teams. What if you could consistently deliver products that exceed expectations?

The Problem: Feature Creep and Unclear Priorities

I’ve seen it happen countless times: a product manager, armed with a grand vision, tries to implement every single feature request that comes their way. They want to please everyone, but the result is a bloated, unfocused product that satisfies no one. This is feature creep in action, and it’s a common pitfall for even experienced product managers in the technology sector. Imagine trying to build a house by adding every single amenity imaginable – a bowling alley, an indoor water park, a professional recording studio – without a clear plan. You’d end up with an unlivable mess. The same principle applies to product development.

A major contributing factor is often the lack of a clear prioritization framework. Without a structured approach, decisions become subjective, influenced by the loudest voices or the most recent requests. This leads to wasted time and resources on features that have little impact on the overall product goals. I recall a project where we spent three months developing a highly requested, but ultimately unused, social sharing feature. The post-launch data showed dismal adoption rates, a clear indication that we had misallocated our efforts. For more on making the right calls, see our article on data-driven strategy.

The Failed Approach: Saying “Yes” to Everything

Early in my career, I fell into the trap of trying to accommodate every stakeholder’s request. If the sales team wanted a specific integration, I’d prioritize it. If a customer complained about a missing feature, I’d add it to the backlog. The result? A chaotic roadmap, constant context switching for the development team, and a product that lacked a clear identity. We were constantly reacting instead of proactively shaping the product’s direction.

We attempted to manage this by simply adding more people to the team. The logic was simple: more developers, more features delivered. However, as Brooks’s Law states, “adding manpower to a late software project makes it later” – and that’s exactly what happened. The increased communication overhead and coordination challenges outweighed any potential productivity gains. We ended up with a larger team delivering fewer features, and the features we did deliver were often of lower quality. This is where I learned the painful truth: saying “no” is often more important than saying “yes.” It’s a critical skill for any successful product manager. Don’t make the mistakes others have made; avoid these fatal errors.

The Solution: A Framework for Ruthless Prioritization

The key to overcoming feature creep and delivering impactful products lies in adopting a robust prioritization framework. There are several options available, but one that I’ve found particularly effective is the RICE scoring model. RICE stands for Reach, Impact, Confidence, and Effort. Each factor is assigned a numerical value, and the RICE score is calculated using the following formula:

RICE Score = (Reach x Impact x Confidence) / Effort

Let’s break down each component:

• Reach: How many users will this feature impact within a specific timeframe? This could be measured in users per month, users per quarter, or any other relevant metric. For example, if you anticipate that a feature will be used by 1,000 users per month, the Reach score would be 1,000.
• Impact: How much will this feature impact each user? This is a subjective assessment, typically rated on a scale of 1 to 3 (e.g., 1 = low impact, 2 = medium impact, 3 = high impact).
• Confidence: How confident are you in your Reach and Impact estimates? This is also a subjective assessment, typically expressed as a percentage (e.g., 50% = low confidence, 80% = medium confidence, 100% = high confidence).
• Effort: How much effort will it take to implement this feature? This could be measured in person-months, story points, or any other unit of work.

By assigning numerical values to each factor, you can objectively compare different features and prioritize those with the highest RICE scores. This approach helps to remove bias and ensure that you’re focusing on the features that will deliver the most value to your users.

For example, let’s say you’re deciding between two features: Feature A and Feature B.

• Feature A: Reach = 500 users/month, Impact = 3, Confidence = 70%, Effort = 2 person-months. RICE Score = (500 x 3 x 0.7) / 2 = 525
• Feature B: Reach = 1000 users/month, Impact = 2, Confidence = 90%, Effort = 4 person-months. RICE Score = (1000 x 2 x 0.9) / 4 = 450

Based on these scores, Feature A would be prioritized over Feature B, even though Feature B has a higher Reach, because Feature A has a significantly lower Effort and a higher Impact.

The Implementation: OKRs and Continuous Feedback

Prioritization is only half the battle. Once you’ve identified the most important features, you need to ensure that they align with your overall product goals. This is where Objectives and Key Results (OKRs) come into play. OKRs are a goal-setting framework that helps teams to focus on what matters most and track their progress towards achieving their objectives. An OKR consists of:

• Objective: A qualitative description of what you want to achieve. It should be ambitious and inspiring.
• Key Results: Quantitative metrics that measure your progress towards achieving the objective. They should be specific, measurable, achievable, relevant, and time-bound (SMART).

For example, an Objective for a product might be: “Increase user engagement.” Key Results could include:

• Increase daily active users (DAU) by 15% by the end of Q3.
• Increase average session duration by 10% by the end of Q3.
• Reduce churn rate by 5% by the end of Q3.

By establishing clear OKRs at the product level and cascading them down to individual team members, you can ensure that everyone is working towards the same goals. This alignment is essential for delivering impactful products. Make sure your OKRs are visible to everyone on the team, and hold regular check-ins to track progress and identify any roadblocks. I like using Confluence to document and share OKRs, ensuring transparency and accountability.

But even the best prioritization framework and well-defined OKRs are useless without continuous feedback. Product managers need to constantly gather feedback from users, analyze data, and iterate on their product based on what they learn. This involves conducting user research, analyzing usage data, and monitoring customer support channels. We use Amplitude to track user behavior and identify areas for improvement. I also make it a point to conduct regular user interviews to gain qualitative insights into user needs and pain points. Don’t underestimate the power of simply talking to your users. If you want to build what users actually want, consider Lean Mobile principles.

The Results: A Case Study in Atlanta

At my previous company, a SaaS provider located near the intersection of Northside Drive and I-75 in Atlanta, we were struggling with low user engagement and high churn. Our product, a project management tool, had become bloated with features that were rarely used. We decided to implement the RICE prioritization framework and establish clear OKRs to focus our efforts. We also ramped up our user research efforts, conducting interviews with customers across various industries, from construction companies using the tool for projects near the new Westside Park to marketing agencies managing campaigns in Buckhead.

Using the RICE framework, we identified three key features to prioritize: a simplified task management interface, a more intuitive reporting dashboard, and a mobile app for on-the-go access. We set the following OKRs for the next quarter:

• Objective: Increase user engagement and reduce churn.
• Key Result 1: Increase daily active users (DAU) by 20%.
• Key Result 2: Reduce churn rate by 10%.
• Key Result 3: Increase average session duration by 15%.

We spent the next three months focused on developing and launching these three features. We held daily stand-up meetings to track progress, and we conducted weekly user testing sessions to gather feedback. We even visited a local construction site near the Fulton County Courthouse to observe how users were using our product in the field. (Here’s what nobody tells you: sometimes the best user research is simply watching people work.)

The results were dramatic. At the end of the quarter, our DAU had increased by 25%, our churn rate had decreased by 12%, and our average session duration had increased by 18%. We had exceeded all of our OKRs. Moreover, customer satisfaction scores increased significantly, and we received positive feedback about the simplified task management interface and the mobile app. The RICE framework and OKRs had helped us to focus our efforts on the features that mattered most, and the continuous feedback loop had allowed us to iterate on our product and deliver a better user experience. This resulted in a 15% increase in quarterly revenue. If you’re in Atlanta, UX/UI can improve your ROI, too.

For product managers in technology, mastering prioritization and feedback loops is not just about managing products; it’s about leading teams and driving real business value. It requires discipline, data, and a healthy dose of empathy.

Ready to reclaim your product roadmap and deliver results? Start by implementing the RICE framework on your next project. I guarantee you’ll see a difference. If you’d like to learn more about the right analyses, see our article on mobile product success.