Time Zone Sanity Guide

Every distributed team has a golden overlap window — usually 2–4 hours where most people are online. Find yours and treat it as sacred. This is the only time for real-time meetings, quick decisions, and pair work. Outside that window, work is async. Post the overlap hours in your team docs and calendar defaults. If your overlap is less than 2 hours, you have a design problem, not a scheduling problem — restructure teams to cluster time zones or accept fully async workflows.

If one person is always joining at 7am or 10pm, they will burn out. Rotate meeting times so the burden shifts. A simple rule: the meeting owner picks a time in the overlap, but if someone has had 3 early/late calls in a row, they get the next 3 at a civilized hour. Document this in a shared tracker. Even better: record every meeting so people in impossible time zones can watch at 1.5x speed instead of losing sleep.

Slack, emails, and docs should always reference times in UTC (or the company's declared default zone). "The call is at 3pm" is meaningless to a distributed team. "The call is at 15:00 UTC" is unambiguous. Most calendar tools can display dual time zones — teach your team to set this up. When sending invites, include the recipient's local time in parentheses: "15:00 UTC (11am ET / 8am PT / 4pm GMT)."

For non-urgent decisions, adopt a 24-hour rule: proposals are open for comment for one full business day before a decision is made. This gives every time zone a chance to weigh in. The proposer posts the decision framework, options, and recommendation in a doc by 5pm UTC. Comments close at 5pm UTC the next day. If no objections, the recommendation passes. Objections must include an alternative or the decision moves to a call in the next overlap window.

A Friday 5pm deadline in New York is already Saturday in Sydney. If your team spans the Pacific, Friday deadlines create weekend work for someone. Move deadlines to Thursday EOD or Monday morning. Similarly, Monday morning standups in Europe are Sunday night in the Americas — rotate standup days or go async. Small calendar adjustments signal respect for personal time more than any policy document.

Team bonding across time zones is where most companies fail. A virtual happy hour at 6pm London is lunchtime in New York and 3am in Tokyo. Instead of one event, run three regional socials with a shared async activity: a photo challenge, a playlist swap, or a "show us your desk" thread. Record highlights and share them. The goal isn't perfect attendance — it's inclusion.