Back to browse
How do you prioritize user feedback without going insane?

How do you prioritize user feedback without going insane?

by superproton·Feb 18, 2026·2 points·0 comments

AI Analysis

●●SolidSolve My ProblemSlick
The Take

Pretty spare and focused: a public voting board, straightforward idea cards and roadmap/privates boards, plus integrations called out (Jira, Linear). That's useful if you just want a single canonical place to point users. But it's solving a very crowded problem — the UI looks tidy, but there's no obvious differentiator like advanced prioritization, analytics, or unique workflows that beat GitHub Issues/Canny for teams that already have a stack.

Category
Target Audience

Indie makers, product managers, small SaaS teams and community-driven projects

Post Description

Genuine question for HN – I've been struggling with this for years across side projects and my day job. Feature requests come in from everywhere: Slack, email, Twitter DMs, GitHub issues, support tickets, random conversations. I've tried spreadsheets, Notion databases, pinned messages – nothing sticks. The loudest users win, not the best ideas. The problems I keep hitting:

No single place to point users to when they say "I have an idea" No way to let users signal what actually matters to them I forget half the requests within a week Zero visibility for users on whether their feedback was even heard

I got frustrated enough to build something. It's called Plaudera – a dead simple public feedback board with voting. I'm literally using it to collect feedback on itself right now:

https://feedback.plaudera.com

But honestly I'm more curious about what's worked for others. Do you just live in GitHub Issues? Is there a workflow I'm missing? For those running small teams or solo projects – how do you decide what to build next?

Similar Projects

SaaS●●Solid

CandyDocs – Simple, developer-friendly documentation for SaaS teams

It bundles knowledge base articles, a public roadmap with voting, structured feedback boards, release notes and API reference into one branded portal — exactly the convenience product teams ask for when they're juggling GitHub issues, Canny and a separate docs site. The admin UI in the screenshot (analytics, content counts, role controls) reads clean and usable, but this lives in a crowded field; success will depend on smooth imports, strong integrations and demonstrable SEO/search benefits.

SlickSolve My ProblemShip It
mukul767
203mo ago