If you work with people in multiple time zones, you've probably made the calculation error. It's 2pm here — what time is it for them? You know it's a 7-hour difference but is that ahead or behind? You do the math, get it slightly wrong, and schedule a meeting at 8pm their time.
This is a solved problem that most people solve badly.
The Common Approaches (and Their Problems)
Phone world clock app: You have to switch apps and unlock your phone. Fine, but friction.
Google "time in [city]": Fast, but requires that you remember to check and then do arithmetic. Error-prone when you're tired.
Scheduling tool with time zone detection: Good for meetings, but not helpful for "is it reasonable to message this person right now?"
Mental math: You're going to make mistakes. Everyone does.
What Actually Works
The most reliable thing I've found is making world clocks ambient — visible without any action. When I open a new browser tab, I see time in London, New York, and Tokyo alongside my local time and weather.
I use Weather & Clock Dashboard for this. It's a Firefox new tab extension that shows multiple world clocks along with local weather. The combination sounds random but works well in practice — both are things I want to check at the start of a browser session.
How Many Clocks Do You Need?
For most remote workers, three clocks cover 90% of needs:
- Your local time
- The time zone where most of your collaborators are
- One more time zone for anyone you work with regularly
More than 4-5 clocks becomes visual noise. The goal is instant legibility, not comprehensiveness.
Time Zone Etiquette
Things worth knowing if you work across time zones regularly:
"Working hours" is not universal: 9am-5pm is the US default but the UK often starts earlier, much of Asia has split schedules, and Europe has a midday lunch break culture that's genuinely taken seriously.
The async message question: Before sending a message, the question isn't "is it their business hours?" but "will this create an expectation of immediate response?" If yes, wait. If it can be async, send it.
Calendar invites should show time zones explicitly: "3pm" is ambiguous. "3pm EST / 8pm GMT" is not. Add the recipient's time zone to the invite title when scheduling across zones.
Overlap windows: For synchronous work, identify the window where everyone is online. For a US East + UK + India team, that window is roughly 2-5 hours depending on DST. Protect it for synchronous calls; use async tools for everything else.
Time Zone Tools Beyond World Clocks
For scheduling across multiple zones: Savvy Time (savvytime.com) lets you pick cities and see overlapping working hours at a glance.
For calendar blocking: many calendar apps let you show a secondary time zone on the calendar grid. Useful for visualizing your schedule from a collaborator's perspective.
For recurring meetings: rotate the "inconvenient" time zone. If you have a weekly meeting with EU + US, alternate between 4pm EST (9pm Paris) and 9am EST (3pm Paris). Nobody always wins, nobody always loses.
The Cognitive Load Argument
Working across time zones adds cognitive overhead. Small steps to reduce it — ambient world clocks, explicit time zone labels, async-by-default communication — add up. The overhead never goes to zero but it can go from "constant friction" to "occasional calculation."
The new tab world clock is a small thing. It's one fewer mental context switch per day. Across a year, that's not nothing.
Top comments (0)