User Feedback Integration Strategies for Smarter Product Decisions

I’m honestly frustrated.

I’m not even charging. I literally removed sign up and login so people can just open it and use it immediately. Just open and try

And still received nothing. Not even a single line of feedback.

I’m not even asking for money. Just thoughts.

It’s also hard to even find the right people to show it to. It now feels like one of the hardest part is finding people who care enough to say anything.

how are you guys actually getting real users to respond?

What platform are you using?

Are you posting on Users? Twitter? LinkedIn? Discord?

Are you cold DMing people?

Are you offering incentives?

Are you hopping on calls?

Are you running ads just to get testers?

I have a small EdTech product with a few hundred users but find myself struggling to engage with them beyond support tickets. This makes it hard to understand what is working well, what I can improve, and to gather testimonials for social proof on my landing page.

Does anyone else struggle with this? What have you done to get better engagement from users?

Hi, all!

First post here after a few months of lurking.

I was wondering if any of you would be willing to share your methods of processing and consolidating user feedback and feature requests* where you have multiple channels and ways for users to share their thoughts?

Where I work (a SaaS company), we have lots of different places where users make requests or provide feedback:

- in-app feature requests
- requests and feedback made via email and live chat
- conversations had with members of our Sales team
- review sites

etc etc.

We do capture feedback from our apps and store it all in one spot, but requests that come in via other channels can be harder to keep track of. I have colleagues in CS and Sales who will do their best to log feature requests, but ultimately this is a very manual task and we end up with suggestions and requests in multiple locations.

Ideally, I'd like to have everything in one lovely pool that's index- and searchable by product teams, but I've yet to find a solution.

Any tips or insights you'd be willing to share from your own experience?

Thanks in advance!

*I should stress that we don't simply churn out features based on requests, but they do provide hints at areas that we may want to investigate further.

Quick curiosity question for no-code founders (Bubble, Webflow, etc.):

Once your app is live, how are you actually gathering user feedback today?

• Embedded forms (Typeform, Tally, etc.)?
  
• Sidebar widget / in-app feedback tab?
  
• Hotjar / Microsoft Clarity surveys?
  
• NPS emails or in-app messages via Intercom/Customer.io?
  
• Just a Slack community or email?
  
• Something else?

Especially interested in lightweight setups for bootstrapped apps with

Hey everyone!

I’ve been a PO for a bit and just transitioned to a PM role at a startup a few months ago. As a PO at my old company I was never permitted to talk to clients and this is a weak spot for me.

I want to foster a Problem first, Solution second approach with my new role which means lots and lots of user interviews. Right now, we have a mile long list of features with no validated user input and I want to show leadership a more data based approach to picking our features for the roadmap.

That being said, any advice for collecting feedback? Right now I’m compiling a list of power users for specific features with a plan to set up some open ended reviews to see how they use our product and what their pain points are.

When you're collecting feedback from users, how do you decide when you actually have enough information to take action?

Sometimes you hear the same suggestion from a few users and it seems important, but you're not sure if it's a real pattern or just a small sample.

Do you wait for a certain number of people asking for the same thing?

Or do you look at other signals like:

• user behavior

• churn reasons

• feature usage

Trying to figure out how others approach this balance between listening to feedback vs. just building.

Hey product peeps - my team has been struggling with gathering user feedback and wanted to get some advice, as we're really keen on making data-driven decisions (it's our core focus this quarter)

Problem: Whenever we push out surveys or feedback requests in-app, we either get very little response or we end up overwhelming our users with too many questions - we've literally had people write this in the comments :(

Curious what are your go-to methods for gathering actionable user feedback.. specifically without overwhelming people?

Any specific tools or approaches you swear by? (specific tools would be faaaantastic)

Hey everyone, curious what folks here do when they're in the super early stages, like you have a hypothesis about a problem but no product yet. How do you find the right people to talk to and actually get useful feedback? Cold LinkedIn outreach? Something else? Would love to hear what's worked for you. Thanks!

I’ve been trying to understand how people handle feedback in early-stage products and honestly it seems kind of messy.

Some people use forms, some use tools, some just rely on emails or DMs…

Curious what you’re doing right now — and more importantly, what’s annoying about it?

Google forms for your sales/CS team and email/chat requests. Pin it in their slack channel.

create a form with structured fields (customer name, channel/source, request category, brief description, customer segment, rough priority signal/deal size) and have it feed directly into a Google Sheet.

That sheet becomes your searchable pool, and you can filter/sort/aggregate by any field.

You should already have outputs for in app requests and reviews. If not create them.

Getting real user feedback is always a struggle. What’s worked for me is mixing in-product feedback (like micro-surveys) with direct, personal outreach—email, or even niche communities where users already hang out.

