2 ms·
I also find that communication/sync overhead is less efficient in remote teams (I have been working in globally distributed teams, since the early 1990s). It's
by ChrisMarshallNY 3y ago
I also find that communication/sync overhead is less efficient in remote teams (I have been working in globally distributed teams, since the early 1990s).
It's been my experience, that everyone (from the lowliest IC to the CEO) fails to understand the cost of team synchronization. That's a [set of] topic[s] that would fill an entire bookshelf, and anyone that gets it right, could live in opulence.
That isn't necessarily a bad thing, but it needs to be planned for, by managers and architects.
Architects need to design systems that allow ICs to have more personal agency, while encouraging synchronization (an approach that I use, is blackbox implementations, and whitebox APIs). The more an IC can work on their own, the better, but we still need that transparency.
Managers need to know when it's OK to send work to remote agents, and when work is required in-office. They need to know their teams well enough to be able to choose wisely. Human nature is a big deal. Until the entire workforce is AI, you'll always have those pesky humans in the mix, with their annoying emotions and personal lives.
Also, and this is almost never talked about, is that different people work differently. Some folks are almost superhuman, when left alone, while others just screw the pooch.
They may both be incredible employees, but they need to be handled differently.
Unfortunately, modern HR practice, is to treat every employee exactly the same as every other one (and there are actually valid reasons for this).
TL;DR, it's not simple, there's no "one policy to rule them all," and good managers are hard to find.