The promise of remote work that gets the least scrutiny is also the most consequential: the ability to hire the best person for a role regardless of where they sleep. Firms reach for it constantly and then quietly retreat, because a team spread across eight time zones that still runs on meetings is a team where someone is always awake at the wrong hour. The retreat is avoidable, but only if the firm understands what actually makes distance workable. It is not overlapping hours. It is asynchronous work, and async has a hard prerequisite.
Overlap does not scale, documentation does
A globally distributed team has a fixed enemy, which is the shrinking window in which everyone is awake at once. If the operating model depends on that window, the team is capped by geography no matter how good the hires. The all-remote company GitLab has organized itself around removing the dependency. It runs handbook-first, with communication documented in a public handbook that would exceed 2,000 printed pages, and it states plainly that asynchronous work is impossible without strong documentation, because otherwise a single follow-up question blocks a colleague for hours or days (GitLab handbook, 2026). That last clause is the entire time-zone problem in one sentence. When the person who can answer your question is asleep, the difference between a documented answer and an undocumented one is the difference between continuing and stalling for a full working day.
This is a self-reported case rather than a measured outcome, and it should be read with that limit in mind. But the mechanism is not exotic. It says that a written record lets a colleague in another time zone serve themselves the answer instead of waiting for overlap. Documentation converts a synchronous dependency into an asynchronous one, and it is that conversion, not a generous set of shared hours, that makes distance survivable.
Output-based judgment is the other half
Removing the need for simultaneous presence forces a second change. If a manager in one hemisphere cannot observe a report in another, the manager has to evaluate results rather than activity. Matt Mullenweg, who runs the globally distributed company Automattic, builds his account of distributed maturity around exactly this shift, placing the move to judging work by output rather than hours at the center of the model (Mullenweg, 2020). His is a practitioner's view rather than a study, and his stronger claim that a distributed firm beats any in-person one is asserted without evidence. Treated as a design principle rather than a proven result, though, it fits the time-zone case precisely. Across distance you cannot manage the clock, so you must be able to manage the deliverable.
The experimental record gives some reassurance that judging work this way does not sacrifice performance. In the randomized Trip.com trial, hybrid workers were evaluated on output and showed no measured drop in performance ratings or promotions relative to fully office-based peers (Bloom, Han and Liang, 2024). That study was not about time zones, and it should not be stretched to claim more than it measured. What it does support is the narrower link this argument needs, that output can be assessed without co-presence and the assessment holds up.
The advantage on offer
Put the two pieces together and the payoff is concrete. A firm that documents rigorously and judges by output is no longer bidding for talent in one metropolitan labor market. It can hire the strongest candidate on three continents and let them contribute on their own clock, because the handbook answers the questions that would otherwise require a shared hour. The competitors still running on meetings are quietly restricting themselves to whoever can attend at the same time, which is a narrower and more expensive pool than they admit.
A caution belongs here. Nothing in the evidence proves that a fully distributed, follow-the-sun operation outperforms a co-located one in general. The Trip.com trial covered a single Chinese firm and studied hybrid, not global async, and GitLab's account is the company describing its own practice. The defensible claim is smaller and still valuable: async plus documentation is the specific capability that turns a scattered team from a coordination tax into a hiring advantage.
The practical read
A leader who wants to hire across the map should stop negotiating meeting windows and start auditing documentation. The right test is simple. If a new engineer in a time zone twelve hours away joined tomorrow, how many of their first-week questions could be answered by a document rather than a person? The higher that number, the more of the world the firm can hire from. The competitor across the street who still schedules everything is quietly paying a premium to hire from a single time zone, and calling that constraint a culture. The advantage of distributed work was never the office you closed. It was the map you opened, and async, built on documentation and output-based judgment, is the only thing that keeps it open.
Sources
- GitLab handbook (2026). Handbook-first and asynchronous work. States that async is impossible without documentation because a follow-up question otherwise blocks a colleague for hours or days, the core mechanism that makes cross-time-zone work viable. https://handbook.gitlab.com/handbook/company/culture/all-remote/asynchronous/
- Mullenweg (2020). Five Levels of Autonomy. Practitioner model centering the shift to judging output over hours, the management change that distance across time zones requires. https://ma.tt/2020/04/five-levels-of-autonomy/
- Bloom, Han and Liang (2024). Hybrid working from home improves retention without damaging performance (Nature 630). Shows output-based evaluation held performance and promotion steady, supporting the claim that work can be judged without co-presence. https://www.nature.com/articles/s41586-024-07500-2