|
|
|
|
|
by zith
747 days ago
|
|
This is my experience in very small companies (think a <10 person startup). The value of everyone knowing a lot of what's going on from immersion is immense. You can have very little processes around information sharing (which takes time to set up and fine tune!), very little time to convince people what needs to be done (it's obvious from the conversation the other side of the room is having), and all the nuance of in-person communication is kept. Once a company gets a little bit bigger, the processes around information sharing, planning and other communication has to be in place anyway. Teams need to collaborate, work needs to be tracked, there has to be meetings for planning. Once you're already doing that you might not lose anything by going remote. |
|
In my experience, it's not _entirely_ that simple though. For some people, chatting and video calls feel super awkward and makes them avoid communication. For other people, in-person is super awkward and has the same effect. There are a lot of nuances. I suspect RTO happens in companies run by the former type, and remote happens in companies run by the latter. As a CTO (did that for more than a decade), I always tried to give the team what they need. But even then, when in doubt, I suppose I often went for what I would need, if I was them.