Five Countries and the Handoff Problem

On international technology programmes, work rarely fails inside someone's task. People are good at their jobs. It fails in between.

It fails at the handoff from product to engineering, between one country's team and the next, whenever the context stays in someone's head and the next person has to guess, or ask again, or start from an assumption nobody wrote down.

What distance really does

At AURES Group, I coordinated teams across France, the United States, the United Kingdom, Germany and Australia. Time zones are the obvious problem, because they shrink the hours when people can decide together. The less obvious problem is context. What is evident in one office is invisible in another, and the same sentence does not mean the same thing to everybody.

The instinct, and what worked

The instinct is to add coordination: more meetings, more reports. Mostly that adds noise.

What worked was structural. One clear owner at every moment. Reasons that travel with the task, not just the instruction. And no silent endings: a piece of work finishes with a result or a visible blockage, never with nothing.

The objection

Writing things down feels slow when everybody is busy. It is, on the first day. It stops being slow around the third time somebody in another country would otherwise have had to wait until tomorrow for an answer.

Before you add another meeting, draw the handoffs. Each arrow on that diagram is a place where work can get lost.