We try to solve that in two ways:
1. We'll intelligently bubble up stuff that has a lot of discussion or activity, along with the context, even if that activity is happening in other apps. (Lots of comments on a google doc).
2. I personally think the asynchronous nature of a feed stops people from spamming irrelevant garbage. In my experience, project channels always devolve at points to jokes/references/and stuff that people may think twice about posting to a wiki or feed.
The author addresses how to reduce the amount of notification spam in slack, but doesn't really get to the root of why there are so many notifications in the first place.
At Rendevu (https://rendevu.co), we think that's because people are attempting to use slack for more than it is -- mainly, using it to broadcast team information (documents / decisions / faqs), that then get pushed above the fold in channels by memes / gifs / other chatter, and then have to be reposted again and again.
We're building an intelligent feed that aggregates information from the tools you already use (Gsuite / Trello / Slack), and gives your team one place to stay on top of things. It's in alpha right now, but feel free to sign in and try it at https://rendevu.co. Any feedback is much appreciated :)
I think the alternative is posting important information to a feed that intelligently updates itself, rather than into channels where it gets pushed above the fold.
We're building this at Rendevu (https://rendevu.co) and running an alpha right now, feel free to check it out.
At Rendevu (https://rendevu.co), we think the problem you're describing is due to Slack's (or any messaging app's) inherent synchronous nature.
We're building an intelligent asynchronous feed that aggregates discussions from all the other apps you already use (google / jira / trello / invision), and gives your team a one stop place to find info that doesn't go stale like a wiki.
We're running an alpha right now at https://rendevu.co. Feel free to check it out if you get the chance.