Working remotely across time zones is one of those problems that sounds simple until you're living it. When your team is spread across San Francisco, New York, London, and Singapore, the cognitive overhead of converting times in your head adds up fast.

Here's the setup that's helped me stay oriented without reaching for a time zone converter every time someone schedules a meeting.

The Core Problem

The real issue isn't just knowing what time it is somewhere else — it's the continuous awareness of where everyone's day is relative to yours. When I'm starting my morning, is my London colleague finishing their day? Is someone in Singapore about to drop offline? This context changes how I communicate and what I expect in terms of response times.

Checking a website or doing mental math doesn't give you ambient awareness. You need the information persistent and visible.

World Clocks on the New Tab

I added Weather & Clock Dashboard to Firefox specifically for the multi-timezone clock feature. Every time I open a new tab, I see my local time alongside clocks for the cities where my team is based.

The difference between this and checking a website is that it requires zero intent. I don't have to decide to check — it's just there. After a few days, your eye naturally glances at those clocks when you open a tab, and you build an automatic sense of what everyone's day looks like.

Why Weather Matters for Remote Work

The extension also shows a 3-day weather forecast for your location. This seems unrelated to remote work, but it's actually useful: if you're deciding when to do heads-down focus work, knowing a storm is coming (and you might lose power or internet) is relevant. If you have a standing desk or work from a home office, knowing the weather affects whether you crack a window or whether you're comfortable in your setup.

Mostly though, the weather being there is just convenient — one less reason to leave the browser.

Structuring Async Communication

World clocks help you respect time zones when scheduling. A few practices that work alongside the clock setup:

Record the recipient's local time when writing async messages. Instead of "can we sync tomorrow at 2pm?", write "can we sync tomorrow at 2pm my time (10pm your time / London)?". People don't have to calculate — they just check if that works.

Use ISO date format for dates. Write 2026-11-15, not November 15th or 15/11. No ambiguity about day/month order across regions.

Block your own overlap hours. If your team overlaps from 9-11am your time, protect that block. Use it for meetings. Reserve your non-overlap hours for async work.

Calendar Setup

Google Calendar and Outlook both let you display multiple time zones in the sidebar of the day/week view. Set this up once — add every time zone your team is in. When you're scheduling, you can see at a glance whether a proposed time falls in business hours for everyone.

Pair this with the new tab clocks and you have the same information available whether you're in your calendar or just browsing.

The Small Things Add Up

When you're not constantly recalculating time zones in your head, you have more mental bandwidth for the actual work. These are small ergonomic wins, but across a week of remote work they're meaningful.

The world clock on a new tab is the kind of thing where once you have it, you can't imagine going back to opening tabs and seeing nothing useful.