Leading Teams Across Borders

An international programme is rarely held back by a lack of talent. It is held back by distance: different countries, different habits, and different ways of understanding the same sentence.

At AURES Group, I managed and coordinated different teams across France, the United States, the United Kingdom, Germany and Australia on retail technology programmes. On those programmes, every team could do excellent work and the whole could still slip.

What had to move forward

The subjects were heavy: migrating kiosk and self-service applications from WinDev to React, content management systems for interactive kiosks, integrated payments and cash automation. Each of them touched product, engineering and clients at the same time.

My role was to keep everyone aligned. I organised the work between teams, arbitrated priorities across projects, and followed delivery quality. The technical implementation belonged to the technical teams.

Where the work gets lost

Time zones shrink the hours when everyone can decide together. Teams do not share the same context, and what is obvious in one office is invisible in another. Testing happens far from where the product is really used.

Work rarely failed inside someone's task. It failed between two people, at the handoff, when the reasons for a decision stayed behind. Hence the rule that guided how I worked: one clear owner for each piece of work, and reasons that travel with the task.

What it taught me for what came next

When I started building AI agent systems, I recognised this problem immediately. A general agent handing a request to a specialist loses context exactly as one team does when it passes a file to another.

Work rarely fails inside someone's task. It fails at the handoff. Multi-agent systems break in exactly the same place.