4 ms·
Like others have said, this story has been repeated numerous times in some variation in the past and has never panned out. I think the reason is that many peop
by _fat_santa 5y ago
Like others have said, this story has been repeated numerous times in some variation in the past and has never panned out.
I think the reason is that many people conflate "remote" with "asynchronous". Having a company go fully remote is one thing, having a company move to a culture of asynchronous work is something completely different.
Some tech companies will be able to do this, but the problems really arise for companies that have to keep "business hours" here in the US. Take a major chain store, a healthcare company, a <insert traditional buisness> software provider.
These businesses have to balance and on-shore workforce with an off-shore workforce. There will be people that work on the ground, and they will obviously have to be on-shore, so will upper management most likely. What about the other layers in the organization. From a high level it sounds simple but when you dive down into which teams support which teams and report to which managers and yada yada yada, where you draw the line all of a sudden becomes much harder and fuzzier.
Most companies that will do what you are talking about have already done so. The reason the water hasn't leveled off more to other parts of the world like you are saying is either due to existing business constraints or risk aversion to possible constraints an offshore team may impose.
- redisman 5y agoAsynchronous is the real difficult part. A lot of companies already have offices in locations with good engineering talents and they usually work as a independent unit. It’s just really hard to coordinate a project when you have 0-1h of possible overlap time for meetings