For a distributed team, a recurring all-hands across several time zones is difficult to run well. It is also essential. Done well, it gives people across continents one weekly moment to hear the same information together. Done badly, it becomes a 45-minute burden for attendees and excludes those unable to join.
We have run all-hands meetings and spoken with many distributed teams about theirs. The format below is not the sole option, but it reliably addresses two common problems: exclusion caused by scheduling, and meetings that deliver status instead of building shared context.
Address the time zone issue directly
No time slot is neutral across a team separated by more than six hours. In Tallinn, Nairobi, and Vancouver, the UTC+3/UTC+3/UTC-8 split guarantees inconvenience for someone. A 9am Tallinn call is 9am Nairobi and midnight Vancouver. A 5pm Tallinn call is late evening Nairobi and 8am Vancouver.
Many teams choose a time convenient for most people and treat those in difficult time zones as an afterthought. Those teammates attend fewer meetings, feel farther from company decisions, and are often the first to lose context.
State the constraint openly and rotate who bears it. Hold the all-hands twice per quarter at a time favoring European and African time zones, then twice per quarter at a time favoring American time zones. Everyone carries the inconvenience for roughly half the year instead of a minority carrying it year-round. It is uncomfortable, but fair.
Cap it at 40 minutes
An all-hands should be shorter than most teams expect. Its purpose is shared context, not complete information delivery. Detailed information can be shared asynchronously. The live meeting is for matters that gain value from everyone being present: important decisions, cultural signals, and direct questions.
Forty minutes supports three sections: ten minutes for company updates, fifteen minutes for team topics and discussion, and fifteen minutes for questions. Repeated overruns indicate that some topics do not belong in an all-hands or that the updates were not prepared well enough beforehand.
Set a simple rule: purely informational items, such as a project shipping, this month's revenue, or a process change, go into a pre-read sent 24 hours before the call. Use meeting time for real-time exchange. This can reduce an hour-long all-hands to 35 minutes.
Use a format that avoids status dumps
Status dumps are especially tempting in distributed teams, where leaders want everyone informed. But a meeting of one-way reports rarely justifies its time cost. People can read updates asynchronously, but they cannot ask follow-up questions or read the room asynchronously.
Use four structural elements. First, prioritize decisions over updates: open with only company-level decisions made since the previous meeting, plus brief reasoning. Cover what was decided and why, not everything that happened. Second, choose one featured topic: give one subject the full group's discussion time, rather than five subjects shallowly. Third, include open questions: reserve a five-minute segment for anyone to ask anything. This can reveal information leadership did not know it needed to share. Fourth, create a written record: capture decisions and new action items from the featured topic during the call, not afterward.
Support people who could not attend
An all-hands that serves attendees but not absentees is only half complete. In a distributed team, people may miss a call because of time zone, childcare, illness, or urgent conflicting work.
The usual solution is to record and post the call. That helps, but longer recordings receive few views. Someone who missed the meeting is more likely to watch a twelve-minute edited highlight than a forty-minute complete recording.
Pair the recording with a structured summary covering decisions, key points from the featured topic, and resulting action items. Write it during the call, then publish it within two hours of the meeting ending, not two days later. Absentees can read the summary, while the recording remains available for anyone needing full context on a particular topic.
Track all-hands action items carefully
All-hands meetings often produce action items that are poorly tracked because the context is company-wide and ownership is unclear. "Marketing will update the positioning document" sounds specific, but it is not. Which person in marketing? By when?
An all-hands is a highly visible place for commitments to vanish. If a leader says "we will address the onboarding issue," the entire team hears it. If nobody tracks or follows up, the entire team sees that too. Dropped commitments cost more reputationally here than in a team standup.
Capture each all-hands action item to the same standard as any other task: a named owner, a precise description, and a deadline or review point. Vague commitments made before the whole team are especially risky.
What an effective all-hands achieves
A weekly all-hands is not mainly for transferring information. Its central job is to show that a distributed team remains one group, rather than isolated people working in parallel. The meeting is a ritual that strengthens shared identity.
Format and tone matter as much as content. A corporate broadcast misses this goal, even when its information is useful. Include genuine uncertainty, such as "we have not decided X yet, here is what we are considering," real questions, such as "does anyone see a problem with this approach?", and visible follow-through on earlier commitments. These practices build the trust that lets a distributed team function as one unit instead of a group of contractors.
The tactical guidance matters less than establishing that cultural foundation. A mediocre format backed by genuine openness works better than a perfect format that broadcasts prepared decisions to an audience that is not truly participating.