The Problem With Collecting Feedback in Slack, Email, and DMs
Customer feedback is valuable, but when it's spread across Slack, email, DMs, and support chats, important insights get lost. Here's why scattered feedback leads to poor product decisions and how to fix it.
Jessé Cruz
4 min read
.png)
At first, collecting feedback feels easy.
A customer sends an email.
Someone opens a support ticket.
A user messages you on Slack.
Another sends a DM on X.
You tell yourself:
I'll remember this later.
You won't.
Feedback starts scattered
When you're building a small product, feedback comes from everywhere.
- Slack
- X
- Discord
- Support chats
- Customer calls
At first, this feels like a good thing.
Users are engaged.
They're sharing ideas.
They're helping you improve.
But there's a hidden problem.
Every piece of feedback lives somewhere different.
The feedback graveyard
Most feedback never gets lost immediately.
It slowly disappears.
A customer asks for a feature in Slack.
A few weeks later, another customer asks for the same thing by email.
A month later, someone sends a similar request through your support chat.
You don't connect the dots.
Not because the feedback isn't important.
Because it's scattered.
Eventually, your roadmap becomes based on memory.
And memory is a terrible product management system.
The loudest voice wins
When feedback is spread across different channels, another problem appears.
The loudest users get the most attention.
The customer who sends five follow-up messages feels more important than the customer who quietly submitted a great idea once.
This creates a dangerous bias.
You start prioritizing based on visibility instead of impact.
No visibility, no patterns
The real value of feedback isn't the individual request.
It's the pattern.
One request means almost nothing.
Ten users asking for the same thing means something.
But you can only see patterns when feedback is centralized.
Otherwise, every request looks isolated.
The hidden cost
The biggest cost isn't losing feedback.
It's losing confidence in your decisions.
When someone asks:
Why are we building this feature?
You don't have a clear answer.
When someone asks:
How many users requested this?
You don't know.
When someone asks:
What should we build next?
You're guessing.
A better approach
The solution isn't collecting more feedback.
It's collecting feedback in one place.
A place where:
- Requests are searchable
- Similar ideas are grouped together
- Users can vote
- Priorities are visible
- Roadmaps stay connected to feedback
The goal isn't to create more process.
The goal is to stop relying on memory.
Final thoughts
Feedback is one of the most valuable assets a product has.
But only if you can find it later.
The moment feedback starts living across Slack, email, DMs, and random conversations, you're no longer managing feedback.
You're managing chaos.
And chaos doesn't scale.
Best,
Jessé