←back to thread

238 points aml183 | 1 comments | | HN request time: 0.225s | source

We are a remote company. Everything is going well. No plans to be in person, but I’d say we can do a better job at communicating. Any tips or articles to read?
Show context
paxys ◴[] No.42150868[source]
Make conversations public by default. If you use Slack, make team channels, project channels, announcement channels etc. all public. Discourage 1:1 and private communication unless really necessary, especially for engineering topics. This single change will have an immense impact on overall company culture.
replies(15): >>42150920 #>>42150993 #>>42151105 #>>42152006 #>>42152011 #>>42152642 #>>42155060 #>>42155607 #>>42158830 #>>42185599 #>>42185634 #>>42185891 #>>42185940 #>>42186302 #>>42192048 #
oc_elder ◴[] No.42152011[source]
I can appreciate the thinking here, but it not ideal. Different details are relevant to different people. And async is inefficient for many situations. Yes publish findings/results, but overcommunicating has a cost.

Better to create different channels (sync, async, 1:1, broadcast), provide guidance and trust workers.

replies(2): >>42152296 #>>42155339 #
1. broken-kebab ◴[] No.42152296[source]
It's not necessary about trust, or relevancy. I believe motivation is contagious, and making communications hearable/visible for all most of the time can be beneficial because of this.