4 ms·
I am in the Japanese timezone. I am working with people in central Europe, East Canada and Silicon Valley. Have worked in such a way for years. The secret is j
by Iv 5y ago
I am in the Japanese timezone. I am working with people in central Europe, East Canada and Silicon Valley. Have worked in such a way for years.
The secret is just: no meetings. Meetings should be exceptional. If you have discussions in a timezone, record it for those who can't attend. Prefer async, prefer written communication.
Have lots of one-on-one communication.
90% of the meetings I have ever attended were counter-productive anyway and were just there because a middle manager wanted to feel useful by wasting devs time. If you are having a meeting where one person is doing most of the talking it can be done async. Feedback can be given async. Demos can be done async.
Some conversations need realtime, but most of these can happen one-on-one, recorded for people who are in a different TZ.
Yes, that's a different way of working, but it is not too hard, we have the tools and it makes sense. The only obstacle is a culture of the useless meeting. Kill it, embrace the async world. Keep realtime communication for meaningful 1-on-1.
- TrueGeek 5y agoThis is very accurate. I'm in the US eastern time zone but working with teams in the Pacific time zone, IST, and CEST constantly. My employer cancelled all of our leases when everyone went home so we're now all remote 100%, but that doesn't really change anything about having to work remote. Embracing async communications is the key. If I send you a message at 3am just reply when you are ready. If I need a real time meeting I can schedule it, but that's rare for developer communication.