Ask HN: What timezone do you use in conversation with a distributed team?
We are scattered around there world, originally with a core group on the west coast. So we kind of use PT + relative time, like...
"Let's sync about X at 1pm PT in ~3 hours"
Which works okay, but I don't love how it forces the non west coast people to do the extra time conversion step all the time. Not that that's so hard, but it is not so egalitarian as I would like to be striving for.
So we are wondering about switching to UTC in conversation. Has anyone tried that? Or used any tools that were actually effective at normalizing time references in conversation? How do you do it?
4 comments
[ 25.9 ms ] story [ 22.7 ms ] threadWhat would be better is if we could add more than 2 timezones to google calendar, then it'd be easier. But still not hard. My rule is the place that has the bulk of the people is who gets the most favorable time for the meeting. That way if 4 people are in one TZ and one person in another, we inconvenience the one person, if anyone has to be, not the 4. For some meetings I have switched it up, when it is me and one other person I will alternate who does late vs early etc, so it is a shared burden. This helps the team all feel equal, regardless of title or position.
Do you ever think it would be easier if you all just declared, "we only deal in UTC at this company" and then everyone would just get used to doing their own conversion? Or would that be more trouble?
There are systems that exist like calendly that helps you solve one to one meeting issues. For example, it works great for interview scheduling when people are in different timezones, but for internal meeting and coordination process is better then automation IMO.
Process here is easier. Use google calendar to find 2-3 times everyone is available (at least internal people) and send them out, that is the fastest way if you aren't already on the phone talking to everyone. This way it only takes 1-2 communications at most to schedule a meeting. You have to bake timezone management and meeting process into the company culture, it is really important. Just like I always add 24-48 hours to any estimate when I know it involved me speaking with the team in India.
Last point, meetings should be avoided for things where a document can be created, and comments added to it for the communication. We use Quip, write up the details in Quip, ask everyone for feedback by a specific date/time and then you move forward from there. It stops a lot of unnecessary meetings and lets you do things faster. It follows the adage of slow down to go faster.
I've been leading remote teams since 1997, which started because we had people in India, Germany and the U.S. The struggles we ran into over the years were all solved by setting basic processes and building a culture around accountability to the process. One key is reducing unnecessary meetings and using documentation and comments.