10 Slack Principles for Teams Who Actually Want to Get Work Done
Over a decade ago, I wrote my first article on written office communication: The Ten Commandments of Email. Since then, office texting has become a hot topic, and with Slack's invention, we were given yet another digital way to assemble the Tower of Babel. Here are some thoughts on how to use Slack effectively. Notice I did not Slack them to you!
1. Slack Only When Slack Is the Most Efficient Method to Communicate
Just because Slack exists doesn’t mean you should use it. Sensitive topics, performance issues, emotionally charged conversations—those should be live. Slack is great for quick exchanges to help coordinate actions or update progress, not nuanced discussions. Slack feels informal, and the writing style follows. Also, don’t use Slack as a system of record; use a collaboration tool, spreadsheet, or Google Doc.
2. Channel and Thread Hygiene Matters
Use well-named and appropriate channels and, when relevant, reply in existing threads. Use a pin to define a channel if helpful. Label your message so people know how to triage it. Dumping a major update into a random channel with an ambiguous opener is how things get lost. Also, don’t create a new channel for everything, and don’t resurrect dead ones unless you really need them.
3. Don’t Bury the Lead
Put the core point, question, or decision first, not in paragraph four. Slack is consumed on phones, in meetings, while walking between buildings—optimize for cognitive load.
4. Use Bullets, Not Blobs
Stream-of-consciousness messages are Slack malpractice. Use bullets, numbers, or a short checklist. If you want someone to respond, outline the questions. The more structured the message, the faster the reaction.
5. Explicit Call to Action
Tell people what you want, who needs to do it, and what “done” looks like. Vague Slack messages create orphaned work streams. Taking 10 seconds to clarify the call to action (CTA) saves hours of back-and-forth and reduces operational confusion.
6. Deadlines Aren’t Rude—They’re Alignment Tools
After your explicit CTA, set a deadline. Both “Whenever you can” and “ASAP” are ineffective.
If timing matters, say so: “Need feedback by 3 pm PT.” If timing is not pressing, why is it in Slack? Slack is real-time, and it's a concentration-disrupting system.
7. Use FYI—And Use It Correctly
Slack encourages oversharing. Tagging something as FYI helps team members filter, but only if you also write one sentence explaining why you’re sending it. Dumping in a long thread with zero context is just passing the cognitive cost downstream–and if it's something that people will need later, pin it in the channel. Again, choose the channel for this wisely.
8. Tone Discipline Matters Even More on Slack than Email
Written tone is already fragile in email; Slack accelerates misinterpretation.
Avoid sarcasm unless the relationship can absorb it. Avoid venting in channels. Avoid ALL CAPS unless the building is literally on fire (and pull the alarm). Use emojis thoughtfully and sparingly. When the stakes are high, don’t Slack: meet, Zoom, or call.
9. Don’t Abuse @Mentions (Especially @channel and @here)
Using @channel for non-urgent items is the communication equivalent of pulling the fire alarm because you can’t find your water bottle. Be thoughtful with @mentions overall. Use them sparingly and purposefully. And resist the reflexive “Thanks!” message that pings 40 people.
10. Read It Twice Before You Hit Enter
Slack feels fast, but the consequences are lasting. Glance back and check: Is it clear? Is it concise? Does it create work or reduce it? Can a tired, brilliant, overloaded teammate parse it at 2 a.m.? If not, fix it. The 15-second investment is worth it. Slow is smooth and smooth is fast.
