|
|
|
|
|
|
by inter_netuser
1790 days ago
|
|
|
i wonder how companies survived until now with all kinds of outsourcing, outstaffing, contractors in 5 different timezones, vendors in 12 different timezones, regulators in 3 different time zones, separate divisions for APAC, EMEA, US and so on...? ...but just can't handle remote employees that they have so much more control over? Sounds like complete nonsense to me. If they can handle vendors located on a different continent - they can handle remote employees, full stop. I'll believe the complaints about WFH when they'll ban offshoring. |
|
|
All of this involves varying degrees of transaction costs (ie. how hard is it to have everone aligned, communicating effectively, etc). Outsourcing is usually done for (parts of) jobs that can be easily carved out into fairly complete packages.
For example, have the QA team offshore, or outsource the design or slide-deck preparation. Most dev outsourcing is also done at least per-component if not per-project.
True distributed teams are HARD. But having everyone aligned, on the same page and motivated, if half (or more) of the team is remote, means a lot more effort on clear communication, management, etc and many office patterns will need reworking.
As one example, onboarding (esp junior) team members is much harder, as new people learn as much by osmosis as by reading the documentation.
This is not to diss WFH - I prefer it to office esp. cubicle hell - but we should be realistic about the challenges involved.