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
> 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.