How to Collect Product Feedback (Without Losing Your Mind)

The problem with "just use Slack"

Most teams start collecting feedback the same way: a Slack channel, a Google Sheet, or a Notion page. This works for about two weeks. Then the Slack channel becomes a graveyard, the spreadsheet has 47 duplicate rows, and nobody can remember which Notion page has the feedback.

The issue isn't laziness. It's that these tools weren't built for feedback. They're built for communication, data, and notes. Feedback needs something else: a way for users to submit ideas, a way for other users to vote on them, and a way for you to track what you're doing about it.

What good feedback collection looks like

A good feedback system has three parts:

1. A public place to submit ideas. Your users need a URL they can go to and type "I wish this product did X." No login hoops, no 5-page forms. Just a title, a description, and a submit button.
2. Voting. Not all feedback is equal. When 50 people upvote "add dark mode" and 2 people upvote "add Comic Sans support," you know where to spend your time. Voting turns noise into signal.
3. Status tracking. The fastest way to lose trust is to collect feedback and never respond. Users need to see that their idea is "Planned" or "In Progress." It shows you're listening.

The approaches (ranked by sanity)

1. Dedicated feedback tool (recommended)

Tools like FeedMango, Canny, and Nolt are built specifically for this. Users submit feedback, others vote, you update statuses. It's the right tool for the job.

2. GitHub Issues (for open source)

If your users are developers, GitHub Issues works surprisingly well. Reactions serve as votes. Labels serve as statuses. The downside: non-technical users won't use GitHub.

3. Google Forms + Spreadsheet (the classic)

Free and flexible, but no voting, no status tracking, and no public visibility. You're collecting feedback into a black hole. Users submit and never hear back.

4. Slack channel (please don't)

Feedback in Slack is like writing notes on water. Messages scroll, threads die, and your best feature idea is now buried under 200 messages about what to order for lunch.

Tips for actually using the feedback you collect

• Review weekly, not daily. Set a time each week to go through new feedback. Daily reviews lead to reactive building.
• Don't build everything that's popular. Votes show demand, not importance. Sometimes 3 votes on a security fix matters more than 50 votes on dark mode.
• Close the loop. When you ship something, update the status and let voters know. This builds trust and keeps people coming back.
• Separate feedback from bug reports. Use different boards or categories. Feature requests and bugs need different workflows.
• Make it public. A public roadmap shows users you're listening. It also reduces "when is X coming?" messages by 90%.

The bottom line

Collecting feedback is easy. Everyone has opinions. The hard part is organizing it so it's useful, and showing your users you actually care. A dedicated tool makes this dramatically easier. Whether it's FeedMango or something else, stop using Slack for this. Your sanity will thank you.