The Friday afternoon Slack ambush

It's 4:55 PM on a Friday. You're closing tabs, mentally checking out, when a Slack notification pings. It's your manager: "Hey, do you have a second?" And then... nothing. No context. Just a blinking cursor. You reply "Sure, what's up?" and watch the typing bubble appear and disappear for five agonizing minutes. You spend the weekend convinced you're getting fired, only to find out Monday morning they just wanted the link to a specific Figma file. Remote communication is a breeding ground for paranoia. Without tone, body language, or facial expressions, your brain naturally fills the silence with the worst possible scenario. It means a lazy typing habit doesn't just waste time—it actively burns trust and makes you look incredibly unprofessional.

Mistake 1 — The "Naked Greeting" (and the anxiety it causes)

Sending "Hey" or "Hi [Name]" and waiting for a reply is a micro-aggression. You're essentially holding the other person hostage, forcing them to pause their work, say "hello" back, and wait while you slowly type out what you actually want. It's selfish. It says: my time is more valuable than your focus. Stop treating Slack like a phone call where you need a handshake before you can speak. Put the greeting, the context, and the ask in a single message. Instead of: "Hey, are you free?" Try: "Hey Sarah, when you have a moment today, could you review the Q3 copy draft? No rush, just need your sign-off by tomorrow noon." This gives them the context they need to prioritize it without breaking their flow.

Mistake 2 — Passive-aggressive Slack codes

We all know the codes. "Per my last message" means can you read? "Just checking in" means why haven't you done this yet? "As previously discussed" means we already talked about this, you forgot, and now I'm annoyed. These phrases are corporate-approved passive aggression. They feel safe to type, but they make the recipient immediately defensive. If you need an update because a deadline is looming, just say that. Skip the polite-looking passive-aggressive padding. Instead of: "Just checking in on this." Try: "Hey Mark, I need the onboarding numbers by 2:00 PM to finish the client presentation. Is there anything blocking you that I can help clear up?" It's direct, it's helpful, and it doesn't make you sound like a disgruntled auditor.

Mistake 3 — The multi-paragraph wall of text

Slack is not a memoir. If you send a massive, eight-hundred-word block of unformatted text, nobody is going to read it. They will skim it, miss the core request, and you'll end up frustrated. People consume chat messages differently than emails—they scan for action items. If you make them dig through a wall of text to find your point, you're offloading your thinking onto them. Keep it tight. If a message is longer than three paragraphs, it shouldn't be a Slack message. Use bold text for deadlines, bullet points for lists, and keep the fluff to a minimum. If you actually need a deep discussion, write a brief collaborative document and share the link, or ask for a quick five-minute huddle. Don't force your team to decode a novel.

Mistake 4 — The public call-out

Tagging someone in a public channel with fifty people to point out a bug or a missed deadline is a terrible move. Even if you wrap it in polite language, it feels like public humiliation. The moment you do this, the other person goes into survival mode. They will stop trying to fix the problem and start trying to protect their reputation—usually by blaming someone else, pointing out an ambiguity in the spec, or getting defensive. The rule is simple: if you're praising someone, do it in public. If you're correcting them, do it in a DM. Keep the focus entirely on the work, not their competence. Instead of posting a bug in #general, send a private message: "Hey Alex, I noticed the mobile layout is missing the pricing table we discussed. Let's review the brief together for five minutes to see where the gap is." It lets them fix the mistake without feeling like they have to defend their honor in front of the whole company.

How to practice difficult remote conversations

It's easy to agree with these rules while reading an article. It's much harder to follow them when you've been waiting three days for a reply, your project is late, and you're typing with angry, aggressive keystrokes. When you're stressed, your brain defaults to its worst habits. You either write a passive-aggressive zinger or bottle it up until you snap. This is why you need to practice saying the hard things first. You can use cosskill to run a few low-risk dry runs. Try the Coworker persona to practice confronting a teammate who is ignoring your pings, or use the Rosenberg persona to help you translate your frustrated, angry drafts into clean, direct communication before you hit send. Taking five minutes to test your wording on an AI is usually the difference between a quick alignment and a multi-day Slack war.