4 ms·
I work at a company where everyone is expected to be in the office. But we have early birds and night owls employed by the same company to work together. We don
by jhgaylor 7y ago
I work at a company where everyone is expected to be in the office. But we have early birds and night owls employed by the same company to work together. We don't have a formalized solution as night owls do as you described and get on up if they have work due in the morning. Or the early birds will stay up late to help the night owls finish.
But a lot of companies take on "Core hours" and essentially solve the timezone problem even with a physical office. With core hours management is deciding that they don't want to solve the "timezone issues".
I wonder how well the opposite end of the spectrum would work. Our async communication tools are pretty good these days. You could keep someone solving the problem all day long with just 3 or 4 hires but instead people choose to work on the problem in scheduled bursts of 6 hours with their entire team.
- jypepin 7y agoif you are interested and want to solve this for your company, look into Gitlab. They are solving it and have very good public documentation on this.
- emilycook 7y agoGitLab employee here, yes we do! I honestly couldn't go back to a company without asynchronous communication. https://about.gitlab.com/handbook/communication/ https://about.gitlab.com/handbook/communication/
- brodock 7y agoAlso GitLab employee here. I work for the Geo team (geographical replication and disaster recovery), and funny thing is we are also sparsely geographically distributed. No single person in the same country. We have people spread out with all impossible timezones combinations, from US west-coast, Brazil, Europe (east/west) going all the way to Australia.