Slack promised to kill email and instead gave us a second inbox that never closes. The difference between a team where Slack works and one where it's a source of constant anxiety mostly comes down to how people write messages. A few habits make all the difference.
No naked "hey"
The classic anti-pattern: sending "hey, quick question" and then... nothing, while you type the actual question. The recipient sees the notification, stops what they're doing, and waits. Send the whole message at once:
- Bad: "hey" → (typing...) → "you around?" → (typing...)
- Good: "Hey — when you get a chance, can you check whether the staging deploy picked up yesterday's config change? Not urgent, end of day is fine."
One message, complete context, explicit urgency level. The recipient can triage it instantly.
Threads are not optional
Replying in-channel to a threaded conversation scatters the discussion and notifies everyone twice. Keep the conversation where it started. Likewise, if a thread has clearly outgrown Slack — twenty replies, three decisions, two disagreements — it's time for a call or a written summary, not reply twenty-one.
Write for the person who reads it in four hours
Slack feels synchronous but usually isn't. The best messages assume the reader is not online right now:
- Include enough context that they don't have to scroll up.
- Link the ticket, doc, or PR you're referring to instead of saying "that thing from earlier."
- Make the question answerable in one reply: "Should we ship Friday or wait for the fix?" beats "what do you think about the release?"
Urgency belongs in words, not channels
@channel at 6pm because you're excited about something is how teams learn to ignore @channel. Reserve broadcast notifications for genuinely time-critical, everyone-affected news, and say the urgency explicitly: "need an answer in the next hour" or "whenever you're back is fine." Teams that mark urgency honestly get faster responses on the messages that matter.
Rewrite before you hit enter on the hard ones
Tone travels badly in short text. A terse "why did this change?" can read as an accusation when you meant it as a question. For messages with any emotional stakes — disagreements, pushback to a senior colleague, delivering unwelcome news — it's worth a second pass. Tools like Wrivio exist for exactly this: rewrite the message right from your desktop with a keyboard shortcut, choose something like "clear and firm" or "friendly," and see word-by-word what changed before you send.
Status and availability are messages too
A two-line status ("heads down until 2, ping me for anything urgent") prevents a dozen "you there?" messages. So does actually responding to messages with an emoji reaction when a full reply isn't needed — 👀 for "seen, will respond later" and ✅ for "done" cover most of it.
The one-scroll rule
If a Slack message takes more than one scroll to read, it should probably be a document with a link and a two-line summary. Long-form thinking belongs somewhere it can be found again — Slack's search is where context goes to die.
