Product Teams Drowning in User Feedback
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)
“feedback is brutal, especially when people just ghost. have you tried offering something small in return for their time, like a $5 gift card or early access to a feature? sometimes that shifts the dynamic.”
“Asking at the moment of friction works better when the question names one thing. in our tester posts we name a single flow to break rather than asking what people think (dEssence, ours). a general ask gets you looks clean, congrats.”
“Ask at the moment of friction, not days later. A one-click prompt like “What stopped you here?” with three reasons plus Other will usually teach you more than a general feedback email.”
“Problem People in the room file a request and never see it again inside the product. To know whether it exists, was picked, or shipped they have to open GitHub. During the workshop the facilitator wants to point at the app, not at GitHub, to show "here are the requests so far and where each one is". Proposed behavior At the bottom of /request feature , under the interview and the form, a section "Requests so far" lists every feature request filed to the harness repository: open ones first (newes”
“Do you need to file a feature request? [x] I have searched the existing feature requests and pull requests. [x] I believe this is a legitimate feature request, not a question or bug. Feature Request Description DeepTutor history pickers currently filter only the conversation title and the last message included in each session summary. A learner cannot find an older conversation by searching for a term that appeared earlier in the transcript. Add bounded, server side full conversation search acro”
“Agree. We are trying to do exactly this. One challenge is the product is constantly evolving, so feedback gets outdated quickly.”
“More feedback can still overwhelm the team’s decision capacity. I’d use the aggregate to find recurring friction, then sample the original conversations behind each pattern before prioritizing it. Every summary should link back to the exact interaction, show how often the problem appeared, and preserve counterexamples. That keeps the “why” available when someone questions the aggregate later.”
“Ticketing system that outlines exactly what information is required to report a bug.”
“On the Review screen the only answers are Apply and Dismiss. To say "split Videos by topic" or "put the arXiv papers under Research" you have to leave Review, open the chat drawer and type there, and the connection between what you saw and what you asked is lost. Acceptance A one line "Ask for changes…" input at the bottom of Review. Enter or Ask sends it as a normal chat message (same privacy gate, same proposal flow) and takes you to the chat so the reply and the new proposal appear where they”
“Please confirm: [x] I have searched existing feature requests (open and closed) and found no duplicates. [x] Me or my organization is currently an active sponsor of the product at the $99, level. Problem Statement I have a vauge memory of this being discussed before, but can't find any reference to it. Our SDM's have requested if we can generate more specific reports from the scheduled reports. As an EG, they use CIPP for the montly licenced user report for their monthly meetings. Currently they”
the classroom hour worked because you watched kids walk away. in-product feedback is almost only from people who stuck around long enough to type. the people who bounce never write in. summarizing…
“This post is the only place where Requests, Promotions, and Feedback about software are allowed to be made. Any posts for the same outside of this thread will be deleted. Unfortunately we are experiencing a time where we are seeing many start ups and coders trying to branch into the Logistics area that surpass our capacity to filter. Instead of deleting dozens of posts a day, this is an opportunity for them to still post. Will try to make this a reoccurring post, we will see how its received and”
“The ability to turn off page discussions permanently for a workspace (especially personal) instead of having to do so manually for every single page.”
“What problem will this feature address? NA Describe the solution you'd like NA Describe alternatives you've considered NA Additional context NA Will you send a PR to implement it? Yes”
“appreciate that, and yeah the private feedback part was honestly the whole reason I started building this instead of just using a form. it's a real signature step, not just a checkbox, happens right after they edit the wording and approve it. so edit, consent, and sign all happen on the same screen for them, no separate docusign-style flow. curious what you're using right now if anything, or is it still the nice-paragraph-please email for you too?”
“From: Open Book Reader Feedback (studio feedback alias) Subject: Open Book Reader feedback Received: Sun, 06 Sep 2026 08:57:37 +0000 Reporter feedback (no description — user sent the prefilled template unchanged) App context App: open book reader Platform: chrome ReportSource: uninstall survey Reason: Missing a feature I needed <details <summary Raw metadata JSON</summary </details An uninstall survey response citing a missing feature , with the free text box left blank — so the reason is known”
“Thanks for sharing that. The change in how people consolidated feedback is useful to hear. I would want one person to resolve conflicting notes before they reach the designer, otherwise even two revision rounds can turn into a lot of separate requests.”
“Summary When a step inside the student workflow fails, the desktop app gives almost no feedback. Today I pressed Begin Workflow, it ran for about half a second, and every student card flipped to Stopped 0%. Nothing on screen says which step failed, why, or what to do next. The information that would answer those questions is partly recorded in the project database, partly discarded before it gets there, and none of it is reachable from the UI. I'd like a way to see what actually happened: at min”
“Product Feedback - Middle Mouse Button open New Window in the Old Sidebar. On the New one, it doesn't work. Only with the 'Recents' and 'Favorites' type of tab. Please fix this, this is extremely important!”
“i'd expect that to be a multiselect with removable chips, not a single text field. a small add-model button could make the flow a lot clearer.”
“My first reaction is that the value is not necessarily having six survey formats. It is helping a product team ask the right question at the right moment and know what to do with the answer. Otherwise, choosing among six surveys may become another research decision for the customer. Which type has received the strongest response so far, and what decision was the user trying to make when they embedded it?”
Ux and a feature that makes day to day life for people better
I am building an app called Callout around opinions and reactions. One thing I keep noticing is that a Like hides the reason behind the tap: agreement, support, curiosity, or simply acknowledgement.…
“Folks, I think the problem is far more intricate than where is your single source of truth. It’s about relevance. A request for a feature 3 months ago or a behavior trend before redesign could be obsolete and damaging if it’s being considered. With the rate if change accelerating in our software and customer demands shifting and having more options, we need to make calculated bets. Source of truth can help but what more helpful is tracking how far off you are from your predictions based on your”
“I agree with the distinction, especially for SaaS where a feature can solve today’s pain while also showing where the product is heading. I’m working on a small tool around review analysis, pikwisely(dot)site, and even there I’d rather leave room for what the insight could enable next instead of treating every output as the final answer.”
“I feel like you have two asks here? One it how to handle feedback from users and one is tooling? I think feedback from users is important yet everyone wants something differernt. Its up to the leaders of the bussiness to ensure that any feedback being considered is one that builds the best possible product. Just because feedback has been left doesn't mean that is valid and doesnt mean that is something a large selection of your users actually need or want. On the tooling side, if you are alr”
“the "return after first browse" question is the hardest one. for me its usually a habit loop: either i get a personalized nudge or theres some social signal like "your stack" or "trending in your network". right now your three feeds are functional but none create that pull. id experiment with a weekly digest or a "save for later" that emails me when a saved repo hits rising. on the discovery side, ive been playing with something that tracks keyword mention”
Suggestion: Separate ‘Correct Answer’ from ‘Like/Dislike’ Feedback
“Checklist [x] I searched exising issues and no one else requests similar feature. [x] I think that 25%+ users are positive towards this feature. Describe the feature 这是一个扑克牌游戏，能否有优秀的java框架来优化代码架构，现在的UI我很不满意，不是一个成熟的扑克牌游戏，AI机器人出牌逻辑也不人性化，能否根据我玩游戏，来优化机器人，玩的时间越多，出牌能力越强 而且这个出牌模型可以迁移 基于以上考虑，能否对当前项目进行重构 Additional context No response”
“I have 2 apps, both without any good customer feedback collection mechanism. My apps are very customer focused, and so I wanted a way to figure out specifically which features to build next for my users. I first looked for existing solutions, but most were $20+/month, or self-hosted and difficult to setup. Many of these tools had tons of cool features which justified the price, but I did not want all of that. I created Simple Feature Board with the intent of being as cheap as possible (free tria”
“A real problem to be addressed but with challenges. Assuming the scan results are accurate ( no false alarms ), will be the people to fix them or your product also provides tools to fix the inconsistency content all together automatically ?”
“Hi, I just found this plugin and you've done a great job with it so far. I wanted to recommend a feature request: Make the categories ("Type") multi selectable please. The main use case is that the crafter ones can really clutter the screen, but I'd like to be able to view all field levequests at once for example, or view all grand company levequests at once.”
“Is your feature request related to a problem? When the self driving inbox opens an implementation PR for a report, nobody is assigned on the GitHub side. The report knows who its suggested reviewers are (the latest suggested reviewers artefact), and it already uses that list to pick the auto start identity and to send Slack pings. But the PR itself lands with no assignee, so a reviewer only finds out about it through the inbox or a Slack notification, and their GitHub "Assigned to me" view stays”
Feature Request: More colors please! Or a custom color picker!
“Feature request Is your feature request related to a problem? Currently, we have 23 projects set up in our Posthog organization, and we plan to increase the number in the future. ( 100) When I moving to another project, it is too much trouble to look around this list to know where to click. Describe the solution you'd like It would be nice to have a favorite (star) function for frequently viewed projects, and if you favorite them, they would be located at the top of the project list. Debug info”