The short version
- An office runs services nobody invoices for. Spread the team across four time zones and every one of those services still has to happen, now with an owner against it and a slot in the week.
- Correction latency breaks first. A wrong assumption now waits for the overlap window to open before anybody is awake to contradict it.
- Post work in progress in a shared channel rather than a finished version in a document. Correction only lands on work other people can see.
An office runs a set of services nobody puts on an invoice. Somebody contradicts your wrong assumption before you have built on it, and you can see who is drowning without having to ask. Our team works across four time zones and none of that arrives on its own. Each service has to be rebuilt as something with an owner and a place in the week.
What does an office actually give a team?
Four things, none of which appear on the lease. Correction speed, because a wrong assumption said out loud gets contradicted by whoever hears it. Load visibility, because you can see who has not left their desk. Context absorption is the half of every conversation never addressed to you and absorbed anyway. The fourth is onboarding by proximity, where a new person learns the standard by watching somebody hold it rather than by reading it.
None of that was free. It was bundled into the rent, and it worked because everybody paid the same overhead during the same hours.
What the office supplied, and what has to replace it:
| What an office did | How it happened | What replaces it |
|---|---|---|
| Corrected a wrong assumption | Overheard | Work in progress posted in a shared channel |
| Taught the standard | Sitting near someone who held it | Recorded walkthroughs plus a written standard |
| Carried decision context | Hallway conversation | Decisions recorded where the work lives |
| Built relationships | Proximity and lunch | Scheduled 1-1s with no agenda |
Which of those breaks first when a team spreads across time zones?
Correction speed. A wrong assumption that would have been contradicted in the room now waits for the overlap window, and across four time zones the overlap window may not open again until tomorrow.
Load visibility goes quieter still. On a video call everyone looks the same.
What replaces overhearing?
Working in the open, which is a habit rather than a tool. The draft goes into a shared channel while it is still wrong. The half-built page gets a link before anyone asks for one. Correction can only land on work that other people can see.
The client-facing version of the same habit is one shared channel per relationship rather than a scattering of direct messages. A decision reached in a direct message does not exist for anybody else on the team.
How do you schedule what used to be ambient?
Put an owner and a time against each one. Correction gets a shared channel and an expectation that unfinished work appears in it. Decisions get recorded where the work lives instead of inside a private thread. For onboarding, a recorded walkthrough plus a written standard the new person can read before anybody is awake to ask.
That is more administration than an office needs, and it is the real price of distribution. We run 8 client accounts and 11 brands this way on a weekly delivery cadence, with every client call held on a Monday or a Tuesday, which keeps the overlap window for the conversations that genuinely need everybody awake at once. The recordings from those calls become action items on the Wednesday, each with an owner and a date. Everything else moves as writing.
We work across four time zones, so every service the office ran ambiently has to be scheduled explicitly, with a name against it.
Is distribution worth the overhead?
Yes, and the reason is hiring rather than rent. Across 40+ countries of operating, the person I wanted for a given job has rarely been within commuting distance of an office I already had. The roster now carries 3 AI engineers sitting inside a marketing team.
The trade is real. Everything the office did ambiently comes back as something a person has to sit down and write.
More on the shape of the week: batching every meeting into two days. More on the cadence: shipping weekly.
Frequently asked questions
What do you lose when a team goes fully remote?
Four services an office ran at no visible cost: correction of wrong assumptions, visibility of who is overloaded, the context you absorb from conversations not addressed to you, and onboarding by proximity. Every one of them still has to happen. Each now needs a named owner and a slot in the week.
How do you replace hallway conversations on a distributed team?
By working in the open rather than in private. Drafts and half-built work go into a shared channel while they are still wrong, and decisions get recorded where the work lives rather than in a direct message. Correction only lands on work other people can see.
How many time zones can a team span before it stops working?
The count matters less than the overlap. We work across four time zones, and the hours everybody is awake for are the only synchronous resource the team owns. Decide what that window is for before anything fills it, because everything you do not spend it on has to survive being written down instead.
Do distributed teams need more meetings or fewer?
Fewer meetings and more writing. A meeting moves information by forcing everybody into the same hour, and across four time zones that hour is the scarce thing. Writing moves the same information without spending the overlap, and a recorded walkthrough can be watched twice by somebody who was asleep the first time.
What is the real cost of running a remote team?
Administration. Everything an office did ambiently becomes something a person has to write down and put on a calendar with their name against it.
Sources
- Chua Network delivery data across 8 client accounts (internal fact bank)
- Chua Network engagement records, anonymized (internal experience bank)
