Should you send an email or a Slack?

Email vs. Slack isn’t a personality test. It’s an operating decision about where a piece of information lives — and at most companies, the answer to that decision is “wherever the person who sent it felt like at 3pm on a Tuesday.”

That’s how teams end up arguing about decisions nobody can find. Get this right early and you become the person other people copy.

The pattern that teaches this

You send an important update in Slack. It gets one thumbs-up. A week later, in a meeting, someone says with genuine confusion:

“Wait — when did we decide that?”

Nobody did anything wrong. You used a tool that’s great for conversation for something that needed a record. The two are not the same. Slack is for thinking out loud. Email is for “here is the thing.” Most early-career mistakes happen because nobody draws this line.

The two-question rule

Two questions get you 80% of the way home:

1. Is this urgent?
2. Do I need a paper trail?

Then:

• urgent, no paper trail → Slack
• not urgent, paper trail → Email
• urgent and paper trail → Slack to act, email to lock it in

Memorize that table. It will save you from approximately one bad week per year for the rest of your career.

When to use email

You need email when you need a durable record — anything that someone might say “I didn’t see that” about later. Confirmations, approvals, final requirements, money. The bar isn’t legal; it’s whether you’d be comfortable recapping the decision out loud six months from now without checking.

Email is also the default for external or formal tone. Clients, vendors, executives. Even internally, an email signals “this matters.” That’s not a vibe. It’s literally how senior people parse signal.

And email wins for long context. If your message has sections, attachments, or a “first read this, then this” structure, Slack turns it into scroll-purgatory. Use the right shape.

When to use Slack

Real-time collaboration. Quick decisions. The “is anyone else seeing this?” panic. Two-line questions like “Do we have the latest deck link?” or “Who owns the API key rotation?” These are the right questions to send in Slack and the wrong questions to send in email — sending those via email is how you become the new grad people quietly avoid.

Coordination notes also belong in Slack. “Running 5 minutes late.” / “I’ll take this ticket.” / “In the lobby.” Don’t email these. Just don’t.

The part nobody tells you: which Slack channel

Email vs. Slack is the easy question. Which Slack venue is the harder one. The defaults:

• Public channel — when the answer helps others or you want visibility
• Thread — when you’re responding to a specific message (keeps the channel readable)
• DM — when it’s sensitive, personal, or genuinely one-to-one

If you DM everything, you create hidden work and the team doesn’t learn from your questions. If you post everything in public channels, you create noise that everyone tunes out. The first month at any new job, watch how your manager and the most-trusted senior on your team handle this. Then copy them. Slack hygiene is mostly mimicry.

A few patterns that come up constantly

A Slack thread turns into a decision. Recap it in the thread, then send a one-paragraph email summary. “Confirming what we landed on: X. Owner is Y. Deadline is Z.” That’s a 90-second move that prevents a 30-minute meeting next quarter.

You’re escalating a risk. Slack to alert, email to document. The email format that reads as “I’m on it” rather than “I’m panicking”:

• What’s happening
• Impact
• What you’ve tried
• What you recommend
• What you need from them

Skip any one of those bullets and the message tilts toward panic.

You have a question you should have looked up. Five minutes of homework, then the smallest possible question: “I checked X and Y, still don’t understand. Is the answer A or B?” That’s the question senior people are happy to answer. The unfiltered version isn’t.

—

I still mess this up sometimes. Sent a quasi-staffing decision in a Slack DM last quarter and three people didn’t see it for a week. The rules are simple. The discipline is the work.

For the update format that works in either tool, steal the Status update template.