| Yes, spontaneous things can happen when in person. Many of those spontaneous things are time sucks and not productive. Remote work has so many things going for it, it does not make sense to me to use a different model. Commute time is eliminated, as are commuting costs. That is time better spent. Remote communications have a built in forcing-function making us gather our thoughts before we type them in or call someone. This isn't a barrier to most. Is for some, typically the people who do a fair bit of idle chat or don't tryto solve things themselves for at least 20m before asking others. Remote communications can be recorded. Serves as both a knowledge repository that can be gone back to, and as an audit trail for legal purposes. Remote communications allow tools to be built into the conversation. In person we have a whiteboard, and someone has to take a photo of the whiteboard when done. Remote communications allow collaboration with wide area geographies where in-person travel would be too costly to do frequently (e.g., England and U.S.). Remote communications can be async, allowing staff who keep different schedules to easily collaborate. This could be as simple as another layoff, but I think it's more management that are used to the usual way of doing things. In my experience with remote vs non-remote I have seen a clear bias of older management to be less likely to embrace remote comms. I've also seen plenty of outliers on both ends, so that hypothesis might not hold water. I am curious what the age range of Roblox management is, compared to remote-first companies like Github. |