Product Teams Drowning in User Feedback
279 posts across 21 communities in the last 30 days; 69% from GitHub.
“Hey founders has a stranger ever reached out with feedback on your product, like a real bug with a fix, a reliability issue, or a feature idea? What was it about, and what made you reply or ignore it?”
“Heads up: the "How it works" and "What I'd love from testers" sections in your post came through empty, so readers see headings with nothing under them; worth editing before people skim past. Since Giver is built for friend groups, a solo tester sees an empty app; inviting…”
“I get it, having two overlapping tools is annoying to justify. The one I'd miss is feedback triage: Zapier can copy a row into a database, it can't read a rambling comment and work out which team owns it, and that judgment is the whole job. If you can already write your rules…”
Product teams are overwhelmed by the volume and disorganization of user feedback from various sources. They struggle to consolidate, prioritize, and translate this feedback into actionable product decisions, leading to wasted time and a lack of clarity around priorities.
SOURCES (60)
“the widget itself is clean but the analytics side feels bare. I’d want some way to tag feedback by feature area and maybe a trend graph so I’m not just scrolling through raw entries trying to spot patterns [re: What else would you need from…”
“Problem Agents often finish and move a task to Your Review ( review by user ) while I'm working in another window. Nothing audible happens, so tasks sit there waiting on me without my noticing. Current behavior src/mainview/task sounds.ts defines sounds only for completed and cancelled ( TaskSoundStatus = "completed" | "cancelled" ). Both sit behind one toggle, playSoundOnTaskComplete (Settings → Notifications → Task complete sound). No other status transition can play a sound. Requested behavio”
“What should we add or change? Creating a compatible ctx.ui revision for every extensions might be a bit of a huge task, so an incremental feature that could bandaid every individual user's issue with extensions that rely on terminal ui is to correct how the script output is shown. i.e if there. is a sub model picker extension that requires tui interaction, the user could implement a workaround that prints a list, where Pi dispatches extension commands before model preflight, so these run with no”
“fwiw if youre posting your landing page, include a one-liner about who the target user is. makes it way easier for people to give useful feedback instead of just reacting to the design [re: Feedback Friday]”
“totally with you on the feedback being actionable. maybe they could even include examples of common pitfalls or misconceptions interviewers see. also, UI testting with real users could help identify any rough edges before launch, that way they can nail the first impression. [re: Building a system design & architecture interview prep tool — would love your feedback!]”
“Checklist [x] I made sure that there are no existing issues open or closed which I could contribute my information to. [x] I have read the README and my problem isn't listed. [x] I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise. [x] This issue contains only one feature request. Feature description I'm aware that uploading multiple files at once isn't doable as a way to combat rate limit, but what about doing it "the send”
ChatGPT UI Feedback – Project Visibility in Recents
“Since your feedback emails went unanswered, try one specific question after an in-app action. That is easier to answer than a general feedback request. [re: My first two customers came within 2 days of launch. Now it's been 3.5 weeks of nothing and I'm struggling to stay motivated]”
“"Congrats on the launch, Elie! "With team comments, can two teammates see that the other is already drafting a reply? That bit of coordination could be useful for founders sharing a support inbox." Requested by: https://x.com/foundrcode/status/2111725217475158525”
“Honest feedback in a niche community usually comes when people have a little skin in the game. A free survey gets polite answers. A refundable deposit or a small paid beta gets the truth, because only people who really want it will bother. On pricing, I would start at whatever a lifter would not think twice about. Zero users means the goal is proof that someone pays, not perfect margin. You can raise the price later once the app has results behind it. Curious, do you have any kind of waitlist go”
“Before launch I'd keep it boring: pick one place where every piece of feedback lands, whether it came from a call, an email or a support chat. A shared doc or a simple Airtable is plenty at 5–10 customers. Then book a 20-minute call with each of your first customers in month one and ask them to walk you through the last time they used it, which tells you more than any survey. If you want a tool, Canny and Featurebase are the usual feature-request boards; full disclosure, I'm building Tet”
“In our beta, requests often sound identical until we watch the actual workflow. Six users may be asking for one feature, or six exceptions wearing the same French-tax hat. [re: France first, everyone else later = bad decision ?]”
“Pre submission checklist [x] I searched existing issues (open & closed) and found no duplicates Problem / Use Case I observe more and more (half baked) features being added to thaw. Maybe this is what everyone wants, however, for people like me who came to Thaw for one simple reason: minimal main menu bar and convenient access through a second / expandable menu bar. Now, we have menu bar styling, profiles, hooks, triggers, groups, ... while the core functionality still isn't bug free. Cursor jum”
“I think getting genuine feedback from users is the biggest challenge for indie devs and small teams especially if they come from multiple sources like Reddit, Facebook, TikTok, and Instagram. So what if there was a simple widget on your website where users can post recommendations and upvote on features they like? Well, I built Euclid BUT what makes Euclid different from other feedback tools? Well, its the AI engine living on the backend. It helps you with duplicate feedbacks, consolidates data,”
“someone handing you a fix they already wrote is about as good as unsolicited feedback gets tbh [re: Think about the last time a stranger sent you feedback on your product. Did you reply?]”
“hello thank you for feedback i modified it based on your suggestions can u take a look would love to hear more suggestion. im curious did you sign up for app if not may i ask why not also was wondering how do you recommend i advertise the app [re: Title: [Beta] VISION — A self-guided personal growth web app]”
“hello thank you for feedback i modified it based on your suggestions can u take a look would love to hear more suggestion. im curious did you sign up for app if not may i ask why not also was wondering how do you recommend i advertise the app [re: Title: [Beta] VISION — A self-guided personal growth web app]”
“Hey founders has a stranger ever reached out with feedback on your product, like a real bug with a fix, a reliability issue, or a feature idea? What was it about, and what made you reply or ignore it? submitted by /u/turtleyikes [link] [comments]”
“Hey founders has a stranger ever reached out with feedback on your product, like a real bug with a fix, a reliability issue, or a feature idea? What was it about, and what made you reply or ignore it? submitted by /u/turtleyikes [link] [comments]”
“Heads up: the "How it works" and "What I'd love from testers" sections in your post came through empty, so readers see headings with nothing under them; worth editing before people skim past. Since Giver is built for friend groups, a solo tester sees an empty app; inviting testers in pairs or small groups, or asking each to bring one friend, tests the part that matters. Saying US-only up front, as you did, keeps invites away from people who can't use the shops. I make”
“Hi, I have some requests for features that would be very handy for more experienced users of the app. 1. Toggle for the verification system While the verification system is nice, I think there should be a toggle to disable it. I know that you can force downloads of unverified versions, but this is something you have to do manually for each application and it also disable auto updates. 2. Toggle for the Platform Asset Matching filter While this filter is handy for users not very familiar with arc”
“add better labels for issues like labels for exemple: game idea has been added rejected not posible ... also when creating an issue ad more criterias like have i checked the roadmap checkbox + if its a game idea please make 1 issue per game idea and not 1 issue with 3 game ideas all stuff like that :D (btw if you need help managing issues and prs i can help lol i just learned about this project yesterday and got the calculator like a week ago but im alrady down on making games on it)”
“Testers will come faster if you hand them one job instead of five features: set up a single comment-to-DM trigger on a real post and say where it stuck. Agencies will also want to know what access EzReach takes on a client account and whether AI replies can wait for approval before sending; a line on that does more than the Meta Verified badge alone. For actual users, go where creators and social media managers trade Instagram workflow problems, with a post about juggling DMs across tools; found”
“Right now the post is just a link, so readers have to guess what they're judging. The sidebar here asks you to "Please add a description of your product", and feedback requests do better with one line on who the recipe card creator is for and one specific question, like whether a first-time visitor understands what they get or whether the finished card looks ready to print. I make ThreadFox. Our AI employee can introduce your recipe card creator in recipe communities whose rules al”
“🎯 What feature would you like to see? Please describe the feature as clearly as possible. What should it do? What problem does it solve? ✨ Why is this feature useful? Explain the benefit of the feature. Who would use it and in what context? 💡 Possible ideas for implementation Do you have any suggestions for how it could be built? Feel free to share links, mockups, or code snippets. 🙋 Would you like to help? [ ] Yes, I’d like to contribute [ ] I can help with testing or feedback [ ] I have que”
“Great feedback and very detailed, too. Thanks for your reply. That gives me something to think about! [re: Feedback Friday]”
“Such a great tip. I don't know why I didn't even think of that. I'm going to redo so many things today. Again thank you [re: 🗳️ Product Feedback for Notion]”
““Could reduce a lot of manual work” is the kind of feedback that sounds great and doesn’t tell you much yet. I’d ask 2 or 3 of those healthcare consultants to run one actual client review through it this month. Then watch whether they come back for the second client without you chasing them. That tells you more than any amount of positive reactions. And when you talk to consultants, I’d ask about the last time a compliance review went wrong or took way longer than they quoted. If AI makes them n”
“Fair point on narrowing the feedback ask: telling lifters to find the first ✦ callout they disagree with is way more actionable than asking for general impressions. And good callout on the landing page: the two-question setup and sample workout preview are right on the front page before you ever have to drop an email for the magic link, so you can see the math before signing in. [re: [Web] [Free] Rebar - the workout app that shows its math, looking for beta testers]”
“Is your feature request related to a problem? Please describe. We manage multiple projects in which varying numbers of documents are assigned to different annotators. Currently, it is difficult to keep track of each annotator's remaining workload and identify who has completed their assigned documents or has no work left, unless they proactively report their progress. Describe the solution you'd like A centralized manager dashboard that provides an overview of all annotators and their current wo”
“Yes projects are easy , people are not. Have all their feedback in one place . [re: Managing client feedback is harder than managing the actual work]”
“Thanks for offering to add those checks. I can contribute the test scenario, but I'm not committing to a Zapier setup in exchange. Please don't count my feedback as one of the integration's required real-user tests. The main distinction I'd want preserved is that an unavailable page stays 'unknown' until a successful recheck confirms a change. [re: Help needed: Looking for 2 people to test a free backlink checker on Zapier (5 mins)]”
“do you batch all comments into one pass or does it handle them sequentially? feels like ordering could matter if later comments depend on changes from earlier ones [re: notion is basically my context + presentation layer now]”
“Hey everyone, To get better feedback on my web tools (BrowserDone), I added a small dynamic badge to the feedback modal: - Default: Normal feedback modal. - Verified Usage: Turns golden automatically once the user actually tests or runs the tool. - Instant Alert: Sends the feedback along with context straight to my Telegram bot. This helps me instantly separate feedback from people who actually tested the tool from random visitors. Would love to hear your thoughts or suggestions on this approach”
“If you miss a feature, pick one vibe-coded project and contribute. Absolutely! pick one and contribute to it. Unless of course there are so many missing features that it only makes sense to start from scratch. To be fair to vibers, I doubt they know how to contribute, ie creating a pull request, merging etc [re: Arrmada]”
“Turn your feedback list into three tasks: find this Sunday's service time, open the visit information, submit Member Connect with fictional details. Ask what broke or confused them at each step; that is feedback you can quote when you apply for production access, starting with the small-screen spacing note on Member Connect above. Testers who opt out before day 14 break the 14 days, so ask them to stay in after they finish. I make ThreadFox. Test Rounds puts Midway Church SD in a round of 14”
Feature request: A Dedicated “Knowledge Contribution” Button