There’s a channel on your Slack called something like #wins or #closed-deals or #revenue. Someone set it up with good intentions. A deal closes, a notification fires, the team sees it. Simple.

Except it isn’t working. You know it isn’t working because the channel gets ignored. Because when something genuinely big lands, it disappears into the same feed as everything else. Because you’ve watched a rep close the biggest deal of their career and get three emoji reactions before the conversation moved on.

The problem isn’t that people don’t care. The problem is that your wins channel treats every deal the same — and when everything gets the same signal, the signal stops meaning anything.

A notification is not recognition. This is the thing most teams miss when they set up a wins channel. They’ve solved the information problem — the team knows a deal closed — but they haven’t touched the recognition problem at all. They’ve just created a feed.

Recognition requires weight. It requires the moment to feel different from the one before it. A €500 renewal closing is information. A €50,000 new logo closing is an event. If your Slack channel pings identically for both, you haven’t created a wins culture. You’ve created a ticker.

The rep who just closed the big one knows exactly how that close landed in Slack. They remember. It either felt like something, or it didn’t. And if it didn’t, that’s not a small thing — it’s a signal about whether this team actually sees what people do.

The fix isn’t complicated, but it does require a decision most teams never make: what actually counts as a win worth calling out, and at what level?

This means setting thresholds. Not arbitrary ones — thresholds that reflect what’s genuinely hard to close on your team, what represents real progress, what the team would actually want to celebrate. A five-rep SaaS team scaling from €50k to €500k ARR has different thresholds than a team running high-volume transactional deals. Both can have a wins channel that works. Neither will by accident.

Thresholds also solve a second problem: they stop the channel from becoming a compliance exercise. When everything posts automatically, nobody feels like they chose to celebrate anything. The wins channel becomes maintenance rather than meaning. When there’s a threshold — when something has to actually earn its place there — the posts that do land carry more weight.

There’s a related question most teams also skip: who needs to see what, and in what form?

A team-wide channel makes sense for deals above a certain size, or for new logos, or for anything that represents a genuine milestone. But the rep’s manager probably wants to know about every close. The CEO might want a weekly summary rather than a real-time feed. Finance has different needs again. Most teams end up with one channel trying to do all of these jobs, and doing none of them well.

The notification that reaches everyone should be the exception, not the default. The exception is what makes it feel like something.

None of this requires a complex Slack setup or a new tool. It requires someone — probably you — sitting down for thirty minutes and making a few deliberate decisions. What’s a win? What size warrants a team-wide callout? What does that callout actually say — is it just a deal name and a number, or does it include something human, something that tells the story of the close?

That last part matters more than most managers think. A message that says “Deal closed: Acme Corp, €45k” is information. A message that says “Emmet just closed Acme Corp at €45k — six-month cycle, three competitors in the mix, closed on a Friday afternoon call. Huge one.” is recognition. The difference is thirty seconds and the decision to treat it like it matters.

Recognition that feels real doesn’t happen automatically. It happens because someone decided it was worth doing properly.

The wins channel is a small thing. But the small things are usually where you can see whether a team’s culture is intentional or just running on default. Most teams are running on default. The channel exists, the notifications fire, and everyone quietly knows it isn’t quite working — without ever stopping to ask why, or what it would take to fix it.

It wouldn’t take much.