Honestly, I never viewed Slack as synchronous. I kept all notifications off, and checked it whenever I had a few minute break or wanted to catch up on our office's conversation.
Slack allowed anyone to contact me by tagging me or @here, so it was obvious when someone wanted it to be synchronous (therefore breaking my communication), but the grand majority of communication was asynchronous unlike email - which does a poor job of differentiating between messages that should (and shouldn't) break attention.
I work fully remote and that's what I think as well. It's a thing that let's you wait or respond immediately, up to you. That's the major selling point.
Depends on company culture, of course. But my team is also distributed from -8 to + 10 UTC. So nobody is expecting someone who is asleep to write back to them.
Another thing to note is the presence of other sources of communication, like GitLab issues. If you have those you don't always have to ping a live person in sync mode. Often you can just pick up an issue and do it with minimal input.
Hem, plain classic emails offer the very same thing: it's up to you respond quickly or leave the message behind... IMAP IDLE is not exactly a new thing...
They mentioned this in the article - "Slack is capable of being both sync and async, though we’ve noticed that there does seem to be some social expectation of a quick response on Slack regardless of how explicitly we state otherwise."
That is the first thing I do when I install a slack client at a new job. Turn off all the notifications. Then I check it when it makes sense for me.
I give team members my phone number and say "text me if you need something ASAP". People don't do that unless it really is important, in my experience.
At least for me, the whole problem with Slack is how many/how often I get @mentions or DMs, not the other stuff. Sure the other stuff is async, that’s not really the issue at least for me and lots of others
Slack allowed anyone to contact me by tagging me or @here, so it was obvious when someone wanted it to be synchronous (therefore breaking my communication), but the grand majority of communication was asynchronous unlike email - which does a poor job of differentiating between messages that should (and shouldn't) break attention.