4 ms·
I have worked remotely for a company that was otherwise very much a traditional non-remote environment; I have experience partly distributed teams and now manag
by sz4kerto 7y ago
I have worked remotely for a company that was otherwise very much a traditional non-remote environment; I have experience partly distributed teams and now managing a fully remote one.
I think partly remote will always, without an exception, create a significant information asymmetry that will result in non-remote workers becoming the leaders in the company. (plug, sorry:) I have written a small post about migrating to remote: https://blog.patientsknowbest.com/2020/04/01/51-basic-rules-of-managing-distributed-teams https://blog.patientsknowbest.com/2020/04/01/51-basic-rules-... - even in _theory_ you could fully embrace remote workers if some others see each other in person regularly, the latter group won't, can't and likely, shouldn't stop exchanging information in ways that 1) are more efficient 2) excludes remote workers.
- draven 7y ago+1 for the information asymmetry. I'm currently working remotely 4 days a week and there are 2 other devs working remotely between 80% and 100% of the time. One of the main issues is "oral tradition". Information is shared from dev to dev during coffee breaks, and everyone is supposed to somehow know it. The solution is to work as if everyone is working remotely, and in that case that means putting information into writing, either by communicating through archived and searchable channels (ie Slack) or writing docs.