Also, framing matters. If it feels like ‘give us feedback,’ people ignore it. But if they feel like they’re part of making something better, they engage way more.

Happy to bounce ideas if you're down.

Something I’ve been curious about.

User feedback comes from everywhere, support tickets, sales calls, Slack messages, interviews, analytics, etc. In practice, how does that feedback actually make its way into product decisions on your team?

Is it centralized somewhere, or does it mostly live across different tools? And have you ever realized later that something important was missed because the signal was scattered?

Everything starts with documenting what you want to build, then prioritizing that list. I'd get all of your features into a spreadsheet. One row per feature. Then add the following columns: Effort, Expected Value, Expected Savings. In those columns, place 1-10, where 1 is small and 10 is large. You can use Claude or any LLM to help you bucket the features into Quick Wins (Do Now), Big Bets (Do Next), Fill-ins (Do Next/Later) and Time Sinks (Do Later) by calculating the values in those columns. This should help with prioritization. Note, "Expected Value" should align with your KPI's. You could have multiple KPI's (i.e., revenue growth and NPS improvement). In those cases you could consider one column each for KPI, with individual scores. There might be other columns to add.. for instance if a feature you want to build has a dependency on a partner or another part of your organization, you could add that as a column and factor it into your prioritization calculation.

I work as PM for a b2b software company with limited access to customers. I have been responsible for couple of products since last few years but most of them were built when I took over and it was mostly about finding features that solved customer problems etc.

However now I am in charge of a new product where I begin with a clean slate. One limitation is that we don't usually have access to our end users that easily - coz 1. We sell to businesses and then to end users 2. End users tend to be super busy not interested in giving a lot of "interviews"

I am interested in knowing how fellow PMs solve this problem. How does your product discovery process look like? How do you customer insights for your products in a more "proactive" way? The reason I ask people are unhappy with the products they use but sometimes don't complain - nevertheless affects their purchase decisions.

Thanks!

So I haven't tried it yet, but someone recommended I try hotjar, apparently it can help you see how your users are behaving

It might be more useful then trying to get unresponsive users to give you actual feedback.

Also struggling with this (solo PM and drowning generally, but especially with feedback) so following!

The scattered signal problem is real and it gets worse as you grow, not better.

The pattern I've seen most often: feedback lives in support tickets (Intercom/Zendesk), feature requests live somewhere else (Canny, Linear, a spreadsheet), and sales/CS insights live in Slack and call recordings that nobody has time to synthesize. Each source captures a different slice of the user — the frustrated user, the power user, the churned user — and they rarely get stitched together into a coherent picture.

What's worked best in practice:

A single "voice of customer" owner — not a tool, a person (or at least a role). Someone whose job includes reading support queues, listening to call recordings, and translating patterns into product language. Without an owner, even centralized tools stay noisy.

Tagging at the source — every support ticket and sales call note gets tagged by theme before it's closed. Raw volume of a tag is a proxy for urgency. Not perfect, but better than gut feel.

Monthly synthesis — a short doc (not a dashboard) summarizing the top 3-5 user pain themes with verbatim quotes. Quotes move product teams in ways that charts don't.

Curious whether the problem for you is more capture (feedback not being recorded at all) or synthesis (it exists but nobody's connecting the dots)?

I’d treat it like this: 3–5 users saying the same thing, paired with a visible signal in the data (churn spike in a segment, people dropping off at the same step, feature used in a weird workaround-y way) is usually “enough” to ship a small, focused change and then re-measure. Think of feedback as a hypothesis generator and behavior as the fact-checker, and only go all‑in when both are yelling at you in the same accent.

There's no magic number. If three paying customers ask for the same thing unprompted, that's usually enough for me to take it seriously. If 50 free users ask for something, I'm more skeptical.

Weight matters more than count. A request from someone who's paying and actively using the product is worth way more than someone who signed up last week. Same with churn reasons, if multiple people leave citing the same gap, that's a stronger signal than a bunch of upvotes on a feature request.

I track feedback in UserJot and the voting helps surface patterns, but I don't treat vote count as the final answer. Sometimes a low-vote request from a high-value user segment is the right thing to build. Sometimes the most upvoted thing is just the most obvious thing, not necessarily the most impactful.

Honestly you can overthink this. If you keep hearing the same thing and it fits where you want the product to go, just build it. You'll learn more from shipping than from waiting for statistical significance.

For us it's more about sample size than the exact number of requests. If we can collect feedback from a decent group of users and see a clear trend, that's usually enough confidence to move forward. We’ve been using SurveyMars to gather that kind of data because it’s quick to set up.