How do you collect feedback about your product?
Hey hunters! Collecting customer feedback is important to respond directly to their needs. However, there are a lot of ways to collect feedback and manage it. How do you get customer feedback and accelerate growth?
At SigmaOS we have a slack community (sigmaos.com/community) where users come to chat, report bugs and request features. It is an amazing tool and our users in the community are really the ones driving the product forward
I've just added a button on my site for collecting feedback from logged-in users: https://www.unblokd.com/dashboard I also upvoted this recently: https://www.producthunt.com/post... Although if you have a Discord channel with decent engagement, that works best.
The best way is to build a community! In any of the platforms.. PH, Twitter, Facebook, Instagram, Discord, etc. Btw, we’re launching in late April or the start of May. Check out our upcoming PH page: www.producthunt.com/upcoming/eff... Our project is called: Effecto. It’s an app for detailed health tracking. Pretty much for everything that is related to your physical or mental health and every daily factor that can affect you.
We have created communities on different sites and are trying to promote them. Also, we are currently in the beta testing stage and we have recruited a group of testers where they leave feedback in general and on each individual feature. Here is the page, by summer we want to launch https://www.producthunt.com/upco...
We have a survey built into the product, so users can fill this out and provide direct feedback at any time. I also personally reach out to new users once per week to gauge how they're feeling about their experience - manual emails are always a place you can expect good returns 👍
@paul_vanzandt It is a good way for first stages! However, when there are a lot of users, it will become more difficult to send manual emails. But still direct communication is really effective!
i would suggest running a survey on the users
First off, great question - something we all struggle with .. when do we have 'enough' feedback to move. We use a tool called "hellonext.co" - that helps us easily collect feedback and communicate our next features to users (mind you, it requires continuous diligence to publish our changelog) We gather feedback through discussions with a PAB - a Product Advisory Board / A group of end-users that we can consult via email/via messenger/via Twitter every once in a while when we'd like to validate a new feature We gather feedback with Maze (A remote usability testing/and other testing tool) and also with the basics: Google Forms & Typeform (Surveying users) ----- You can also collect Marketing Feedback with a Hotjar integration on your website and use Google Optimizely to run A/B testing easily again a hypothesis. Hope this helps you!
Tried to steer away from the great suggestions everyone had above, building a community is hard but key. Maintaining the community is even harder :) So I'd decide at which stage I am at as a startup and whether I can invest the resources in maintaining that community or delegating that role to another team member!
Hey Daria, I love this topic. I jotted down a few things I have in mind on this topic. I elaborate a bit with audio messages here if you want: https://www.vero.fm/page/recoYAj... # Collect feedback 1. Plan discussion to get feedback on the problem space 2. Do prototype testing to get feedback on the solution space 3. Find any excuses to get into discussions — and ask for specifics 4. Leave the door open (Intercom) — and open it every now and then # Manage feedback 1. Rigorous writings of the discussions 2. Highlights top facts 3. Tag 4. Refine if needed
@daryakhmetova Thanks! I hope it brings a bit more context that plain text. If you know any friends who always goes with audio first, I am sharing weekly update on the project here: https://www.producthunt.com/my/u...
I don't know if my conventional research input would help you, but anyway I need to engage on the platform😂 Okay, on a serious note this is how I do it: 1. Start with Consistency- You need to be as consistent in listening as you are in saying for your product. Create systems for feedback at each important touchpoint in the user's journey like the pricing page, chat, emails, LinkedIn DMs, etc. 2. Start Small, Go Big- Do not ask people to interview straight away, ask short questions, say, in an NPS survey. Then divide the responses into chunks like 1-2, 3-4, and 5 and assign 1-2 representatives for each chunk. Engage with these representatives further and invite them to chat. Figure out what they like or do not like and most importantly, Why! 3. Replicate- Use the qualitative insights you got from the interview to find out if people are having similar challenges on other channels and platforms. That's it.
Long form-based surveys. Customer feedback surveys are the most common way of completing the feedback loop. Short in-app surveys. Customer Satisfaction Score Surveys. Website feedback widgets. Customer Interviews. Transactional emails Suggestion boards MYiClubOnline
I typically do right in person after a participant tries my new sport. I get honest feedback that way. Sending surveys I found are typically a waste of time.
This is a helpful survey framework! Popularized by Superhuman the email client. All about measuring product/market fit and how to use the feedback in this survey to double down on what your most fanatic users love while addressing what holds lukewarm users back from becoming a fan https://coda.io/@rahulvohra/supe...
We created a Feedback Community on our website and added a feedback widget: https://help.useresponse.com/ It helps us to collect qualitative and quantitative feedback in order to decide which feature requests to take into development. We also keep our product development public: https://help.useresponse.com/roa...
hi Daria, we usually send a web story to our customers using Snackeet
Snackeet is a Web story builder kinda like Canva, super easy to use and handful to collect qualitative feedback through dynamic surveys and forms :)