How to collect and use feedback after a product launch to improve future releases?
Elif Duran
13 replies
Hello everyone!
Have you made any major changes to your product after your product hunt launch? How do you spend your post-launch process in terms of developing the product?
Replies
Sharath Kuruganty@5harath
Undefeated Underdogs Podcast
The best way is to use dump every feedback you received in a Notion doc, create a Kanban board, divide the ones that make sense, prioritize, and attack :)
Share
Emaildojo by Netcore Cloud
Hey @elifduran, I totally agree with you!
Collecting feedback from your target audience is a powerful way to improve your product. In fact, after a not-so-great launch, I learned the value of feedback first-hand. Take a look at v1.0 of Emaildojo on Product Hunt versus the current version on https://emaildojo.io There are tons of updates that were driven by user feedback.
I've found that using a variety of channels to collect feedback is key, such as surveys, user interviews, social media, and customer support inquiries. Once you have feedback, it's crucial to analyze it, identify common issues, and communicate with your users about how their feedback is being incorporated into the product roadmap.
Knit API
I'll come back to this as we complete the launch.
But we're primarily focused on increasing ease of use to the platform and are looking at all the feedback on those lines.
How we look at feedback 1. Direct comments / chat etc 2. Product usage tracking
Supatale
How relevant your question is!
We're actually launching Kaleido tomorrow, which is a product that helps transform user pain points into product decisions that matter https://www.kaleido.soπ― And we use Kaleido ourselves to collect feedback and make product decisions based on it.
Product Hunt is just one of the many sources of knowledge we use to improve our product. For example, we find it valuable to compare feedback from Product Hunt to what we've heard from users in in-depth interviews. Thanks to pattern search, which is powered by AI, we can also identify which features are in high demand and prioritize accordingly. And it's always great to see reviews from paying users or those who return regularly. This helps us allocate our limited resources effectively.
Btw if you are interested, please let me know, and we would be happy to provide you with a short demoπββ
Yep, mainly made a few changes to make sure glitches are sorted out
HireQuotient
1. Monitor the comments and feedback on the Product Hunt post and respond to them promptly.
2. Encourage users to leave feedback and suggestions in the comments section.
3. Follow up with users who have shown interest in the product and ask for their feedback.
4. Analyze the feedback received and prioritize improvements based on the most significant impact they will have on the product's success.
AppManager by CompanyDNA AI
I think the best way to do that is to schedule a video call with early adopters/volunteers (approx. 15 people) to test product user flows and record the errors with Loom and add explanations in a doc. After that prioritize bug fixes, low-hanging fruits and plan big rocks for the longer term. Don't forget to collect feedbacks in platform as well!
The post-launch process should be all about analyzing feedback, identifying areas of improvement, and implementing changes.
Pieces for Developers
We are in the process of launching our own Discord server which, imo, is the best way to get as close as possible with your users. We are building a community around our product through Discord and the instant feedback that we are able to get on ideas/releases is game-changing.