←back to thread

238 points aml183 | 1 comments | | HN request time: 0.208s | 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 #
lvspiff ◴[] No.42185634[source]
I'm at a company now where we are trying to do this but the CIO/CEO keep weighing in on EVERY conversation where they disagree with the approaach. The whole reason we are having the open conversation is for ideation and good communication but when a high level person comes along and says "well thats not the way I would do it" everyone decides to go back to 1:1s, direct messaging, and calls so as not to document anything publicly in feat of being called out by the higher ups.
replies(10): >>42186007 #>>42186637 #>>42186791 #>>42186928 #>>42187421 #>>42187662 #>>42187677 #>>42188206 #>>42189059 #>>42189193 #
1. raverbashing ◴[] No.42186791[source]
Private team channels sound like a good compromise

Also someone with good standing in the company to politely point to the CTO that it's not his job to give his 2c at every conversation in slack (typical behaviour of people coming from the technical side)