The companies outpacing their industries right now share one structural characteristic that has nothing to do with their product. Their best engineers are not in the same building. Their operations span multiple time zones, managed by people who have never shared an office and, in most cases, never will. The distributed structure was a deliberate operating decision, made early and designed from the start.
The Hidden Toll of Building Teams in One Place
For most of the last century, building a company meant building it somewhere. A headquarters, a campus, a cluster of floors in the same metropolitan area. The logic was straightforward: proximity enabled communication, communication enabled coordination, and coordination enabled execution. Geography was not incidental to the operation. It was the operation.
The hidden cost of that model rarely got examined. Geographic concentration capped talent access to whatever was available within commuting distance. It tied overhead to real estate in markets that were not always the most efficient. It forced compensation to track zip codes rather than expertise. Companies that built well despite those constraints were not succeeding because of them. They were succeeding in spite of them, and most did not realize the distinction until a competitor operating differently started closing the gap.
Why the Shift Is Structural, Not Cultural
The public conversation around distributed work has mostly been a cultural debate: do people focus better at home, or do they need an office to collaborate? That framing is not wrong, exactly, but it addresses the wrong question. The more consequential argument is about access, specifically about whether the talent a company needs is available within the geography it has historically been willing to hire from.
Pablo Gerboles Parrilla, the Spanish entrepreneur who leads global DevOps infrastructure work through his firm AliveDevOps, has structured his entire model around this principle. His teams are distributed across multiple countries and time zones. They are also, by design, lean, with headcount held to the minimum needed for the work rather than grown to fill an organizational chart.
“There’s no reason to limit yourself to local talent when you can build distributed teams across the world with specialists who’ve already done what you’re trying to do,” he has said. The logic is practical, not philosophical. Specialists who have already solved your specific problem exist somewhere in the world. A geographic hiring constraint is simply a mechanism for not finding them.
Building Around the Business Model, Not the Org Chart
Most companies transitioning to distributed work make the same mistake. They try to replicate the office in a digital environment, which means more synchronous meetings, more activity monitoring, and a persistent anxiety about whether remote employees are actually working. What they fail to do is redesign the operating model to match how distributed teams actually function best.
Gerboles Parrilla takes a different starting point. Every team he builds begins as a blank slate configured around what the specific business model requires, not what a standard org chart would suggest. Roles that can be automated are not filled by people. Generalist hires are avoided in favor of specialists brought in for defined problems. Headcount stays disciplined until growth data makes the case for expansion, not when growth ambition does.
“We build teams like we build products, custom, lean, and aligned with the business model,” he said. That discipline is part of what allowed Gerboles Parrilla to scale from six-figure to seven-figure annual revenue without outside investment, running operations from Costa Rica with a team spread across several countries. Restraint, applied consistently, compounds.
What Distributed Work Actually Demands From Leadership
Distributed teams fail in predictable ways. Most of those failures originate in leadership, not logistics. Physical proximity creates a layer of ambient information that leaders rely on without fully recognizing it: the disengaged expression in a meeting room, the hallway conversation that surfaces a client problem before it becomes a crisis, the shared awareness of what everyone else is working on and how things are going. Remove the office, and all of that disappears. Leaders who depended on those signals tend to discover the gap only after something breaks.
The discipline required to lead distributed teams well resembles high-performance athletics more than it resembles conventional management. For Pablo Gerboles Parrilla, that connection is not abstract. Years of competitive golf trained a specific operating habit: define the goal before the round begins, treat every decision as consequential, and hold execution to an unambiguous standard. Ambiguity is expensive on a golf course. It is equally expensive inside a distributed operation.
He carries those habits into how he runs his businesses today. Weekly payroll is personally reviewed and sent by Gerboles Parrilla every Monday morning. His daily structure begins with a meditation practice and physical training before any client communication happens. Team expectations are set ahead of meetings, not negotiated inside them. None of this is incidental. Structure is what makes distributed execution reliable, and reliability is what allows a lean team to perform at the level a larger one would struggle to match.
Where Distributed Teams Most Commonly Break Down
The most common distributed team failure is not a tool problem or a time zone problem. It is an accountability gap between what a distributed-first policy promises and what the management structure actually delivers. Companies announce remote-first or distributed-first approaches, then continue measuring inputs: hours logged, Slack messages sent, video calls attended. The one measure that matters, whether the work was completed to the required standard on the required schedule, often goes unmeasured entirely.
“Speed without clarity is chaos,” Gerboles Parrilla has observed. “But clarity without speed is just a nice idea that never happens.” Both failure modes show up in distributed teams, sometimes in the same organization. One team moves fast and constantly misaligns on what success looks like. Another team aligns carefully and slowly, then runs out of runway before the work ships. The gap between those outcomes is leadership precision, specifically the ability to communicate expectations clearly enough that a team member in a different country and time zone never has to guess.
A better project management platform does not close that gap. Sharper leadership does.
The Compounding Advantage Most Leaders Miss
There is a long-term benefit to building distributed teams that most leaders only fully understand once they have experienced it. When hiring is global and the structure is tight, the people who end up on the team have almost always confronted the exact problem being asked of them before. A specialist two time zones away who has spent years solving the specific infrastructure challenge your engineering team is stuck on does not appear in a local talent search. The performance marketer who has built distributed marketing operations for a dozen comparable companies is not commuting distance from most headquarters. That is not bad luck. It is a predictable consequence of where expertise actually concentrates.
Gerboles Parrilla has built his ventures on that logic since the beginning, and it shows in how quickly new initiatives move from concept to operational. By the time a traditionally-staffed organization finishes onboarding a new team for an initiative, a lean distributed team assembled from specialists has typically already shipped a working version, gathered early feedback, and begun the next iteration. The speed differential is not a function of harder work. It is a function of better access to people who have done the work before.
Read also: How to Use Technology to Prepare for Job Interviews in 2026
The Operating Standard Has Already Changed
The companies that will define the next decade of competitive leadership are mostly building this way already. The structural shift is not approaching. It has happened. Talent is distributed by default, tools are adequate, and the cost argument for geographic hiring no longer holds in most industries. What has not caught up, in a significant number of organizations, is the management model required to make distributed teams actually perform.
Building across borders, time zones, and organizational structures is a solvable problem. The leaders who have solved it are not managing a workaround. They are running the operating model that everyone else is still trying to reach.
