Published July 2026 · 9 min read
When a team spans San Francisco, London, and Singapore, "let's hop on a quick call" stops being quick. Every meeting becomes a negotiation across sleep schedules, family dinners, and time zones where the workday hasn't even started yet — or ended hours ago. The companies that thrive with global teams don't just "try harder" at scheduling. They've fundamentally redesigned how work happens.
Here's what the data says, and how three of the world's most respected distributed companies — GitLab, Buffer, and Automattic — actually handle it.
The Real Cost of Time Zone Gaps
Harvard Business School researcher Prithwiraj Choudhury and his colleagues published a landmark study in Organization Science in 2024 that quantified what distributed teams instinctively knew: every additional hour of time zone disparity between coworkers reduces real-time communication by 11%. That might not sound dramatic, but one hour of lost overlap translates to a 19% reduction in opportunities to communicate synchronously during the typical workday.
The study, which analyzed communication patterns of more than 12,000 employees at a large multinational corporation, found that workers don't just accept the communication loss — they compensate by shifting conversations outside business hours. Managers and their direct reports experienced a 31% increase in after-hours communication when separated by time zones. Software engineers and other knowledge workers on the same team saw a 30% spike.
But not everyone can time-shift equally. Women — who research consistently shows carry disproportionate caregiving responsibilities — communicated outside business hours at nearly 9% compared to 14% for men. Workers in countries with legal limits on weekly hours (35-39 hours per week) averaged only 9% after-hours communication, versus 32% in countries without such limits. The scheduling burden falls unevenly, and Choudhury warns this can create career-level consequences: "They will be participating in a subset of calls, and that will lead to a deficit of information that could be critically important for their job."
The data aligns with broader trends. As of 2025, 22.8% of U.S. employees work remotely at least part of the time — over 36 million people. Among remote-capable roles, 52% split time between home and office, and 27% are fully remote. And 98% of workers say they want to work remotely at least part of the time for the rest of their careers. Global scheduling isn't a niche problem anymore; it's the new default.
GitLab: The Async-First Operating System
If any company has written the playbook on time zone scheduling, it's GitLab. With 2,000+ team members spread across every major time zone, GitLab operates on a single organizing principle: bias toward asynchronous communication. Their public handbook — which would run over 2,000 pages if printed — documents every process, decision, and workflow so that no employee needs to wait for someone in another time zone to wake up.
The philosophy is captured in GitLab's definition of async work: "Do as much as you can with what you have, document everything, transfer ownership of the project to the next person, then start working on something else."
GitLab doesn't eliminate synchronous communication — they're strategic about where it belongs. Their experts advise using sync for troubleshooting ("10 minutes on Zoom is more efficient than 100 Slack replies"), relationship building ("coffee chats, group social chats"), and urgent incidents. But for everything else — detailed technical conversations, code reviews, project planning — async wins. The key is documentation: if it's not written down, it didn't happen. This handbook-first approach means a developer in Nairobi can pick up exactly where a teammate in Vancouver left off, without ever being online at the same time.
One underappreciated benefit: async communication forces clarity. When you can't rely on a follow-up question getting answered for eight hours, you learn to write messages that leave no ambiguity. GitLab's entire culture is built around this muscle.
Buffer: Small Groups and Timezone Awareness
Buffer, the social media management platform, has been fully remote since long before it was fashionable. At one point, their team spanned 11 different time zones. Instead of trying to find meeting times that work for everyone — a mathematical impossibility — Buffer takes a different approach.
First, they prioritize small-group meetings. Their "daily pair calls" and weekly "mastermind" chats cap at 2-3 people, making it far easier to find overlapping hours. When a larger meeting is unavoidable, they use tools like World Time Buddy to find windows and rotate meeting times so the inconvenience is shared across team members.
Second, they built a culture of radical schedule transparency. Buffer's internal tool — originally built by a developer just for the team and later released as timezone.io — shows at a glance where every teammate is and what their local time is. Team members share travel plans, schedule changes, and even lunch breaks so nobody accidentally pings a colleague at midnight.
Third, they invest in in-person connection. Buffer flies the entire company together once a year for a weeklong retreat. As CEO Joel Gascoigne puts it: "Once you return home, the conversations you have with team members are enhanced. You know the tone of somebody's voice and the way they approach problems and discussions. You read their emails differently."
Between retreats, individual teams hold their own on-sites. The in-person time creates a social fabric that makes async communication across time zones feel less like shouting into the void and more like collaborating with people you actually know.
Automattic: The 15-Year Remote Veteran
Automattic, the company behind WordPress.com, WooCommerce, and Tumblr, has been distributed since 2005 — well before Zoom or Slack existed. With over 1,900 employees in 96 countries, they've had longer than anyone to figure out what works. Their approach is built on written communication as the primary medium. Most internal discussion happens on P2, an internal blogging platform where every project, decision, and debate lives as a permanent, searchable post. There are no standing meetings by default.
Automattic also pioneered the "follow-the-sun" support model: customer support tickets flow from time zone to time zone as each region's workday begins. But they've learned that this model only works for highly structured, routine tasks. For collaborative, creative work — product design, engineering architecture, strategy — "follow the sun" creates more friction than it solves. You need overlapping hours.
This insight aligns with Choudhury's research: routine-task workers successfully switch to async when time zones separate them, but collaborative workers try to match colleagues' hours instead, cutting into personal time. Automattic's solution is to be intentional about which roles require overlap and which don't, rather than applying one policy across the entire company.
What the Data Says About Productivity
The fear that remote and distributed teams are less productive has been thoroughly tested — and largely debunked. A Stanford study published in Nature found that hybrid schedules showed zero negative impact on performance, with a 33% drop in employee turnover. Research from Stanford and McKinsey found that well-organized hybrid teams are approximately 5% more productive than both fully remote and fully in-office teams. Companies save an average of $11,000 per year for each remote worker.
Yet a persistent trust gap remains: 85% of business leaders struggle to feel confident that remote employees are productive, while 87% of those employees report being productive. Microsoft calls this "productivity paranoia." The companies that have solved it — GitLab, Buffer, Automattic — don't rely on surveillance. They build systems where output is visible and measurable by default, because all work lives in shared, transparent channels.
Five Patterns That Actually Work
Across these companies and the research, five patterns emerge:
1. Default to async, reserve sync for what only sync can do. Troubleshooting, relationship building, and crisis response justify real-time conversation. Status updates, project planning, and code reviews don't. GitLab's rule of thumb: if you can't write a clear agenda, you shouldn't be scheduling the meeting.
2. Document everything as if the next person starts in a different time zone. Because they probably do. The single most impactful investment a global team can make is writing things down — decisions, context, rationale, next steps. If it only exists in someone's head or a Slack thread from three weeks ago, it may as well not exist.
3. Distribute the scheduling burden fairly. Rotate meeting times so no single time zone always bears the early-morning or late-night slot. Buffer rotates; many teams at GitLab alternate. If your meeting always lands at 9 PM for your Singapore colleagues, you're signaling that their time is less valuable.
4. Match your collaboration model to the work, not the org chart. Routine tasks can run follow-the-sun. Complex collaborative work needs overlapping hours. Automattic and the HBS research both confirm: one-size-fits-all scheduling policies create frustration everywhere. Be explicit about which roles need real-time overlap and design teams accordingly.
5. Invest in the relationships that make async sustainable. Async communication falters when people don't trust each other. Annual retreats, team on-sites, and even virtual coffee chats aren't perks — they're infrastructure. They build the social capital that keeps written communication from being misread as hostile or cold across cultural and linguistic barriers.
The Bottom Line
The companies that handle global scheduling well don't have a secret scheduling tool or magic meeting time. They've accepted that synchronous-first workflows don't scale across continents, and they've built organizations where work moves forward whether or not anyone is online at the same time. That means writing more, meeting less, and designing teams so that time zone overlap — or the lack of it — is a feature of how you work, not a bug you're constantly fighting.
Need to find meeting times across multiple time zones? Try the Time Zone Meeting Planner →