4 ms·
In a global but not-remote company the team responsible for the particular service that failed is probably still concentrated in one office. Bringing in people
by CrazyStat 5y ago
In a global but not-remote company the team responsible for the particular service that failed is probably still concentrated in one office. Bringing in people from other offices who aren't familiar with the problem service probably isn't that helpful.
- Steltek 5y agoYou can have knowledge silos in either kind of company. We didn't magically get better at spreading work around or writing documentation just because we went remote.
- iamstupidsimple 5y agoThis has nothing to do with remote. Remote teams are usually concentrated in the same timezone too. In-office global companies make a point of having at least a few teams owning a service for this very reason.