5 ms·
I'll try to list a few that other comments here haven't mentioned: - Don't be needlessly vague. Instead of saying "we need to chat, can you hop on Zoom?" say "
by piinbinary 5y ago
I'll try to list a few that other comments here haven't mentioned:
- Don't be needlessly vague. Instead of saying "we need to chat, can you hop on Zoom?" say "we have a new development in project X, can we chat about it on Zoom?" Instead of saying "I need help," say "I need help learning how to use this API." Instead of "can you look into this?" ask for what you actually need.
- Instead of sending a screenshot of text, send the actual text. It's rude to force the recipient to re-type the text to (for example) search for the error message in their code.
- Don't use leet-speak or other shortcuts. Writing 'u' instead of 'you' makes the recipient feel like you don't respect them.
- Check that instant messages are the right format for what you are trying to do. Sometimes writing a document and sharing it is a better approach.
- Follow the conventions in a channel for using threads. Threads become more important in high-volume channels with lots of concurrent conversations.
- If a channel has a welcome message with instructions, pay attention to them!
- karmakaze 5y agoExcellent points. I'll add that for error messages that sometimes the text isn't copy/pasteable and a screenshot may show extra context that might be useful. In all cases, it's important that the information be verbatim, don't paraphrase or unduly shorten messages.