Often synchronous communication is applied by managers because they lost control of their team and now try to monitor them closer so they don't step out of line.
It's like working overtime to compensate for bad planning or dropping home-office work all together because the company does bad.
I'm not saying 1:1 video isn't needed for some situations, but every day and even every week is often overkill. The best projects I had only required 1:1 videos every few months, most of them even only at the beginning.
The other strange thing you hear a lot is that any attempt to get people to be on-site or on-video (basically anything other than fully async, text only) is attributed to control-freak tendencies by terrible managers. Again going back to my above point and the fact that so many people here agree that video is better for them, I wish we could dispense with speculatively attributing motives so negatively and give people the benefit of the doubt that, right or wrong, they hold their POV because it is what they actually believe is best.
Guess, I'm seeing it like that, because I worked with control freaks.
I get that some people--perhaps especially engineers--would rather just be left in their cave to communicate asynchronously if and when they want to. But I don't blame managers/leaders for considering that a suboptimal practice taken to an extreme.
Personally, I mostly work fairly independently on a day-to-day basis but I also work with both formal and informal broader teams and it definitely helps to know the people I work with as something other than a nickname on chat.
You end up getting rid of meetings — people gathering in real-time :)
It is honestly so refreshing. I feel like I have teammates (not just text in Slack/Email). I feel like I understand who they are and how they communicate.
@samanthalee233 That's great! I tried to log in to suggest the change, but it did not work with my normal Gitlab account.
Sync/real-time communication is not needed for all the processes in a remote team, and you should go async by default and only use sync for cases where you _really_ have to get together. This is how companies Gitlab [1] have really become successful in doing remote work.
A remote team can be successful by using async/non-real-time communication, especially when you're pairing it with an async platform like Standups which is built from the ground up to support the async comm style. I wrote a blog article about how async is determinant to make remote work "work" within your team/org [2].
[1] https://about.gitlab.com/handbook/communication/
[2] https://standups.io/blog/how-async-communication-can-help-yo...