Working in a Global Team Across Time Zones

A team spread across several time zones cannot rely on a conversation in the corridor to settle a question. Decisions happen in documents, in threads and in the few hours when people overlap. The habits this requires feel slow at first, and they make work easier for others to judge, which matters more when the person doing the work is not in the room to explain it.

Why written decisions carry the weight

A decision that is only spoken exists for the people who heard it. Someone in another time zone may learn about it a day later from a summary that has already drifted, and a colleague who joins next quarter has no way to find out why it was made. A written decision can be read by anyone, reviewed later and reversed with a clear reason rather than an argument about who remembers what.

A decision record does not need to be long. It should include the question, the options considered, the choice, the reason for it, and the people who need to act on it. Storing it where the team will look, and linking it from the place where the work happens, keeps it findable. Writing the reason often surfaces weak arguments before the decision is made, which is a benefit in itself. A flawed argument is cheaper to fix on the page than in a meeting. A record also reduces the cost of onboarding, because a new colleague can read the history of a decision instead of asking the same people to explain it again.

Asynchronous updates people actually read

An update that people read starts with what changed, then what is blocked, then what is needed from whom and by when. The request goes first, because a reader several hours ahead or behind may only see the top of the message before their day moves on. Status messages should not repeat context everyone already has. Linking to the background rather than retyping it keeps the update short.

A standing weekly note can replace many small meetings. Keeping its format the same each week lets readers learn where to look and skip what they do not need. When a reader must respond, a specific question with a date works best. "Any thoughts?" produces silence in a distributed team. "Can you confirm by Thursday whether the new export format works for your reports?" produces an answer, and it tells the reader exactly what is being asked of them. Updates can also name the time zone of any deadline, since a date written without one causes avoidable confusion across regions.

Using the overlap window well

Hours when the whole team is online are valuable, and they should go to the things writing cannot settle. Disagreement that needs back-and-forth, a design choice with many competing trade-offs, or a sensitive conversation about workload usually belongs in the overlap. Routine updates do not, and filling the overlap with them wastes the one time everyone can talk at once.

An agenda should be prepared in advance, with the reason for each item. The meeting should end by stating the decisions and their owners, and the written outcome should be sent the same day. Without that last step, a meeting that reached a conclusion produces a slightly different understanding in each person who attended, and the disagreement returns in the next thread with more heat than before. Rotating meeting times, where the regions allow it, spreads the inconvenience of early and late calls more evenly, and that fairness shapes how people judge the process.

Handling disagreement across distance

Disagreement is harder when tone is lost. A message that reads as blunt may be meant as efficient, and a polite message may hide a real objection. Naming the disagreement directly, stating the reasoning, and asking what would change the other person's view turns a standoff into a set of conditions that both sides can check. That final question is the one most often skipped.

Communication norms also differ across cultures. Some people expect a lot of context before a proposal, while others want the conclusion first. Some treat silence as agreement and others as thinking time. Asking rather than assuming is the safer habit, and when a reply surprises, it is worth checking what it meant before reacting. The trade-off is that decisions can take longer, but they tend to be better documented and less likely to be reopened without cause. Naming norms openly at the start of a project, such as how quickly replies are expected and how disagreement should be raised, prevents many of the misreadings that otherwise build up.

Career effects and a practice exercise

Distributed work can make visibility depend on writing. A person who writes clear decision records becomes known for their judgment. A person who works well in conversation but writes little may be overlooked, and people in less central time zones can find their contributions harder to see. Being aware of this is the first step toward managing it deliberately.

Practice for one week. Write one decision record and one update in the format above. Then ask a colleague in another time zone to read both without any background and say what they would need in order to act. If they had to ask something, the record is incomplete, and the missing question shows what to add. Repeat the exercise the following week. The aim is writing that works for a reader who was not in the room, which is the same standard that makes work easy to judge. Over time the records also become evidence in performance conversations, since they show judgment that would otherwise be visible only to people who happened to be online.