ThemeThe hybrid setup
CardCard 54 of 65
Questions5 to explore
StepMake it fair across locations

Time Zones

How our locations affect how we work together

Time zones do not make collaboration impossible, but leaving them unaddressed makes everything harder than it needs to be.

A team spread across two or three time zones needs to decide where shared time lives: which hours overlap, how much of that overlap is protected for synchronous work, and what happens in the hours when people cannot reach each other. Without this agreement, the default is usually that the timezone with the most people (or the leadership) sets the hours, and everyone else adapts, often at cost to their own working day.

Time zones also shape async norms. If someone sends a message at the end of their working day and expects a reply before they start the next one, but the recipient is eight hours behind, the expectation will not be met. Strong teams name the time zone reality and build their communication norms around it, rather than treating it as an exception.

Make it explicitWrite down the overlap hours available to the whole team, agree which of those are protected for synchronous work, and share this with the team so no one has to work it out individually.

How strong hybrid teams handle it

The same building block, handled well. These are patterns from teams that work well across locations, offered as illustrations to react to, not rules to copy.

Protect the overlap

When time zone overlap exists, strong hybrid teams treat those hours as shared infrastructure, not as default meeting time to fill. They protect overlap hours for the collaboration that genuinely requires real-time interaction and keep async in the remaining hours.

Record and recap synchronous sessions

Strong distributed teams with time zone spread record key meetings and publish a brief written summary, so team members who could not attend the overlap hours can follow along without having to piece it together from the chat.

Rotate meeting times when possible

When significant overlap does not exist, strong teams rotate meeting times across available windows so the burden of inconvenient hours falls on different people at different times, rather than always falling on the same person.

Time zone visibility in tools

High-functioning distributed teams display local times in their communication tools (calendar invites, scheduling tools, shared directories) so no one has to do mental arithmetic to know when 3pm in Berlin is for their colleague in Singapore.

Questions for your team

Use these on your own or in a group. There are no right answers, only better conversations.

What is the actual window of overlap for the whole team, and is everyone's working day shaped around that?
Who has had to consistently adjust their working hours to participate, and was that a deliberate agreement or a silent expectation?
How does your team handle a decision that needs to be made when part of the team is not yet online?
Are the response-time expectations on your main communication channels realistic across all time zones represented?
What has been the most concrete cost of time zone spread for your team in the last three months?

Watch for

The team member who is always the one attending meetings outside their working hours will notice, even if they do not say so. This builds quiet resentment faster than almost anything else.
Async work only compensates for time zone spread if the team has genuinely agreed on how async communication works. Otherwise, time zones just mean that things take longer and no one knows why.
Teams often treat time zone issues as a problem for the people with the inconvenient location, not as a structural design question the whole team owns.