The US executive hire whose team is mostly somewhere else

A large number of US executive roles now carry a shape that would have been unusual a decade ago. The seat is in Austin or Boston or the Bay Area. The reporting line runs to a US leadership team. And most of the people the person will actually lead sit somewhere else entirely: a capability centre in India, an engineering site in Poland, a delivery organisation assembled from 3 acquisitions.

The brief for that role is usually written as though none of that were true. It describes the function, the scale, the domain and the leadership level, all specified the way they'd have been when the whole organisation sat within 2 floors of each other. The distributed part shows up, if at all, as a line near the bottom about experience managing global teams, which every senior candidate will claim and which distinguishes almost nobody.

So the search optimises for the parts of the job that are legible and familiar, and leaves the part that'll actually determine whether the person succeeds to be discovered in the first 2 quarters. The brief describes the smaller half of the job. The half that decides the hire is the one nobody wrote down.

When the majority of an organisation sits outside the executive's time zone, the executive stops leading the organisation directly and starts leading it through whoever runs the site. That person was usually hired before the executive arrived, often reports through a different line, and holds relationships and context the new leader doesn't have.

This is a genuinely distinct competence, and it isn't what being good at managing remote reports prepares you for. It involves setting direction precisely enough that it survives being relayed, giving up the informal correction co-located leaders apply a hundred times a week without noticing, and building enough trust with a site leader that bad news travels upward at speed. Executives who haven't done it tend to compensate by adding meetings, which eats the overlap window they have and buys very little.

The failure mode is quiet and slow. The executive stays close to the part of the organisation they can see, the US-based product or commercial layer, and the larger part runs on inherited momentum. 6 months in, delivery is fine and nothing's obviously wrong. 12 months in, the site has quietly optimised for a direction nobody restated, and the gap is expensive to close.

Every distributed executive role has a hard constraint that never appears in the job description: the number of hours per day in which both halves of the organisation are awake. Depending on the geography it can be generous or it can be about 2 hours, and it does more to shape how the job is done than almost anything in the brief.

Executives who handle this well treat those hours as a budget to allocate deliberately, and they spend it on the things that genuinely require synchrony: decisions with real disagreement in them, escalations, the relationship with the site leader. Everything else moves to writing, and the quality of their written communication rises accordingly. Executives who handle it badly fill the window with status, arrive at the genuinely contested decisions with 10 minutes left, and defer them a day at a time.

This is worth probing directly in a search, because it separates people cleanly. Ask a candidate how they structured their overlap hours in their last distributed role. Those who've thought about it have a system and will describe it without prompting. Those who haven't will describe their calendar.

The most reliable signal in this assessment is the texture of the answers. Ask someone who's genuinely run an organisation across a time gap to describe a decision they delegated and then had to unwind, and you'll get a specific quarter, a specific person, a specific misunderstanding, and a change they made afterwards that they still use.

Ask the same question of someone whose distributed experience was 2 reports in another office, and you get principles. Over-communicate. Build trust. Assume positive intent. All true, all unfalsifiable, and all available to anyone who's read the same articles the panel has. Principles are what people offer when they don't have the specifics.

The same test works on the failure side, which is where it matters most. A leader who's done this at scale will readily describe the thing they got wrong, usually a version of assuming that agreement in a meeting meant agreement, or discovering too late that their site leader was managing upward rather than reporting. That candour is what having been through it sounds like.

Most searches for these roles run entirely within the US. The panel is US-based, the references are US-based, and the site the person will actually lead meets them after they start. It's understandable, because scheduling across a time gap is annoying, and it's a mistake. The constituency with the most at stake has no voice in choosing their own leader.

Adding one conversation with the site leadership changes two things. It gives the panel a read they can't otherwise get, because the questions that surface whether someone can lead at distance are obvious to people who've been led at distance. And it starts the working relationship before day 1, which is the relationship the executive's success will mostly run through.

It also sends a signal to the candidate worth sending. A leader who's told, during the process, that the organisation they'll run gets a say in hiring them learns something accurate about the company. So does a leader who's told the opposite by omission.

The repair here isn't a new assessment methodology. It's writing down the part of the job everybody knows about and nobody specifies: how much of the organisation sits elsewhere, how many hours of overlap exist, who the site leader is and what they own, and which decisions have to cross the gap. That takes an hour, and it changes the search materially, because it changes what the panel is allowed to weigh.

Done properly, it also changes the candidate pool. Some strong people will look at an honest version of the role and decline, which is a good outcome discovered early rather than a resignation discovered in month 9. Others who didn't look obvious on paper, because their last title was smaller or their logo less familiar, will stand out, because they've actually done the hard part of this job before.

The distributed executive seat is a different job, with a different centre of gravity, and at a great many companies it's being filled by a process built for the co-located one.