Local time is comfort; overlap is capacity
Teams argue about whose morning standup should win. The useful question is different: how many hours per day can two or more people work together without someone sacrificing sleep every week?
Overlap is finite. Local pride is infinite. Planning that starts from "we always meet at nine here" exports cost to the farthest teammate until they quit or go quiet.
Draw the overlap map first
List core contributors with IANA time zones. For each pair, compute shared 9:00 to 17:00-style business overlap using a planner, not guesswork (team timezone planner).
Color three bands:
Green: overlap four or more hours on most days.
Yellow: overlap one to three hours.
Red: no reasonable overlap without night work.
Put the chart where hiring managers see it before they add a fourth continent.
Assign work types to bands
Green hours: decisions, pairing, sensitive feedback, incident command.
Yellow hours: short syncs, quick clarifications, handoffs with strict agendas.
Red hours: async only. Writing, reviews, recorded walkthroughs, tickets with context.
When a decision lands in a red band for half the team, the decision is wrongly timed, not the people.
Rotate sacrifice, do not institutionalize it
Sometimes overlap is yellow for everyone if someone rotates early or late slots.
Rotation beats permanence. If one region always takes the 07:00 call, that region will under-index in meetings and over-index in attrition.
Finding fair meeting times includes fairness rules worth adopting literally.
Async carries everything that does not need green
Status updates, RFCs, comment threads, and recorded demos consume overlap only when they fail.
Default to durable writing (async status people read). Meet when the decision tree says so (when a remote team needs a meeting).
DST and policy changes move overlap
Overlap is not constant. US and EU daylight shifts can remove an hour without drama if you expect it (DST mistakes).
Recompute overlap when headcount changes. A hire in Singapore reshapes the map more than a hire two states away.
Managers: measure overlap before scope
Promising "daily live sync with the whole team" assumes green overlap exists. If it does not, the promise is a hidden overtime policy.
Scope deadlines should name which hours decisions can happen. "Feedback within one overlap window" beats "feedback within twenty-four hours" when windows are three hours wide.
Pride phrases to retire
- "We are a global team, someone can always join."
- "It is only once a week" (for the person it is always early).
- "They chose to live there" (you chose a hiring geography).
Replace with: "Here is our overlap chart; here is what we do outside it."
Wider playbook
Timezone collaboration without chaos ties overlap to handoffs, ownership windows, and client expectations.
Local clocks matter for sleep. Overlap matters for shared work. Optimize the second on purpose and local comfort stops being a zero-sum fight.
Hiring and overlap
Before adding a region, rerun the map. A brilliant hire in a red band can still work if their role is async-first. A hire expected to lead daily live reviews in a red band will fail or burn out.
Job posts should state overlap expectation in hours, not "flexible global team."
Clients outside the team map
External clients add another layer. Their business hours may sit entirely in your yellow band. Batch client calls into green when possible, or price the inconvenience into your retainer.
Do not pretend client calls are "quick" when they land outside your team's shared hours every week.
Review overlap quarterly
Headcount, DST, and client mix change. Put "update overlap chart" on the quarterly ops checklist next to access reviews.
Stale charts cause fresh arguments.
Lead by example in yellow bands
If you are in the green band, do not schedule all client calls at your convenient morning without checking who goes red. Propose two options in UTC and let the far colleague pick.
Small courtesies reduce the politics that overlap math alone cannot fix.