Ah, I meant this in a more generic sense – I expect “how do I run a remote organization?” to be a highly important question for everyone in the coming months, and I thought it was worth including in the LW Research Agenda. Updated the title to be a little more clear.
Okay. From a practical point, one thing I’ve found is working remotely from the office introduces two immediate challenges.
First is the loss of the informal information flow—the remote person just quickly drops out of the loop. When the whole team suddenly becomes becomes remote that informal information flow is just gone. New communication patterns might help mitigate that. I now one of the clients I used to work with had a policy that all emails related to work got sent to everyone. That might not be what you need but they strongly felt that insured the corporate distributed knowledge was preserved and in some cases extended—sometimes really good insights came from people not directly working on a particular project; sometimes brand new opportunities were seen because multiple teams notices some common threads.
Avoiding the pressure to micromanage will likely be important. Clear goals statements, progress milestones and probably some good mechanism to raise a hand to point up an emerging problem.
When people get moved from the office to working remotely you will likely find that there were all sorts of things taken for granted that made one more productive—or just made the work easier. Before cutting ties with the office everyone should closely survey their remote work environment to make sure they can do the job remotely as well as in the office from pure procedure steps. Do I really have sufficient desk space or am I trying to work off the kitchen table? With the table work—is the light right? Too many distractions maybe? What about things like screen space? Access to applications remotely—does the VPN really kill the connection so you know it will take twice as long to get results back?
If the organization doesn’t already have experience with operating on a remote basis it really needs a few dry runs to learn what it doesn’t know. So will be the people. Does the organization have time to do that?
Contact lists—yes, everyone has the office directory but that might not be too helpful when everyone is not remote. Does the phone system support call forwarding—and does that functionality expose the number the call is then forwarded to. Is that a problem? How well will everyone work if all they have is a cell phone. What’s the backup plan there—online tools (Skype, Zoom, MS Teams or other tools might be good but also might be problematic based on various security setting or bandwidth to the remote location (I am guessing home—so another twist there is who else is in the house? Does everyone have a work space or will people be trying to work out of their bedrooms in a shared house?)
Most of that is mostly mechanical aspects.
One of the soft aspects is loss of vision—people cannot monitor each other as they do in the office. That will probably lead to some tension over (not too much) time. It’s natural for most of us to see the work we do and see the work not done by others we needed them to do. (I think there have been so posts on LW in that vein of thinking). That’s part of a culture shift moving for the co-located office to everyone remote. How best to minimize that type of dynamic should be considered. Maybe some type of group conference call where everyone can share experiences, what’s working and what is challenging might help keep everyone feeling they are all in the same boat with one another and not a case of multilateral “me-them” feelings.
These are they types of things I’ve see or experienced.
If you are thinking about your own organization my suggestion would be some trial runs. The organization was not setup initially for the remote structure so unlikely to have what is needed to support that. There will be a learning curve.
In terms of how to manage the output and make sure the organizational output keeps getting produced you probably already have most of that. They might be a few things you can think about the are directly observed during the normal course of the day. If they are really important from a “run the company” view what is the proxy in the remote setting? What is the impact of generating that proxy measure on just getting the job done?
Ah, I meant this in a more generic sense – I expect “how do I run a remote organization?” to be a highly important question for everyone in the coming months, and I thought it was worth including in the LW Research Agenda. Updated the title to be a little more clear.
Okay. From a practical point, one thing I’ve found is working remotely from the office introduces two immediate challenges.
First is the loss of the informal information flow—the remote person just quickly drops out of the loop. When the whole team suddenly becomes becomes remote that informal information flow is just gone. New communication patterns might help mitigate that. I now one of the clients I used to work with had a policy that all emails related to work got sent to everyone. That might not be what you need but they strongly felt that insured the corporate distributed knowledge was preserved and in some cases extended—sometimes really good insights came from people not directly working on a particular project; sometimes brand new opportunities were seen because multiple teams notices some common threads.
Avoiding the pressure to micromanage will likely be important. Clear goals statements, progress milestones and probably some good mechanism to raise a hand to point up an emerging problem.
When people get moved from the office to working remotely you will likely find that there were all sorts of things taken for granted that made one more productive—or just made the work easier. Before cutting ties with the office everyone should closely survey their remote work environment to make sure they can do the job remotely as well as in the office from pure procedure steps. Do I really have sufficient desk space or am I trying to work off the kitchen table? With the table work—is the light right? Too many distractions maybe? What about things like screen space? Access to applications remotely—does the VPN really kill the connection so you know it will take twice as long to get results back?
If the organization doesn’t already have experience with operating on a remote basis it really needs a few dry runs to learn what it doesn’t know. So will be the people. Does the organization have time to do that?
Contact lists—yes, everyone has the office directory but that might not be too helpful when everyone is not remote. Does the phone system support call forwarding—and does that functionality expose the number the call is then forwarded to. Is that a problem? How well will everyone work if all they have is a cell phone. What’s the backup plan there—online tools (Skype, Zoom, MS Teams or other tools might be good but also might be problematic based on various security setting or bandwidth to the remote location (I am guessing home—so another twist there is who else is in the house? Does everyone have a work space or will people be trying to work out of their bedrooms in a shared house?)
Most of that is mostly mechanical aspects.
One of the soft aspects is loss of vision—people cannot monitor each other as they do in the office. That will probably lead to some tension over (not too much) time. It’s natural for most of us to see the work we do and see the work not done by others we needed them to do. (I think there have been so posts on LW in that vein of thinking). That’s part of a culture shift moving for the co-located office to everyone remote. How best to minimize that type of dynamic should be considered. Maybe some type of group conference call where everyone can share experiences, what’s working and what is challenging might help keep everyone feeling they are all in the same boat with one another and not a case of multilateral “me-them” feelings.
These are they types of things I’ve see or experienced.
If you are thinking about your own organization my suggestion would be some trial runs. The organization was not setup initially for the remote structure so unlikely to have what is needed to support that. There will be a learning curve.
In terms of how to manage the output and make sure the organizational output keeps getting produced you probably already have most of that. They might be a few things you can think about the are directly observed during the normal course of the day. If they are really important from a “run the company” view what is the proxy in the remote setting? What is the impact of generating that proxy measure on just getting the job done?