I have my own rule— it’s that I don’t respond to “hi and wait”’s on Slack (unless of course from within my own team/group/mgmt). “External” hi’s just go unansw

I have my own rule— it’s that I don’t respond to “hi and wait”’s on Slack (unless of course from within my own team/group/mgmt). “External” hi’s just go unanswered. Simply because I get too many of them. If the person can’t take the time to include a concise summary of exactly what they need with that “hi,” well then, they’ll move on to someone else (they’ll be simultaneously pinging various other people on our team in any case). Usually they will get the picture and follow up within 15-20 minutes with their actual ask, but if it’s not important enough for them to make that extra effort, then it’s definitely not important enough for me. BTW, I never do the “hi and wait” thing myself. If I need something from someone on another team, I of course say hi. But in the same initial communication, the next sentences are a summary of exactly what I need, as concisely as possible. I do this as a courtesy, because no one has time for hi’s, nor chit-chat. As far as the actual article though— I highly do NOT agree with telling someone something is OK or resolved, when it’s actually not. That is simply very bad.