Slack Is Not Texting
Slack occupies an awkward space between email formality and text message casualness. Too formal and you sound robotic. Too casual and you sound unprofessional. The norms vary by company, by channel, and by who's watching — and nobody tells you the rules.
The fundamental Slack etiquette error: treating it like a text conversation. Sending 'hey' on its own line. Then 'quick question.' Then waiting for a response before asking the actual question. This creates three notifications, requires the recipient to context-switch three times, and communicates nothing until the fourth message.
The fix is simple: one message, complete thought. 'Hey [Name] — quick question: [the actual question with enough context to answer it].' One notification. One context-switch. One response. Done.
Channel Communication Rules
Use threads for everything that isn't a standalone announcement. The main channel feed should be scannable — not a wall of conversation that requires reading 50 messages to understand what happened.
Tag people only when they need to see it. @channel means everyone needs to see this now. @here means everyone online needs to see this now. Neither should be used more than once or twice a week. If you're @channeling daily, you're either posting too many urgent things (prioritization problem) or nothing is actually urgent (judgment problem).
Don't DM something that should be in a channel. If the answer would help others, post it where others can see it. If it's truly private or personal, DM is appropriate. The test: would I be embarrassed if this appeared in a public channel? If no, post it publicly.
Timing and Response Expectations
Set your own response expectation: 'I check Slack at 9 AM, noon, and 3 PM. For urgent issues between those times, text me.' This prevents the always-on anxiety that Slack creates while being explicit about your availability.
Don't read into response timing. A delayed Slack response is not passive-aggression. It's someone who was doing their actual job. If something is genuinely urgent, say so: 'Time-sensitive — need input by 2 PM.' Without that signal, assume async.
Weekend and after-hours messages: if you must send them, preface with 'Not urgent — for when you're back on Monday.' This two-second addition prevents hours of recipient anxiety about whether they need to respond now.
Emoji and Reaction Culture
Emoji reactions are Slack's most underrated feature. A thumbs-up on a message confirms you've read it without creating a new notification. An eyes emoji says 'I'm looking into this.' A checkmark says 'done.' These reactions replace dozens of 'sounds good' and 'got it' messages.
Read the room on emoji culture. Some teams use custom emojis extensively — learn and use them. Some teams are more conservative — match their energy. Using party emojis in a channel where the culture is professional creates dissonance.
Never use Slack reactions to communicate disagreement or sarcasm. A thumbs-down on someone's proposal in a public channel is not constructive feedback — it's a public dismissal. Use words for disagreement. Use reactions for acknowledgment.
Top comments (0)