Slack Etiquette for Every Kind of Thinker

Slack etiquette rules for clear, calm team chat: how to ask for things, flag urgency, use threads and write messages that work for every kind of thinker.

Good Slack etiquette makes messages easy to act on. Put the full request in one message, say how urgent it is in words, give a real time, and keep decisions in the thread where everyone can find them. Avoid messages that create worry without information, like "hey, got a sec?" These habits help everyone, and they matter most for people who read messages literally or find vague pings stressful.

This article builds on "Your Slack Has a Neurotypical Bias," a talk by BRYGE AI founder Rebecca Koniahgari at LDX3 New York 2026. The talk looked at how everyday chat habits quietly assume that everyone reads between the lines the same way, and what teams can change.

Why does Slack etiquette matter?

Chat is fast, short and constant. That is its strength, and also why it causes so many misunderstandings. Short messages leave out context. Tone is hard to read. Urgency is often implied rather than stated.

People fill in those gaps differently. A message one person reads as casual, another reads as alarming. Someone who reads words literally may miss a hint entirely. Someone who is sensitive to tone may spend an hour worrying about "can we talk?" This is not about one group being better at chat. It is about defaults that leave too much unsaid.

12 Slack etiquette rules that work for everyone

1. Put the whole request in one message

Instead of "hey" and waiting for a reply, write the full question. The reader can answer in one go, whenever they are ready.

Instead of	Try
"Hey, got a sec?"	"Quick question about the API review: should we use v2 or v3 for the new endpoint? Any time today is fine."

2. Say how urgent it is, in words

Urgency is one of the most common sources of worry in chat. Say it plainly: "Not urgent, any time this week" or "Urgent: the deploy is blocked until we fix this."

3. Never send "can we talk?" without a reason

A meeting request with no context can cause real anxiety. Add the topic and the stakes.

Instead of	Try
"Can we talk?"	"Can we talk for 15 minutes this week? Not urgent. I want to discuss the API review."

4. One ask per message

If a message has four questions, the reader may answer one. Number them if you must send several, or split them into separate messages.

5. Lead with the action

Put what you need first, then the background. "Could you review PR #482 by 3pm? It fixes the login bug from this morning."

6. Give real times

"By Thursday at 3pm" is clearer than "soon," "EOD" or "when you get a chance." Time zones matter too: say which one.

7. Turn question-shaped orders into honest requests

"Would you be able to look at this?" can sound optional when it is not. If you need it done, say so kindly: "Could you look at this by Friday? It's needed for the release."

8. Use threads, and keep decisions in them

Reply in threads so conversations stay together. When a decision is made, write it clearly in the thread: "Decision: we're going with v3. Jordan will update the docs by Monday."

9. Write down what was agreed on calls

Decisions made in a huddle or a hallway are easy to lose. A one-line summary in the channel helps people who process information differently and anyone who was not there.

10. Close the loop

If you ask something and it gets resolved elsewhere, say so in the original thread. Open loops leave people wondering whether they still need to act.

11. Use mentions on purpose

Use @channel and @here only when everyone needs to see it now. Mention specific people when you need something from them, and say what.

12. Respect focus and offline time

Not everyone replies instantly, and that is fine. Use status messages to show when you are focusing or offline, and expect others to do the same. A slow reply is not a rude reply.

Which Slack habits create extra work?

The Communication Burden Audit, the framework from the LDX3 talk, groups problem messages into patterns. Some of the most common:

Urgency ambiguity: the reader cannot tell how urgent something is.
Buried action items: the actual ask is hidden at the end of a long message.
Multi-ask compression: several requests packed into one message.
Implicit tone: the meaning depends on reading tone that is not there in text.
The false no-rush: "no rush" on something that is actually needed soon.
Open loops: questions that are never clearly answered or closed.
Verbal-only decisions: agreements made on calls that never reach the channel.
Question-shaped directives: requests phrased as optional questions.

The audit shows teams how to find these in their own channels in one sprint, and how to rewrite each one.

Try it: one message, two readings

The message as written:
"We've been seeing some weird API responses lately. Might be worth taking a look when you get a chance."

How it could be misread:
One engineer may read it as a casual observation and do nothing. Another may sense that something is badly wrong and drop everything. The writer actually meant: please investigate this week.

A version that works for both people:
"Could you look into the inconsistent API responses by Thursday? It's affecting about one in ten checkout requests. Not an emergency, but it needs fixing before the release."

What Slack etiquette should managers follow?

Managers' messages carry extra weight, so small changes have a big effect.

Never leave a vague ping overnight. "Can we chat tomorrow?" from a manager can ruin someone's evening. Add the topic and "nothing is wrong" if that is true.
Separate feedback from chat. Give meaningful feedback in a one-on-one or a considered written message, not a quick DM.
Model the habits. If you write clear asks with real times, your team will too.
Ask how people like to communicate. Some prefer a call for complex topics, others prefer writing. Ask, then use what they tell you.

Slack etiquette and neurodiversity

Many neurodivergent people describe chat as both helpful and hard. It is written, which many prefer, but it is also fast, vague and full of unwritten rules. Neurodivergent people are not a monolith, so there is no single fix, but explicit, predictable messages help most readers, whatever their neurotype.

The goal is not a special set of rules for some people. It is better defaults for everyone, so no one has to spend energy decoding what a message meant.

Frequently Asked Questions

What is good Slack etiquette?

Put your full request in one message, say how urgent it is, give a real time, use threads, keep decisions written down, and respect people's focus and offline time.

Is it rude to just say "hi" on Slack?

It is not rude, but it makes the other person wait to find out what you need. Put your question in the same message instead.

How do I show urgency on Slack without stressing people out?

Say the urgency in words and give the reason: "Urgent: the deploy is blocked until this is fixed." For non-urgent things, say "not urgent" explicitly.

Should decisions be made on Slack?

They can be, as long as they are written clearly in the thread with who is doing what by when. Decisions made on calls should be summarized in the channel afterward.

How can Slack be more inclusive for neurodivergent employees?

Use explicit asks, real deadlines and stated urgency, avoid vague pings, summarize decisions in writing, and ask each person how they prefer to communicate.

BRYGE AI works inside Slack through the Chrome extension. Write your message, see how it could be misread, and send a version that works for both of you. Try it free.