Launches
Coming soon
Upcoming launches to watch
Launch archive
Most-loved launches by the community
Launch Guide
Checklists and pro tips for launching
Products
News
Newsletter
The best of Product Hunt, every day
Stories
Tech news, interviews, and tips from makers
Changelog
New Product Hunt features and releases
Community
Discussions
Ask questions, find support, and connect
Streaks
The most active community members
Events
Meet others online and in-person
Advertise
How to post?
  1. Discussions
  2.  → When did you set up a user feedback group? (e.g. Slack,...

When did you set up a user feedback group? (e.g. Slack, Discord)

Richard Fang
8 replies
Did you do it super early, during your beta or when your product was generating revenue? Trying to find the line between too early and too late right now 😅

Replies

Bill Sengstacken
Have a feedback channel set up and ready to go before you push that beta or MVP - you need feedback *early* to ensure you're on the right track. Fair warning - don't jump on every request for a feature or a change if it will delay an upcoming update. But if you get enough similar feedback, then you should put it on the product roadmap. DO acknowledge the feedback you get. You might want to create a specific #wishlist channel, as well as one for generalized support and non-feature feedback.
Share
Arseniy
User feedback channels were enabled from the get go - no point in interating your product development if the underlying foundation is already disliked, and you can't know if it is unless you are getting feedback from your alpha/beta testers.
Share
Cezary Dobrowolski
In https://employplan.com we've had a Slack channel since the very first users. User feedback is the best way to determine the way you should develop your software (not in all cases of course). Also even the brightest UX designer won't prepare flawless design: it's very important to get rid of any bugs or holes as soon as possible. You don't need a discord or slack though. Simple "let us know what you think" with a email provided may be a source of a great feedback. ;)
Share
Gabriel Bujold
We were asking users individually at the beginning. Now that we're working on the second version of our product, we're using canny.io to get feedback on elements such as new features & bugs. I think it's more about an ongoing process that trying to shoot for the "right moment". If you have an MVP, then I would build specific milestones: First 10 users, first 50, first 100, etc. Afterward, it's about having a process to get ongoing feedback but at first, I think it's very important that you listened to your customers.
Share
Mr Ethar Alali
From the beginning. Indeed, the project we had was technically a co-production. The users who provided feedback also became our beta clients.
Share
Danyub Mustefa
Before we had a product, we took feedback on the UI designs. Though will not recommend asking them about what they need, users looking for X but asking for Y wasted quite a bit of our time.
Share
Ronak Jain
Use https://beamdock.com. It's a free portal where your request can request for a feature, add feedback or even upvote an already created feature/feedback. Your users also get to schedule a User Interview automagically, if that's a part of your current product management workflow. There are a lot of other features, happy to discuss this over a call and understand your use-case.
Share
Dejon Brooks
I used Discord. I was able to get over 70 active beta users and was able to build a great tight community + lots of product feedback.
Share