Managing teams across five different time zones reveals whether an organisation is well designed or merely well connected
The promise repeated over the last ten years was tempting: with videoconferencing and instant messaging, distance would cease to be a real obstacle. Any company could build global teams without paying the price of geographic dispersal. Technology would resolve coordination, and coordination would resolve collaboration.
That promise was partially true and completely insufficient.
What digitalisation eliminated was the cost of transmitting information between continents. What it did not eliminate was the cost of interpreting that information consistently, of making decisions without ambiguity, and of maintaining working relationships capable of withstanding the accumulated friction of weeks without face-to-face contact. Technology reduced technical distance. Organisational distance remains intact for the majority of companies that believe they have already resolved it.
The analysis recently published by Art Markman in Fast Company on the three factors that determine the performance of globally distributed teams is not a conceptual novelty. But its value lies elsewhere: it is a silent diagnostic of the organisational maturity of any company that operates with people separated by time zones. Reading its three recommendations not as management advice but as audit criteria reveals something more uncomfortable than a scheduling problem: it reveals poorly executed design disguised as a cultural challenge.
When digital proximity produces teams that know each other from a distance
The first point of the analysis is the one that most unsettles CFOs: the explicit recommendation to invest in periodic in-person meetings for globally distributed teams. Not as an added benefit. As an operational mechanism.
The conceptual foundation cited in the article points to a phenomenon that organisational psychologists document with consistency: people who are physically distant become abstract to those who work with them. This is not a metaphor. It is a description of how social cognition functions under conditions of spatial separation. A colleague in Singapore whom you have never met in person ends up reduced to their function on Slack and to the quality of their video connection. They cease to be a professional with a history, a context, nuance — and become a functional node in the team. That is not cohesion. It is minimal coordination with high exposure to poorly managed conflicts.
The recommendation to structure those in-person encounters around concrete projects, with separate time for strategy and informal activities, responds to an organisational design logic that companies typically ignore when they view corporate travel as a discretionary cost. The problem is not the cost of the flight. The problem is that without that investment, teams tend to consolidate along geographic lines, because professionals who share a time zone spend more hours together and frequently share cultural context as well. The predictable result is a global team that operates as two or three regional teams with a layer of formal coordination on top. The illusion of integration conceals the real fragmentation.
This is a design failure, not a communication failure. And it has measurable consequences: it slows decisions that require alignment between regions, produces divergent interpretations of the same objectives, and generates asymmetries of influence in which the nodes with the greatest overlap in working hours capture more attention and resources from central leadership.
The schedule is not an administrative detail
The second dimension of the analysis points to something that appears logistical until it becomes a retention crisis: the explicit management of working hours in teams that operate across continents.
The typical trap works as follows. A company hires talent in three or four regions of the world. Messaging tools are always active. No clear policy exists regarding expectations for responses outside local working hours. The result is that some team members end up functioning as nodes of permanent availability — not because anyone asked them explicitly, but because the ambiguity of the design made it implicitly inevitable.
The article proposes specific controls: defining working hours clearly, including in job descriptions any foreseeable out-of-hours responsibilities, building project calendars that incorporate the real coordination time between regions, and designing handoffs between time zones that extend the company's operational day without extending each individual's personal working day.
Each of those controls seems reasonable in the abstract. The majority of organisations do not implement them because doing so requires someone to deliberately design the system, and that design forces an acknowledgement that the current operating model carries hidden costs that are being absorbed invisibly by certain members of the team. Market figures illustrate the scale of the problem: the proportion of meetings involving multiple time zones grew by eight percentage points since 2021, and messages received outside average working hours already exceed five dozen per person per day, according to data compiled from enterprise productivity platforms. This is not a marginal burden.
The cost of not designing working hours does not disappear. It is transferred to the employee. And when the employee has absorbed that cost long enough, they resolve it in the only way available to them: they leave. The cycle of turnover in poorly designed global teams is not diagnosed as an organisational design failure. It is diagnosed as a talent retention problem and answered with more benefits. The symptom receives treatment. The structural cause remains.
A shared language does not guarantee shared interpretation
The third dimension is the most subtle and, in terms of operational risk, probably the most costly: differences in language and culture within teams that believe they are communicating clearly because they use the same words.
The example cited in the article captures the mechanics with precision. A phrase such as "can you handle that?" can function as a direct instruction in one cultural context, and as an informal, low-priority enquiry in another. Neither party is making an error. Both are operating according to their habitual linguistic and cultural conventions. The problem appears afterwards, when the task has not been completed and each party recalls the interaction differently because both interpreted it differently from the very first moment.
This is not a problem of courtesy. It is a problem of undocumented responsibility assignment that remains invisible until the project exposes it. And it has a second layer that the article identifies with additional precision: differences in the relationship with hierarchy. In organisations with flatter structures, the expectation is that team members will challenge the leader when they detect a problem. In organisations with more hierarchical cultures, silence in the presence of leadership does not mean passive agreement. It means active respect for authority. A leader who interprets that silence as validation is making decisions on the basis of incomplete information without knowing it.
The operational response proposed by the article is more literal communication and more explicit documentation: confirming decisions in writing, assigning responsibilities by name, recording deadlines, and creating formal processes for channelling disagreement. What it does not say, but what emerges from the analysis, is that implementing those processes requires leadership to first acknowledge that its current communication model assumes a cultural homogeneity that does not exist. That acknowledgement is not trivial in organisations where the communication style of central leadership is perceived — frequently without examination — as the neutral or universal style.
Collaboration software grew. Organisational maturity, far less so
The market for collaboration tools for distributed teams projects sustained growth over the coming years. Available estimates place the specific segment of team collaboration software at around 44 billion dollars in 2026, with projections carrying it beyond 85 billion dollars by 2033. The broader remote-work technology market exceeds 69 billion dollars in 2026 on a comparable trajectory.
Those figures describe a market growing with conviction on the basis of a premise that the article indirectly questions: that the problem of distributed teams is primarily technological. Corporate investment in collaboration software has not declined. Neither has the difficulty of managing teams operating across multiple continents.
The gap between those two curves is not an accident. It reflects the fact that organisations continue to purchase technical solutions for problems that originate in design. A more sophisticated messaging system does not resolve ambiguity in the assignment of responsibilities. A project management platform does not build the interpersonal trust that develops in in-person settings. Tools are transmission layers. They are not interpretation layers or cohesion layers.
This does not invalidate investment in technology. It invalidates such investment when it is used as a substitute for the design decisions that no one wants to make because making them requires admitting that the current operating model has structural flaws. It is more comfortable to add a tool than to redesign how working hours are distributed, how decisions are documented, or how much budget is allocated to in-person meetings that the CFO continues to classify as a discretionary cost.
The organisational maturity of a global team is not measured by the number of platforms it uses. It is measured by the clarity with which it knows who decides what, when a response is expected, and what silence means in each part of the team. None of those three things comes pre-installed in any software on the market.
An organisation that connected its people with good tools but did not design the work system that sustains them has not resolved the problem of distance. It has merely made it faster and more visible.
