Managing a distributed team is not managing a co-located team over video. The best practices that work rely on written communication, deliberate structure and an acceptance that some things take longer.
Across five time zones, the usual advice about frequent calls stops applying entirely.
Asynchronous by default
The foundational decision. If most work requires people to be online simultaneously, a wide time-zone spread will not function.
In practice this means decisions are documented rather than made in conversation, questions are asked in a way that does not block the asker, and status is visible without a meeting. It also means accepting that a decision requiring input from three regions takes two days rather than an hour — and that this is usually fine.
The common failure is a team that claims to be asynchronous while all real decisions happen in a call that one region cannot attend. People in that region learn that their input arrives after the fact, and they disengage.
Write things down, properly
Written communication is the primary medium, and the quality of writing becomes a core competence rather than a nice-to-have.
Three practices carry most of the benefit.
Decision records. What was decided, why, what alternatives were considered, who decided, when. A short document per significant decision. This prevents the same argument recurring and lets someone in another region understand the reasoning without asking.
Context in requests. A message saying “can you look at this?” costs a round trip of twelve hours. The same message with the background, what you have tried and what specifically you need resolves in one.
Default to public channels. Information in direct messages is invisible to everyone else and has to be repeated. A team that works in open channels accumulates searchable context.
Overlap hours
Pure asynchrony is harder than it sounds for anything requiring real-time discussion. Some overlap is necessary.
Across five time zones, a universal overlap may be two hours or none. Two approaches work.
A defined core window where everyone is expected to be available, accepting that it is early for some and late for others, with the burden rotated rather than always falling on the same region.
Hub overlaps where no universal window exists: each pair of adjacent regions has an overlap, and information flows along the chain. Slower, and it does not require anyone to work at 3am.
Protect the overlap for things that genuinely need synchronous discussion. Using it for status updates wastes the scarcest resource the team has.
Meetings
Fewer, shorter, and with a written alternative where possible.
Every recurring meeting should have a stated purpose and a periodic review of whether it still serves it. Status meetings should generally be replaced by written updates, which are faster to produce, faster to consume and searchable afterwards.
Record what is recorded, and write a summary regardless — a recording nobody has time to watch is not inclusion.
Rotate times for anything recurring. A weekly meeting permanently at 7am for one region is a decision to disadvantage that region.
What distance makes worse
Four problems that exist in every team and are amplified by distance.
Ambiguity about ownership. In an office, confusion surfaces quickly. Remotely, two people can work on the same thing for a week. Name an owner for everything, explicitly.
Small misunderstandings compounding. Without tone and body language, a terse message reads as annoyance. Assume good intent, and when something feels wrong, move to a call rather than exchanging increasingly careful text.
Uneven visibility. People in the headquarters time zone are more visible and get more opportunities. This is the most serious equity issue in distributed teams and it requires deliberate correction — in promotion decisions, in who is asked to lead things, and in whose questions get answered.
Isolation. Some people thrive remotely and some struggle, and the struggling is less visible. This is a management responsibility rather than a culture-activity problem.
One-to-ones matter more
In a distributed team, the regular one-to-one is often a manager’s only reliable window into how someone is doing.
Keep them, do not cancel them, and make them about the person rather than about project status, which should be written down elsewhere. Thirty minutes weekly or fortnightly is a reasonable baseline.
Ask directly about workload, blockers and whether they feel connected to the work. Remotely, nobody volunteers that they are struggling.
Onboarding is where distributed teams fail most
A new starter in an office absorbs context by proximity. Remotely they absorb nothing unless it is written down.
This means documentation has to be good enough for someone to self-serve, a named buddy in a compatible time zone matters more than usual, and the first month needs more structure than a co-located equivalent. See employee onboarding.
In-person time
Most successful distributed companies bring people together periodically — commonly twice a year for several days.
Use it for what distance makes hard: relationship building, contentious discussions, planning that benefits from a whiteboard. Not for status updates or presentations, which work fine remotely and waste expensive time together.
Hiring for distributed work
Not everyone works well remotely, and the attributes that predict it are not the ones most interviews test.
Three that matter. Written clarity — the ability to explain something unambiguously in text is the core competence of a distributed team, and it is directly observable from a written exercise or from the candidate’s own emails. Self-direction — comfort making decisions without checking, and judgement about when checking is warranted. Proactive communication — flagging a problem before being asked, which is the behaviour that distance makes essential and that nobody can supervise into existence.
Time zone is a real constraint and should be stated honestly in the job description rather than discovered at offer stage. “Must overlap four hours with Central European Time” is a fair requirement; discovering after hiring that the overlap does not work is expensive for everyone.
Tools, briefly
Tooling matters less than the practices it supports, and a few decisions reduce friction materially.
One place for long-form written material, searchable, where decisions and documentation live. One place for conversation, organised around topics rather than people. One place for work tracking, where the current state of anything can be seen without asking. And one shared calendar showing everyone’s working hours in their own time zone, which removes a surprising amount of daily friction.
The failure is not too few tools but too many overlapping ones — three places where a decision might be recorded means no reliable place to look. Pick one of each and be strict about it.
Goals in a distributed team
Alignment is harder at a distance, because the informal correction that happens in an office does not occur. Written, visible goals do more work in a distributed team than in a co-located one, where people pick up priorities by proximity.
Whatever framework is used, the requirement is the same: everyone can see what the team is trying to achieve this quarter and how it is progressing, without asking. OKRs are one way to do that, and the discipline matters more than the format.
Frequently asked questions
How much time-zone overlap is needed?
Two to four hours between people who work together closely is a common target. Wider spreads work with genuinely asynchronous practices and require more discipline.
Should remote teams have core hours?
A short defined window helps, provided it is reasonable for everyone and the inconvenience is shared rather than always falling on the same people.
How do you build culture remotely?
Mostly through how work is done — how decisions are made, how disagreement is handled, how people are treated. Social events help at the margin and do not substitute for the substance.
Is remote work less productive?
The evidence is mixed and depends heavily on the work and the practices. Teams with good written communication and clear ownership generally do well; teams that replicate office habits over video generally do not.
