Why Feature Request Volume Lies: The Silent Churn and Workaround Problem
TL;DR: Feature requests reflect who speaks up—not what hurts most. Rivers surface silent churn signals and workarounds that reveal real demand.
The illusion
“We got 30 requests for X, so it must be important.”
Maybe. Or maybe 30 people share a sales playbook.
Two signals better than request counts
- Workarounds: spreadsheets, manual exports, copy-paste rituals
- Silent churn: non-usage, drop-offs, “we stopped using it” notes
How rivers reveal this
- support verbatims mention workarounds
- CS notes show disengagement patterns
- help searches show confusion even without tickets
Takeaways
Count outcomes, not requests.