Most advice about distributed work is about tools. The actual difficulty is narrower and more stubborn: a fixed number of shared hours per day, and a decision about who pays for the shortfall.

Start by measuring, not discussing

Scheduling arguments usually run on assertion — "mornings are impossible for me," "that's the only time that works." They resolve quickly once the shared window is on the table as a number.

Compute the overlap for every pair on the team. It takes minutes and it changes the conversation from preference to constraint. See time zone overlap.

Write things down, seriously

Every team says it values documentation. Distributed teams across a wide gap depend on it in a way co-located teams do not, because the cost of an undocumented decision is not "someone asks later" — it is a full day of blocked work.

What has to be written, at minimum:

Decisions, with the reasoning. The reasoning is what stops the decision being relitigated in a timezone where nobody was present.
Current state of anything someone else might pick up.
Anything said in a call that a non-attendee would need.

The test: can someone eight hours away make progress on this without asking a question? If not, it is not written down yet.

Protect the overlap from status

The single most common waste is spending a narrow shared window on updates that could have been read.

Reserve synchronous time for what genuinely needs it:

unblocking someone who is stuck,
decisions with real disagreement,
anything with emotional content — feedback, conflict, bad news,
the relationship itself, which does not survive on text alone.

Everything else belongs in writing.

Rotate the bad hour, and say that you are doing it

If the overlap is narrow, someone takes an unsociable call. The failure is not that this happens — it is that it happens by default, landing on whoever joined most recently or objects least.

Rotating monthly works. Rotating weekly does not: nobody's sleep adapts and everybody is mildly annoyed.

Rotating also makes the cost visible to people who were previously insulated from it, which tends to improve the scheduling decisions that created it.

Give people real decision authority

A remote colleague who must get approval is idle for the half of the day when the approver is asleep. Widening what they can decide alone is usually a bigger productivity change than any tooling.

Expect the transitions

Twice a year, clocks change — and not everywhere on the same date, and not everywhere at all. Any recurring cross-region meeting can silently move by an hour in mid-March and late October.

Two defences: define recurring machine schedules in UTC, and put a reminder in the calendar to check the human ones at those two moments. See Eastern Time to GMT.

Write times unambiguously, always

Name the city, not an abbreviation. "3pm ET" is safe; "3pm EST" is wrong for most of the year; "3pm" is a coin flip. CST means US Central and China Standard Time; IST covers India, Ireland and Israel.

For anything machine-read, use a UTC timestamp.

Timezone: World Clock Widget

A world clock, converter and live day/night map for iPhone — 325 cities, offline, no account.

What it does

Figures on this page are computed from the IANA time zone database. Last generated 2026-08-18.

Working across time zones