Product teams face significant challenges when prioritizing roadmaps due to numerous ideas and inputs. Quantitative scoring methods help reduce subjectivity, though experts caution that "even skilled product experts are bad at correctly estimating both the work required and the amount of value it will provide to users."
Using Scores in Combination with Product Discovery
The most effective approach combines scoring with sustained product discovery efforts. The recommended workflow includes:
- Enable one or more scoring mechanisms (GLIDR supports RICE and Pain vs Frequency, among others)
- Score new ideas as they arrive, moving processed ideas to a "Candidate" column
- Filter by score to identify high-potential ideas for discovery work
- Use evidence from discovery to make shipping decisions based on real customer data
This methodology allows teams to avoid common scoring pitfalls by grounding decisions in actual market feedback rather than estimates alone.
Supported Scoring Frameworks
GLIDR provides four prioritization scoring options: