The same decision that takes an afternoon in one room can drag on for what feels like forever across three offices. The work is not harder. The distance is. Here is why time zones add drag to decisions, and what actually cuts it.
The handoff gap
When your teammates are asleep while you work, every question you send them lands in a queue. You ask, then you wait for their morning. They answer, then they wait for yours. A conversation that would take ten minutes face to face turns into a slow exchange of one message per side per waking period. Nobody is slow. The clock is just doing the waiting for them.
This is why a simple approval can stretch out without anyone doing anything wrong. Each round trip costs a full sleep cycle, and a decision with even one follow up question needs several. The delays add up quietly, and no one can point to who slowed it down.
Fewer hours where everyone is awake
Add a third time zone and the window where everyone is online at once shrinks, sometimes to almost nothing. That shared window is where fast decisions happen: the quick "yes, do it" that needs three people at the same time. When the window is small, those calls get crammed into it and pile up, or they slip to the next day because the right person had already logged off. In practice, teams end up rationing that window, saving it for the decisions that truly need everyone and letting the rest wait.
The cost is waiting, not working
Most of the delay is not thinking time. It is dead time between messages, when a decision sits blocked because the one person who can approve it is offline. The team is busy the whole while, just busy on other things. The decision waits in the background, and every day it waits, someone is building on an assumption that has not been confirmed.
That is the quiet tax of distance. Not slower work, but more time spent waiting on each other, and more work done on top of choices that are not settled yet.
Why sending more messages does not fix it
The natural reaction is to communicate more: longer updates, more channels, a note for every step. It rarely helps, and often makes things worse. More messages means more to read when you come online, and more places a decision might be hiding. Volume is not the problem. The problem is that the answer lives in one person's replies, and that person is asleep when you need them.
You cannot out-message a time zone. Ten careful updates still wait for the reader to wake up. What changes the math is not sending more, it is making the decision reachable without the sender at all.
What actually helps
Two things cut the drag. The first is deciding, in advance, who gets to make which call alone, so that not every decision needs a live meeting. Clear decision rights mean fewer things have to wait for the shared window.
The second is writing decisions down where the next person can read them without waiting for you. If a teammate coming online can see what you decided, why, and who approved it, they do not have to hold their work until your morning. The handoff happens on the page instead of in a live reply.
Both come down to the same move: take the answer out of one person's head and put it somewhere the team can reach when that person is asleep.
Where StandIn comes in
StandIn is built for exactly that gap. You write one short brief at the end of your day, and while you are off, it answers your teammates from what you wrote, with a source under each answer, and says so plainly when the answer is not on record. A teammate coming online in another time zone gets what they need without waiting for your morning. The clock still turns. The decision stops waiting on it.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.