In this article, I propose to consider the problems that many different teams and companies faced during the 2020 remote-pandemic year, to understand what went wrong when moving from the office to a remote location.
Yes, I understand that it is already 2021, and many have already figured it out on their own. But practice shows that not so many succeeded as many would like.
I said all this in the Code of Code podcast .
However, I am sure that there are people who do not want to listen to a podcast for half an hour, but want to read a structured text in 5-10 minutes. Therefore, I will post it here, in the hope that it will find its interested reader.
Small disclaimer: I run a telegram channel called Timleid Evidence . Therefore, all my tips and tricks seem to be pretty obvious and float on the surface. However, when communicating with different teams, it turns out that everything is not always so clear and understandable. It is also important that the value of obvious advice increases significantly if you apply them more or less comprehensively.
I'll make a reservation right away that I consider any team in which at least 1-2 people work remotely to be a partially distributed team. And I am campaigning for the understanding that even with such a (so far) small number of employees, the growth of the remote part of the team is possible, and you need to build your work processes so that they work normally for a fully distributed team.
If this is not done, then everything can end with the fact that the distributed part of the team will not be able to merge into office-oriented processes and will fall off. And then you will say that "the remote control is to blame and it is impossible to work like that!"
Let's take four main problems: The problem of control , The problem of communication , The problem of organizing working conditions , The problem of health.
Control problem
. . - , , . , , , .
, , . .
( :)) , , , , , .
-
-.
. ? ? ? ? ? ? . .
, . , , . , , 15 , , , - .
. , , , . , . , - : , , , . .
, : , "", , , , "". ? , , , "" , ?
. , " , , , ". , - , - , - , . , , , , .
. !
- - , - .
3 :
?
?
?
, .
- , , , , 10 20 .
, , 10-15 , 1 . , .
, .
. . 2-3 : , () - , .
, - . . .
:
.
, :)
- . , 15-30 , 5.
, , .
, , .
, , .
, , , . , : 4 .
, . , , , , . .
, :
. , , , . : - , .
: " , , ". .
, , , . , , . , , . , , ?
, .
, - :
., . " ".
. " " ( ).
, . :
"" .
N "" " " " " " 13" "?".
" , , ASAP {{ }} !"
, .
- . , , .
15-20 , , , , , .
( )
:
, ? , , / , . . .
, , . , , .
, , - , . "" . N , , . . . , , , .
, . - - , - , - , ", , ".
, , , , , . , ? , , , , , .
- , , , , . .
, - .
. , - , . .
.
, , . - , , , wi-fi .
. , .
, - . , - .
, , , , .
( ), . , , , , . , - , , , " , ", .
, , / , / () . . , .
, , , . , - , / , . , , , , - ?
. , , - , - , , .
, , . :
. , , . - , , .
- , . - . - , , , . - , , .
, , , , , .
, -, : , , , . . , 8 , 8 , 8 "", .
. , . :) 2-3 - , , , , , .
- , ", ". - . . , , , , , , , , . - Nike Training Club. , , , , - .
. . , .
. . . , - . . , - , . , , , .
, , 8 , , . , , , , , .
, - . , , . , , , .
- . , - , . - , /, , , . , " ", , , .
- . , , . - , - . . - . - , , . - . , .
- - .
, , . , , , , .
. , - , . - , , , . , .
- . , , , .
, , , . (, , ), . , .
, , . - . , , / , , , " , ".
Learn to write clearly and ethically, cultivate self-discipline, build trust in each other, try not to let processes and people take their course, take care of yourself and your colleagues.