Earlier in my career, I held full accountability for a workforce exceeding a hundred people, distributed across three locations on different continents, with complete responsibility for profit and loss across all of them. We were growing quickly — in excess of thirty-five percent year over year, consistently, which is the sort of figure that reads impressively on a slide and conceals almost everything difficult about actually living through it.
Nobody had warned me that the genuine difficulty would not be hiring. Recruiting at that pace is, with sufficient discipline, a largely mechanical problem. The genuine difficulty was quieter: ensuring that a decision made in one office reflected the same judgment, the same priorities, and the same standards as a decision made in another, when the people making those decisions had never occupied the same room.
Distance does not cause the drift. Silence does.
The first time I noticed the problem, it did not present as a crisis. It was something small — two teams in two locations had quietly arrived at different definitions of what "complete" meant for a client deliverable. Neither definition was wrong, precisely. Each team had simply resolved the ambiguity locally, in isolation, because no one had made the definition explicit enough to travel across a time zone.
Multiply that by a hundred small ambiguities, and the result is an organization that appears unified on the org chart while behaving, in practice, like three distinct companies operating under a shared name. That is the real risk in scaling across geographies. It is not communication lag in the conventional sense. It is that every unstated assumption gets independently reinvented, differently, in every location, and the divergence surfaces only once the versions collide in front of a client.
What actually closed the gap
Regular calls and periodic travel helped at the margins, but the meaningful shift came from being deliberate about which decisions required central authority and which could reasonably be left to local judgment — and committing that distinction to writing rather than trusting it to instinct. Client-facing quality standards, pricing discipline, and anything touching the brand remained centralized and non-negotiable, identical everywhere. How a local team organized its own workflow to meet those standards was theirs to determine. Stated plainly like this, the distinction sounds self-evident. It took the better part of a year, and a handful of uncomfortable client conversations, to get right in practice.
The other factor that mattered more than I had anticipated was placing people from different locations on the same projects, rather than merely the same org chart. A shared org chart creates the impression of one company. Shared work creates the reality of one.
What I would tell someone beginning this now
If you are scaling a team across borders, allocate genuine time to the unglamorous work of articulating what "good" looks like before you require a hundred people to arrive at that definition independently. It is a less compelling use of time than closing the next significant client, and it will spare you the discovery, made the hard way, that three offices quietly built three different versions of your company without anyone having decided to.