Email is generally a better async tool than slack/messaging because it has a generally longer response time expectation. Further when composing an email you ha

Email is generally a better async tool than slack/messaging because it has a generally longer response time expectation. Further when composing an email you have a big open canvas, and an implied workflow of writing, editing, and then finishing before you hit send. The workflow in slack tends to be ad-hoc, stream-of-thought, off the top of head burst-of-questions. As a recipient this can be incredibly disruptive. As an introvert it often strikes me that even the sender doesn't quite know what they are getting at until midway through. Obviously email can be used just as poorly, but the built-in workflow bias of the two makes this anti-pattern the default on messaging platforms. Further on the recipient end, it his harder to setup rules to triage important senders/content away from the noise in slack than it is in email. Lastly, slack especially gives the sender too many tools to disrupt & cause mayhem. You really only need 1 malicious user in your slack org to make it extremely noisy. On the email side, someone who is trying to get attention generally sends 1 email with "everyone & their mother" cc'd. On slack, they instead tend to drop into multiple different channels & DMs to try and get attention. Each of these messages to different channels/DMs may set off different threads of noise on the recipient side as people are unaware of other channels/DM recipients trying to address the question. Plus the ability to force more attention with @user/@here/@channel, and force notifications through even if recipient has them paused.