On a personal level, you could mute channels and only read them when your highlighted words are used (your name, project names, etc.)
On the opposite end, you might like the tool Threads https://threads.com/? It acts more like an asynchronous message board for communication. When a conversation needs to happen, you invite the relevant people to the thread. The thread is publicly available to anyone in the channel to read, but it doesn't notify them by default. You can still tag someone into the thread for their perspective. Decisions that come out of a conversation can be highlighted so that anyone can find the relevant information without having to read the back-and-forth.
Either way, when there are information workflow problems at an organization, those are usually caused by poorly designed or enforced internal processes, not the tools themselves.
I can't find the article that I read, but someone mentioned that it's beneficial to have different communication tools for short-term and long-term memory. Slack is great for quick, one off conversations. At the point that you find yourself discussing a larger issue and coming to a decision with long-lasting impacts... or needing to refer back to information frequently... the information should no longer be living in a chat application.