3 ms·
Broadly speaking: Be considerate of others' time. Specifically: - Be concise and quick. Write out a succinct message, review it, include necessary links, and
by PragmaticPulp 5y ago
Broadly speaking: Be considerate of others' time.
Specifically:
- Be concise and quick. Write out a succinct message, review it, include necessary links, and then hit send.
- Avoid formalities ("Hey" "How are you" "Do you have a minute?"). Just get to the point and let them respond when they're ready.
- If it should be an e-mail, send an e-mail. If it needs to be a meeting, schedule a meeting. If it's best discussed in person, find the person. Resist the lazy temptation to use instant messages for everything.
- Watch the hours. If it's 9PM at night and you don't need a response by morning, wait until morning to send it. Or send an e-mail.
- Use group channels when appropriate. If you're discussing something the entire team needs to hear, use the team channel. If you're having a back-and-forth debate with one person, take it to a thread or private message.
- Show you've done your homework. Before asking someone for help, be prepared to list what you've tried and why it failed. Don't ask coworkers to help you with things that could be answered by reading the documentation or using Google.
- piinbinary 5y ago> Use group channels when appropriate I would strengthen this statement to "use group channels unless inappropriate." There are definitely topics that shouldn't be discussed publicly, but for everything else, I think it's best to default to using a public channel. I can't tell you how many times people give me a bunch of details in a direct message, only to have to replay all those details when someone else is added to the conversation. Using direct messages is also rude if you are doing so in an attempt to bypass a team's normal process for handling incoming requests.
- cosmotic 5y agoI've seen people get quite upset when I skip the "hi, how are you" bits. Know your audience I guess.