Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Async communication = email overload?

Now I’m the first to say I find synchronous communication (eg Slack) to cause massive productivity loss for an organization & can also cause employee burnout … but how do companies that have a culture of async communication not fall into a similar bad issue of email overload?



My gut feeling tells me that as of late I am not able to stay on top of my inbox.

The past 3 years I was able to leave for the day with no unread messages.

The last few months I am unable to keep up. ~20 unread messages and several unanswered Skype chats each day.

Other team members also noticed an increase in the amount of mails.


what makes you think that Slack must be synchronous and that asynchronous == email?


I’m curious now, what would you view then as examples of both synch and async communication?


I think async and sync is more about expectations, with the caveat that a non-recorded zoom meeting is sync, while a recorded zoom meeting can be async. That being said, I feel it's my responsibility to have my notifications tuned properly so I'm not interrupted.

So to me synchronous comms are comms that can't be consumed asynchronously. The only text version of that I can think of is an exploding Signal message or similar. Any non-recorded video message is synchronous.


A key example of async communication are tickets/issues and merge requests.

Slack can be both depending on the situation

Calls are definitely sync, although I guess voicemail is async




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: