The hardest part wasn’t building — it was knowing what users actually felt
The hardest part wasn’t building — it was knowing what users actually felt
Post
As a builder, I underestimated how messy user feedback gets once real people start using your product.
Not because users don’t care — but because feedback shows up everywhere:
Slack DMs
Random emails
One-off messages after meetings
“By the way…” comments that never get written down
The real problem for me wasn’t collecting feedback — it was losing context, urgency, and patterns. By the time I reviewed things, the emotion was gone and decisions felt guessy.
I ended up fixing this by routing feedback into a place the team already lived (Slack), so:
feedback arrived while it was still fresh
conversations happened naturally
patterns became obvious without dashboards
This completely changed how fast we shipped and what we prioritized.
Curious how other founders handle this:
Do you centralize feedback or let it stay scattered?
How do you avoid building off the loudest voice only?
(For context, this is what I built for myself and a few teams later: https://retour.tech)
Happy to share what worked and what didn’t if useful.
Replies