Synchronous chat is spam and we need to be better about understanding the productivity hit that cokes with always-on comms where we expect instant response.
Until one day a manager sends something urgent, and then explodes in anger because 30 minutes later no one has reacted yet.
To completely convey that there's no timeliness requirement for even a basic acknowledgement means you aren't actually managing anyone and/or your team is so gifted in efficiency your position isn't really needed in that organization.
I wonder if you're more of a mentor they go to when something isn't working or you're just wasting some company's time and money posting useless crap on their chat.
Are you just talking about Slack or are you talking about other methods of communication? If it's the former then wtf point does it serve other than as a morale booster to goof off with.
I rarely need something done with any degree of urgency. That generally implies a lack of planning on my part. If my team is functioning correctly, everyone knows why they should be focused on, what's next, and how that fits into the roadmap for the near term, generally quarterly.
In my team people look at it when they have the time or could use a context switch, and if you need them immediately adding @username send them a notification during business hours.
Which, of course, is only one person's experience amongst many, and different people will have different experiences.
For people like me, however, the problems listed in this article are painfully obvious, especially with regard to false sense of urgency. When everything is urgent, nothing is urgent, except my heart rate.
Slack isn't really the issue here: it's any form of synchronous communication (IRC, someone coming to your desk, getting a phone call). Slack just happens to be the latest flagship for the interruption armada, swooping in with their false urgency and lack of sufficient information.