I'd add in IM for quick 1-to-1 chats but that's all.
It has a way to go, but I found it the right mix of persistent, long-form discussion and decision making using Threads, and sync communication using Messages. It's the best of both worlds, if you can educate a team to use it properly.
On your point, slack has brought fluidity and lightheartedness to our internal comms. IMHO less demanding than "chat apps" and way better than email chains for internal comms.
I think you meant "synchronous" here ;)
EDIT - thanks to everyone correcting me on the sync vs async! I fixed it in the original comment.
https://www.worldwidelearn.com/education-advisor/questions/s...
https://status.net/articles/synchronous-vs-asynchronous-comm...
In my part of the world people will cringe and frown if they heard I am not using WhatsApp. I can understand them, I'd probably do the same thing if I heard someone does not use email. Personally I have trouble and probably mild OCD just to check every emails in my few email accounts, imagine going through all the Whatsapp groups messages. I'd rather voluntarily go to hard labour rather than reading the WhatsApp group messages.
What we need is an email++ with asynchronous nature of email and the convenient but not the intensity of WhatsApp, if that makes sense. Google Wave probably come close but it came earlier than expected and gone as soon as it arrived. Perhaps someone can utilize CRDT/Automerge to make it even better than Wave by going local-first.
I have trained my colleagues and boss to never expect a response right away. We’re also forced to use Skype at work which is a plague because people are lazy and will call about anything and everything without thinking it through. So same thing there, I’ve disabled all sounds, filter notification emails away, set my self to busy all the time, and never answer calls when they come in except it it was agreed upon beforehand (so, like a meeting)
I try and force these incurable skypers to send an email instead: it forces them to really think their stuff through, organize it in a more structured way, and takes me two minutes to answer instead of having a 15 min call that is all over the place.
And I don’t get interrupted while trying to visualize complex things in my head.
This is a great way to handle people who jump straight to "let's just do a call, it'll be easier [for me]"
For people who are like this, I will often just say I'm not available for a call for a few hours, and ask them to send me a written message in Slack instead. Most of the time, I am able to just help them async on Slack instead of spending 30min-1hr (x2 since we're both in it) in a call.
You said "asynchronous communication is detrimental to your health". Since asynchronous=email, I read "email is detrimental to your health". I thought you meant the contrary (slack is detrimental to your health -> synchronous communication is detrimental to your health) so I though it was a mistake.
Wasn't it?
Threads/Conversations are the only way to talk in normal team channels. This means that messages are automatically grouped on topic and you can ignore the ones you don't care about. I have never worked with a Slack team that used threads effectively and so you regularly end up reading a load of stuff you don't care about to find the stuff you do care about.
Separation between a Team channel and a chat channel. Chat channels are more like normal Slack conversations - they end up being fairly synchronous. The Team channel is where the more asynchronous stuff goes. We have a strong project convention (almost a rule) to use use a Team channel if more than 2 people are involved. It helps visibility and means that conversations default to async. But if I write a direct message to someone then it's because I want to interrupt and get an answer and so they get pinged.
This means I get pinged a few times a day about things I need (as SW Lead) to deal with, and the rest of the time I can just catch up on threads when I'm waiting for a compilation.
For context, my company (https://prestodoctor.com) has spent tens of thousands of dollars on Front licenses, so I'm not just some random nay-sayer :-)
Slack is detrimental to team communication in several ways, and bringing it to email is a mistake imho. Slack combines the stress and urgency of text messaging with the importance of email. Your Slack becomes a Facebook or Twitter feed - another infinite feed that addicts you to some level. Since it's a chat, the conversations are shallow and disorganized. For example, search never worked properly in Slack for me. Furthermore, synchronous communication has proven poor for wellness and work-life balance.
I know Slack just got acquired and its the hot new thing but email is great as it is - its our ways of using it that need to change.