An impact score estimates how much value a product initiative could create for customers, the business, or a strategic goal. Product teams use it to compare work that competes for the same time and development capacity.
How an impact score works
There is no universal impact scale. Teams commonly use 1 to 5, 1 to 10, or named anchors such as low, medium, and high. The important part is defining each level before scoring. For example, a score of 5 can represent an initiative that removes a critical problem for a target customer segment. It can also represent work that materially advances a current company goal.
A good impact score is tied to evidence. Useful inputs include customer votes, affected segments, revenue, problem severity, research, product analytics, and strategic alignment. Impact is still an estimate, so teams should record their assumptions and revisit the score when better evidence appears.
Impact is one axis in an Impact Effort matrix. It is also a factor in RICE prioritization and ICE scoring. Each method defines and combines impact differently.
FAQ
What is an impact score in product management?
How is an impact score calculated?
Is an impact score objective?
The faster, easier way to capture user feedback at scale
Join over 5,204 product managers and see how easy it is to build products people love.
Did you know 80% of software features are rarely or never used? That's a lot of wasted effort.
SaaS software companies spend billions on unused features. In 2025, it was $29.5 billion.
We saw this problem and decided to do something about it. Product teams needed a better way to decide what to build.
That's why we created ProductLift - to put all feedback in one place, helping teams easily see what features matter most.
In the last five years, we've helped over 5,204 product teams (like yours) double feature adoption and halve the costs. I'd love for you to give it a try.
Ruben Buijs
Founder & Digital Consultant