Some distributed companies run effortlessly across eight timezones; others slowly die from one unavoidable 9 PM meeting. The difference is rarely the tools. It's policy. Here's what the teams that make multi-timezone work look like from the inside, including the policies they refuse to bend.
1. An Explicit "Overlap Hours" Contract
The functional teams don't pretend everyone works everywhere all the time. They publish a grid: each person's working hours, in their own timezone, and the shared overlap window (often 2–4 hours a day) where live collaboration is expected. Meetings are scheduled inside the overlap. Full stop. This one document eliminates more politics than any other single decision.
2. Individual Office Hours Instead of Cultural Guilt
Instead of everyone being on-call for the one person whose timezone is "inconvenient," good teams assign each individual a visible "office hours" block. Want a meeting with the Singapore dev? Pick from their published window. This replaces the negotiate-every-time ritual with a calendar you can trust without asking.
3. Written-by-Default Communication
If a decision can be made in writing, it is made in writing. Recorded walkthroughs replace live demos half the time. Documents carry the decisions; meetings confirm them. This is the same "async default" from the remote work guide, and it's not optional at company scale; a company of 50 that works "live-first" fires its people in 6–12 months of meetings nobody wants.
4. Rotation That's Actually Fair
Some meeting must be live, and someone will eat the awkward hour. The teams that survive make it fair: the awkward slot rotates by clock, not by seniority, so it's not always the same person at 6 AM. In practice, fairness compounds; a person who took the 6 AM slot last month is far more willing to take it again in six.
5. "No Meetings in Your Off-Hours, Period"
Mutable-hours teams forbid meetings outside published windows unless everyone in the meeting opts in in writing. The exemption exists precisely so it's rare. Unrestricted "quick syncs" at 9 PM are how distributed companies quietly lose their best people.
6. The DST Transition Gets Reviewed, Not Reacted
Experienced distributed teams put a recurring note on the calendar for the last week of March and October: "check US–EU differences." They know the two-week gaps exist, so they check their standing meetings against fresh conversions rather than waiting for someone to be an hour early. One team I know even converts all standing meetings once per month, by date, for exactly this reason.
7. Time Is an Accessibility Issue
And the best teams frame it that way. A colleague joining at 6:30 AM isn't being difficult; they're participating from a place where the clock is different. Teams with a healthy culture treat scheduling fairness with the same seriousness as salary fairness. The people who matter notice, and they stay.