> If all information is visible and everything is well documented, it should be rare to have the situation where one person is the only one that can answer that

> If all information is visible and everything is well documented, it should be rare to have the situation where one person is the only one that can answer that question. This will totally still happen for remote teams, but I think it happens more in other organizations that rely on face time and verbal information exchange. I worked at my last job for just over 2 1/2 years and, while we had an actual office, for the first two years I was there, we also had a true "unlimited vacation/remote work" policy. It wasn't unheard of that some people would take 4-6 week vacations and others would work remote for multiple months. Documentation was great, but you can't document everything you know, so there will always be gaps. I'm a developer, so these will be dev focused, but some scenarios I can remember where one specific person was needed are: - Legacy code. Bob was the only one around when this code was written and it hasn't been touched in years, now it's breaking and no one understands why. (In an ideal world, there wouldn't be knowledge silos like this, but there always are) - Specialties. Most developers know this tool, but Bob is an expert. We need to do something that requires an expert. We need Bob. - Bob left an ominous, yet vague comment on my PR. I don't want to merge until I get clarification. (something like "This looks hacky. I guess it works, but we should probably change this ASAP." or "Eww")