It’s astonishing how many companies are still struggling with the remote culture. The worst-case scenario is when people responsible for fostering culture don’t see the problem. Communication was always crucial. With the remote setup, it’s even more vital as writing is simply hard and requires practice.

Slack already has an excellent article about etiquette - bookmark it to your general channel or add it to the onboarding guide!

I want to recap a few points from that list and add a few own pointers.

Private messages are evil unless they need to stay private - if someone asks you something that you can share on a designated channel - redirect that question there. And use threads for further discussion; use threads in general - it avoids unnecessary noise and allows to keep the conversation contained in a single place.

Private channels are evil unless they need to stay private - relying on some person to invite you to the club creates a peculiar atmosphere and not a very inclusive culture in my book. By default, keeping channels public increases transparency and reduces knowledge sharing and discovery traction.

Use reactions. Seriously, it’s a super-underrated feature, not only because of this:

Emoji can be surprisingly complex for being such a simple tool. They can represent real workflows. For example, people can put their 👀 on something to tell everyone they’re reviewing it and then a ✅ when they’ve completed their review. You can use emoji to claim requests or ask for volunteers with a ✋as well.

It’s also great for mimicking social interactions - if some message made you laugh - use an appropriate reaction! Don’t be afraid to add custom emojis that fit your mood! Reactions are a great and effortless way to give feedback to other people sitting behind the screen. There is nothing worse than posting a message in a vacuum.

Pre-recorded videos can be pretty effective. They have a downside as you can’t just search the content of the video, it’s not hearing-impaired friendly, but in some cases - like giving some status updates/preparing demos, asking questions while showing context at the same time - it can be a great tool. Not sure what to use? Try Loom or Veed or Clickup clip or CloudApp or whatever that fits your needs.

Context is king. Don’t assume folks from the other side know what you know. I can only recommend a fabulous talk by Jordan Raine presented at RailsConf 2021 - Refactoring: A developer’s guide to writing well that covers this and way way more - watch it, share it and let’s get better at writing together!