Time zone overlap
Finding the hour that works — and what to do for the teams where there isn't one.
Work out the real overlap
Write each person's working hours in UTC and find the intersection. Do it once and write it down, because everybody re-derives it badly in their head every time a meeting is scheduled.
- London and New York: roughly 13:00–17:00 UTC. Comfortable.
- London and Singapore: roughly 08:00–10:00 UTC. Tight, and early or late for somebody.
- San Francisco and Singapore: effectively none. Anything synchronous costs somebody their evening.
When the overlap is zero
Stop trying to find the hour. A team with no shared working hour needs its coordination to be async by design, not a rotating sacrifice — rotation sounds fair and in practice means everybody is tired some of the time instead of one person all of the time.
How Hearso handles it
A team sets its own drop time, and the round is available for the whole day from there. The content clock belongs to the team rather than the server, which is why a team in Auckland gets its round on its own morning instead of on the server's calendar date.