[ebzlo]

I think the distinction between async and sync messaging is really critical here and highlights a different form of communication that folks are incorrectly using Slack to solve.

When I was at Facebook, this type of communication was extremely abundant and took place on Workplace. When you are pushed information, there is some expectation to respond (as highlighted by the author). However, Workplace's opt-in type of communication via feed didn't have this problem. And interestingly isn't really prevalent outside forums and groups (which I don't think are used commonly at companies).

I think splitting out that kind of behavior was beneficial, it wasn't email (which is a push that people ignore), but rather a subscribe where there was no stigma to be late, and people could take their own time to catch up on posts.

[matchbok]

Exactly. 99% of workplace coms don't need to be synchronous. Slack assumes that they do. Thus you get tons of noise and chatter and the feeling that you have to check it all the time.

Hell, even the idea of a chat room isn't productive to getting "work" done at all IMO. If you aren't watching it every minute, you immediately lose all the context and knowledge. It's such a waste.

[smacktoward]

But it means everybody has to keep one eye on Slack at all times, which translates into huge "engagement" numbers for Slack. So "synchronous everything" may be bad for you, but it's great for them!

[sotojuan]

Nah. Just turn off all notifications outside of mentions. If people want to reach you they can mention or message you. I do this and don’t check Slack for hours or even a whole day.

Most problems people have with Slack are people problems.

[ams6110]

I'm not on Slack, we have Lync or whatever Microsoft calls it now at work. I have all notifications off, so I only notice new messages when I bring that window to the foreground.

[Benjammer]

>Most problems people have with Slack are _design_ problems.

FTFY