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)
“Ongoing for 2 years we adjust it weekly at first but now once in maybe 3 months. It will pay off eventually. We ask the users opinion when making the wrong choices what he or she would want to see and put that into the…”
“I've found it helps to keep the utility narrow until you see users hacking together their own workarounds for that review step, like dropping Miro notes next to the pins. If they aren't forcing a manual fix, the demand isn't there yet. I normally aggregate data from Reddit to validate first. Happy to share some examples of how I have done this in the past.”
“Has removing a feature ever improved your product or made the user experience better? what was it and why did you decide to remove it? submitted by /u/ari_k_e [link] [comments]”
“I don’t like them at all. I hate how it mixes in archived products that now have to be removed with an additional filter. It also screwed up collections that used an “OR” and puts a bunch of random shit in there what I have no clue how it even got there. It was easier to sort before too, and if you have multiple pages of products then it’s even harder to sort. The only sorting upgrade that I would find useful would be to move out of stock items to the end of the collection automatically, and the”
“I’m curious how other solo founders and small SaaS teams are managing customer feedback. Are you using something like Canny or Featurebase, keeping requests in Notion or Trello, working from a spreadsheet, or just searching through old emails and support messages? I wanted something super simple: a small feedback widget, idea board, voting, statuses, public roadmap, and changelog in one simple workflow. That’s it… no bloat. I’ve been building BareFeedback. The working version is here: https://ba”
“As far as I know, I think Telegram offers now the ability to make sub-group. The solution to your issue is to create multiple sub-groups - one for support, one for feedback, one for general chat,etc. Even localised ones if you have multiple users from a country and they're super active. In the past, we used to get the messages on Telegram but asked the users to complete a ticket on a website so we'd have all the tickets in one place.”
“What magic bullets/tweaks have you successfully implemented to improve the quality of incoming tickets? We have users who will submit low effort tickets that are either un-actionable due to lack of details/critical info, have misinformation, or are the completely wrong form? We have specific forms for specific common issues that are clearly labeled. The forms prompt for the minimum necessary info for the particular issue; hostname; ilo hostname/ip/pw, etc. When using the correct form there is au”
“By the way, I just requested an expert audit from the adorable Produck 😂 I can't wait to hear his assessment. I can't yet speak to the quality of the report at this time, but I have to say the experience so far has been delightful. I love the overall premise, I adore the branding & I'm just such a fan of the wonderful homepage animations & quirky on-scroll behaviour. This is a super unique, memorable & terrific site.”
“We've experimented with a few different approaches, and asking people to leave the product almost always meant fewer responses. Even something as simple as opening a new tab or asking them to sign in again created enough friction that many users just didn't bother. What worked better for us was keeping feedback lightweight. A small embedded form for new ideas, plus a way for users to upvote existing requests, gave us both qualitative feedback and a rough signal of demand. Votes aren'”
“well rather disappoint few people than turn the product into a mess. not every popular request is worth building....”
“I struggle with this a bit too mate. It’s hard not to just keep looking at the stats go up and down, and hoping more peeps with review and so forth as well as find time to do all the rest of it. I started in April and I too am hoping this will settle with time too :) You are definitely not alone in this!”
“Every quarter the top requests roll in, and every quarter the loudest ones are features that would turn my product into something bigger and blurrier. This time I said no to three of the five. Here's the reasoning I keep coming back to. The people asking loudest for the big features are usually the ones closest to churning anyway, because they want a different product than the one I'm building. Building for them costs me the focus that keeps my actual core users happy. When I went back t”
“Thank you for taking the time to test it and write such detailed feedback! It's really useful. You're right about the sign-up flow and the lack of measurement guidance—I'm already redesigning both. The gender/category point is also something I'll improve by letting users choose the shopping category before recommendations. I also appreciate the comments about the target audience and messaging; I'll make the homepage clearer about what Malabis does. Thanks again!”
“this is really good i also want to add that i want my app to be like a messaging app where i message task instead of adding them”
“Every product gets feature requests, but saying “no” is sometimes the better decision. Was there a feature everyone wanted that you decided not to build? Looking back,was it the right call? submitted by /u/Basic_Bad6389 [link] [comments]”
“Leave a comment on this post if you have any of the following types of feedback that you would like to reach the Notion Team: 💡 Feature Request 🗳️ Product Feedback Please begin your message with the indicating category above for greater clarity. e.g.: 💡 Feature Request — I would like this feature . Please aim to list a singular feature request or bit of feedback, so that upvotes can clearly represent which features users wish to upvote. The goal is to consolidate meaningful feedback making it”
Absolutely. Well said. Give the people what they want and need
“thanks so much! i’m trying to improve the UI/UX and make it more accessible. if you don’t mind, what parts of it did you find to be too noisy?”
“I’m not arguing for dashboards. I’m telling the OP to figure out the users’ JTBD An individual prompting a report is fine, but the second 2 people try to prompt the same question/report, these days it’s unlikely they’ll produce the same thing. A department dashboard has different JTBD than an individual’s.”
“Honestly, the Slack pile-on might be more useful than the polite one-to-one replies. One person complaining could be an edge case, but if a whole thread jumps in, the problem is clearly shared and annoying enough to interrupt their work. I’d probably learn more from those moments than from trying to make every quiet user talk.”
“There are a lot of templates for adult and kids. Just my 2 cents -- center the category filters and make them a little bigger at the top of the template cards. When user clicks a category, would be slick if the filtered templates fly into place and the page autoscrolls down to the templates at the same time.”
“I'd be happy to do a formal review and give honest feedback. Submit a feedback request on BetaBloom.”
“I agree with you bro. Feature requests tell you what users think they want, but confusion tells you where the product is failing. I’d prioritize fixing confusion every time”
“A good beta test should measure whether users can complete the main task without help. If people repeatedly ask what happens next, that is probably a product design issue rather than a documentation issue.”
“🗳️ Product Feedback – be honest with users when you downgrade AI functionality on the back end instead of silently introducing limits and making people pay the same price for a downgraded product”
“I'm researching how small teams (1-30 people) collect product and workflow feedback for users. Do you use tools, if so, what? (Canny, Frill, Nolt, Zendesk, Intercom, Google Forms, something else?) What's the most frustrating part of your current process? If you've tried feedback boards, did they actually help you prioritize work? Do you spend more time reading individual feedback than actually acting on it? I know Canny is pretty popular but I want to know if the feedback boards (wit”
“For qualitative feedback I use an in-product widget that captures it as users experience the app. I've been using Reqio - it's embeddable, captures bug reports, feature requests, and unexpected behavior with pre-sorting on submission. The two-way async threads let the team reply in a dashboard and users get notified by email. No per-user pricing so it doesn't blow a solo founder's budget.”
“I’m building one specifically to attack the hassle of reading through those 100s of feedbacks by just listing 5 actions you need to do and why doing it (risk of churn from specific topic, old feedbacks left unnoticed, trends on building a feature, and so on) based on your live data (currently runs on the background every hour but you can manually run it always) It also groups and dedupe feedbacks together dynamically, you don’t need to mark duplicate or split or merge I would really appreciate i”
“Hi everybody, To be completely honest i am a people person so my first thought was going around asking people for their opinion about what software they use and what they need to make it better but that is not the way to go anymore. Last post i made to ask around was met with hostility. Or they asked a ton of money to answer a question that might help them in the future. I always get the answer "we don't work for free" or we work for a living in contrary to you or you scum trying t”
“Working with community data, one pattern keeps showing up: participation is heavily skewed. You might have thousands of users, but feedback comes from a small, active slice. The rest don’t respond, don’t vote, don’t fill out surveys. Then decisions get made based on that narrow input, and later you see weak adoption or indifference. It’s a sampling problem, but we often treat it like a volume problem. A newsletter I follow mentioned voice.fun recently. Early Solana concept where people record op”
“I tried spreadsheets, Notion and Discord for months. Eventually I build a web app by myself to track the feature request or feedback from my user. There are other apps that provide feature to track your feedbacks like canny, upvoty etc but they are expensive and really bloated with enterprise features.”
“The question that gets me past polite feedback is, "What did you expect to happen next?" I ask it immediately after someone hesitates or backs out, without explaining the screen first. Their answer usually reveals the mental model they brought in, so you can tell whether the problem is confusing UX or a value proposition that never landed. A second useful one is, "What would you do instead if this disappeared tomorrow?" If the answer is basically nothing, that is a good signa”
[Buffer] ★★ 2/5 (v15.6) — I wish I could turn off certain features like AI and the comment score. I don't want all my data being fed to an AI, and I…
“every feedback friday is just twenty people trying to build the exact same scheduling app”
“I think having a clear priority system helps a lot. Not every request deserves the same urgency. We started separating bugs, urgent issues, feature requests, and general questions, and it made support feel much less reactive. The loudest customer isn't always the highest priority.”
“In many warehouses, valuable feedback comes from floor workers, supervisors, drivers, and operations teams, but it often gets lost across emails, chats, spreadsheets, and meetings. How does your organization collect and track operational feedback? Paper forms? Spreadsheets? Internal software? Team meetings? I recently came across a tool called Spotem that focuses on organizing feedback and insights from different sources, which got me thinking about how warehouses handle this process today. Link”
Send email and give them a bonus for participating in a form feedback
“I have been noticing a pattern while building Chirpy, a social media planning tool, that has helped me interpret feedback more clearly. When people describe a problem, they usually describe the symptom, not the workflow. A few examples: "I need better AI captions" The workflow problem is often not the caption. It is that they have no repeatable way to turn one business event into platform specific posts. "I need more content ideas" The workflow problem is usually decision fat”
“💡 Feature Request — native backup solution. This would go a long way in pitching Notion to my organization”
“Leave a comment on this post if you have any of the following types of feedback that you would like to reach the Notion Team: 💡 Feature Request 🗳️ Product Feedback Please begin your message with the indicating category above for greater clarity. e.g.: 💡 Feature Request — I would like this feature . Please aim to list a singular feature request or bit of feedback, so that upvotes can clearly represent which features users wish to upvote. The goal is to consolidate meaningful feedback making it”
“I’m developing exactly this system which helps with feedback and support management.”
“I like this approach because it turns scattered feature requests into something structured and manageable instead of reacting emotionally to whoever is shouting the loudest in the moment overall system”
“i would rather recommend not working on a feature that is not mentioned by too many people. One way you can solve this is by compiling a weekly or biweekly pole of all the features request and then ask in your community which of these problem you want solved in next two weeks. ( check dm though perhaps i can help you out more )”
“Hello, thanks for offering to participate in this feedback exchange. I did my review and first impressions on your iOS app. To answer your questions First impressions. Visually, I think you show from first impressions that you are not some shmo making an app, but took time to make sure that the design looks professional. Well done on that. The “sleep, heart rate and smart ring” description in the App Store didn’t make sense to me, are you limited on characters? It might make more sense to say so”
“Was this coming from one larger customer or was it that multiple customers started asking for the same thing?”
“This is how product scope starts expanding. One request sounds small then you realize it touches the entire user experience”