Cut to me, in my house, flipping off your Slack message. Respond, or mark as unread, don't confidently ask me to do extra, completely redundant work for you.
If you don't like the office norm of Slack and wish it was email then too bad, same if it was the other way around too. It's now your problem to bridge Slack->email or email->Slack.
This is terrible woefully out-of-touch advice if the audience is anything other than executives who have enough clout to make the world move around them. If you're one of those people that is important enough that you can make everyone who wants to talk to you use your preferred communication medium then this might be actionable advice for you.
I swear we as a society didn't understand, didn't value the work administrative assistants and secretaries did (organizing all your communication being one of them) and we've been trying and failing to replace them ever since.
or risk forgetting to help you.
...or needing to scroll back through hours/days of messsges (ones that actually could be immediately answered or discussed, hopefully),
to find all the times they've agreed to help someone,
instead of you putting your (intricate, and/or technical request, from the context) into an email, ticket, or whatever you've all agreed upon.
I think that is the inflection point.
If you don't have a system in place, as an org, many people just don't think about it - find the closest, easiest text box, Send-Tweet. Or holler across the aisle of cubes at someone who is trying to concentrate...
Emphasis mine, this is literally the point I'm making but from the perspective of an office that agreed to use Slack. Which is most offices that have Slack. If email or a bug tracker is the norm then you use that, and you would be equally rude if in that situation you tried to make them Slack you instead because "you don't check email."
I know that's probably what their marketing department would like to hear, but that sounds horrific unless you're doing something quite mundane.
Which...if you're reaching out with a request time-dense enough that someone asks it be forwarded to email...it sounds like you're not doing mundane stuff.
etc
Oh, well the office also uses email. There are in fact places that use slack for time sensitive things and email for other things.
Given the author’s net worth and close relationship with zuck, this line from the post (and the whole post honestly) is his way of telling you how he’s going to dictate communication processes. So there are lots of things that might sound reasonable or interesting but at the end of the day the author just rabidly wants to monetize you.
> If someone sends me a chat that isn’t time sensitive, I redirect them to email
Also, to parent and siblings: does it change your mind if you factor in that the author is CTO at Meta? Not in a simpering "ooh he's so important" way, in a practical "he gets a lot of communication and having a system helps" way.
If the CTO wants to convey the message that, in the future, such requests should come through email in the first place, it's still better to wait, then respond through Slack, and then leave a note about protocol in the future. Why is it better? Because they're leaving this note when they aren't so busy, rather than interrupting whatever they were doing to write it.
They're people. Get them out of the ivory tower!
Not to imply I have a Rolodex full of these types, but I'm on first name basis with at least three. I'm just an SRE/Architect. Whoopee!
The CTOs in my paths all have managed to exist among us peons creating that information. I find the idea of them being overwhelmed with it hilarious.
We're supposed to believe they're so busy they can't answer your question right now, but they can later - if only you ask them somewhere else? No. Ridiculous performative exercise.
Being so particular to begin with is probably why they have to be so particular.
If anything, those I've known had to go fishing for the truth! They spend/t time with people. Those layers between pose a challenge.
I guess there's some advantage in being the firefighter... the CTOs want to know the sore spots, my positions would know.
I'd be amenable if the suggestion was to post the question in the open for everyone to hear/see. Or open a ticket for a question that's really a project. Going from DM to email is simply bikeshedding.
Just a footnote, I'm a totally random person - not the original poster
Asking people to move to email feels like a passive aggressive way to add enough friction to discourage question asking.
When someone Slacks me something that's clearly non-urgent, I just hit Save on it and come back to it later. No big deal. It's actually a wildly useful and probably underutilized feature.
Requiring others to message you _just so_ to match your own particular idiosyncrasies, because you insist on bending reality to your will rather than working in the same plane as everyone else, makes for a colleague that others dread interacting with.
Did somebody gently redirect you to email instead of Slack when you felt Slack was your medium of choice? You can always respond with, "Sorry, email doesn't work for me because [reasons], please reply here, thanks!"
Everything is a negotiation. Get good at negotiating and these issues become trivial.
Looks like the author has a similar approach.