How to estimate the value of new product ideas
Last updated: February 2025
Exceptional ideas can lead to breakthrough products. But how do you determine which ideas are truly exceptional? This is not always easy — especially if you are sorting through hundreds of requests from customers and internal teams. But as a product manager, it is part of your job to evaluate new product ideas and choose which ones to incorporate into your product plans.
Estimating the value of a new product idea begins by defining what value means to you. This is important. Not only will your definition of value be the basis for reviewing ideas and requests, it will help you prioritize the most impactful work throughout the entire product development process.
Generally, product value refers to your ability to meet business goals and provide what customers need. But it has many layers to it and can be tricky to measure because there is no universal value equation. It will take you some time to consider everything that gives your product worth — but this guide will help give you a head start. Read on to discover how to examine and measure the value of an idea from different angles.
Collect and prioritize product ideas in Aha! Ideas — free 30-day trial.
This is an example of how to measure product idea value with a scorecard in Aha! Roadmaps. Aha! Roadmaps includes many of the basic features included in Aha! Ideas and is great for teams looking for an all-in-one product development solution.
Feel free to skip ahead:
Why should you estimate the value of product ideas
It can be tempting to say "yes" to every idea — especially when a request sounds promising on the surface. After all, you want to move quickly and respond to customer needs. Other times, you are so busy that your knee-jerk reaction is to immediately say "no" to anything new.
But there are problems with both of these approaches. Pursuing every idea that comes your way can cause you to lose sight of your strategic plans and what you need to accomplish. You might also find yourself chasing trends or building features that do not meaningfully improve the product. At the same time, rejecting new ideas too quickly can mean overlooking valuable opportunities to differentiate your product or better serve customers.
You want a more balanced approach. When you apply a logical and quantitative lens to your vetting process, you can be as objective as possible about the intrinsic value of each idea. This allows you to assess each insight based on how it aligns with your strategy, contributes to business goals, and meets customer needs. And once you understand how each idea stacks up against the others, you can determine which ones to implement.
Related:
5 factors to consider when estimating the value of product ideas
Value is determined by your strategy and customers. So your definition of value may be different than ours. But let's look at five factors that commonly contribute to product value. You can use this list (or add your own components) to better understand and estimate the value of new product ideas.
The most effective product teams assess value at multiple stages of product development. An initial estimate should happen early in your idea management process — when an idea is raw and unrefined. As you move into roadmapping and scoping, its value may fluctuate. Continue to refine your estimates during feature definition through to production. Of course, not every idea will make it onto your roadmap — a quick value estimation upfront may be all you need to decline an idea.
Population
Population refers to the number of people that will benefit from an idea should you choose to implement it. If you use idea management software or another tool to capture product ideas, you can estimate the population by looking at votes and customer data.
Questions to ask:
How many people does this idea affect?
How many customers have voted for this idea?
How many customers have submitted similar requests or ideas?
How often do customer-facing teams hear this same request or similar ones in conversation?
Will this attract new customers?
Need
Some ideas will garner more enthusiasm than others, but these may not always be the most impactful ones. You need to separate the novel and "nice to have" ideas from the "need to have" — the ones with the most potential to create meaningful experiences for customers.
Questions to ask:
What is the impact of this idea on current customers?
How important is it for those that require it?
How will it help our customers achieve their goals?
How will it improve customer loyalty?
How will this improve the Complete Product Experience (CPE)?
Strategy
Your product strategy should always guide your product plans. This includes evaluating product ideas — where strategy can help you to make quick decisions. When a request does not support your overall objectives, respectfully say no and explain to the person who submitted it why it does not support your goals. For ideas that do align with strategy, dig in to understand the potential impact.
Questions to ask:
How closely is this idea connected to company/product strategy?
Does the idea support our goals?
What is the estimated impact on our goals?
Does it align with current initiatives?
What are the advantages and disadvantages of pursuing this idea?
Effort
Every idea has a price tag, so to speak, and your time and resources are precious. That is why you should estimate effort as part of an idea's value — even if your initial estimates are not perfect. You can explore specific cost details and requirements once vetted ideas are promoted to planned work.
Questions to ask:
How much work will it take to build?
How long will it take to build?
What resources and technology are required?
Does the team have enough capacity to build this?
Could we bundle this idea with something similar that is already planned?
What are the estimated costs for maintaining this idea once it is built?
Confidence
At the idea stage, nothing is concrete. Customer needs can change over time — and so can your business strategy. Estimating your confidence in the idea's value will help you measure how certain you are about its worth at a given moment.
Questions to ask:
What is your certainty of the population?
How certain are you that it meets customer needs?
How confident are you that it aligns with your strategy?
How accurate are your effort estimates at this stage?
By evaluating these five areas, you will have a well-rounded understanding of the potential value of any customer request or idea. Start here, then consider adding more factors specific to your industry or customer base as needed. These factors will also serve as a framework for refining the estimated value of your ideas over time.
Related:
How to measure and track the value of an idea
Estimating the value of a product idea is a great exercise — but what happens next? The steps below walk you through one approach to turning your ideas into an action plan with the help of a value scorecard:
Assign a score for each value factor. For example, you might initially say that an idea is high-, medium-, or low-effort. Using a numerical value (typically from 1-10) turns this estimate into a metric you can track.
Create a product value scorecard. A value scorecard aggregates the individual metrics into one overall value score — giving you a uniform method for comparing ideas. You can use a weighted calculation to give certain factors more pull than others. (For example, strategy alignment could be more important to you than effort required.)
Rank ideas based on value score. Once you have an overall value score for each idea, you can easily rank ideas from most to least valuable.
Promote the most valuable ideas to features. Set a value score threshold for promoting ideas to features that you plan to build and add to your product roadmap. Once promoted, you can do a more detailed analysis to decide when and how to implement each feature.
Continue to check in on value. Value scores will shift over time, so make sure to update value metrics as you uncover more customer needs or pursue new product goals. You should also return to your value scores after features are shipped. Collect feedback from customers to see if your confidence levels were accurate — and the value you perceived is what was received. You can use a product value report to measure the impact of shipped features and refine your approach over time.
Scoring is now built for greater accessibility — you can set each metric by tabbing and manually entering a value.
You can use simple spreadsheets to manage product ideas and build a basic value scorecard. But it can be challenging to keep scores updated with document versions changing and new ideas always rolling in. To streamline your process, try idea management software that includes dynamic value scoring functionality — so you can collect, manage, and estimate the value of new product ideas in one place.
Additional resources:
FAQs about estimating the value of new product ideas
What role does customer feedback play in evaluating product ideas?
Analyzing customer feedback can help product teams validate demand and prioritize the most impactful ideas. You can scope out direct requests and study usage patterns to assess value and feasibility. Our suggestion? Do this work in Aha! Ideas, where you can centralize feedback and analyze trends. This ensures decisions ultimately align with customer needs.
How often should I reassess the value of a product idea?
Regularly — especially as market conditions, customer needs, and business priorities evolve. This might happen on a monthly or quarterly basis, depending on your product and organization. Ideas that seemed high-value initially could become less relevant over time, while others gain urgency. A structured approach, like a product value scorecard, helps teams evaluate ideas consistently and revisit them with fresh data. In Aha! Ideas and Aha! Roadmaps, you can use custom scorecards to assess impact at every stage of the product development process.
How do I estimate effort and development costs for a new idea?
Work closely with engineering to assess complexity and resource needs. Together, you can consider factors like scope, technical feasibility, and time to build. Teams can use Aha! Roadmaps to link ideas to planned work and estimate effort alongside other priorities.
