Running an Executive Team Split Across Time Zones
A leadership team spread across time zones tends to drift toward one default: whoever happens to be awake and in the room decides, and everyone else finds out later. That pattern quietly concentrates power in whichever time zone matches headquarters, regardless of who's actually best positioned to decide.
Fixing this isn't about more meetings. It's about making sure a decision doesn't require everyone to be online at once.
Write the decision down before it's made, not just after
Every real decision should exist as a short written record: what was decided, why, who made the call, and what would change it. This matters more for a distributed team than a co-located one, because the informal hallway context that fills in gaps for people in the same office simply doesn't exist for someone eight time zones away.
Circulate the decision log the same day, not at the end of the week. A decision that a colleague learns about three days later, after already acting on the old assumption, creates exactly the kind of friction distributed teams are most vulnerable to.
A useful written decision record captures:
- What was decided, stated in a sentence or two that someone in a distant time zone can read without any hallway context.
- The reasoning behind the call, so colleagues who were offline can see why it was made and challenge it constructively.
- The named person who made the decision, so everyone knows who owns the outcome and whom to ask about it.
- What new information would change the decision, which tells colleagues when to raise a concern instead of quietly working around it.
- The date it was circulated, ideally the same day, so nobody acts on an outdated assumption for several days.
How do you fix and protect a real overlap window?
Identify the two or three hours where the most people across time zones are reasonably awake, and reserve that window specifically for decisions that need live discussion rather than filling it with routine status updates that could just as easily be async. Burning the one shared window on updates that don't need a live discussion is a common, avoidable mistake.
Rotate which time zone bears the inconvenience of an early or late call when a live discussion is unavoidable outside the overlap window. Always defaulting to the same person's evening or early morning erodes goodwill quietly over time.
How do you assign a default decision-maker per domain?
Rather than deciding case by case who has final say, assign a named owner for each major decision area in advance, so a time-sensitive call doesn't stall waiting for someone in a far time zone to wake up and weigh in. The owner should still solicit input from anyone materially affected, just not require their live presence to actually make the call.
Revisit these assignments periodically as roles shift. An ownership map set a year ago can quietly become outdated as the team's structure changes.
Watch for the time-zone power imbalance specifically
It's easy for whoever shares a time zone with the founder or CEO to become the de facto decision filter, simply because they're available for every impromptu conversation the others miss. Notice when the same one or two people keep showing up in every important thread, and check whether that reflects their actual role or just their time zone's proximity to headquarters.
Give leaders in other time zones a standing, protected way to raise something urgent outside the overlap window, rather than leaving it to informal messages that might not get seen for hours.
For example, if the same two leaders near headquarters appear on every important thread, try a simple audit. List the last ten significant decisions and note who was consulted, who decided, and which time zone each person sits in. If the pattern shows one region deciding most of them, the cause is usually availability, not authority. The fix is to give the underrepresented region ownership of specific domains, and to route their input into the written record before the decision is made, not after. Review the same list a quarter later to see whether the pattern has actually changed, and adjust the ownership map if it has not.
The specific habit that breaks this pattern for good
Before closing out any significant decision, ask explicitly whether everyone materially affected has actually weighed in, not just whoever happened to be online when the conversation started. This single check, asked consistently, catches most of the drift toward decisions being made by availability rather than by who should actually be deciding.
Onboarding a new executive into an already-distributed team
A new leader joining a distributed team often defaults to whatever hours feel natural to them personally, without realizing they're inheriting an existing, carefully negotiated overlap window. Walk them through the current schedule and the reasoning behind it explicitly in their first week, rather than letting them discover the pattern by trial and error.
Ask them directly, early, which hours genuinely don't work for them long term and why. It's far easier to adjust a shared schedule once, deliberately, than to slowly renegotiate it after months of quiet friction that nobody actually names directly until it's already affected how included the new leader feels on the team.
What Good Looks Like
A well-run distributed leadership team has a named default decision-maker for every major domain and a written decision log that goes out the same day a call is made.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Frequently Asked Questions
How often should a distributed leadership team meet with everyone live?
Less often than a co-located team might assume they need to, and with a clear agenda that justifies requiring live attendance. Reserve live time specifically for genuine discussion and decisions, and handle status updates asynchronously.
Should decision logs be visible to the whole company, or just leadership?
That depends on the sensitivity of the specific decision, but a written record should exist regardless of who can see it. Even a leadership-only log solves the core problem of someone finding out about a decision late and having acted on outdated information in the meantime.
What if one time zone consistently ends up making more decisions than the others?
That's the pattern to actively watch for and correct, usually by assigning explicit domain ownership rather than letting availability decide informally. If it persists despite that, it's worth naming directly rather than assuming it will self-correct.
Is a fully async leadership team realistic, with no live overlap at all?
It's possible but harder to sustain over time; even a small protected overlap window meaningfully improves the speed and quality of genuinely hard decisions. Most distributed leadership teams find some regular live time is worth protecting even when the schedule is inconvenient.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
Optery vs DeleteMe for Distribution Company Owners
A pitfalls-first checklist for wholesale and supply chain distribution executives comparing Optery's automated removal to DeleteMe's service.
Wholesale Distributors: Working Capital Is the Whole Game
Thin margins and heavy working capital define B2B distribution. A step-by-step look at the fractional CFO vs controller decision for a distributor.
Adding an Outside Board Member at a Family Distribution Business
A worked example of a family-owned B2B wholesale distributor adding its first outside board member, and how that changes governance tooling needs.
Pitfalls in Hiring a VP of Supply Chain
Pitfalls a B2B wholesale or supply chain distribution company should watch for when choosing a search firm versus an executive marketplace.
Carta vs Forge For A Family-Owned Distribution Business
Family succession and working capital constraints shape how a B2B wholesale and supply chain distribution business should weigh Carta against Forge.
A Founder's Buyout: Loan, Equity, or Both?
A worked example of a wholesale distributor's founder financing a key employee's ownership buy-in with a loan, equity, or a blend of both.