I work on site in an early stage startup, and I think it's about commitment to a communication model.
We have a 2x2 grid. On the top we have 'in person' and 'remote'. Down the side we have 'synchronous' and 'asynchronous'. I've worked in companies trying all five (yes) of these combinations. This is my experience.
- in person, synchronous: everything happens in meetings. Business likes the certainty of meetings, engineering doesn't like the disruption. With the right accommodations, most people are content.
- in person, asynchronous: everyone's in the office, and no-one knows why. The CEO offers vague maritime platitudes.
- remote, synchronous: "can you go on mute" now causes a company-wide gag reflex. Everyone's happy because they can apply for new jobs without being noticed. (Seriously, the company I worked in that did this had absurd turnover, for this reason.)
- remote, asynchronous: engineers contribute to discussion when they have time. Hotshot managers want there ideas validated now, though. Despite this contention, most people are happy.
- hybrid: A cabal has formed in the office. Finally, it formalizes when a Jira account named 'Office' appears. When a remote worker creates an issue, the cabal convenes to decide a response. There is no room for negotiation. Gradually, the remote staff evaporate. Only the hive mind remains.
We have a 2x2 grid. On the top we have 'in person' and 'remote'. Down the side we have 'synchronous' and 'asynchronous'. I've worked in companies trying all five (yes) of these combinations. This is my experience.
- in person, synchronous: everything happens in meetings. Business likes the certainty of meetings, engineering doesn't like the disruption. With the right accommodations, most people are content.
- in person, asynchronous: everyone's in the office, and no-one knows why. The CEO offers vague maritime platitudes.
- remote, synchronous: "can you go on mute" now causes a company-wide gag reflex. Everyone's happy because they can apply for new jobs without being noticed. (Seriously, the company I worked in that did this had absurd turnover, for this reason.)
- remote, asynchronous: engineers contribute to discussion when they have time. Hotshot managers want there ideas validated now, though. Despite this contention, most people are happy.
- hybrid: A cabal has formed in the office. Finally, it formalizes when a Jira account named 'Office' appears. When a remote worker creates an issue, the cabal convenes to decide a response. There is no room for negotiation. Gradually, the remote staff evaporate. Only the hive mind remains.