As a 100% remote worker for the last 5 years or so, I've found that chatting over Slack, IRC or similar is typically more effective than audio or video. Well, with one caveat: It must be searchable. As soon as an audio or video call has completed, it's lost. A searchable chat log isn't and can be referenced as needed. Of course, there are times when a video or audio chat are definitely preferred. In those occasions, the outcome of the meeting should be shared with the team over messaging.
Have discussions in the open. Don't make assumptions about who should be involved in a particular discussion. This behavior emulates turning around in one's chair to chat about something with a peer with others in the room who can freely join in. Threaded discussions in Slack are a great way to do this without polluting the channel with cross-talk.
I've also asked this elsewhere, but I'm curious if others have found a good replacement for white boarding discussions. These are invaluable, especially when talking about system architecture. The best I've found so far is Wacom tablets with collaborative Google Draw. Unfortunately it kinda falls apart when you start writing text.
Thanks for your response Demian. I agree with written discussions being held in the public sphere. Helps the entire team consume the information at their own pace. I'll definitely add it to our internal guidelines. :)
Great points Demian! Have you found Slack to get overwhelming if all conversations occur in public?
Haven't really found a replacement for whiteboards for sure. I had worked on a HW project to make a remote whiteboard, would have been pretty useful now. Video if you are interested: youtube.com/watch?v=uxmVtfF6pIo
Couple things:
As a 100% remote worker for the last 5 years or so, I've found that chatting over Slack, IRC or similar is typically more effective than audio or video. Well, with one caveat: It must be searchable. As soon as an audio or video call has completed, it's lost. A searchable chat log isn't and can be referenced as needed. Of course, there are times when a video or audio chat are definitely preferred. In those occasions, the outcome of the meeting should be shared with the team over messaging.
Have discussions in the open. Don't make assumptions about who should be involved in a particular discussion. This behavior emulates turning around in one's chair to chat about something with a peer with others in the room who can freely join in. Threaded discussions in Slack are a great way to do this without polluting the channel with cross-talk.
I've also asked this elsewhere, but I'm curious if others have found a good replacement for white boarding discussions. These are invaluable, especially when talking about system architecture. The best I've found so far is Wacom tablets with collaborative Google Draw. Unfortunately it kinda falls apart when you start writing text.
Thanks for your response Demian. I agree with written discussions being held in the public sphere. Helps the entire team consume the information at their own pace. I'll definitely add it to our internal guidelines. :)
Great points Demian! Have you found Slack to get overwhelming if all conversations occur in public?
Haven't really found a replacement for whiteboards for sure. I had worked on a HW project to make a remote whiteboard, would have been pretty useful now. Video if you are interested: youtube.com/watch?v=uxmVtfF6pIo
Nope, not overwhelming at all, so long as the discussions are kept threaded. Topical channels help as well.