The "this customer asks for it weekly" trap
When a customer asks for a feature every week, it sounds like demand. Often it's the same customer's same need being heard once and re-counted six times.
Sales notes "customer X asked for this feature." Customer success notes the same. Support notes it. Three months later, your product team is told "we've heard this from customers every week" — and it's the same customer, surfacing through multiple channels.
What's actually happening
Different teams report the same feedback as if it were independent signals. The total count looks like demand. The distinct customer count is one. Building for one customer is a different decision than building for many — and the data was misleading throughout.
The fix
Track requests by distinct customer, not occurrence. Note who asked when, not just that someone did. The picture changes immediately. A feature "asked for every week" is often a single customer making sure you heard them — which is a valid signal but a different one.
Count unique customers, not unique requests. Most feature lists confuse the two.