01
Specificity
Does the feedback describe a real workflow, a current workaround, and a concrete outcome?
Product evidence scorecard
Check whether a piece of customer feedback is strong enough to influence the roadmap.
Strong product evidence is specific, repeated, and easy to compare against other signals. Use this scorecard as a fast filter before you bring a request into planning, triage, or a roadmap review.
02
Frequency
How often does the problem happen in practice: daily, weekly, monthly, or rarely?
03
Evidence strength
Is the signal supported by direct quotes, repeated reports, support volume, or usage patterns?
04
Cluster potential
Can this problem be grouped with similar submissions from other customers or segments?
05
Decision readiness
Is the next action clear: deeper discovery, a prototype, a roadmap bet, or no action yet?
A practical rule of thumb
If a submission is vague, low-frequency, and disconnected from any broader pattern, it probably needs more discovery before it should change the roadmap. If it is specific, repeated, and supported by evidence from multiple sources, it deserves real prioritization attention.