How do you know when user feedback is actually worth building versus just a one-off request?
by•
When you're early post-launch, everyone has an opinion on what your product is missing. It's so easy to get pulled in five different directions trying to please the loudest voices.
I've caught myself almost rebuilding the roadmap just because two people asked for the same feature on the same day.
How do you filter out the noise and figure out which feature requests will actually move the needle for retention?
18 views
Replies
Two requests for an integration could mean two different problems. I'd ask each person to show the task they can't finish and their current workaround. Try solving it manually first and see whether they come back to use that solution before building the integration.
@al_kub I'd try a small prototype or manual workaround before committing to a full build. Do people return to use it without prompting? Repeated use would strengthen the case, though I'd still want to check whether it helps them stick with the product.