The real problem with global teams
For a team spread across San Francisco, London and Singapore, there is no hour of the day when everyone is comfortably at work. A call at 8 am in San Francisco is 4 pm in London and midnight in Singapore. If nobody plans for this, the same people end up taking the worst hours week after week, and over time they burn out or leave.
Good global teams treat time zones as a design problem. They decide how work will flow across hours, which meetings need to be live, and how to share the burden fairly. This playbook gives you a framework for doing that, whether you are a manager, a team lead or an individual who wants to improve the way your team works.
Principle 1: Make fewer meetings live
The most effective step is to reduce how many meetings need everyone at the same time.
Ask of every recurring meeting: could this be an update in writing, a short recorded video or a shared document? Live meetings are best for decisions, sensitive conversations, brainstorming and relationship building. Status updates, announcements and routine reviews are often better handled asynchronously.
A useful rule is that any meeting that needs to be live should have a clear purpose and an agenda circulated in advance. People joining at midnight deserve to know their time is being used well.
Principle 2: Use the overlap windows
Every team has some overlap, even if it is small. Identify the hours where most people are working, and keep live meetings within them.
For a team across San Francisco (UTC-8), London (UTC+0) and Singapore (UTC+8), overlap between all three does not exist in a normal day. But two of three do. London and San Francisco overlap in the San Francisco morning. London and Singapore overlap in the London morning. Plan meetings for two regions at a time where possible, and record them for the third.
Principle 3: Rotate the pain
If a weekly meeting must involve all three regions, rotate the time so that the inconvenience is shared. For example, alternate between a time that suits the Americas and Europe but is late in Asia, and a time that suits Europe and Asia but is early in the Americas.
Document the schedule clearly, and revisit it every quarter. Rotating also builds empathy, because everyone experiences what it is like to attend a difficult-hour call.
Principle 4: Write things down
Written communication is the backbone of global teamwork. A few habits make a large difference.
- Write complete messages. Include context, the decision needed and a deadline, so that the reader can act without a back-and-forth.
- Summarise meetings in a shared document with decisions, owners and dates.
- Record key meetings and share them with people who could not attend.
- Use clear naming for documents and tasks.
- Keep one source of truth, such as a project board, so everyone can see status.
Principle 5: Design handoffs
A team across time zones can make progress around the clock if handoffs are well designed. At the end of each person's day, they leave a short note for the next person: what was done, what is blocked, what needs attention.
A simple handoff template:
- Done: What was completed.
- In progress: What remains and where files are.
- Blocked: What you need from someone else.
- Next steps: What the next person should do first.
When handoffs are consistent, a task can move from Asia to Europe to the Americas in 24 hours without a single live meeting.
Principle 6: Set response-time expectations
Clarify how quickly people are expected to reply. In a global team, an immediate response is often impossible, so decide what is reasonable.
- Normal messages: reply within one working day.
- Urgent issues: use a defined channel and escalation path.
- Out-of-hours messages: do not expect an answer until the recipient's next working day.
Writing these expectations down avoids misunderstandings and stress.
A sample meeting schedule
Imagine a team with members in San Francisco, London and Singapore.
- Weekly team meeting: Rotates between 9 am London (1 am San Francisco is too early, so use 4 pm London for the Americas and Europe) and 9 am London for Europe and Asia. Alternate weeks. Record each.
- Daily updates: Written, posted in a shared channel by the end of each person's day.
- One-to-one meetings: Scheduled at times that suit the individuals, ideally within the working day of both.
- Quarterly planning: A longer session at a time that is fair, with extra preparation and breaks.
Tools that help
- Shared calendars with time zone display.
- Scheduling tools that show time zones for each participant.
- Project management software with clear task ownership.
- Video recording tools for short explanations.
- Shared documents for decisions and notes.
Choose a small set of tools and use them consistently. Too many tools create confusion.
Protect people's health
Regular late-night or early-morning meetings affect sleep, mood and performance. If someone repeatedly attends difficult-hour meetings, consider compensating them with time off, flexible hours or a different schedule.
Leaders should also model good behaviour. If the manager is always online at midnight, the team may feel pressure to do the same.
Be aware of culture
Time zones are not the only difference. Working styles, holidays and communication norms vary across regions. Be mindful of local holidays, such as Lunar New Year in many Asian countries, Diwali in India, or Thanksgiving in the US. Share a calendar of holidays so that nobody schedules a major deadline on a day when part of the team is off.
Also be aware of language. If English is a second language for some people, speak clearly, avoid idioms and provide written summaries.
Handling daylight saving changes
Daylight saving transitions shift the gap between regions by an hour twice a year. Remind the team before these changes and check recurring meetings. Using UTC as a reference in some documents can reduce confusion, but make sure people know how to convert it.
Common mistakes
- Scheduling every meeting at the manager's convenience.
- Ignoring daylight saving.
- Not recording meetings.
- Assuming that everyone can respond instantly.
- Having too many recurring meetings.
- Never reviewing the schedule.
Frequently asked questions
How many live meetings should a global team have?
As few as possible. Start with the ones that truly need real-time discussion and reduce the rest.
What if the CEO is in one region and wants all meetings at their time?
Explain the cost to the team, offer alternatives such as a rotating schedule and recordings, and use data on attrition or fatigue if you have it.
How do we build team culture without shared hours?
Use occasional in-person gatherings, virtual social events at rotating times, and channels for informal conversation.
Summary
A global team can work well across time zones when it designs for them. Keep live meetings to a minimum, use overlap windows, rotate inconvenience, write things down, and build reliable handoffs. Treat people's sleep as a limited resource, and review your approach regularly.
