One of the easiest traps in product development is thinking feature requests are about features.
Most of the time, they aren't.
When someone asks for a feature, they’re usually describing something that didn’t work the way they expected. The feature they’ve suggested is simply their best guess at how to fix it.
That’s what makes them so valuable.
Not because they tell you what to build, but because they reveal where people are struggling.
The more interesting question isn’t, “Should we build this?”
It's, “What happened that made someone ask for it?”
Sometimes the answer is exactly the feature they requested.
Sometimes it’s a confusing interface. Missing information. An unclear workflow. Or a default that doesn’t match how people actually use the product.
The feature request tells you where to look.
Understanding the problem tells you what to build.