[diggan]

> 1. Gitlab somehow statistically tracks public / DMs. Haven’t implemented at my startup but if anyone knows a simple way to do - please let me know.

If you use Slack, I think the admin panel already contains the number of messages in channels VS DMs. Long time I last saw it myself, but I think it was missing a breakdown on how many members of the Slack received the channel/"public" messages (as not everyone is part of every channel, 2 member channels vs 200 member channels for example), maybe it looks different now.

> 5. Slack Is Great But (SIGB) - teach people that they don’t need to read everything. Many people get overwhelmed

I think this happens when Slack is the "source of truth", because the ephemeral feeling it gives since it's a chat ultimately. If you instead use a wiki/whatever to actually collect things that are important, there is less stress about possibly missing out on important things. Make summaries by week/month and it'll be even easier for people to catch up easily, which means even less stress :)

[patrickhogan1]

Thank you! I'll check out the Slack admin panel! I removed that item from my main message because I was concerned some people might misinterpret "tracking" as something invasive (e.g., reading messages). What you're describing is exactly what I'm looking for—just the stats—to support public disclosure and knowledge sharing.

[Buttons840]

The "source of truth" and the place you post dank memes and ask what people are doing for the weekend--those shouldn't be the same place. Slack is not a good "source of truth".

[mozman]

Slack is meant to be addictive. I only use the web client and modify it with tampermonkey

All notifications disabled and I only read when pinged. davison updates are the only mechanism allowed.

[j33zusjuice]

How the hell do you get by with that? I’m jealous. I’ve gotten pinged by my fucking EVP for not responding to questions in chat fast enough (non-critical, too!). At least no one gets on me for missing emails. I don’t even read those.

[diggan]

> How the hell do you get by with that?

You have a company policy that allows that. For example, if anything is decided in Slack, it has to be "codified" somewhere else, like a wiki. Then you'll be able to justify not reading through all messages.