Home
Starting Up
Case Studies DB
Products
Ideas DB
Vibe Coding Tools
Subscribe to IH+
Starting Up
Case Studies
Ideas DB
Products DB
Join
8
Likes
8
Comments
How do you collect user feedback?
by
Rishi
Follow-up question:
What's the hardest part of the process for you?
If you want to collect user feedback, check out muchofeedback.com.
MuchoFeedback. lets you add a simple feedback box to your site in minutes. No per-seat pricing, no feature gates — just $5/month.
If you’re early-stage and just want honest user feedback, it might help: muchofeedback.com
I really recommend using a public feedback board (with feature voting) to capture all the user feedback, feature requests and bug reports. It keeps all your product feedback in one place so you can easily make sense of it and make the correct product decisions when building your project.
The tool that I am building is called Featurebase and it does all of that for free, check it out if you are interested: https://featurebase.app/
Cool, love the landing page and your comparison pages to other tools like Canny. That was my first question and this page really nailed it!
I'm also working on a feedback collection tool but focusing only on async video. Kinda like Loom but for user feedback. We are super early, just started building this month.
One idea when we are further along would be to integrate with your tool so that once a user records a screencast from our shared customer's app, they can also auto-create a featurebase item. Just thinking out loud. I see a world where both tools could complement each other really well.
Best of luck - featurebase looks awesome!
I personally think the "hardest part" is "talk to users", but are some tools like:
https://www.hotjar.com/ to see how your users interacts with your product
https://splitbee.io/ to see the actions, create funnels from your users
but, I have started talking to friends that are using my product, to learn how to talk to users I don't know
Thanks for your sharing! I have a lot of experience talking to users as a product manager. I definitely recommend reading The Mom Test. The main idea is to ask users what they currently do vs. focusing on your ideas or solutions or what they would use in the future (or would pay for).
The book is more geared to pre-product validation of your idea, but a lot of the ideas apply to existing product conversations.
Focus on their current workflows, problems, and the outcomes that they want or opportunities they are excited about. Learn more about the phases that frustrate them the most and why.
Then it's your job to think about and work on the solution after the call. I've found that solution brainstorming on calls with clients is often waste of time. It's fine to do as long as your expectations are set properly.
You shouldn't be relying on their ideas of how to solve their own problems. Not to say they aren't intelligent or good problem solvers, it's just that you're in a better position to think more broadly about how you can nail the underlying pain points in a more complete and elegant way not only for them, but for other customers also.
I also highly recommend this thread on things to avoid when talking to customers: https://twitter.com/SaraSodineParr/status/1349931485835517955
Hope that helps!
One thing I've seen used is UserZoom - it's essentially Zoom specifically made for the use case of user research, hence the name. It lets you have spectators, and the participants can't see them as the researcher asked the participant questions. This gives you a "transparent window" effect.
Cool - I could see this as super helpful for bigger teams to have more people able to join in on the insights.
It's like those interrogation scenes in movies but for user research 😂
Hey ! On that regards we developed Jimo ( https://usejimo.com/ ) to get user feedback on your product developments. Feel free to check it out ^^,