Working with a team in another country, and the hours between you

The overlap window is the whole constraint

Working with colleagues in another country gets described as a cultural problem, and occasionally it is, but the thing that actually decides how your week goes is arithmetic. Two locations share a certain number of hours in which both are awake and at their desks, and every question that needs an answer from the other side either fits inside that window or waits for the next one. Almost everything else follows from that single number.

Where the overlap is six hours, the arrangement feels close to normal and nobody remarks on it. Where it is two, one misunderstanding costs a day, and three misunderstandings in sequence cost the better part of a week without anybody having done anything wrong. Find out what your real overlap is in the first fortnight, because most of the advice you will be offered quietly assumes a larger one than you have.

A round trip is the unit of delay

The useful way to think about a request that crosses time zones is not how long the work will take but how many round trips it needs. A question that can be answered yes or no costs one. A question that will produce a clarifying question in reply costs two, and by the time that has played out, two working days are gone and nobody has done anything except read.

That changes how you should write. Anticipate the obvious follow-up and answer it in the same message, supply the context that makes a reply possible without a second exchange, and where your request has two plausible readings, say which one you mean. It feels laborious compared with leaning over to ask someone sitting near you. It is still considerably faster than waiting until tomorrow to find out they read it the other way.

Where a decision genuinely needs conversation, spend the overlap on that and nothing else. Status updates and anything a person can read at their leisure should never occupy a shared hour, because those hours are the scarcest thing either team has.

The calendar nobody sent you

Public holidays are the most common ambush, and they rarely surprise anyone except the person waiting for a reply. The working week is not universal either; in parts of the world it does not run Monday to Friday, and in others the standard day starts and finishes hours away from yours. Some countries effectively close for a week at a fixed point in the year, and a plan that ignores that will fail on schedule.

Put the other location’s holidays into your own calendar during your first month, ask what the normal working hours actually are rather than what the contract says, and find out whether there is a season when the office empties. This is unglamorous work and it prevents a category of failure that is otherwise invisible until it happens to you.

Directness does not survive the journey

The colleague writing to you may be working in their second or third language, and the fluency you see in their writing is not always the fluency they have in a live call. Politeness registers differ too. In some working cultures a flat no is normal and carries no charge; in others the same message arrives as a comment about timing or difficulty, and treating it as anything other than a refusal will waste a fortnight.

Your own phrasing is being decoded on the same terms, and it may be landing as blunt, or as so hedged that nobody can tell what you want. Neither is a character judgement. It is worth asking a colleague on the other side, once and privately, how your messages read, because that is a question people answer honestly and almost nobody thinks to ask.

Somebody is absorbing the inconvenience

When two places barely overlap, meetings happen early for one side or late for the other, and the cost lands on real evenings and real mornings. Watch where it lands over a couple of months. If the recurring calls are always uncomfortable for the same office, that is a decision the organisation has made, whether or not anyone framed it as one.

Often the burden falls on whichever side is smaller, newer or more junior, which is the least defensible basis for it and the most common. A rotating schedule costs nothing except a little administration. If yours does not rotate, it is reasonable to raise it once, framed as sustainability rather than grievance, and then to note the answer, because how a place responds to that question tells you a good deal about it.

What you can change from where you sit

Default to writing. Record the decision rather than the discussion, keep the record somewhere both sides can reach it, and treat anything agreed only on a call as provisional until it exists in text. Build one genuine relationship on the other side, because a person who will tell you informally that a plan is unpopular there is worth more than any amount of process.

The honest limit is that no personal habit fixes a badly designed arrangement. If your role requires continuous live collaboration across a two-hour overlap, you are being asked to solve a structural problem with willpower, and that ends the way it usually ends. Naming the constraint clearly, in terms of what is achievable rather than what is unfair, is the most useful thing you can do with it.