4 ms·
Even in a remote world, it's still pretty painful to deal with large timezone differences. I don't want to work with people in india if I'm in the america time
by novok 6y ago
Even in a remote world, it's still pretty painful to deal with large timezone differences. I don't want to work with people in india if I'm in the america timezone set, and if they could choose, people working for american companies in india would probably feel the same. Similar with european offices. NYC, Brazil and SF can all interact with each other well enough.
So even if the software world was remote, I still think you'd probably have to move to an american timezone somewhere.
- r_c_a_d 6y agoI agree. When I worked in London for Nokia I tried to keep to Finland time where possible, as it made things a lot easier. Then they added teams in India and China and it became a nightmare.
- seanmcdirmid 6y agoTry organizing a meeting with attendees from Beijing, Redmond, and Cambridge. Ya...it doesn’t work. India is the absolute worst for the USA because they are almost 12 hours off.
- disgruntledphd2 6y agoFrom my experience working with global teams, as soon as you have Asia & EMEA, you need to go to two meetings if you actually want to retain said staff. This is annoying, but it's much better than people taking meetings at midnight, which is what happens otherwise.
- novok 6y ago2 meetings work fine for large company / departmental scope presentations, because only %1-5 of the people in the meeting have to do the midnight thing, but break at the 5-10 person level unfortunately. Someone is forced into a midnight meeting somewhere as part of syncing up planning between teams at the very least.
- disgruntledphd2 6y agoNot necessarily. It just requires the manager/lead to run two meetings. I did this with small teams for many years, and it's annoying but it can be done. I generally aimed to have everyone together 1/quarter in person to do the higher level planning stuff, which would be much more difficult in the times of Covid.